Skip to content
uxerhub

Design engineer job description template

By Sergio Gualda · 3 min read · Updated

In software, a design engineer works between design and frontend, often owning the design system and the details that make an interface feel right. The title also means something very different in mechanical and electrical engineering, so say “software” in your first line. Then state which side of the role weighs more on your team.

The template

About the role: We're hiring a design engineer for our software product, [name]. You'll sit between design and engineering, and you'll spend roughly [60%] of your time in code and [40%] in design tools. You'll report to [title].

  • You'll build and look after [our design system or component library], and decide what belongs in it.
  • You'll prototype in code so the team can judge how something feels before committing to it.
  • You'll handle interaction details like motion, transitions and states that a static design can't describe.
  • You'll work directly with designers and engineers, and settle disagreements about what's worth the effort.
  • You'll hold a quality bar on shipped interfaces and know when to let something go for a deadline.
  • You have experience shipping production frontend code with [your stack].
  • You can show design work of your own, or show how your code improved someone else's design.
  • Nice to have: experience running a design system across several teams.

Decide the balance before you publish

The percentages in the first paragraph do more work than the rest of the listing. A designer who codes and an engineer with taste are both called design engineers, and they want different jobs. If you don't know the split yet, write down the first three projects this person would take on, and it'll be obvious.

Frequently asked

What's the difference between a design engineer and a frontend developer?
A frontend developer is judged mainly on building features reliably. A design engineer is also judged on how the interface feels and on the system behind it. Plenty of people could do both; the listing should say which you're measuring.
Do design engineers need a design portfolio?
They need something that shows taste and judgment. That might be a portfolio, a public component library or a set of prototypes. Ask for whichever suits how your team will use them.