About
Engineering the whole picture.
I care about software as a product, not just as code — how it is designed, how it ships, and how it behaves for the people who depend on it.
Over my career I've worked across the stack: designing APIs and data models, building web frontends, wiring up integrations, and keeping systems running in production. I like problems where the constraint is real — performance budgets, messy legacy data, systems that can't go down.
Outside of work I build personal projects and apps, a few of which live further down this page.
Selected work
Things I've built.
placeholder cards — swap in your real projects
Your headline project
Two or three sentences on the problem it solved, your role, and the measurable impact it had. Link to a live demo or case study if you can.
An app you shipped
Side projects show range and initiative. Describe what it does, who uses it, and one interesting technical decision you made along the way.
A tool or library
A utility, library, or contribution you're proud of. Even small tools tell a reviewer a lot about how you think and how you write code.
Experience
Where I've been.
placeholder entries — swap in your history
Senior Software Engineer · Company name
One or two lines on scope and ownership: the systems you ran, the team you worked in, and the result that mattered most.
Software Engineer · Company name
Focus on what changed because you were there — a migration landed, a product launched, a process that got faster.
Developer · Company name
Early-career roles still count: name the stack you learned and the first real production system you were trusted with.
Contact
Let's build something worth shipping.
Got an interesting problem, a project, or just want to talk shop? The fastest way to reach me is email.