We're looking for a Design Systems Engineer to take ownership of our design system's end-to-end pipeline — from design tokens in Figma, through automated token transformation and component libraries, to visual-regression-gated delivery in production. This person sits at the seam between design and engineering: fluent enough in design to argue token semantics with designers, and strong enough in code to ship the infrastructure that turns design decisions into shippable, tested components.
This is the kind of role where one day you're reconciling a naming conflict between Figma and code, and the next you're diagnosing why a component renders differently in production. You'll be the steward of the system that every product team builds on top of.
Your responsibilities:- Owning the design token pipeline, you keep Figma as the single source of truth and drive tokens through to consumable CSS/SCSS variables and a component library, while managing primitive → semantic → component token tiers, naming conventions, and the inevitable gaps and conflicts.
- The component library is yours to build and maintain, as you review components against design specs, fix fidelity issues, and govern variants and APIs.
- In this role, you run design-to-code automation, programmatically extract tokens and component context from Figma, and build tooling (including AI-assisted workflows) that reduces the manual work of keeping design and code in sync.
- As the owner of visual-regression and accessibility infrastructure, you maintain a CI-integrated pipeline (visual diffing + automated a11y checks) with baseline management and PR gating, hosted on cloud infrastructure in collaboration with our DevOps teams and our Azure cloud infrastructure.
- When migrations are on the table, you lead the technical parts of component and token migrations by planning and executing phased rollouts that swap legacy components for the modern system spec-by-spec, with explicit sign-off and before/after evidence, while protecting backward compatibility.
- By documenting and transferring knowledge, you keep architecture decisions and conventions written down so the system stays maintainable beyond any one person.