Technical

I build systems that stay coherent as they grow.

My focus is clarity, explicit trade-offs, and work that can evolve without losing its integrity.

Principles

I prefer simple interfaces and boring reliability.

I make trade-offs explicit and revisit them intentionally.

I treat constraints as design inputs, not inconveniences.

I optimize for maintainability and observability.

I aim for systems that are legible to the next person.

Technical leadership

I lead teams the way I build systems: clear expectations, psychological safety, and shared ownership. I invest in practices that make good decisions easier—tight feedback loops, calm communication, and accountability without blame.

What I work on

Infrastructure and tooling, integration-heavy systems, service architecture, and practical AI-enabled workflows—especially where reliability and clarity matter more than novelty.

Selected work

Private

Some of my favorite work is private: internal platforms, reliability tooling, and systems built around real teams and real constraints.

How to engage

If you're reaching out about something technical, include context, constraints, timeline, and what “done” means.