I build the parts of the system that have to hold up under pressure.

I'm a full stack engineer who ended up specializing in the parts of a system most people would rather not own — data consistency, failure recovery, the stuff that only matters when it breaks. I got there by building small products end-to-end early in my career and finding I liked the systems side more than I expected to.

Most of my recent work has been as an early or founding engineer at small teams, where the architecture decisions I make in week one are still load-bearing two years later. That constraint has shaped how I think about software: prefer boring technology, write code that's easy to delete, and treat every abstraction as a decision that has to earn its complexity.

Outside of client work, I spend time on open source tooling for developer workflows, and I'm slowly working through every mechanical keyboard switch type a person probably doesn't need to try.