Overview

My work lives in the space between code and infrastructure — designing APIs that hold under real load, building pipelines that don't drift, and making the decisions that keep production boring. Boring production is a feature.

I've spent most of my career in domains where a bug isn't a bad UX moment — it's a compliance incident. That sharpens how I think about failure modes, edge cases, and the cost of being wrong.

The most important decisions I make aren't about which framework to use — they're about what happens when the queue backs up at 11pm on a Friday.

What I work on

Backend services and the parts of cloud architecture that decide whether a system survives its second year of growth. API design, database performance, message-driven workflows, deployment pipelines — and the failure modes that hide between them.

I'm most useful close to the system boundary, where small decisions compound into incidents or into operational quiet. I prefer the quiet.

How I work

I break problems into the smallest honest unit before writing code. I write systems with clear seams so they can be changed without surgery. I optimize for the person on call six months from now — usually a future version of me.

Good engineering, to me, is less about chasing complexity and more about making trade-offs that hold up after the launch blog post is forgotten.

What I'm looking for

A Staff or Principal Engineering role where the hard problems are architectural, not political. Remote-first, async-friendly, high trust. I'm also open to fractional advisory engagements for early-stage teams building in fintech or healthcare — places where one engineering decision can change the next eighteen months.