A senior engineer who treats reliability as a feature.
I like doing things properly. I care about documenting work, working closely with business and design, and proposing improvements when I see a better way forward. I stay involved across the full lifecycle of the software, because I like owning what I build and having real impact on the outcome.
I want code that is easy to read, easy to maintain, and easy to adapt without a meeting. I care a lot about testing too, but not just for coverage. I want tests that give real confidence and make change safe. I try to apply good practices consistently, but I also stay pragmatic and adaptable when the situation needs it. I especially like working on distributed systems, event-driven architectures, and systems that need to stay reliable as they grow.
Case studies — in progress.
I'm publishing deep-dives on the systems I've designed and built. First posts coming soon.
Case studies on the systems I've designed and built — coming soon.
Notes on systems, performance, and engineering culture.
Long-form posts on the parts of backend work that don't fit in a PR description. First entries coming soon.
Long-form posts on the decisions and trade-offs that don't fit in a PR description.
Let's talk about what you're building.
I'm open to thoughtful conversations about backend systems, architecture, and senior roles with real technical scope.