What Are You Worth? 2026 Engineering Salary Bands

In my first VPE year at Mews, interviews alone took about 40% of my capacity. Hundreds of comp conversations from the paying side of the table. Since then, 3,662 1:1 leadership sessions on the asking side.

The same failure shows up on both sides. The candidate quotes a country median. The manager quotes a budget. Neither can say what the person in the room is worth, so the louder one wins.

I wrote it on my salary page and I stand by it: you do not know your number, so you negotiate blind. This post is the fix. It gives you the 2026 Western-Europe bands for engineers and for engineering managers, and the skill model that tells you which band is yours.

Country medians answer the wrong question

The best crowd data is genuinely good. The levels.fyi Europe heatmap is the strongest dataset in the game; its German slice alone held 3,360 salary submissions as of March 2026. If you want to know what the market paid other people, start there.

But look at the spread the median hides. In one Hacker News thread on that heatmap, an engineer posts his company’s transparent internal bands: 34K junior, 49K mid, 62K senior. A few comments later, someone else calls 100-110K the realistic senior number. Same continent, same year, same job title. Nearly double the money.

A median tells you what other people got. It says nothing about what you are worth.

That spread is not noise. Two things drive it: company tier and level. A body shop and a product scale-up pay different bands for the same title, and inside each company, level decides where in the band you land. The 62K senior and the 110K senior in that thread are both telling the truth about different tiers.

You cannot change the tier math from inside a negotiation. You can change the level argument. Level is not years of experience. It is a bundle of demonstrable skills, and skills can be scored.

The 2026 bands, engineer and EM

These are the bands I compiled for the two calculators in July 2026. Gross EUR per year, Germany/Netherlands hub tier. Sources, so you can check me:

• levels.fyi Europe heatmap, the largest crowd dataset
• its Germany slice, 3,360 submissions as of March 2026
• the transparent company bands engineers posted in that HN thread

Individual contributor track:

Management track:

Switzerland, London, and US-headquartered remote roles pay above these bands. Southern and Eastern Europe, and the body-shop tier anywhere, pay below.

Read the overlaps before the ceilings. A senior engineer’s band covers most of the EM band. A staff engineer reaches into director money. The management track is a different job, not a pay rise, which is exactly why I tell engineers deciding on the switch to run the readiness question first and the salary numbers second.

15 skills decide your level. Not your years.

Each calculator scores 15 concrete skills, three per pillar. The engineer set:

And the EM set, because leading is a different job:

The detail that does the real work: the pillar weights shift with your level.

Core craft is 45% of a junior’s score and 15% of a staff engineer’s. Impact moves the other way: 15% at junior, 30% at staff, because impact across teams is what companies pay staff engineers for. The weights follow how level rubrics at product scale-ups trade craft for scope as you go up; if your company weighs things differently, the sliders are yours to move. Score yourself with the wrong level’s weights and you get the wrong number.

AI leverage is a salary pillar now

One pillar is shared across both tracks, and it did not exist in comp models three years ago.

The market gap is documented: 78% of organizations now use AI in some form, yet only about 1% of executives call their company’s rollout mature. An engineer who genuinely ships with AI daily is scarce in a market where nearly everyone claims to. Scarcity prices.

One number from the model that surprises people: AI leverage weighs 20% for a junior and 10% for a staff engineer. At junior level, AI is the biggest instant output multiplier available. At staff level, judgment and impact dominate, and AI is table stakes.

How to use your number

The score is not the point. The conversation you have with it is. What worked for the people across my table at Mews, and what I coach now:

• Score yourself honestly, then once more as your skeptical manager would. The gap between the two runs is your credibility gap, and it is the first thing to close.
• Your two weakest pillars are the raise plan. A number without a plan is a complaint. “I am at senior band because X and Y; here is what closes the staff gap by Q2” is a case.
• “Levels.fyi says” never survived my CFO. A demonstrated-scope case did. A case a budget owner can defend upward has three parts: the scope you already demonstrated, the band evidence, and a date. That is the whole case; the 8-step long version just builds each part out.
• If the number and the plan meet a wall, change companies, not your number. A company that will not pay your band is giving you information about the company.

Run it: two calculators, ten minutes

The developer salary calculator and the engineering manager salary calculator are free: score your 15 skills, get your weighted level and your 2026 band position, plus a PDF skill report if you want it. Prefer an AI client? Both run as tools on my MCP server: add marian.coach/mcp and ask it what you are worth.

And when the number is on the screen and the conversation with your manager is the next step, preparing exactly that conversation is what I do with mentees every week.