Engineer first. It shows in the work.

I’ve spent about ten years building software for startups and product teams, usually as the engineer who owns a problem end to end: the data model, the services, the interface, and the unglamorous operational details that decide whether any of it survives contact with real users.

I work best when I’m trusted to make the calls and held to the result. I’d rather ship something solid and simple than something clever and fragile, and I care more about a team being able to maintain the work than about impressing other engineers with it.

Most of my work comes through people I’ve shipped with before. Between projects I’m usually reading code, sharpening my tooling, or learning whatever makes the next engagement go faster.