Foundations first.
Founding designer for early-stage technical startups: strategy, design systems, interfaces.
The systems I built as a company's first designer.
What got built on those foundations, and other product work.
One person from idea to shipped. Fewer handoffs, less lost in translation.
Start with the problem, not the screen. Talk to the people who sell, support and use it.
Foundations, components and docs, so every new screen ships faster than the last.
Prototype with AI so ideas become working software, with specs engineers can rely on.
Ship, watch how people actually use it, then refine. The design isn't done at launch.
At AmpliPhi, I joined before there was a repo. At SEDA, I was the first full-time designer, came in after the engineers had built v1, and grew into Head of Product. Both times I started with the foundations: the strategy, the system, then everything built on it.
I got here the long way: audio engineering school, a sales job and a startup of my own. Then I taught myself UI, and went from junior UI designer to product designer in three months.
I learned the basics at a coding bootcamp, and for the past year I've built with AI: front ends, internal tools, small oracles. I'm not a career engineer. AI lets me get a working version in front of people fast, and talk to developers in their language.
I'm happiest where design, data and code meet. Off the clock I produce electronic music.
dreamer / self learner / poutine lover / world creator / composer / watch collector / bad painter

Hiring your first designer?
Say hello →