I help companies figure out what to build, how to build it, and how to keep it standing once they do.
Learn moreI've spent my career working on high-traffic systems — the kind where the margin for error is small and the cost of getting it wrong shows up immediately. I work closely with tools like ClickHouse and Supabase, and I'm comfortable operating at every layer of the stack, from the logic of a NAND gate up to the product decisions that determine what gets built at all.
I'm most useful when the problem is messy: unclear ownership, competing priorities, or infrastructure that's quietly becoming a liability. I get into the work, understand the constraints, and help figure out a real path forward.
I genuinely love this work — and I'm lucky to do it alongside a team I actually like.
Most problems aren't where they appear. I try to understand how the pieces fit together before touching anything.
A good plan that never ships is just a document. I focus on what it actually takes to get things done and keep them done.
People tell you what they need if you pay attention. I try not to let internal assumptions override what the data is actually saying.
Technology is a means to an end. I'm comfortable across stacks and don't have a horse in most of the debates.
Shortcuts tend to compound. I'd rather build something slower that doesn't need to be rebuilt in 18 months.
Rebuilt the core architecture behind a product used by millions of people every month — without breaking anything in the process.
Pulled together product, engineering, and ops teams that weren't talking to each other and got them moving in the same direction.
Helped a platform rethink its approach entirely — user growth tripled, and the transition was clean enough that most users never noticed it happened.
My homepage. I read it the way some people read the newspaper — first thing in the morning, looking for what's actually happening in the industry before anyone's had time to spin it.
The further down the stack you go, the more interesting it gets. I'm drawn to how physical constraints at the chip level ripple up into every software decision made above it.
There's something satisfying about understanding how things work from first principles. High-level networking and logic gates are where I go when I want to think clearly again.
I've been fortunate enough to work with people I genuinely like. That matters more than most job descriptions let on.
I started out writing code and slowly realized the hardest problems weren't technical. They were about how people work together, what they're actually trying to accomplish, and whether the thing they're building is the right thing to be building at all.
I work with people who are serious about what they're building — not chasing a trend, but trying to make something that genuinely works and lasts.
If that sounds like you, I'd like to hear about it.