01.
I build products from zero, and the design function that scales them.
For the last two years that has meant working with AI-native first companies, most recently leading design through Series A at Hike, where I owned an agentic platform for medical providers and set up how the team ships. Before that, Lyft, Meta and Apple, where I learned what rigour looks like when millions of people touch the thing every day.
01.
I build products from zero, and the design function that scales them.
For the last two years that has meant working with AI-native first companies, most recently leading design through Series A at Hike, where I owned an agentic platform for medical providers and set up how the team ships. Before that, Lyft, Meta and Apple, where I learned what rigour looks like when millions of people touch the thing every day.
02.
My default is to ship something real and let usage decide.
Ideate, design, ship a working V0 into a live environment, measure it, and put the findings straight back into an update that ships the same week. In one recent instance, I increased sign-up clients up over 500% in thirty days. It also changed how the company builds, which is usually the more durable result. I use AI across every workstream, from research synthesis to production code, and I prototype in code rather than hand over a file.
03.
I started with assembler and other coding languages in high school, building graphics and sound driven by streaming data.
That never really stopped. I still combine data flows, colour, graphics and music into coded experiences, and I compete in hackathons across Europe and New York, solo and in teams, where the design and the engineering are the same job and the deadline is 48 hours. It's the shortest explanation of why I work the way I do.