Software Engineer, Design Systems

📍 Job Overview

Job Title: Software Engineer, Design Systems

Company: Whatnot

Location: San Francisco, California, United States

Job Type: FULL_TIME

Category: Engineering - Design Systems

Date Posted: 2026-08-25

Experience Level: 5-10 Years

Remote Status: Hybrid (Co-located with hubs in US, UK, Ireland, Poland, Germany, Australia; must live within commuting distance of San Francisco or New York hub)

🚀 Role Summary

• Spearhead the development and evolution of the Whatnot Design System (WDS) across iOS, Android, and Web platforms, ensuring consistent, high-craft, and accessible UI for all product teams.

• Own and advance the design token architecture, including base, semantic, and component tokens, and manage the automated pipeline for syncing these from Figma to production codebases across all platforms.

• Serve as a collaborative partner to product designers, actively participating in spec reviews, pressure-testing component APIs, and building essential tooling like Figma plugins and component playgrounds to maintain design and engineering alignment.

• Elevate UI quality through a focus on accessibility, dark mode, RTL support, haptics, automated testing (snapshot and visual regression), and exploring AI-assisted workflows for component and token migration.

📝 Enhancement Note: This role is positioned as a senior individual contributor within the Design Systems team, with significant ownership over critical infrastructure that impacts the entire product development lifecycle. The emphasis on cross-platform development (iOS, Android, Web) and a hybrid work model requiring proximity to a physical hub suggests a need for strong communication, collaboration, and the ability to balance remote flexibility with in-person team synergy.

📈 Primary Responsibilities

• Develop, maintain, and evolve native components for iOS (Swift/SwiftUI), Android (Kotlin/Jetpack Compose), and web (React/TypeScript) as part of the Whatnot Design System (WDS).

• Implement and manage a robust design token architecture, ensuring seamless synchronization from Figma to code repositories via automated pipelines.

• Collaborate closely with Product Designers on UI specifications, component API design, and identifying and addressing gaps between design and implementation.

• Build and enhance tooling that bridges the gap between design and engineering, such as Figma plugins, code connectors, and component playgrounds.

• Drive improvements in UI quality by implementing best practices for accessibility, theming (including dark mode), internationalization (RTL), and integrating automated testing strategies like snapshot and visual regression testing.

• Contribute to the development of component telemetry and explore AI-driven solutions to streamline component and token migration processes.

• Actively participate in code reviews, provide constructive feedback, and mentor junior engineers on design system best practices.

• Stay abreast of emerging trends and technologies in design systems, front-end development, and mobile development to continuously improve WDS.

📝 Enhancement Note: The responsibilities clearly indicate a hands-on engineering role with a strong focus on cross-functional collaboration. The emphasis on "shipping consistent, accessible, high-craft UI" and "raising the bar on quality and leverage" points to a senior engineer expected to influence and improve existing processes and standards. The mention of WDS 2.0 suggests involvement in a significant platform evolution.

🎓 Skills & Qualifications

Education:

• Bachelor's degree in Computer Science, a related technical field, or equivalent practical work experience. Experience:

• 5+ years of professional software engineering experience focused on building user-facing products.

• Demonstrated experience in building or maintaining a design system, including component libraries, design tokens, and versioning strategies. Required Skills:

• Proficiency in shipping production UI on at least two of the following platforms: iOS (Swift/SwiftUI), Android (Kotlin/Jetpack Compose), or Web (React/TypeScript).

• Hands-on experience with design token architecture and management (e.g., Figma variables, Tokens Studio, style-dictionary-like pipelines).

• Proven ability to design and implement robust component APIs that are developer-friendly and easy to use.

• Strong collaboration skills with product designers, including comfort with Figma, understanding of variants, properties, and auto layout.

• Deep understanding and practical application of accessibility standards (e.g., VoiceOver, TalkBack).

• Experience with theming, dark mode implementation, and internationalization (RTL support).

• Experience with automated testing methodologies, including snapshot and visual regression testing. Preferred Skills:

• Experience building Figma plugins or other design-to-code tooling.

• Familiarity with documentation platforms such as Supernova or Storybook.

• Experience with AI agents or tools for accelerating component and token migrations.

• Enthusiasm for working across all three platforms (iOS, Android, Web).

• Experience with haptics, component telemetry, and performance optimization.

📝 Enhancement Note: The requirement for experience on "at least two of our three platforms" and "genuine enthusiasm for flexing across all three" highlights the cross-functional nature of the role. The preference for experience with specific tooling and AI agents suggests the company is forward-thinking and looking for candidates who can contribute to innovative solutions.

📊 Process & Systems Portfolio Requirements

Portfolio Essentials:

• Demonstrable examples of design system components built and maintained for at least two platforms (iOS, Android, Web).

• Case studies showcasing the implementation and impact of design tokens, including how changes were propagated across platforms.

• Examples of collaboration with designers, illustrating how design specifications were translated into production-ready code.

• Projects that highlight a strong focus on accessibility, theming (dark mode, RTL), and automated testing for UI components.

• Evidence of building or contributing to developer tooling that enhances the design-to-code workflow. Process Documentation:

• Showcase documentation for design system components, including API usage, best practices, and intended behavior.

• Provide examples of how design token pipelines were established and managed, detailing the synchronization process from design to code.

• Illustrate workflows for integrating new components or updating existing ones within a design system framework.

• Document approaches to ensuring cross-platform consistency and managing platform-specific nuances within a unified design system.

📝 Enhancement Note: For a Design Systems Engineer role, the portfolio is crucial for demonstrating practical application of concepts. The focus should be on tangible results, collaboration, and technical execution across different platforms. Clear documentation of processes and the impact of their work will be highly valued.

💵 Compensation & Benefits

Salary Range: $207,000 - $230,000 USD per year.

Benefits:

• Generous Holiday and Time off Policy

• Comprehensive Health Insurance options including Medical, Dental, and Vision.

• Work From Home Support:

  • Home office setup allowance.
  • Monthly allowance for cell phone and internet expenses.

• Care Benefits:

  • Monthly allowance for wellness activities.
  • Annual allowance towards childcare expenses.
  • Lifetime benefit for family planning, including adoption or fertility expenses.

• Retirement Savings:

  • 401k offering for Traditional and Roth accounts in the US with employer match up to 4% of base salary.
  • Pension plans available internationally.

• Monthly allowance to "dogfood" the Whatnot app, encouraging employees to use and understand the product.

• Paid Parental Leave: 16 weeks of paid leave, with a one-month gradual return-to-work option (company leave allowances run concurrently with country requirements).

Working Hours: 40 hours per week (standard full-time).

📝 Enhancement Note: The salary range provided is competitive for a senior Software Engineer role in a major tech hub like San Francisco. The benefits package is extensive, emphasizing employee well-being, family support, and professional development, which is attractive for senior talent. The "dogfooding" allowance is a unique perk that underscores the company's commitment to product immersion.

🎯 Team & Company Context

🏢 Company Culture

Industry: E-commerce / Live Shopping Marketplace / Technology. Whatnot operates at the intersection of social media, e-commerce, and live streaming, creating a unique marketplace for collectors and enthusiasts. This fast-paced environment requires agility and a user-centric approach.

Company Size: The company is a rapidly growing startup, indicated by its recent funding and recognition as a top startup employer. This suggests a dynamic, potentially less bureaucratic environment where individual contributions can have a significant impact.

Founded: The company was founded with the mission to enable anyone to turn their passion into a business and bring people together through commerce. This foundational principle likely drives a culture focused on entrepreneurship, community, and empowering sellers.

Team Structure:

• The Design Systems team is likely a specialized engineering function, working closely with Product Design and individual product teams across iOS, Android, and Web.

• Collaboration is expected to be cross-functional, with engineers partnering daily with designers and potentially interacting with platform engineering leads.

• The "remote co-located team" model means that while remote work is supported, there's an expectation of connection and collaboration within designated geographic hubs (e.g., San Francisco). Methodology:

• Data-Driven Decisions: The emphasis on metrics (component adoption, migration velocity) suggests a data-informed approach to design system development.

• Agile Development: The mention of moving fast and a lack of a "playbook" points towards agile methodologies, rapid iteration, and a willingness to adapt.

• User-Centricity: Staying close to users and focusing on impact are core tenets, meaning design system decisions should ultimately benefit both buyers and sellers on the platform.

Company Website: https://whatnot.com

📝 Enhancement Note: Whatnot's culture is described as action-oriented, curious, and focused on outcomes rather than credit. The "remote co-located" model is a key aspect, indicating a blend of remote flexibility with intentional in-person collaboration, particularly for roles requiring close partnership with design and product teams.

📈 Career & Growth Analysis

Operations Career Level: This role is a Senior Software Engineer level within the Design Systems discipline. It implies a high degree of technical expertise, ownership, and the ability to influence technical direction within the design system domain. The expectation is to not only execute but also to contribute to the strategic evolution of the system.

Reporting Structure: While not explicitly stated, a Senior Design Systems Engineer typically reports to an Engineering Manager or Lead for Design Systems. They would be part of a broader engineering organization, collaborating heavily with Product Design leadership and individual product teams.

Operations Impact: The Design Systems team has a profound impact on operational efficiency and product quality. By providing a robust, consistent, and well-documented set of UI components and tokens, they enable product teams to ship features faster, reduce bugs, maintain brand consistency, and improve overall user experience across all platforms. This directly contributes to customer satisfaction, retention, and the platform's scalability.

Growth Opportunities:

• Technical Specialization: Deepen expertise in cross-platform UI development, advanced design token architectures, and cutting-edge design system tooling.

• Leadership Potential: Opportunity to become a technical lead or architect within the Design Systems team, mentoring other engineers and driving architectural decisions.

• Cross-Platform Mastery: Gain comprehensive experience across iOS, Android, and Web development within a unified system context.

• Process Improvement: Lead initiatives to improve the design-to-code pipeline, automation, and tooling, directly impacting engineering velocity and quality across the company.

• Industry Influence: Contribute to the broader design systems community through talks, articles, or open-source contributions, leveraging Whatnot's innovative approach.

📝 Enhancement Note: The role offers significant opportunities for technical growth and leadership within a specialized but critical area of software engineering. The emphasis on cross-platform development and advanced tooling suggests a path for engineers looking to become experts in modern UI development practices and design system architecture.

🌐 Work Environment

Office Type: Whatnot operates a "remote co-located" model. This means while employees can work remotely, they are expected to live within commuting distance of designated "hubs" in the US (San Francisco, New York), UK, Ireland, Poland, Germany, and Australia. This suggests that while full remote is an option, there are physical office spaces available for collaboration, team events, and focused work.

Office Location(s): The specific role requires living within commuting distance of the San Francisco or New York hubs. This implies access to office facilities in these locations, offering a blend of in-person and remote work opportunities.

Workspace Context:

• Collaborative Environment: The hybrid model and emphasis on in-person time for planning and problem-solving suggest a culture that values both focused individual work and dynamic team interaction.

• Tools and Technology: Expect access to modern development tools, cloud infrastructure, and potentially dedicated spaces for design system work within office hubs. The role involves working with cutting-edge tools for design and development synchronization.

• Team Interaction: Opportunities for direct collaboration with designers, fellow engineers on the design systems team, and potentially product managers and engineers from various product teams to gather feedback and ensure alignment.

Work Schedule: Standard 40-hour work week, with flexibility inherent in the remote-first aspects of the company's policy. However, the hybrid requirement for this role necessitates living within commuting distance of a hub, implying a need for availability during core business hours for cross-functional collaboration, particularly with designers and engineers.

📝 Enhancement Note: The "remote co-located" aspect is crucial. It's not fully remote without geographic constraints; it's a hybrid model that leverages distributed talent while encouraging in-person collaboration in specific locations. This suggests a need for strong communication skills and the ability to manage time effectively across different working modes.

📄 Application & Portfolio Review Process

Interview Process:

• Initial Screening: A recruiter or hiring manager will review your application and resume, looking for alignment with the core requirements and experience.

• Technical Phone Screen: A conversation with an engineer from the Design Systems team to discuss your background, experience with design systems, cross-platform development, and problem-solving approach.

• Take-Home Assignment/Design Challenge: A practical exercise to assess your skills in building components, working with design tokens, or solving a specific design system problem. This might involve creating a small component library or demonstrating how you'd approach a cross-platform sync.

• On-site/Virtual On-site Interviews: Multiple interviews with various team members, including engineers, designers, and potentially engineering leadership. This will involve discussing your take-home assignment, diving deeper into your portfolio projects, behavioral questions, and system design scenarios related to design systems.

• Final Round: Potentially a conversation with a senior leader or executive to assess cultural fit and overall alignment with the company's vision.

Portfolio Review Tips:

• Showcase Cross-Platform: Clearly present examples of your work on iOS, Android, and Web. Highlight how you ensured consistency and managed platform-specific nuances.

• Detail Design Token Implementation: Provide specific examples of your design token architecture, how you managed the pipeline from Figma to code, and the tools you used.

• Illustrate Collaboration: Use case studies to describe your process of working with designers, from reviewing specs to iterating on component APIs.

• Highlight Impact: Quantify the impact of your work whenever possible. Use metrics like adoption rates, reduction in UI bugs, or improvements in development velocity.

• Focus on Quality: Emphasize your contributions to accessibility, theming, and testing. Demonstrate your commitment to building robust and trustworthy components.

Challenge Preparation:

• Familiarize Yourself with WDS: If possible, explore Whatnot's public-facing design or components to understand their current style and approach.

• Practice Design-to-Code: Be ready to demonstrate how you translate Figma designs into clean, maintainable code for your chosen platforms.

• Tokenization Strategy: Prepare to discuss your approach to organizing and managing design tokens for scalability and consistency.

• Accessibility & Testing: Be ready to explain your thought process for ensuring components are accessible and how you implement automated testing.

• Cross-Platform Nuances: Anticipate questions about handling platform-specific design patterns and user expectations.

📝 Enhancement Note: The interview process is structured to assess technical depth, collaborative ability, and practical application of design system principles. A strong portfolio that clearly demonstrates cross-platform experience, design token expertise, and collaboration with designers will be critical for success. The take-home assignment is a key opportunity to showcase these skills.

🛠 Tools & Technology Stack

Primary Tools:

• Mobile Development: Swift, SwiftUI (iOS); Kotlin, Jetpack Compose (Android).

• Web Development: React, TypeScript.

• Design Tools: Figma (including variables, auto layout, plugins).

• Design Token Management: Experience with tools like Tokens Studio, or familiarity with pipeline concepts like style-dictionary.

• Versioning & Package Management: Git, npm/yarn, CocoaPods/Swift Package Manager.

Analytics & Reporting:

• Component Telemetry: Potential for custom implementations or integration with analytics platforms to track component usage and performance.

• Snapshot & Visual Regression Testing Tools: Jest, Percy, Applitools, or similar frameworks for automated UI testing.

CRM & Automation:

• While not directly customer-facing, design system tools often integrate with broader development pipelines. This might include CI/CD tools (e.g., Jenkins, GitHub Actions, CircleCI) for automated builds and deployments of component libraries.

• Documentation Platforms: Supernova, Storybook, or custom-built documentation sites for design system components.

📝 Enhancement Note: Proficiency across all three platforms (iOS, Android, Web) is a key differentiator. Experience with Figma and its advanced features, coupled with a solid understanding of design token architectures and automated testing, are critical technical requirements. The mention of AI agents points towards an interest in leveraging emerging technologies for efficiency.

👥 Team Culture & Values

Operations Values:

• Bias Toward Action: A culture that encourages taking initiative and moving quickly to solve problems, rather than waiting for explicit direction.

• Genuine Curiosity: A desire to understand the "why" behind what is being built and to explore new approaches and technologies.

• Outcomes Over Credit: A focus on achieving collective success and delivering impact, with less emphasis on individual recognition.

• Close to Product & People: A commitment to understanding user needs and the practical application of the product, fostering empathy and user-centric design decisions.

• High-Craft UI: A dedication to building visually appealing, polished, and high-quality user interfaces that enhance the user experience.

• Efficiency & Leverage: Continuously seeking ways to optimize processes and maximize impact through well-designed systems and tooling.

Collaboration Style:

• Partnership with Design: Treating designers as integral collaborators, fostering a symbiotic relationship where design and engineering feedback loops are continuous and constructive.

• Cross-Functional Integration: Working closely with product teams to ensure the design system meets diverse needs and integrates smoothly into their development workflows.

• Open Communication: Encouraging clear and frequent communication, especially in a hybrid/remote environment, to ensure alignment and shared understanding.

• Knowledge Sharing: A culture that values sharing best practices, learnings, and challenges related to design systems and cross-platform development.

📝 Enhancement Note: Whatnot's values are geared towards a fast-paced, innovative startup environment. The emphasis on "bias toward action," "outcomes over credit," and "close to product and people" suggests a team that is driven, collaborative, and deeply invested in the success of the platform and its users.

⚡ Challenges & Growth Opportunities

Challenges:

• Cross-Platform Synchronization: Maintaining perfect consistency and parity across iOS, Android, and Web platforms, especially during rapid development cycles.

• Token Architecture Evolution: Evolving the design token system (WDS 2.0) to be more robust, scalable, and easier to manage as the product grows.

• Adoption Velocity: Encouraging and supporting product teams to adopt new components and migrate from older systems, overcoming potential inertia or technical debt.

• Bridging Design & Code Gaps: Continuously improving the tooling and processes that ensure seamless translation from Figma designs to production code.

• Balancing Specialization and Breadth: Excelling in design systems while maintaining proficiency across multiple development platforms (Swift, Kotlin, React).

Learning & Development Opportunities:

• Deep Dive into Design Systems: Become an expert in the latest trends, best practices, and tooling in the design systems space.

• Cross-Platform Engineering: Enhance skills in Swift/SwiftUI, Kotlin/Compose, and React/TypeScript through hands-on application and mentorship.

• Tooling and Automation: Develop expertise in creating custom tooling (Figma plugins, code generators) and automating complex workflows.

• Architectural Design: Contribute to the architectural decisions of the design system, influencing its future direction and scalability.

• Mentorship: Opportunities to mentor junior engineers and share knowledge, developing leadership skills.

📝 Enhancement Note: The role presents opportunities to tackle complex, impactful challenges at the forefront of design system engineering. The growth paths are clearly defined for technical deepening and leadership within this specialized domain.

💡 Interview Preparation

Strategy Questions:

• "Describe a time you had to convince a team to adopt a new design system component or pattern. What was your approach, and what was the outcome?" (Focus on influence, collaboration, and demonstrating value.)

• "How would you approach designing and implementing a new design token architecture for a growing product? What are the key considerations for scalability and maintainability across platforms?" (Focus on technical strategy, understanding of tokens, and cross-platform thinking.)

• "Walk me through your process for ensuring accessibility standards are met for a new UI component you're building. What tools or techniques do you use?" (Focus on practical application of accessibility and testing.) Company & Culture Questions:

• "What interests you about Whatnot's mission and its position in the live commerce space?" (Research the company's values, recent news, and market position.)

• "How do you see the 'remote co-located' model impacting your work and collaboration within the Design Systems team?" (Demonstrate understanding of hybrid work dynamics and how you'd thrive.)

• "Describe a situation where you had to work closely with a designer to resolve a conflict or ambiguity in a UI specification. How did you ensure a positive outcome?" (Highlight collaboration, communication, and problem-solving skills.) Portfolio Presentation Strategy:

• Structure Your Narrative: For each portfolio piece, clearly articulate the problem, your approach (technical details, collaboration), and the impact/outcome.

• Show, Don't Just Tell: Use live demos or well-annotated screenshots/videos to showcase your work. For code examples, be prepared to discuss specific implementation choices.

• Highlight Design Token Workflow: Clearly explain your process for managing tokens from Figma to code, emphasizing automation and consistency.

• Quantify Impact: Use metrics wherever possible (e.g., "Reduced UI bug reports by X%", "Increased component adoption by Y%").

• Tailor to the Role: Emphasize projects demonstrating cross-platform experience, design system contributions, and strong collaboration with designers.

📝 Enhancement Note: Interview preparation should focus on demonstrating a deep understanding of design systems, cross-platform development, and collaborative problem-solving. Be ready to articulate your process, showcase tangible results through your portfolio, and connect your experience to Whatnot's specific needs and culture.

📌 Application Steps

To apply for this Design Systems Engineer position:

• Submit your application through the provided Ashby link, ensuring your resume is tailored to highlight your experience in design systems, cross-platform development (iOS, Android, Web), and collaboration with designers.

• Curate Your Portfolio: Select 2-3 key projects that best showcase your design system work, including examples of component libraries, design token implementation, and cross-platform consistency. Prepare to discuss the challenges, your solutions, and the impact of these projects in detail.

• Prepare for Technical Deep Dives: Review your experience with Swift/SwiftUI, Kotlin/Compose, React/TypeScript, Figma, and design token architectures. Be ready to discuss specific implementation details and best practices.

• Research Whatnot: Familiarize yourself with Whatnot's product, mission, values, and recent news. Understand their approach to commerce and technology.

• Practice Your Presentation: Rehearse presenting your portfolio and answering common interview questions, focusing on clarity, conciseness, and demonstrating your problem-solving approach and collaborative style.

⚠️ 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.

---