About This Opportunity
Asana’s Design System team builds the UI primitives and component APIs used by hundreds of engineers. The vision: product engineers rarely need to write CSS. The team prioritizes craft, quality, and cross-functional collaboration, continuously improving the system in ways that compound over time.
Why I’m Excited
- “Bridge design and engineering” - This describes my career
- Accessibility Focus - Explicitly required, my strength
- Systems Thinking - QA → Design → Dev progression gave me this naturally
- Sweeping Impact - Changes compound across every product surface
- Craft and Quality - I care about getting the details right
Key Qualifications Match
| Requirement | My Experience |
|---|---|
| 2+ years frontend | 7 years across QA, design, and development |
| TypeScript, React, CSS | Daily use, primary stack |
| Systems thinking | Career built on understanding how pieces connect |
| Cross-functional collaboration | UX background, daily design-engineering partnership |
| Accessibility | Led WCAG compliance improvements, color contrast standards |
| Teaching/mentoring | Documented best practices, supported team adoption |
Why Design Systems Fit Me
My career progression is unusually well-suited for this:
- QA Specialist → I think about edge cases, reliability, and how changes compound
- Interaction Designer → I understand design intent and can translate it accurately
- UX Designer/Developer → I’ve implemented designs and know where friction occurs
Most engineers come from one side of the design-engineering divide. I’ve worked on both sides, which is exactly what design systems work requires.
What I’d Build
Based on the job description, I’m particularly excited about:
- UI Primitives - Stacks, Drawers, layout systems that eliminate CSS friction
- Component APIs - Interfaces that scale across hundreds of engineers
- Accessibility patterns - Building inclusive design into the system by default
- Documentation - Helping teams leverage the system effectively