A product engineer, end to end.

I started out as a frontend engineer who cared a little too much about how things felt to use. I was never satisfied stopping at the surface — why was the API slow, why did this bug keep coming back — so I kept following problems down the stack until I was building whole products end to end.

Then I worked with startups that scaled fast. I helped grow a real-time mobility marketplace through hypergrowth to an acquisition, and learned hard lessons about reliability on networks that fail and systems that have to stay fair under load.

When Web3 arrived I built governance products and got a little obsessed with legibility — making it possible for ordinary people to understand what they were signing on-chain. The tech was new; the real problem was always UX and trust.

These days I build AI products, where that same theme dominates: capability is cheap, trust is everything. What I actually enjoy is the messy middle — taking a vague idea, arguing about the right architecture, and turning it into software that holds up in production. I'm usually one of the first engineers on the ground.