Product Designer, Design Systems

About the role

<div class="content-intro"><p><span style="font-size: 12pt;"><strong>About DevRev</strong></span></p> <p>At DevRev, we're building the future of work with <em>Computer</em> – your AI teammate. Unlike traditional tools, <em>Computer</em> unifies all your data sources, tools, and workflows into a single AI-ready platform, giving employees real-time insights, proactive suggestions, and powerful agentic actions. It extends your existing software with AI-native apps and agents that work alongside your teams and customers – updating workflows, coordinating across teams, and eliminating repetitive work. We call this Team Intelligence: human-AI collaboration that breaks down silos, brings people back together, and frees you to solve bigger problems. Backed by Khosla Ventures and Mayfield with $150M+ raised, DevRev is trusted by global companies across industries.</p></div><h4><strong>About the role</strong></h4> <div> <p>You own the Arcade Design System - the structural layer every product team at DevRev builds on. You'll define how components behave across contexts, how tokens translate intent into implementation, and how a growing design team contributes to a coherent system without fragmenting it. This isn't component art; it's the architecture that makes an entire platform feel like one mind designed it.</p> </div> <div><strong>What you'll do</strong> <div> <ul> <li>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.</li> <li>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.</li> <li>Drive Figma library governance - versioning, contribution models, and release cadence so product designers always work from a single, trustworthy source.</li> <li>Collaborate directly with engineers on component APIs, prop contracts, and migration paths. You think in implementation terms.</li> <li>Turn recurring questions into documentation or patterns rather than ad-hoc fixes. Make self-service the default.</li> <li>When three teams solve the same problem differently, propose the unified pattern.</li> <li>Mentor L1-L3 designers on systems thinking through workshops, education sessions, and structured critique.</li> </ul> </div> <div><strong>What you'll bring<br></strong> <ul> <li>5-8 years of product design experience, with significant time in design systems, component libraries, or platform/infrastructure design.</li> <li>Expert Figma skills - advanced component architecture, variants, variables, and library management at scale.</li> <li>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.</li> <li>Deep understanding of token architecture - not just using tokens but defining hierarchies, naming conventions, and semantic structures that hold across themes, modes, and platforms.</li> <li>Experience working embedded with engineering on component migration, API design, or design-to-code pipelines.</li> <li>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.</li> </ul> <h4>Who you are</h4> <ul> <li>When you see inconsistency across the product, it's a structural problem you feel compelled to solve.</li> <li>Before adding a token tier or component variant, you can name every context it will appear in and every team it will affect.</li> <li>Before finishing any component, you've considered its prop contract, token dependencies, Figma structure, and migration path as one coherent decision.</li> <li>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 co

Skills