Product Designer (Design Systems)

Join DevRev as a Product Designer (Design Systems) and take ownership of the Arcade Design System, the foundation for every product team. You'll define component behavior, maintain the token system, drive Figma library governance, collaborate with engineers, and mentor designers. This role requires a deep understanding of token architecture, expert Figma skills, and a passion for optimizing the platform.

• Posséder le système de design Arcade, en définissant le comportement des composants et en garantissant la cohérence du système.
• Gérer les composants Arcade de bout en bout, en veillant à ce que l'écart entre la spécification et le produit livré soit négligeable.
• Collaborer directement avec les ingénieurs sur les API des composants, les contrats de propriétés et les chemins de migration.
• Experience working embedded with engineering on component migration, API design, or design-to-code pipelines
• Before adding a token tier or component variant, you can name every context it will appear in and every team it will affect
• 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
• Expert Figma skills - advanced component architecture, variants, variables, and library management at scale
• 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 don't optimize for comfort - you optimize for the platform, even when that means reworking your own earlier decisions as the system evolves
• 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
• When you see inconsistency across the product, it's a structural problem you feel compelled to solve
• 5-8 years of product design experience, with significant time in design systems, component libraries, or platform/infrastructure design
• 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