I make complicated systems feel like nothing at all.

I write embedded software for electronic warfare systems in Southern California. Fixed memory, fixed power, deadlines measured in microseconds. The best possible outcome is that the person relying on it never once has to think about the thing I built — which is also the job in product.

I'm moving into product because the decisions I found most interesting were happening upstream of me: which problem we picked, who we picked it for, and what we were willing to trade away. I've spent the last stretch of my career pushing toward those conversations — writing internal proposals, taking them to chief engineers and program leadership, and learning that the technical argument is rarely the one that decides anything.

What I'm looking for: products where a lot of people use a shared, constrained system at the same time, and the experience either holds up or falls apart in public. Theme parks and live venues are the clearest version of that. Consumer platforms with hard systems underneath are the same shape of problem.

The case studies are the fastest way to see how I think.