> Markdown version of [/jobs/ext/2624182-design-systems-engineer](https://www.wearedevelopers.com/jobs/ext/2624182-design-systems-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Design Systems engineer - **Company:** DESIGNS AND WHATNOT LLC - **Location:** San Francisco, CA, United States (Remote available) - **Experience:** Expert - **Contract:** Permanent contract - **Skills:** Application Programming Interfaces (APIs), Artificial Intelligence, Apple IOS, Regression Testing, Software Engineering, TypeScript, Management of Software Versions, Document Enterprise Platform, ReactJS, Swiftui, Kotlin, Material UI, Information Technology, Production Code, Jetpack Compose, Figma, Api Design - **Published:** August 24, 2026 - **Apply:** https://www.dice.com/job-detail/6c5c5699-2417-4646-aa9c-58c2ad163f41 ## About the Role As our next Design Systems engineer you should have 5+ years of software engineering experience building user-facing products, plus: * Bachelor's degree in Computer Science, a related field, or equivalent work experience. * Shipped production UI on at least two of our three platforms - iOS (Swift/SwiftUI), Android (Kotlin/Jetpack Compose), and web (React/TypeScript) - and genuine enthusiasm for flexing across all three. You follow the work to whichever platform needs it most. * Hands-on experience building or maintaining a design system: component libraries, design tokens (e.g. Figma variables, Tokens Studio, style-dictionary-like pipelines), versioning and migration strategies, and API design that other engineers love to use. * A strong track record of cross-functional collaboration with designers - you're comfortable in Figma, can speak fluently about variants, properties, and auto layout, and treat designers as partners in defining component behavior rather than handing work over a wall. * Care for the details that make components trustworthy: accessibility (VoiceOver/TalkBack), theming and dark mode, internationalization/RTL, testing (snapshot, visual regression), and documentation. * Bonus: you've built Figma plugins or design-to-code tooling, worked with documentation platforms like Supernova or Storybook, or used AI agents to accelerate component and token migrations. ## Description The Whatnot Design System (WDS) is how one product ships coherently across iOS, Android, and web. We're in the middle of WDS 2.0 - a ground-up evolution of our tokens, components, and the pipeline that connects Figma to production code on all three platforms. As a Design Systems engineer, you will: * Build and evolve Whatnot Design System components across iOS (Swift/SwiftUI), Android (Kotlin/Compose), and web (React/TypeScript), so that every team ships consistent, accessible, high-craft UI - measured by component adoption, migration velocity, and reduction of one-off UI in the product. * Own and extend our design token architecture - base, semantic, and component tokens - and the automated pipeline that syncs them from Figma through our token repository into each platform's codebase, so a change made once lands everywhere without breaking changes. * Partner daily with product designers as a true collaborator: reviewing specs and redlines, pressure-testing component APIs and naming, flagging gaps between Figma and code, and building the tooling (Figma plugins, code connect, component playgrounds, snapshot galleries) that keeps design and engineering in lockstep. * Raise the bar on quality and leverage: accessibility by default, dark mode, RTL, haptics, snapshot and visual regression testing, component telemetry, and AI-assisted workflows that turn a Figma component into a first-draft implementation. We offer flexibility to work from home or from one of our global office hubs, and we value in-person time for planning, problem-solving, and connection. Team members in this role must live within commuting distance of our San Francisco or New York hub. You People who do well at Whatnot tend to be comfortable figuring things out as they go, biased toward action, and genuinely curious about what they're building. They care more about outcomes than credit and stay close to the product and the people using it. ## Related Videos - [Design Systems and how to develop consistent and scalable products with them](https://www.wearedevelopers.com/videos/639-design-systems-and-how-to-develop-consistent-and-scalable-products-with-them) - [Boost Productivity with AI: Figma & Playwright MCP Workflows - Aris Markogiannakis](https://www.wearedevelopers.com/videos/1768-boost-productivity-with-ai-figma-playwright-mcp-workflows-aris-markogiannakis) - [Kotlin Multiplatform - True power of native code reuse](https://www.wearedevelopers.com/videos/4-kotlin-multiplatform-true-power-of-native-code-reuse) - [From Zero to Mobile Developer in 45 Minutes With SwiftUI](https://www.wearedevelopers.com/videos/183-from-zero-to-mobile-developer-in-45-minutes-with-swiftui) - [Bridging the Gap](https://www.wearedevelopers.com/videos/794-bridging-the-gap) - [Fireside Chat with Kris Rasmussen, CTO at Figma](https://www.wearedevelopers.com/videos/982-fireside-chat-with-kris-rasmussen-cto-at-figma) ## Related Articles - [Are design and development really just the same thing?](https://www.wearedevelopers.com/magazine/520-are-design-and-development-really-just-the-same-thing) - [16 Best Free React UI Libraries in 2025](https://www.wearedevelopers.com/magazine/148-16-best-free-react-ui-libraries-in-2025) - [10 Essential Figma Plugins for Frontend Developers in 2023](https://www.wearedevelopers.com/magazine/262-10-essential-figma-plugins-for-frontend-developers-in-2023) - [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers) - [Declarative Design and a fresh take on collaboration with developers](https://www.wearedevelopers.com/magazine/595-declarative-design-and-a-fresh-take-on-collaboration-with-developers) - [Dev Digest 121 - AI goes offline](https://www.wearedevelopers.com/magazine/456-dev-digest-121-ai-goes-offline)