Building process-driven teams that ship

I bring ten years of experience from US tech companies into a Tel Aviv team, and I'm explicit with the engineers about what that means: after you work here, your next role should be at Google or Meta. Its not about the logos but the engineering habits those teams take for granted, and pulling ours up to the same standard.

I lead as a contributor: code reviews, occasional pairing, and picking up the difficult or thankless piece of work no one else wants. It keeps my technical judgment honest, shortens the feedback loop on tooling and process decisions, and earns the trust to ask hard things of the team.

Good process isn't bureaucracy — it's what lets a team move quickly without things quietly breaking. I push hard on rigorous code review and standardization across the SDLC: every consistent step is one more thing automation can take off our plates, and every shared convention is one fewer judgment call slowing down a review.

I cleaned up our error logs so alerts actually mean something again, and treat monitoring and instrumentation as a first-class concern. When something breaks now, we know within minutes, and we know what.