How I work
Four principles I keep returning to.
Useful architecture means clearer decisions, fewer production surprises, and a team that can carry the work forward.
- Start from what production shows you. Diagrams only help when they explain real code, failures, and who owns what in the live system.
- Name what you know vs. what you’re assuming before committing to a plan.
- Rewrite is a last resort. Stop the bleeding, preserve delivery, migrate deliberately.
- Build team capacity, not dependency. Useful work ends with clearer systems and decisions your people can own.
Experience
Experience with real scope.
What I’ve owned and shipped. Confidential client work stays off the page.
Product foundations and the first engineering team
Responsibility. Backend, frontend, realtime workflows, deployment, and product foundations. Built and led an early engineering team of five.
APIs, integrations, and high-load backend systems
Evidence. Maintained and extended 20+ production APIs and delivered 10+ new APIs in one global product environment.
From architecture decisions to runtime behavior
Scope. Architecture, backend, cloud, CI/CD, reliability, AI-assisted workflows, and connected-product boundaries.
Current focus
Where I’m investing now
Areas I’m actively working in — not a requirement for every project.
- Production AI & real-time voice — Voice and agent products — testing quality, monitoring failures, knowing when a human should take over, and keeping scope under control.
- Connected products & IoT — From what the device reports to what your backend and product do with it.
- AI-assisted engineering — AI-assisted development: structured prompts, review, and controls so the team stays in charge of what merges.
