Frontend Engineer: Design System & Tokens

Perplexity; Seattle (WA); On-site; USD 220,000 - 405,000; Full time

Job summary

Perplexity is looking for a frontend engineer to build the design system behind every Perplexity product. It is the component library and design language shared across web, iOS, Android, macOS, and Windows – the primitives, tokens, and interaction patterns that every product team builds on top of.

Its users are internal, spanning product teams and a broad range of contributors across the company. The components you build become the foundation all of them rely on, with APIs that stay coherent as

Qualifications

• 4+ years building production frontend
• Experience with a design system, component library, or shared UI platform is a plus
• Strong React and TypeScript, and CSS
• Working accessibility knowledge (WCAG, ARIA patterns)
• Comfort collaborating with designers on visual and interaction language

Responsibilities

• Design and build core primitives - overlays, inputs, navigation, feedback - with coherent APIs
• Work across the design-token pipeline - authoring, generation, and per-platform publishing across web, iOS, Android, macOS, and Windows
• Partner with design to translate Figma systems into typed, documented components
• Migrate product surfaces onto shared primitives without breaking them
• Build accessible components by default with keyboard, focus, contrast, and screen readers
• Support consuming teams through docs, visual regression coverage, and on-call rotation

Skills

React

TypeScript

CSS

Design System

Accessibility

Collaboration with Designers

Tools

Design Tokens

Job description

Perplexity is looking for a frontend engineer to build the design system behind every Perplexity product. It is the component library and design language shared across web, iOS, Android, macOS, and Windows – the primitives, tokens, and interaction patterns that every product team builds on top of.

Its users are internal, spanning product teams and a broad range of contributors across the company. The components you build become the foundation all of them rely on, with APIs that stay coherent as