I build systems that people can trust after the demo.

What I do today

Work arrives on WhatsApp, in email, in a form, in a chat, and then someone has to move it by hand. I make those channels behave like one system, with a record of what arrived and what happened to it. Around that I put the things that decide whether it is still running a year later: a model that is checked rather than trusted, a failure that raises an alert instead of going quiet, and a document that goes to a person when nothing should be confident about it.

Clients work directly with me. If a simpler solution is enough, I will say so.

Why production shapes it

I started in broadcast and real-time video, where technical failures are public and time matters. That is a specific kind of pressure: there is no quiet window in which to fix something, and no version of the story in which nobody noticed.

From 2021 to 2024 I was VP of DevOps for an interactive video and live-streaming platform, through its acquisition. I owned hybrid AWS and on-premises infrastructure, CI/CD, observability, disaster recovery and production reliability while leading a hands-on engineering team.

These were systems used by national broadcasters, where an outage is public, expensive and very hard to hide. The platform was used by broadcasters including NBC News, MSNBC and ABC.

That background shapes how I build now. I expect things to fail, make the failure visible, and design a safe way back.

Hands-on, and staying that way

I map the process, build the workflow and the custom code around it, write the infrastructure, test the failure modes, and document the handover. Consulting is how I enter a piece of work rather than a separate thing I sell: reviewing what already exists, finding where the cost actually sits, designing the approach, or leading the build.

I have handed systems over to teams on three continents. Documentation and ownership are part of the build, not something I add at the end.

Working remotely worldwide in English, Hebrew and Russian.