About the team

Turo’s design system is live on iOS, Android, and web, but it isn’t yet pulling its weight. Coverage is uneven, and product teams often find themselves working around the system rather than with it. As a staff product designer on the design systems team you’re here to change that. Your mission is to turn the system into the default starting point and build an intuitive and high-quality system that teams reach for naturally. You’ll build a foundation that’s clear enough for people to use today and structured well enough for AI agents, ensuring Turo’s design language scales effortlessly.

What you will do

• Audit & analysis. Take a holistic look at our products to spot where the system is drifting or falling short. You’ll untangle overlapping root causes and find the high-leverage fixes that solve problems for multiple teams at once, ensuring our solutions scale as fast as our products.

• Component lifecycle & governance. Manage the end-to-end lifecycle of components by handling versioning, documentation, and deprecation. You will establish the release cadences and migration paths that product teams rely on to plan their work. By creating a clear governance model, you ensure the system remains stable and predictable as it evolves.

• System architecture & legibility. Build a system that speaks a universal language. You will name and structure components, tokens, and patterns clearly allowing anyone, from a designer to an AI agent, to find what they need to ship. High-quality documentation is a core part of your process, serving both the people building the product and the tools they use to automate it.

• Quality standards & accessibility. Define and enforce quality standards for interaction, visual detail, accessibility (WCAG 2.1 AA minimum), and platform fidelity. Raise the bar through critique, contribution, education, and example.

• Cross-functional partnership. Partner with feature teams through office hours, pairing sessions, and contribution reviews. You will help teams navigate patterns the system doesn't yet cover and decide when a design should become a global standard or remain a local solution.

• Education & advocacy. Teach the system through workshops, clear guidance, and constructive critique. Your goal is to raise the entire team's system fluency so that success is measured by how effectively everyone builds together, not just by what you ship.

• Design-to-code integration. Bridge the gap between Figma and production by building coded starting points, token demos, and high-fidelity prototypes. You have the intuition to choose the right tool for the job, whether it is using canvas-based design tools for exploration, agentic coding tools for rapid iteration, or production code when accessibility and platform fidelity matter most. You will partner with engineering to validate ideas early and ensure system improvements scale across iOS, Android, and web.

Your profile

• 8+ years of experience designing product experiences, with a focus on evolving design systems with gaps and workarounds into trusted foundations. You understand that true success is measured by team adoption and reliability, not just by the number of components you ship.

• Shipped components and patterns used by multiple product teams across mobile and web. You can speak to tradeoffs you made and what you'd do differently.

• Deep fluency with tokens, component architecture, variants, and Figma systems craft.

• Experience with Claude Code (or other agentic coding tools), MCPs, and other AI workflows

• A working model of design system governance. You know when to ship a new layer of the system, when to extend, and when to say no. You can also confidently defend those calls to leadership.

• Experience partnering with platform engineers on implementation, parity, and release cadence.

• A track record of scaling your impact through others. Workshops, written guidance, critique, and mentorship are part of how you work, not afterthoughts.

• Clear written communication. You can write documentation a junior designer, a staff engineer, and an agent can all use.

Bonus

• Experience building and maintaining linters for design teams.

• Exposure to token pipelines, Style Dictionary, or equivalent cross-platform token infrastructure.

• History contributing to acces