Product Designer, Design Systems

• Own Arcade components end-to-end - from Figma source of truth through token architecture to production, ensuring the gap between spec and shipped product is negligible.
• Define and maintain the token system (color, spacing, elevation, typography) - making architectural decisions about naming, hierarchy, and semantic structure that scale across themes and modes.
• Drive Figma library governance - versioning, contribution models, and release cadence so product designers always work from a single, trustworthy source.
• Collaborate directly with engineers on component APIs, prop contracts, and migration paths. You think in implementation terms.
• Turn recurring questions into documentation or patterns rather than ad-hoc fixes. Make self-service the default.
• When three teams solve the same problem differently, propose the unified pattern.
• Mentor L1-L3 designers on systems thinking through workshops, education sessions, and structured critique.

• 5-8 years of product design experience, with significant time in design systems, component libraries, or platform/infrastructure design.
• Expert Figma skills - advanced component architecture, variants, variables, and library management at scale.
• Design engineering sensibility: comfort with design tokens, CSS custom properties, and component APIs (React or equivalent). You can review a prop contract as naturally as a Figma frame.
• Deep understanding of token architecture - not just using tokens but defining hierarchies, naming conventions, and semantic structures that hold across themes, modes, and platforms.
• Experience working embedded with engineering on component migration, API design, or design-to-code pipelines.
• Demonstrated ability to own outcomes, not outputs - you can point to a migration you drove, an adoption metric you moved, or a systemic problem you resolved permanently.

Who you are

• When you see inconsistency across the product, it's a structural problem you feel compelled to solve.
• Before adding a token tier or component variant, you can name every context it will appear in and every team it will affect.
• Before finishing any component, you've considered its prop contract, token dependencies, Figma structure, and migration path as one coherent decision.
• You treat the design system as a product and its users as your customers. When a designer is stuck, your instinct is to help them succeed - not to gatekeep correctness. You earn adoption through empathy, responsiveness, and genuine care for the people building on your work. The system's success is measured by the confidence others feel using it, and that confidence starts with you.
• You don't optimize for comfort - you optimize for the platform, even when that means reworking your own earlier decisions as the system evolves.