Design Systems Engineer with React

Job Description:

This role needs someone who can evaluate the React component library as a production design system: verifying that components faithfully implement the Figma/Compass source of truth, use the correct design tokens, preserve accessibility, expose clean developer APIs, and are safe for broad institutional adoption for .ORG and other React projects at BECU.

They should have strong React and TypeScript skills, but also deep expertise in CSS, design tokens, Tailwind, Storybook, accessibility, visual regression testing, and package distribution. A key responsibility is identifying subtle but important gaps, such as components using Tailwind defaults instead of approved Compass/Figma tokens for shadows, spacing, colors, radius, typography, or states.

The candidate should be able to perform a component-by-component audit covering visual fidelity, token compliance, accessibility, Storybook coverage, API design, package health, and downstream developer experience. They should also be capable of setting up or improving automated guardrails such as static style checks, accessibility tests, visual regression tests, package consumption tests, and automation of updates between Figma and code.

Recommended required skills:

React and TypeScript component library experience

Design systems engineering experience

Strong CSS expertise, including custom properties, cascade, layout, states, and forced-colors/high-contrast support

Design token experience, ideally with Figma variables and token pipelines

Tailwind experience, especially distinguishing approved token usage from framework defaults

Storybook authoring and maintenance

Accessibility expertise beyond automated checks

Visual regression testing experience

Package publishing and consumption knowledge, including exports, tree-shaking, bundle size, and TypeScript types

Strong documentation and audit discipline

Expected deliverables should include:

Component-by-component audit matrix

Token compliance report

Accessibility findings

Storybook coverage gap report

Package health and consumption report

Prioritized remediation backlog

Pull requests for high-priority fixes

Recommended automated guardrails to prevent future drift