Neriya Rosner
Backend-oriented full-stack engineer · Senior @ DoorLoop · Tel AvivI build payments infrastructure at DoorLoop — fund flows and Stripe Treasury, where mistakes are expensive and hard to reverse. I write about what breaks and why: queues, idempotency, and systems that fail loudly instead of silently.
Field notes
What I learned the hard way, written down so I don't have to learn it twice.
Deterministic guardrails for AI-written code
A new approach: as an agent writes more of the code, careful review stops scaling. So I encode each standard — strict types, architectural seams, structure caps — as a mechanical check the model can't talk past — enforced at every layer, from the agent's own AI hooks down to CI.
trustgitSelected work
43 public repos on GitHub. These are the ones worth your time.
An iterative AI task execution framework — runs Claude or Codex in a checklist-driven loop, polls Linear, opens PRs, and iterates with reviewers.
MCP server that exposes XState machines to agents — drive and inspect state straight from the model.
A payment API built with NestJS in a microservices monorepo — REST endpoints across independent services.
A task runner that distributes work across nodes with a shared cache layer for coordination.
A collection of Agent Skills — small, composable, single-purpose tools for coding agents.
A Next.js App Router starter with NextAuth, Prisma, PostgreSQL and Tailwind wired up.
Owning the hard parts
I'm happiest a few layers below the surface. I don't learn an advanced topic just well enough to use it — I go deep enough to own it: design the architecture, set the conventions the rest of the team builds on, and carry it all the way to production. Hand me the gnarly, high-stakes part of the system — the money path, the failure modes, the thing nobody wants to touch — and that's the part I actually want.
It's less a skill than a temperament: read the source, build the mental model, write down what I learned, and turn the scary unknown into something the team can reason about and trust.
When things fail, I'm reliable
Production breaks; what matters is what happens next. That's where I'm at my most useful.
- Failure-mode-first. I design for what happens when a message can't process or a deploy goes bad — before the happy path.
- Recoverable by design. Idempotency, dead-letter queues, replay/redrive, and audit trails so an incident becomes a Tuesday, not an outage.
- On-call ownership. I carry the pager for what I build, and I'd rather be paged than have it fail silently.
- Calm under pressure. Methodical triage, honest comms, and fixing the cause — not just the symptom.
- Findable. Structured logs and tracing so “what's stuck, since when, and why” is answerable in seconds.
About
I'm Neri. Backend-leaning full-stack, currently on payments infrastructure at DoorLoop — fund flows, Stripe and Treasury, the event-driven core that moves customer money. I design for the failure case first: the happy path mostly takes care of itself, so I spend my time on what happens when a message can't process, a deploy goes bad, or a schema drifts under a parked event.
That shows up as a few non-negotiables — strict types (any is a compile error, not a preference), small files, idempotency as a design input, and systems that fail loudly instead of silently. CQRS and the outbox pattern on the inside; an analytics store I query ad-hoc so "what's stuck, since when, and why" is a question I answer in seconds.
Ex-technical-founder: SpecBite, a software-requirements SaaS. My failed startup — I learned more from it than from most things that worked. Before that, a full-stack app licensed to the Israeli courts and police, and a logistics tour in the paratrooper brigade that taught me more about systems than any framework has. On the side I build dev tools like @neriros/ralphy, and I read constantly.
The listening log
~30 a year, mostly while the tests run. A backend engineer's idea of a personality.
What people say
Neriya is a champion! Wholehearted service — even when I needed him at 1am, he was there for me.
A professional in everything related to full-stack and front-end development. A hard worker, committed, sharp-minded and quick to learn. I highly recommend him.
Neriya demonstrated an understanding of proper software engineering, alongside creative thinking and problem solving. I'm happy to recommend him.
Thank you, Neri, for developing and designing our appointment-scheduling website. Our expectations were met and beyond — we're delighted with the results!
I had special plugin requirements for a WordPress site; Neriya understood them and delivered to my complete satisfaction, at a very reasonable price. My next job goes straight to him.
More than six months working together across a variety of projects. The site is beautifully designed, secure, fast and pleasant to use. Highly recommend!
Neriya developed and designed a complicated organizational system for us. Communication was good, and the work was fast and efficient. Highly recommend.
Excellent service — working with Neriya was excellent. Highly recommended, thank you!
Neri, you're a professional senior with high work ethic. I'm happy to work with you!
A professional at crazy levels! He guided and accompanied me through building my website and marketing automation. Absolutely recommend!
Let's talk.
Not job-hunting — but always up for trading notes with like-minded people: payments and systems folks, dev-tool tinkerers, fellow obsessive readers. If the problem is fun and the types are strict, I'm in. I read everything; I reply to most of it.