Careers at Flash DSM

Work on the tools a design system runs on: the Flash editor, Figma plugin, MCP server and Flash Inspect. Six open roles, all remote.

Open roles

Senior Frontend Engineer, Editor

Product · Remote · Full-time

Own the design-system editor: the token tables, the live preview and the component canvas people spend their day in.

  • Build editor surfaces in React and TypeScript that stay fast with thousands of tokens
  • Make the preview render exactly what the exported code will
  • Hold the bar on accessibility, keyboard use and right-to-left layouts

Apply if you have: A complex editor, canvas or data-heavy UI you built and can walk us through.

Apply: mailto:hello@flashdsm.com?subject=Application%3A%20Senior%20Frontend%20Engineer%2C%20Editor

Design Systems Engineer

Platform · Remote · Full-time

Work on the pipeline that turns one set of tokens into CSS, Tailwind, W3C DTCG, Figma variables and the context AI editors read.

  • Extend the codegen exporters and keep every output consistent with the others
  • Improve how a website or a Figma file is read into a real token system
  • Design the formats and contracts other tools build on

Apply if you have: A token pipeline, Style Dictionary setup or exporter you wrote and maintained.

Apply: mailto:hello@flashdsm.com?subject=Application%3A%20Design%20Systems%20Engineer

Figma Plugin Engineer

Platform · Remote · Contract

Own the Flash Figma plugin: variables, text styles and components written into a file, and read back out, without losing anything on the way.

  • Make the round trip between a Flash system and a Figma library exact
  • Handle the Plugin API's edge cases: modes, aliases, collections, limits
  • Keep large files fast, and every write safe to run twice

Apply if you have: A published Figma plugin that works with variables, and its source.

Apply: mailto:hello@flashdsm.com?subject=Application%3A%20Figma%20Plugin%20Engineer

AI Engineer, Generation Quality

AI · Remote · Full-time

Measure and raise the quality of the design systems Flash generates: contrast, ramps, type scales and the components built on them.

  • Build the evals that score a generated system the way a senior designer would
  • Turn failures into fixes in prompts, pipelines and deterministic repairs
  • Track quality per model and per release, so nothing regresses quietly

Apply if you have: An eval suite you built for an LLM feature, and what it changed.

Apply: mailto:hello@flashdsm.com?subject=Application%3A%20AI%20Engineer%2C%20Generation%20Quality

Developer Advocate, AI Editors

Growth · Remote · Full-time

Help teams connect their design system to Cursor, Claude Code and other AI editors through Flash's MCP server, and show what that makes possible.

  • Write the guides, examples and talks that show real teams the workflow
  • Run the community on Discord and bring what you hear back to the product
  • Build sample projects that prove agents can ship on-system UI

Apply if you have: Technical writing or talks about design systems or AI coding that people actually used.

Apply: mailto:hello@flashdsm.com?subject=Application%3A%20Developer%20Advocate%2C%20AI%20Editors

Design Systems Lead in Residence

Product · Remote · Part-time

A few days a month with the team, from someone who has run a design system at a company where many teams depended on it.

  • Review what Flash generates and exports against what real teams need
  • Bring the problems of adoption, versioning and governance into the roadmap
  • Open doors to design system teams who should be using Flash

Apply if you have: You led a design system used by several product teams, for at least two years.

Apply: mailto:hello@flashdsm.com?subject=Application%3A%20Design%20Systems%20Lead%20in%20Residence

Who does well here

  • You have shipped a design system, or the tools around one. Tokens, a component library, a Figma library, a docs site, a build pipeline. Something people depended on, and you kept working.
  • You care how one decision travels. A colour becomes a CSS variable, a Figma variable, a Tailwind class and a line in an AI editor's context. You want all four to agree.
  • You write things down. In the code, in the pull request, in the docs. The next person, human or agent, should not have to guess why.

How we hire

  1. Intro call. 30 minutes on what you have built and what you want to work on next.
  2. Work sample. A small task close to the real job. No trick puzzles.
  3. Team session. Walk us through the sample and meet the people you would work with.
  4. Offer. A clear answer, either way, within a week of the last conversation.

How to reach us

Send a short note and one thing you made. A repo, a Figma file or a page you shipped says more than a CV.