Sr. Design Engineer

Job Description

Senior Design Engineer (Contract)

IIIMPACT. Remote with US hours overlap. Roughly 30 to 40 hours per week, contract to start, with a contract-to-hire path.

About IIIMPACT

IIIMPACT is a product strategy and UX consultancy, 21+ years in business and a three-time Inc. 5000 company. We help enterprise product organizations design and ship better software, and we work AI-native: our builds run through AI coding tools with senior human judgment as the control.

The role

You will build and maintain production-grade component libraries and design systems in code for our enterprise clients. The work is hands-on front-end craft: turning a client's design language into clean, well-documented, reusable components, and keeping them correct as the product evolves. You will work daily with AI coding tools and alongside senior designers.

What you will do

\n
• Build React components to spec from client design sources, with tokens and theming done properly.
\n
• Maintain component libraries over time: updates, refinements, and keeping documentation current.
\n
• Set up and care for Storybook as the living reference.
\n
• Run quality passes with our designers and fix what they catch.
\n
• Document as you build. A component without its written spec is not done.
\n

What we need you to have

\n
• Five or more years of front-end work, with deep React and TypeScript.
\n
• Fluency in Tailwind and shadcn or Radix component patterns, design tokens, and Storybook.
\n
• A design eye. You notice when an accordion arrow is two pixels off, and it bothers you until it is fixed. This matters as much as the code.
\n
• Real experience working with AI coding tools, and a clear view of where they are strong and where they quietly go wrong.
\n
• Self-directed remote habits. You will own work end to end on two-week cycles.
\n

What makes you stand out

\n
• You have rebuilt a legacy or vendor component library in a modern stack.
\n
• You have maintained or governed a design system, not just consumed one.
\n
• Accessibility knowledge and the habit of building to WCAG.
\n
• Experience packaging and publishing component libraries.
\n
• Reading fluency in Figma: variables, tokens, and component structure.
\n

How success is measured

By what ships: the quality of the components, how little rework they cause, and how well they hold up as clients build on them. Not hours in a seat.