Skip to content
Perplexity

Member of Technical Staff (Software Engineer, Design System)

San Francisco; Seattle; New York CityHybrid · United States
Staff · FullTime · AI Products
POSTED 11 AUGVERIFIED 15H AGO
Apply Ask
Role
100 days opentrue age
Past the 62d median close
Same title, closed before
×5
Posted 11 Aug · n=13
Payats field
$220k–405kposted
▲ +29% vs market median $243k
$206k$405k
Market p25–p75
$206k–$284k
Perplexity p25–p75
$309k–$313kn=28
SF Bay Area · n=1222 · 365d to 19 Nov
CompanyPerplexity →
141open roles
Opened · 30d
+13
Closed · 30d
−8
Signal
● Steady+5 net
14d of snapshots · 30d window
Market
9,206open · Staff Software engineering
Opened · 7d
+7178% of open
All software engineering
75,116open
All tracked boards · live 20 Nov · n=9,206
TypeScriptReactCSSSwift/iOSAndroidFigma

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. You will develop component APIs that hold up across dozens of consuming surfaces and are easy for other teams to adopt correctly, contribute to the token pipeline that keeps five platforms visually consistent, and maintain a high bar for interaction quality and accessibility.

Tech Stack: React · TypeScript · CSS · Design Tokens

What you'll do

Design and build core primitives – overlays, inputs, navigation, feedback – with APIs that stay coherent as consumers multiply

Work across the design-token pipeline – authoring, generation, and per-platform publishing across web, iOS, Android, macOS, and Windows

Partner directly with design on the design language itself, translating Figma systems into typed, testable, documented components

Migrate product surfaces off bespoke implementations onto shared primitives without breaking them

Build accessible components by default – keyboard, focus, contrast, screen readers – backed by automated coverage

Support consuming teams through docs, visual regression coverage, and on-call rotation

What we're looking for

4+ years building production frontend; experience with a design system, component library, or shared UI platform is a plus

Interest in building reusable components

Strong React and TypeScript, and CSS

Working accessibility knowledge (WCAG, ARIA patterns, assistive tech)

Comfort collaborating closely with designers on the visual and interaction language

Source · PerplexityFirst seen 3 NovOriginal ↗