DEV Community: Arturs B

I tracked 800 European design engineer job ads. The role barely exists as a job title.

Arturs B — Wed, 26 Aug 2026 05:49:45 +0000

For the last two months I've been pulling every design and product engineering job posting I could find across Europe. 800-plus roles, 11 different ATS platforms, checked every few days so I could see when they appeared and when they came down.

Disclosure before anything else: I run a small firm that places design and product engineers, so I had a commercial reason to gather this. Everything below is in the post, not behind a link, and the method note is at the bottom.

Here's what the data showed.

Only 76 of 800+ postings were unambiguously design engineer roles

The rest were adjacent jobs that get tangled up with it constantly. Frontend, product engineer, founding engineer, design systems, UI engineer. 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, which means anyone searching for one of them misses everyone posting under the others.

Worth saying that 76 is a small clean sample and I treat it as such throughout.

The median role had been live 57 days

Measured from each platform's own publish date to when the posting came down, so it's how long the job was actually up rather than how long I happened to be watching.

For comparison, in the same dataset:

Frontend engineer: 41 days
Design engineer: 57 days
Product engineer: 59 days
Founding engineer: 129 days

There's a pattern in that. The more disciplines a role folds into one hire, the longer it stays empty. Design engineer sits in the middle: specific enough that most applicants don't fit, common enough that companies keep posting it.

The ads ask for craft more than they ask for stack

This was the finding I didn't expect. Across the 76 clean postings:

Craft, taste, polish: 79%
React: 46%
TypeScript: 42%
Backend or full-stack: 22%

The vague, hard-to-measure quality outranks every concrete skill, and it isn't close. Craft appears nearly twice as often as React and roughly three times as often as any mention of backend work.

It's still an engineering job. Nearly half want React, a similar share want TypeScript. But the centre of gravity sits at the surface, where the product meets the person using it.

One company, Buena, put it more directly than I 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."

About one in six of the ads 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, they've been burned.

97% of these roles are senior or above

Almost nobody hires a junior design engineer. Which raises an obvious question: if there are no junior seats, where does the next generation of seniors come from?

They mostly arrive sideways. From frontend, from design, from having founded something. There's no pipeline building them on purpose, because there are almost no entry points.

46% of the ads ask for a portfolio

Far more than you'd see for a standard engineering role. The companies hiring this well seem to have worked out that a CV won't tell them what they need to know, so they look at the work instead.

Which makes sense given the craft finding. A keyword filter catches React. It doesn't catch whether someone will lose sleep over a two-pixel misalignment, or know when to stop polishing and ship.

Salary is basically absent

2% of the postings disclosed a number. Two percent. The public salary aggregators aren't much help either, since most of them are reporting mechanical and hardware design engineers, a different profession that happens to share the words.

I ended up running a separate survey to get a real number, because the job ads simply don't contain one.

Method

800+ design and product engineering roles posted across 11 European ATS platforms, collected from late July 2026 onwards and re-checked every few days. "Design engineer" here means the 76 postings that unambiguously described the software design-and-build hybrid, with hardware, mechanical and electrical roles filtered out. Days open is measured from each platform's own publish date. Reposts are flagged, not removed, which means the figures slightly understate how long some roles were genuinely live.

Happy to answer questions about any of it in the comments.

Your job title is worth €45,000. We surveyed 106 design engineers to find out.

Arturs B — Mon, 24 Aug 2026 10:24:35 +0000

There is no honest public number for what a design engineer earns in Europe.

Search for one and you will find plenty of figures. PayScale puts the German average at €54,006. SalaryExpert says €79,419 for the Netherlands. A UK survey published this year lands on a £49,489 median, with 88% of its respondents mechanically biased.

Those numbers are real. They are also measuring a different job. Public salary aggregators are reporting on mechanical, hardware and electrical design engineers, because that is what the phrase meant for 40 years before software borrowed it.

This is about the other one: the person who designs a product interface and then ships it to production themselves. The role Linear, Vercel, Stripe and Figma hire for. Two jobs, one name, and no reliable number for the second.

So we built the number ourselves. An anonymous survey of 106 design engineers across Europe: what they earn, what their contract calls them, how they work, and what stage of company they work for.

It is not the whole market. It is 106 real people who do this job, answering honestly, which is 106 more than any salary site has.

The headline

€115,000 median total annual compensation. Base plus realistic bonus and equity.

The middle 50% earns between €70,000 and €140,000. Half earn above €100,000. A third earn above €130,000.

The more useful figure is that €70,000 gap between the 25th and 75th percentile. Two people with the same job title can be that far apart.

The distribution is flat

Compensation does not cluster around the median. It spreads almost evenly from €40,000 to over €150,000.

Under €40,000 5%
€40,000 to €60,000 13%
€60,000 to €80,000 16%
€80,000 to €100,000 15%
€100,000 to €130,000 21%
€130,000 to €150,000 15%
Over €150,000 17%

n=102

That is what a role without a settled market rate looks like. There is no cluster because there is no consensus.

The title tax

We asked people to describe the work they do, then looked at what their contract actually calls them. Same work. The title moves the pay by tens of thousands of euros.

Design Engineer €115,000 (n=48)
Product Designer €90,000 (n=15)
Frontend Engineer €70,000 (n=12)
Creative Developer €50,000 (n=7)

Creative Developer has a small sample, so treat it as directional.

Carry the same skills, do the same work, and if your contract says "Design Engineer" you earn a median €115,000. Call the role "Frontend Engineer" and it is €70,000. That is a €45,000 swing on wording alone.

Only 46% of the people in this survey have "Design Engineer" written on their actual contract. The rest are doing the job under a scatter of other names, and being paid according to the name rather than the work.

The gap holds when you compare people at the same experience level, so it is not simply seniority in disguise. We could not test it reliably within a single country, because the samples get too small once split that way. Some part of it may reflect which kinds of companies use which titles.

The market pays for code, not design

We asked people to place themselves on the spectrum between design and engineering.

Mostly code, with design sensibility €115,000 (n=54)
An even split of design and code €102,000 (n=32)
Mostly design, some code €90,000 (n=11)

The further you lean toward code, the more you earn. A €25,000 gap between the ends.

Job ads for this role ask for craft. The market, when it opens its wallet, is still paying for the engineering half.

Pay jumps once, then plateaus
0 to 2 years €90,000 (n=18)
2 to 4 years €90,000 (n=23)
4 to 6 years €115,000 (n=19)
6+ years €115,000 (n=42)

One step up, at around the four year mark, and then it flattens. Someone with six-plus years reports the same median as someone with four to six.

This also gives context to the code versus design gap above, since the code-leaning group contains more senior people. The two effects are tangled together, and a sample this size cannot fully separate them.

What each stage pays
Series C+ / growth €140,000 (n=11)
Series A €115,000 (n=17)
Series B €115,000 (n=11)
Large or public company €115,000 (n=15)
Pre-seed / seed €90,000 (n=24)
Not a startup €70,000 (n=24)

The lowest-paying employer for a design engineer is not an early startup. It is a company that is not a startup at all, at a median €70,000, below even pre-seed.

Where in Europe pays most

Samples get thinner here, so read this as a rough ranking. Only countries with at least 8 respondents shown.

United Kingdom €140,000 (n=19)
Spain €115,000 (n=9)
Sweden €115,000 (n=9)
Germany €90,000 (n=14)
France €70,000 (n=10)
Italy €60,000 (n=8)

The UK leads clearly. Spain and Sweden match at €115,000 despite very different costs of living, which says something about how remote pay is flattening the old geographic hierarchy.

One thing that does not move the number

Fully remote and fully onsite design engineers earn the same median: €115,000. Hybrid earns €90,000.

Being in the office some of the time correlates with earning €25,000 less than being in it all the time, or none of it.

We would not publish that as a law. It may partly reflect which kinds of companies offer hybrid arrangements. But it runs against the usual assumption that remote is the thing you pay a penalty for. Here, remote pays like onsite. It is the middle that loses out.

What to do with this if you do this job

Until now there was no real number to point to, so most people were negotiating off guesses. A €115,000 median will not tell you what you should earn, but it is a reference point where there was none.

The part worth acting on is the title. Pay tracks with what your contract says about as much as it tracks with the work you do. If you are being offered a role under a title that anchors low, that is a conversation to have before you sign, not at your first review.

How we did this

Anonymous survey of 106 self-identified design engineers based in Europe, run in mid-2026.

Compensation is self-reported total annual value, base plus realistic bonus and equity, captured in bands. Medians use band midpoints, so treat them as accurate to within a band rather than to the euro. 102 of the 106 gave a compensation figure.

Cross-tabs are shown only where the subgroup is large enough to mean something. Several country and title cuts were left out as too small to report honestly.

This is a sample of engineers in our network and the networks of those who shared it. It is not a census of the European market.

Originally published on hymera.co. I run design and product engineer search at Hymera. If you do this job and want to be in the next round of the survey, say so in the comments.