WORKING WITH ME

A résumé tells you what I've done. This is the shorter, more honest version of what I'm actually like to build with.

What I Like Building

I like problems that look impossible on a whiteboard — a state space that explodes, a workflow nobody can hold in their head, a platform that grew twelve different ways and now has to feel like one. I'm happiest on the operational tools real people depend on to do real work: the control tower a dispatcher stakes a big call on, the flow half a million operators have to trust, the design system that keeps six surfaces honest. I'd rather make one genuinely hard thing usable than ten easy things pretty. And I like building all the way down now — not just speccing the screen, but prototyping it in code until it actually works.

Teams Where I Thrive

I do my best work close to the problem and close to the people solving it. Small, senior teams where I can talk to an engineer without booking a meeting. Rooms where ambiguity is expected and "I don't know yet — let me build a version" is a normal answer. I want real ownership of one hard surface over a sliver of ten. I value direct, honest feedback over politeness, and I'll give it back the same way. And I'm allergic to process theater — status rituals that produce decks instead of decisions. Give me a clear problem, real users, and people who'd rather ship and learn than argue in the abstract, and I'll go a long way.

Why Enterprise

Consumer design mostly fights for attention. Enterprise design fights for clarity — and I find that far more interesting. The problems are genuinely hard: overlapping states, competing incentives, decades of legacy, and users who will route around anything that wastes their time. Nobody's there for the delight; they're there to get a job done, and when you make that job noticeably easier, you can feel it. The stakes are real, too — the dashboard someone bets a contract on, the flow that gates a multi-billion-dollar business. I like that the work matters to someone's actual day, and that "is it usable" isn't a nice-to-have — it's the whole game.

AI — How It Changed My Workflow

AI collapsed the distance between knowing what to build and building it. I've always been able to spec a system; now I can prototype it in code, wire up the data, and put a working version in front of people in the time it used to take to make a clickable mockup. That changes what design even is for me — I can test a hard interaction against reality instead of arguing about it in Figma. It's how I built and shipped Thios's six surfaces solo, and it's part of my daily workflow now, not a side experiment. I don't think it replaces judgment. It just means one person's judgment can reach a lot further than it used to.

If any of that sounds like the problem you're wrestling with, I'd genuinely like to hear about it — the messy, unsolved kind especially.