The opportunity
We're looking for a design engineer to help build and maintain Waypoint, our design system, across both the Figma library and the production codebase. This is not a "designer who codes a little" or an "engineer who dabbles in Figma" role.
What you'll do
Own and evolve the Figma library for Waypoint: component structure, variants, properties, and documentation, so it stays a reliable source of truth for design teams.
Build and maintain core Waypoint components, contributing directly to our: component packages alongside the design engineering team.
Work across our token pipeline, keeping design tokens in Figma and their code: representations (CSS custom properties, Tailwind config) tightly synced.
Partner with product designers to translate new patterns into system: components, and with product engineers to make sure those components are easy to adopt correctly.
Help define and refine the workflows and tooling that connect Figma and code: (sync scripts, plugins, documentation sites) rather than relying on manual handoff.
Write clear documentation and usage guidance so the system scales without you being the bottleneck.
What they're looking for
- Own and evolve the Figma library for Waypoint: component structure, variants, properties, and documentation, so it stays a reliable source of truth for design teams.
- Build and maintain core Waypoint components, contributing directly to our: component packages alongside the design engineering team.
- Work across our token pipeline, keeping design tokens in Figma and their code: representations (CSS custom properties, Tailwind config) tightly synced.
- Partner with product designers to translate new patterns into system: components, and with product engineers to make sure those components are easy to adopt correctly.
- Help define and refine the workflows and tooling that connect Figma and code: (sync scripts, plugins, documentation sites) rather than relying on manual handoff.
- Write clear documentation and usage guidance so the system scales without you being the bottleneck.
- Weigh in on system architecture decisions: when to add a new component versus extend an existing one, how to version and package changes, how to keep the system consistent as it grows.
- Help shape how Waypoint evolves to serve a third consumer beyond designers: and engineers: the model itself. That means thinking about how components, tokens, and patterns get structured so they're legible to AI systems, not just to humans.
