About
I've spent 17 years in product design and 10 of them asking one question: why do design decisions fall apart at scale?
The answer is almost always the same, there's no shared language. Design systems are my answer to that problem. Not as a collection of components, but as a set of agreements: about naming, about ownership, about what consistency actually means for a given product.
I've built systems from zero at Rover, evolved them across seven products at Chainlink Labs, and consolidated fragmented libraries into unified platforms at Aptos Labs. Each time, the hardest part wasn't the components, it was the governance. Getting teams to trust the system enough to build on it instead of around it.
I'm based in Seattle and looking for my next role. If you're building a design system practice or trying to figure out if you need one, I'd like to talk.

// skills_&_tools
Systems Skills
- Token Architecture
- Component API Design
- Theming & White-labeling
- Cross-platform Systems
- Accessibility (WCAG)
- Governance & Contribution Models
- Design Ops
Tools
- Figma
- Storybook
- Style Dictionary
- HTML / CSS
- React / React Native
- Adobe Creative Suite
- Airtable
// contact