About me

I build distributed backend systems and platform infrastructure: execution engines, event-driven services, and the internal tooling other teams build on top of. Most of my work sits at the boundary between application logic and the platform underneath it: routing, reliability, and the SDKs and generators that let other engineers move faster.

Most of my career has been spent taking ownership inside complex systems already running: a banking platform mid-build, a distributed execution engine already handling millions of executions a minute, and now payment flows inside Intuit's BillPay domain. I tend to ramp up by understanding the boundaries first: where business rules live, what can fail, what needs to stay compatible, and what the system is actually promising to the services around it. After joining BillPay recently, I began taking end-to-end ownership early across validation flows, recurring-payment behavior, post-approval flows, business-rule boundaries, and production observability.

Where a system has needed something that didn't already exist, I have built it: a Kafka routing layer I designed and owned end-to-end, independent of any existing implementation to extend. The same operating concerns shape that work: understanding failure modes, preserving compatibility, and making behavior observable before changing a system others depend on.

Outside of assigned work, I build things to understand them properly: a local RAG platform, an agent-orchestrated delivery pipeline, and a reusable AI code-review system built around explicit review semantics and deterministic validation. They are personal projects, kept clearly separate from my professional work, but they reflect the same instinct: I'd rather understand a system by building it than by reading about it.

I'm based in Bat Yam, Israel · Light Rail access across the Tel Aviv metropolitan area. If you want to talk about backend or platform engineering, the fastest way to reach me is email.