Defining strategy with the founding team

A lot of my work isn’t shipped in a pull request. It happens alongside Phil and the rest of the founding team, deciding which customer signals are worth a roadmap spot, which positioning to lean into, and which deals shape the next quarter.

Sitting close to sales calls, support, and customer interviews means I’m comfortable arguing for sequencing, killing scope, or pushing a bet I think we should make.

Experimenting and prototyping

My career started with making. I picked up a book on HTML and CSS and quickly understood the power of translating an idea into something real.

Every role I’ve had since has followed a similar pattern. Take the research, the conversations, the inspiration, and turn it into something someone can actually use.

That’s why I prototype in code. A static frame can’t surface the friction of a click target, a loading state, or a real dataset.

These days, being able to prototype directly in the actual app, against the actual design system, means we can test and evaluate ideas in a more realistic way.

Closing the loop

Working in a small autonomous team means I can often close the loop on my own: taking customer feedback through to shipped feature without costly developer handoffs.

I understand the technical constraints before I propose a design solution, and iterate with engineering to make sure the feature works as expected.