Product
Interfaces that make complex flows feel calm
The layer where product intent becomes states, constraints, small affordances, and reviewable code.
- Interaction
- State
- Performance
- A11y
I build frontend systems that make complex products feel calm.
My work sits where product intent becomes states, constraints, component contracts, and codebases that get easier to work in over time.
No published notes yet
The first notes are being reviewed before they become public.
Product
The layer where product intent becomes states, constraints, small affordances, and reviewable code.
Systems
Component contracts, token models, documentation, migrations, and accessibility patterns that survive real edge cases.
Teams
Clear module boundaries, useful tests, readable primitives, and decisions documented before they turn into folklore.
Open to
Senior frontend roles on product teams that care about design craft, accessibility, and systems thinking.