Design Systems Lead
Apply at source. Perplexity handles the application directly; Houtini doesn't take a fee from candidates or companies. We curate which companies appear; the listings come from yubhub.
What the team is looking for.
Compensation
We offer a compensation range of $220K – $280K, plus equity.
About the role
We're seeking a Design Systems Lead with extensive experience owning design systems at large organisations. 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.
Responsibilities
- 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
Requirements
- Extensive experience owning design systems at large organisations
- 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
Benefits
- Comprehensive benefits program including equity, health, dental, vision, retirement, fitness, commuter and dependent care accounts, and more
- design systems
- GitHub
- Figma
- React
- mobile development
- web development
- accessibility standards (WCAG)
- semantic design tokens
- scalable component APIs
- building semantic token systems from scratch
- scaling design systems
- defining contribution models and governance
- component tooling and documentation platforms (e.g., Storybook)
- mentoring designers and engineers
Other roles you might consider.
Filtered through the same AI-companies allowlist.
BIM Coordinator / BIM Designer
OpenAI
Brand Copy Lead
Replit
Copywriter
Replit
Manager, Digital Designer
Synthesia
Mid-weight Digital Designer
Synthesia
Product Designer, AI-Native Products (Senior/Staff-Level)
Synthesia
New to AI work? Start with these.
Six pieces of orientation. Most AI-company job specs assume you've done this kind of hands-on work already. If you haven't, an afternoon with one of these is the cheapest way to close the gap.
Claude Desktop, from zero.
The agentic-AI assistant most of the people you'd be working alongside use every day. Install, configure, first useful prompts.
What MCPs areThe best MCPs for Claude Desktop.
MCP servers extend an AI assistant with tools and data. The catalogue most teams use. Useful technical context for any AI-engineering role.
Code with AIClaude Code, the complete beginners' guide.
The CLI for AI-paired development. Required reading if you're applying for any engineering role that mentions agents, or any role full stop.
Run a local modelHow to set up LM Studio.
Running a model on your own machine teaches you more about how AI products work in three hours than a year of using ChatGPT will.
The hardware realityBeginner's guide to AI hardware.
What the infrastructure under the model actually looks like. Useful context for infrastructure, applied-AI and hardware roles.
Browse the stackMCP catalogue.
Eleven MCP servers Houtini maintains or recommends. Each detail page describes a real piece of working AI infrastructure.