RemNavi

Remote position

Design Systems Lead

at Perplexity

Apply on Perplexity →
● Posted this month San Francisco (Remote) $220K - $280K Data

Real Remote Score

64/100

Solid

Comp
25/25
Location
4/25
Source
15/15
Clarity
8/15
Freshness
12/20
Why this score?
  • Compensation · Full salary range disclosed 25/25
  • Location · Specific city or narrow scope 4/25
  • Source · Direct employer ATS 15/15
  • Role clarity · Seniority clear, stack not in title 8/15
  • Freshness · Posted 19 days ago: within last month 12/20

How the Real Remote Score is calculated → · Score appeals & corrections

Salary in context

Above the 75th percentile for Design

Listing floor: $220,000 · Role median across 59 peers: $175,000 · 25th–75th: $148,000–$218,000

Numbers refresh from the live corpus. Compare the full distribution at /tools/salary-index/ or run a city PPP adjustment at /tools/salary-calculator/.

About this role

ABOUT THE ROLE We're seeking a Design Systems Lead with extensive experience owning design systems at large organizations. You'll bootstrap an intuitive semantic token system that supports design and product teams across multiple platforms and frameworks - the foundation that keeps Perplexity's product coherent as we scale. This is a true 50/50 design-engineer role. You'll live primarily in GitHub, where you own the system's repo, while staying fluent in Figma so design and engineering never drift apart. You'll set the bar for visual quality and the technical standards that let feature teams move fast without fragmenting the experience. You'll work at the intersection of design and engineering, partnering with product feature teams across mobile, web, and React surfaces. WHAT YOU'LL DO - Bootstrap and own an intuitive semantic token system that works across multiple platforms and frameworks - Own the design system repo on GitHub: the source of truth for components, tokens, and standards, including versioning, release management, and a clear changelog - Set and uphold a high bar for visual design quality across every surface the system touches - Navigate the nuanced differences between mobile, web, and React UI best practices, and encode them into the system - Define and run the contribution model and governance: review and shepherd inbound contributions from product feature teams, keeping quality and consistency high as the system grows - Keep design and engineering in sync, bridging Figma and code so the system stays coherent end-to-end - Own clear, first-class documentation so teams can adopt components and tokens on their own, and drive adoption across the org through onboarding, office hours, and hands-on support - Bake in accessibility (WCAG) and theming (including dark mode) as defaults, not afterthoughts - Maintain a system roadmap, balancing net-new work, migrations, and deprecations against feature-team needs - Bring new AI tooling into the design systems workflow and help shape how we build systems in an AI-native way - Operate with autonomy in a fast-moving, ambiguous environment WHAT WE'RE LOOKING FOR - Extensive experience owning design systems at large organizations - A true 50/50 design-engineer, equally credible in visual craft and in code - An impeccable eye for visual design - Deep understanding of the nuanced differences between mobile, web, and React UI best practices - Strong product sensibilities to help evaluate and integrate contributions from various product feature teams - Fluency in Figma, but primarily living in GitHub where you own the repo - Experience designing and maintaining semantic design tokens and scalable component APIs - A track record of driving adoption through excellent documentation and cross-functional partnership - Working knowledge of accessibility standards (WCAG) and how to build them into a system - Readiness to work with new AI tooling and genuine comfort with ambiguity NICE TO HAVE - Experience building a semantic token system from scratch across multiple platforms - A track record scaling a design system through a period of fast org growth - Experience defining contribution models and governance for multi-team design systems - Familiarity with component tooling and documentation platforms (e.g., Storybook) - Experience mentoring designers and engineers and growing a design systems practice

Posted via Ashby:perplexity. Applications are handled by Perplexity. RemNavi earns no commission.

Apply on Perplexity →

Compare this role