Member of Technical Staff (Design Systems)

📍 Job Overview

Job Title: Member of Technical Staff (Design Systems)

Company: Perplexity

Location: San Francisco, California, United States

Job Type: FULL_TIME

Category: Frontend Engineering / Design Systems

Date Posted: August 11, 2026

Experience Level: Mid-Level to Senior

Remote Status: Hybrid (with potential for full remote within the US)

🚀 Role Summary

• Drive the development and evolution of Perplexity's core design system, ensuring a unified user experience across all product surfaces including web, iOS, Android, macOS, and Windows.

• Architect and implement reusable UI components and primitives with robust, scalable APIs that support rapid product development and maintainability.

• Collaborate closely with design and product teams to translate visual and interaction language from Figma into functional, accessible, and well-documented code.

• Own the design token pipeline, ensuring visual consistency and brand integrity across all platforms through automated generation and publishing.

• Champion accessibility best practices, integrating WCAG guidelines and ARIA patterns to ensure all components are usable by everyone.

📝 Enhancement Note: This role is positioned within a rapidly growing AI-focused company, emphasizing the critical need for a robust and scalable design system to ensure consistent user experience across diverse product offerings. The "Member of Technical Staff" title suggests a high level of technical ownership and influence within the engineering team, particularly concerning foundational UI architecture. The remote status being "TELECOMMUTE" with a "United States" location requirement implies that while the role is remote-friendly, candidates must be based within the US, potentially with periodic in-person collaboration in San Francisco.

📈 Primary Responsibilities

• Design, develop, and maintain core UI primitives (e.g., overlays, inputs, navigation, feedback components) with API strategies that remain coherent and scalable as consumer surfaces multiply.

• Actively participate in the design token pipeline, contributing to the authoring, generation, and per-platform publishing processes across web, iOS, Android, macOS, and Windows.

• Partner directly with the design team to translate Figma designs and design language into typed, testable, and thoroughly documented components.

• Lead the migration of existing product surfaces from bespoke implementations to shared primitives, ensuring a seamless transition and minimizing disruption.

• Build and rigorously test accessible components by default, ensuring compliance with WCAG standards and ARIA patterns, supported by automated visual regression coverage.

• Provide comprehensive support to consuming product teams through detailed documentation, proactive visual regression testing, and participation in an on-call rotation for critical system issues.

📝 Enhancement Note: The responsibilities highlight a deep focus on foundational UI development and cross-platform consistency, crucial for a company expanding its product ecosystem. The emphasis on API design for primitives and the design token pipeline indicates a need for strategic thinking about long-term maintainability and scalability. Supporting consuming teams and participating in an on-call rotation suggests an expectation of proactive problem-solving and a collaborative, service-oriented mindset within the engineering function.

🎓 Skills & Qualifications

Education: While no specific degree is mandated, a Bachelor's degree in Computer Science, Engineering, or a related technical field, or equivalent practical experience, is strongly preferred.

Experience: Minimum of 4+ years of professional frontend development experience, with a proven track record of building and shipping production-level applications.

Required Skills:

• Extensive experience with React and TypeScript for building complex, dynamic user interfaces.

• Strong command of modern CSS, including preprocessors or CSS-in-JS solutions, for styling and layout.

• Demonstrated experience in building and maintaining design systems, component libraries, or shared UI platforms.

• Solid understanding and practical application of web accessibility standards (WCAG 2.1 AA or higher, ARIA patterns, assistive technologies).

• Proficiency in API design principles for reusable components, ensuring ease of use and maintainability.

• Experience with automated testing frameworks for frontend applications, including unit, integration, and visual regression testing. Preferred Skills:

• Familiarity with design tools like Figma and experience translating design artifacts into code.

• Experience with design token management and generation tools.

• Knowledge of cross-platform development challenges and solutions for web, mobile (iOS/Android), and desktop.

• Experience with performance optimization techniques for frontend applications.

• Understanding of CI/CD pipelines and build tools relevant to frontend development.

📝 Enhancement Note: The required experience level of 4+ years coupled with specific technical skills like React, TypeScript, CSS, and accessibility knowledge points to a mid-to-senior level role. The "plus" for design system experience is elevated to a "required" skill due to the explicit focus of the role. The preferred skills suggest a candidate who can hit the ground running and contribute to broader aspects of the frontend development lifecycle and platform consistency.

📊 Process & Systems Portfolio Requirements

Portfolio Essentials:

• Showcase at least two distinct projects demonstrating your experience with building reusable UI components or a design system.

• Include examples of component API design, illustrating how you've structured props and interfaces for usability and extensibility.

• Provide a case study detailing a process you've implemented or improved, such as a workflow for design-to-code handoff, component testing strategy, or accessibility integration.

• Demonstrate how you've ensured cross-platform consistency or addressed challenges in maintaining a unified look and feel across different environments.

• Highlight projects where accessibility was a primary consideration, with specific examples of features implemented to meet WCAG standards. Process Documentation:

• Evidence of clear and concise documentation for components or systems you've built, including usage guidelines, prop definitions, and examples.

• Examples of how you've contributed to or maintained design token pipelines, including any tooling or scripts developed for generation or distribution.

• Documentation or explanations of your approach to visual regression testing and how it has been integrated into a development workflow.

• Case studies or explanations of how you've collaborated with designers to translate design specifications into functional UI elements.

📝 Enhancement Note: For a role focused on design systems, the portfolio is paramount. It should not just show finished products but the process behind building robust, reusable, and accessible components. Emphasis should be on architectural decisions, API design, and how the candidate has scaled UI development. Demonstrating a systematic approach to accessibility and cross-platform consistency will be key.

💵 Compensation & Benefits

Salary Range: The provided salary range for this role is $220,000 - $405,000 USD per year. This range is competitive for a senior frontend engineering position specializing in design systems in the San Francisco Bay Area, reflecting the high cost of living and the specialized nature of the role.

Benefits:

• Equity: Stock options or grants, providing ownership in Perplexity's growth.

• Health Insurance: Comprehensive medical, dental, and vision insurance plans.

• Retirement Plan: A 401(k) or similar retirement savings plan, potentially with employer matching.

• Fitness Benefits: Subsidies or access to gym memberships and wellness programs.

• Commuter Accounts: Pre-tax benefits for commuting expenses.

• Dependent Care Accounts: Pre-tax benefits for childcare or other dependent care expenses.

Working Hours: The standard working hours are 40 hours per week. While the role is hybrid, Perplexity generally offers flexibility in scheduling, allowing for effective time management to balance project deadlines and personal commitments.

📝 Enhancement Note: The salary range is exceptionally high, indicating Perplexity is seeking top-tier talent for this critical design systems role. The upper end of the range suggests significant experience and impact are expected. The inclusion of benefits like equity, comprehensive health coverage, and retirement plans aligns with standard offerings for competitive tech roles in the US. The hybrid arrangement implies a need for some in-office presence, likely for collaboration, but with flexibility.

🎯 Team & Company Context

🏢 Company Culture

Industry: Artificial Intelligence (AI), Search Technology, Information Retrieval. Perplexity is at the forefront of conversational AI, aiming to revolutionize how users access and interact with information. This fast-paced, innovation-driven environment demands agility and a strong focus on user-centric product development.

Company Size: Perplexity is a rapidly growing startup, likely falling into the 50-200 employee range based on typical growth trajectories for companies at this stage. This size offers a balance of startup dynamism with increasing structure and dedicated teams.

Founded: Perplexity was founded in 2022. Its relatively recent founding means the company is in a high-growth phase, building out its core infrastructure, product offerings, and team.

Team Structure:

• The Design Systems team is likely a focused group of specialized engineers and designers responsible for the foundational UI layer of Perplexity's products.

• This team will report into a broader Engineering or Product department, with close alignment to Product Management and UX/UI Design.

• Cross-functional collaboration will be crucial, involving regular interaction with frontend engineers on product teams, mobile developers, and potentially backend engineers for API integrations. Methodology:

• Data-driven decision-making, leveraging user feedback and analytics to inform design and development priorities.

• Agile development methodologies, emphasizing iterative development, rapid prototyping, and continuous integration.

• Strong emphasis on code quality, testing, and maintainability, especially critical for a foundational design system.

• Collaborative approach to problem-solving, encouraging open discussion and knowledge sharing among team members.

Company Website: https://www.perplexity.ai/

📝 Enhancement Note: Perplexity's focus on AI and search implies a culture that values innovation, technical excellence, and rapid iteration. As a newer company, the culture is likely dynamic and less hierarchical, offering significant opportunities for impact. The design systems team will be a critical enabler for product velocity and consistency.

📈 Career & Growth Analysis

Operations Career Level: This role is classified as a "Member of Technical Staff" (MTS), typically indicating a senior individual contributor role. It requires deep technical expertise in frontend development and design systems, with significant ownership and influence over architectural decisions and technical strategy within its domain.

Reporting Structure: The Design Systems engineer will likely report to a Lead Design Systems Engineer, Engineering Manager, or Director of Engineering. They will work closely with Product Designers and product-focused Frontend Engineers.

Operations Impact: The impact of this role is foundational and far-reaching. By building and maintaining the core design system, this individual directly influences the user experience, development speed, and brand consistency across all of Perplexity's products. A well-executed design system accelerates product development, reduces engineering debt, and ensures a high-quality, cohesive user interface for millions of users.

Growth Opportunities:

• Technical Specialization: Deepen expertise in advanced frontend architecture, accessibility, performance optimization, and cross-platform UI development.

• Leadership: Potentially grow into a Lead Design Systems Engineer role, mentoring junior team members and driving technical vision.

• Cross-Functional Mobility: Transition into broader frontend engineering roles within specific product teams or explore adjacent areas like developer tooling or platform engineering.

• Impact Amplification: Contribute to shaping the future of Perplexity's product interfaces and user experience, directly impacting company growth and user satisfaction.

📝 Enhancement Note: The "Member of Technical Staff" title suggests a career path focused on deep technical contribution and influence rather than people management, though leadership opportunities within the technical domain are likely. The growth potential is tied to the impact of the design system on the company's overall product strategy and execution.

🌐 Work Environment

Office Type: Perplexity offers a hybrid work environment. This typically means a combination of remote work and in-office collaboration days, allowing for flexibility while fostering team cohesion and spontaneous interaction.

Office Location(s): The primary office location is San Francisco, California. While the role is remote-friendly within the US, candidates may be expected to travel to the San Francisco office for key meetings, team events, or specific project phases.

Workspace Context:

• Collaborative Environment: The hybrid model encourages intentional collaboration, with designated in-office days for team meetings, brainstorming sessions, and cross-functional workshops.

• Tools & Technology: Access to a modern tech stack (React, TypeScript, CSS) and design tools (Figma), supported by robust development infrastructure.

• Team Interaction: Opportunities to engage with a diverse team of engineers, designers, and product managers, fostering a culture of shared learning and problem-solving.

Work Schedule: The standard 40-hour work week provides flexibility. The hybrid nature allows for structuring workdays to maximize focus time (often remote) and collaborative time (in-office). This structure supports efficient design system development and iteration.

📝 Enhancement Note: The hybrid nature of the role in San Francisco suggests a need for candidates who can effectively manage their time between remote focused work and in-office collaborative sessions. The emphasis on collaboration implies that communication and teamwork skills are as critical as technical proficiency.

📄 Application & Portfolio Review Process

Interview Process:

• Initial Screening: A brief call with a recruiter to assess basic qualifications, interest, and cultural fit.

• Technical Interview (Design Systems Focus): A deep dive into your experience with building and maintaining design systems, component architecture, API design, and accessibility. This may involve live coding or a detailed discussion of past projects.

• Portfolio Presentation: A dedicated session where you present your portfolio, walking through 1-2 key projects that demonstrate your expertise in design systems, component development, and process optimization. Be prepared to discuss your design decisions, challenges, and impact.

• System Design/Architecture Interview: A session focused on designing a scalable component or system, evaluating your ability to think about long-term maintainability, extensibility, and cross-platform consistency.

• Behavioral/Team Fit Interview: Questions assessing your collaboration style, problem-solving approach, and how you handle feedback and team dynamics. This will likely involve meeting with potential team members and managers.

Portfolio Review Tips:

• Highlight Process: Don't just show polished UIs; emphasize the how and why behind your design system work. Detail your approach to component architecture, API design, and testing.

• Quantify Impact: Where possible, use metrics to demonstrate the value of your contributions. This could include improvements in development velocity, reduction in UI bugs, or increased adoption rates of components.

• Showcase Accessibility: Clearly articulate your contributions to making components accessible. Walk through specific examples of WCAG compliance and ARIA pattern implementation.

• Cross-Platform Narrative: If applicable, explain how you've addressed consistency and challenges across different platforms (web, mobile, desktop).

• Concise & Focused: Select your strongest, most relevant projects. A few in-depth case studies are more impactful than a large number of superficial examples.

Challenge Preparation:

• Design System Problem: Be prepared for a scenario-based question where you might need to design a new primitive or address a common design system challenge (e.g., theming, responsive design, internationalization).

• Code Review Simulation: Practice reviewing code for a component, focusing on best practices, potential bugs, accessibility issues, and API clarity.

• Collaboration Scenarios: Think about how you would resolve disagreements with designers or product managers regarding component design or implementation.

📝 Enhancement Note: Given the specialized nature of this role, the interview process will heavily scrutinize the candidate's practical experience with design systems and their ability to translate abstract design principles into robust, scalable code. The portfolio presentation is a critical component, serving as a direct demonstration of their capabilities.

🛠 Tools & Technology Stack

Primary Tools:

• React: The core JavaScript library for building user interfaces. Proficiency is essential.

• TypeScript: Used for static typing, enhancing code quality, maintainability, and developer productivity.

• CSS: Deep understanding of CSS, including modern features, preprocessors (like Sass/Less), or CSS-in-JS solutions (like Styled Components or Emotion).

• Design Tokens: Experience with concepts and potentially tools for managing design tokens (e.g., Style Dictionary, Figma Tokens Plugin) for cross-platform consistency.

Analytics & Reporting:

• Figma: The primary design tool. Familiarity with its capabilities for component libraries and design systems is crucial for collaboration.

• Storybook: A common tool for developing, documenting, and testing UI components in isolation. Experience with Storybook is highly beneficial.

• Visual Regression Testing Tools: Tools like Percy, Chromatic, or Applitools for ensuring UI consistency and catching unintended changes.

CRM & Automation:

• Version Control: Git is a standard requirement for all software development roles.

• CI/CD Tools: Familiarity with tools like GitHub Actions, GitLab CI, or Jenkins for automated builds, testing, and deployments.

• Project Management Tools: Experience with tools like Jira, Asana, or Trello for task tracking and workflow management.

📝 Enhancement Note: The tech stack is clearly defined, with React, TypeScript, and CSS being non-negotiable. The emphasis on design tokens and tools like Storybook and visual regression testing highlights the specific needs of a design systems role. Candidates should be prepared to discuss their experience with these specific technologies and methodologies.

👥 Team Culture & Values

Operations Values:

• User-Centricity: A commitment to building intuitive, accessible, and delightful user experiences that align with Perplexity's mission.

• Technical Excellence: A dedication to writing clean, maintainable, and performant code, with a strong emphasis on testing and quality assurance.

• Collaboration: A proactive and open approach to working with designers, product managers, and fellow engineers to achieve shared goals.

• Innovation: A drive to explore new technologies and approaches to solve complex problems and push the boundaries of AI-powered information access.

• Ownership: A sense of responsibility for the systems and components developed, ensuring their long-term health and impact.

Collaboration Style:

• Cross-Functional Integration: Actively engaging with product teams to understand their needs and provide them with robust, easy-to-use UI building blocks.

• Feedback Loops: Embracing constructive feedback from peers, designers, and product teams to continuously improve the design system.

• Knowledge Sharing: Willingness to document best practices, share learnings, and mentor others through code reviews, pair programming, and internal presentations.

📝 Enhancement Note: The culture at Perplexity, as reflected in these values, likely emphasizes rapid innovation, technical rigor, and a strong sense of shared purpose. For a design systems role, collaboration with design and product teams is paramount, requiring strong communication and interpersonal skills alongside technical prowess.

⚡ Challenges & Growth Opportunities

Challenges:

• Scalability Across Platforms: Ensuring the design system remains consistent and performant across web, iOS, Android, macOS, and Windows presents significant technical hurdles.

• Balancing Abstraction and Flexibility: Creating primitives that are general enough for broad use while remaining flexible enough for specific product needs can be a delicate balance.

• Adoption and Governance: Encouraging adoption of the design system by product teams and establishing effective governance processes for component updates and new additions.

• Maintaining Accessibility Standards: Continuously ensuring all components meet evolving accessibility standards across all platforms requires ongoing diligence and testing.

Learning & Development Opportunities:

• Advanced Frontend Architecture: Deepen knowledge in areas like state management, performance optimization, and modern JavaScript frameworks.

• Cross-Platform Development: Gain hands-on experience with native mobile development (iOS/Android) or desktop application frameworks to better understand platform-specific challenges.

• Design System Strategy: Develop skills in strategic planning, roadmap development, and stakeholder management for design systems.

• Industry Conferences & Certifications: Opportunities to attend leading frontend and design systems conferences, and pursue relevant certifications in accessibility or specialized technologies.

📝 Enhancement Note: The challenges outlined are inherent to design systems work in a growing tech company. Successfully navigating these will provide substantial learning and growth opportunities, particularly in areas of cross-platform development and strategic system design.

💡 Interview Preparation

Strategy Questions:

• "How would you approach designing a new primitive component, such as a modal or a date picker, to ensure it's reusable across web, iOS, and Android?" (Focus on API design, state management, and platform considerations).

• "Describe a time you had to advocate for accessibility best practices. What challenges did you face, and how did you overcome them?" (Highlight your understanding of WCAG, ARIA, and your persuasive communication skills).

• "Imagine a product team wants to implement a feature that doesn't quite fit within an existing component. How would you guide them and maintain consistency within the design system?" (Assess your problem-solving, collaboration, and governance approach). Company & Culture Questions:

• "What interests you most about Perplexity's mission and its approach to AI?" (Demonstrate your research and alignment with the company's vision).

• "How do you see a strong design system contributing to the success of an AI-first product company like Perplexity?" (Connect your role to business objectives and user experience).

• "Describe your ideal collaboration dynamic with product designers. How do you ensure alignment and effective communication?" (Showcase your teamwork and communication skills). Portfolio Presentation Strategy:

• Tell a Story: Structure your presentation around the problem you solved, your approach, the solution you implemented, and the impact it had.

• Focus on Your Role: Clearly articulate your specific contributions, especially if it was a team project.

• Technical Depth: Be ready to dive deep into the technical choices you made (e.g., component architecture, API design, testing strategies, accessibility implementation).

• Visual Aids: Use clear diagrams, code snippets, and live demos (if possible) to illustrate your points effectively.

• Prepare for Questions: Anticipate questions about trade-offs, alternative solutions, and future improvements.

📝 Enhancement Note: Interview preparation should heavily focus on demonstrating practical experience with design systems, component architecture, and accessibility. Candidates should be ready to articulate their technical decisions and their impact, showcasing both their problem-solving abilities and their collaborative approach.

📌 Application Steps

To apply for this Member of Technical Staff (Design Systems) position:

• Submit your application through the provided link on Ashby.

• Curate Your Portfolio: Select 1-2 key projects that best showcase your experience in design systems, component libraries, or reusable UI development. Ensure these examples highlight your API design skills, accessibility contributions, and cross-platform considerations.

• Tailor Your Resume: Emphasize your experience with React, TypeScript, CSS, and any direct work with design systems or component libraries. Quantify your achievements where possible, especially in terms of improving development efficiency or user experience.

• Prepare Your Presentation: Practice walking through your portfolio projects, focusing on the technical challenges, your solutions, and the impact of your work. Be ready to discuss your design decisions and rationale in detail.

• Research Perplexity: Understand Perplexity's mission, its products, and its position in the AI and search landscape. Consider how a robust design system contributes to their goals.

⚠️ Important Notice: This enhanced job description includes AI-generated insights and operations industry-standard assumptions. All details should be verified directly with the hiring organization before making application decisions.