UIUXAnywhere

Remote UI/UX & product design jobs, worldwide.

Guides

Design systems roles: what design systems designers do and how to become one

By the UIUXAnywhere team · Published November 8, 2026

Systems thinking is in half of all design listings

Design systems are one of the most common topics in remote design hiring. On 8 November 2026, among the 153 listings on UIUXAnywhere with a full description, 76 mentioned design systems, half of them. 30 mentioned component libraries, 19 mentioned contribution or governance, and 8 mentioned design tokens.

Dedicated design systems roles are a smaller, senior niche. Ten roles had "design system" in the title, including "Senior Product Designer, Design Systems", "Staff/Principal Design Systems Lead", "Product Design Manager - Design System", "Principal Experience Designer - Visual Design & Design Systems" and "Lead Engineer - Front End Platform & Design System". Of those ten, four were senior, three lead and two principal.

So there are two levels to this guide: the design systems skills every product designer is now expected to have, and the specialist role for people who want to build systems full time.

What a design system is

A design system is the shared set of reusable parts and rules a company uses to build its products consistently: design tokens, components, patterns, guidelines and the code that implements them. It is a product in its own right, with designers and engineers as its users.

Well-run systems make teams faster (less reinvention), products more consistent and accessible, and changes cheaper (update a component once, not in fifty screens).

What design systems designers do

  • Foundations: colour, typography, spacing, elevation and motion, defined as design tokens that map to code variables, including themes such as light and dark mode.
  • Components: designing buttons, inputs, menus, tables and more, with every variant and state (hover, focus, disabled, error, loading), responsive behaviour and accessibility built in.
  • Patterns: larger, reusable solutions such as forms, empty states, navigation and data tables.
  • Documentation: usage guidance (when to use and not use a component), do and don't examples, content guidelines and accessibility notes.
  • Governance and contribution: how teams request changes, propose new components and contribute back; versioning and communicating changes.
  • Adoption: helping product teams migrate, measuring usage, and finding where teams go around the system and why.

Working with engineering

Design systems roles are unusually close to engineering. A component exists twice, in Figma and in code, and the job is to keep them aligned. Expect to:

  • agree component APIs (props, variants, slots) with engineers, so Figma properties match code;
  • maintain tokens that flow into code, often through a token pipeline;
  • review implemented components in Storybook or a documentation site;
  • test accessibility together: keyboard behaviour, focus, screen reader announcements.

Some roles blur into design engineering, where the designer also writes front-end code. Knowing HTML, CSS and how component libraries are built in React or similar frameworks is a strong advantage; see HTML and CSS for designers.

Skills to build in Figma

  • Components with well-structured variants and component properties (boolean, instance swap, text).
  • Variables for tokens and modes (themes, density, brands).
  • Auto layout throughout, so components resize like their coded versions.
  • Library management: publishing, versioning, and handling breaking changes.
  • Annotations that engineers can rely on.

Measuring a design system

Senior roles ask how you would know a system is working. Useful measures:

  • adoption: share of product surfaces or code using system components;
  • detachments or overrides in Figma, and one-off components in code;
  • time to build common screens;
  • accessibility issues found in audits before and after adoption;
  • satisfaction from designers and engineers who use it.

Moving into design systems work

If you are a product designer:

  1. Contribute to your company's system. Propose a component you needed, design it fully, document it, and work with an engineer to ship it.
  2. Audit inconsistency. Collect every version of a button or modal across your product. An audit makes a compelling case study and a strong argument for change.
  3. Learn the engineering side. Read your component library's code and Storybook; learn how tokens reach production.
  4. Write documentation. Clear guidance is a core skill and easy to show.

If your company has no system, build a small one for a real product: tokens, ten core components with states, a few patterns and documentation.

Showing systems work in a portfolio

Systems work is hard to show with final screens alone. Strong case studies include:

  • the problem: inconsistency, slow delivery, accessibility gaps, with examples;
  • the structure: token architecture, component anatomy, variant logic;
  • collaboration with engineering and how design and code stayed aligned;
  • governance: how others contributed;
  • impact: adoption, time saved, accessibility improvements.

Common design system mistakes

Teams often stumble in the same places:

  • Building a library nobody asked for. Start from the components product teams use most, and the inconsistencies that hurt them.
  • Design and code drifting apart. If Figma components and coded components evolve separately, both lose trust. Agree a shared source of truth and release together.
  • Too many variants. A button with forty combinations is hard to use correctly. Fewer, well-documented options are better.
  • No contribution path. If teams cannot propose changes, they build one-off versions instead.
  • Ignoring content and accessibility. A component is not finished until its text guidance and keyboard and screen reader behaviour are defined.
  • Treating it as a project. A design system needs ongoing ownership, roadmaps and support, like any product. Funding it as a one-off project usually means it decays within a year.

Pay

Only one dedicated design systems role stated pay: $218,000–307,000 a year for a staff/principal design systems lead role in the US. That is not a market rate, but it shows that systems leadership is valued at the top of design pay bands. See what remote design jobs pay for broader figures.

For the tools behind systems work, see Figma and the other tools remote design jobs ask for. The roles below are the newest remote design systems openings; each one shows where you can work from.

Open remote UI/UX roles

  1. Senior Design Systems EngineerRamp · Remote (US)
  2. Senior Frontend Engineer - Design SystemsMercury · San Francisco, CA, New York, NY, Portland, OR, or Remote within Canada or United States
  3. Senior Product Designer, Design SystemsKettle · Remote

More guides