Somewhere in Europe right now, a founder is on their ninth interview for one role, quietly Googling whether the person they're describing is technically a myth.
Here's what happened to them. They needed someone who could design a product and build it. Not a designer who hands off a Figma file and disappears. Not a frontend dev who needs pixel-perfect specs before they'll touch anything. Someone who does both. So they wrote "Design Engineer" at the top of a job post, and they waited.
Then the applications came in. React developers who've never opened Figma. Product designers who can't ship to production. A handful of people who are genuinely one or the other, but not both. Two months later the role is still open, and our founder is starting to wonder if they made the whole job up.
They didn't. The role is real. There just aren't many people who fit it, nobody agrees what to call them, and the way most companies write the job actively scares off the right ones.
We wanted to know how bad it really is. So we pulled every design and product engineering role we could find across Europe — more than 800 postings across 11 hiring platforms. Here's what the data actually says.
What we found
- 57days is how long the median design engineer role sits open. That's about 40% longer than a straight frontend role.
- 97%of these roles are senior or above. Almost nobody is hiring a junior design engineer, which means nobody's training them either.
- 2%disclose a salary. Just 2%. A further 41% compete on equity instead.
Here's the essence, before the detail. The design engineer isn't the slowest role in European tech to fill. Founding engineers take longer. But it might be the most misunderstood, and that's a different kind of hard.
Founding engineers sit open because they're genuinely rare. Design engineers sit open because the wrong people keep applying, and because the way most companies write the job practically guarantees it. The role isn't defined by a stack. It's defined by taste, judgment, and the ability to own something end to end. And none of that shows up in a keyword search.
The rest of this piece is the data behind that, and what to do about it.
The market can't even sort the role
Of those 800-plus roles, only 76 were unambiguously design engineer positions. The rest were adjacent jobs — frontend, product, founding engineer, design systems — that get tangled up with it constantly.
That ratio is itself the story. When a role is well understood, the market files it cleanly. This one doesn't file at all. The same job hides under half a dozen titles, so a founder searching for one of them quietly misses everyone posting under the others.
Worth saying plainly: 76 is a small clean sample, and we'll treat it that way. But it's 76 real postings we read properly, which is more than most people writing about this role ever bother to do.
Two months open, and the more hybrid the role, the worse it gets
The median design engineer role in our data had been live for 57 days. For comparison, a straight frontend role in the same dataset sits open around 41 days. So design engineer takes roughly 40% longer to fill than its closest neighbour.
And it climbs from there. Product engineer roles, a touch broader again, sit open around 59 days. Founding engineer — the most all-encompassing hybrid of the lot — runs to a brutal 129.
There's a pattern in that. The more disciplines a role asks one person to blend, the longer it stays empty. Design engineer sits right in the painful middle — specific enough that most applicants don't fit, common enough that founders keep trying to hire it anyway.
One number makes the scarcity concrete. 97% of these roles are senior or above. The junior version barely exists, which means the pipeline that should be producing these people isn't. The market wants design engineers who already exist, and it is not making more of them.
So what actually is a design engineer? We let the ads answer.
This is where it gets interesting, because the ads don't describe the role the way you'd expect.
You'd assume a hybrid engineering role leads with its stack — frameworks, languages, the usual keyword soup. It doesn't. The single most common thing these 76 ads ask for isn't React or TypeScript. It's craft. Taste. Polish. Some version of "cares deeply about how things look and feel" shows up in 79% of them, more than any specific technology.
Read that again. A vague, hard-to-measure quality outranks every concrete skill on the list, and it's not close. Craft shows up nearly twice as often as React, and roughly three times as often as any mention of backend work. That inversion is the whole role in one chart.
But — and this matters — it's still an engineering job. Nearly half want React, and a similar share want TypeScript. This is not a designer who dabbles in code. It's an engineer whose centre of gravity happens to sit at the surface, where the product meets the person using it. One company, Buena, put it better than we could:
"This isn't a frontend engineer with a design title, and it isn't a designer who prototypes and throws it over the wall." — Buena, from an actual job posting
They're not alone. About one in six of the ads we read defined the role by what it isn't, explicitly ruling out the two archetypes that keep applying. When companies start telling you what a job is not, it's a sign they've been burned. Repeatedly.
The best short definition came from a Finnish company, Agileday, and it's seven words: "you'll fit right in if you have good taste and can build." That's it. Taste, and the ability to ship. Everything else is detail.