A designer who works like an engineer
I design products and the systems behind them. The interesting part is not the screen; it is the rule that makes the next hundred screens agree with it.
- BasedRemote · worldwide
- FocusProduct, design systems, brand
- Works withFounders, product teams, engineering leads
- ToolsFigma, coded prototypes, motion
- StatusAvailable Q4 2026
I start with the decision, not the layout. Every screen has one job, and the job is written down before anything is drawn. It keeps reviews short and stops the product from filling up with things that look useful.
I build on tokens. Colour, type, spacing, and motion are defined as a system first, so engineers inherit rules instead of measurements. The handoff is a specification, not a mood.
I stay through the build. Edge states, empty states, and error copy are part of the design, and I am there for the QA pass that finds the ones I missed.
What I take on
- 01Product strategy and framingPositioning, problem definition, direction memos
- 02UX / UI designFlows, interfaces, prototypes, edge states
- 03Design systemsTokens, components, documentation, governance
- 04Brand and launchIdentity expression, websites, motion direction
- 05Fractional design leadSenior judgment embedded with your team
Three rules I do not bend
One decision per screen
If a screen cannot name the decision it supports, it is not finished.
Tokens before pixels
Colour, type, and spacing are defined as a system first, so every screen inherits the same rules.
Handoff is the product
Documentation, edge states, and acceptance criteria ship with the design, not after it.