Senior Software Engineer

Most engineers spend their careers climbing away from the keyboard. I climbed back to it.

Over three decades I worked my way from individual contributor to architect to running global teams at Docker, JFrog, Sonar, and AssemblyAI — Director- and VP-level seats with real org charts, budgets, and roadmaps. I could have kept going up. Instead, as AI started genuinely changing what software is, I went the other direction: back to building.

These days I run a boutique AI consultancy, Ronin AI, and I ship production systems with my own hands — multi-tenant voice AI grounded in RAG, autonomous agent platforms with provider-agnostic LLM tooling, and, because I can't help myself, a Redis-compatible in-memory database written in Rust on a shared-nothing, multi-shard Tokio runtime. I'm more technical today than I've been in years, and that's by design. What makes me unusual is the combination. Plenty of people can architect a system; far fewer can also build the developer education that reaches 13M+ views, get quoted in Forbes on where AI is taking the developer stack, and lead the teams that turn ambiguous requirements into shipped product. I've spent my career as the bridge — between deep engineering and the developers who use it, between what's technically possible and what actually ships.

The through-line is simple: a relentless bias for building, and an allergy to standing still while the ground moves. After 30 years I'm not leaning on a title — I'm writing database internals and shipping AI because I genuinely love the work.

That's the story.