What a €50,000 salary band tells your best candidate, and a five-minute test to fix it

On Thursday I spoke with a security engineer who has spent fifteen of his eighteen years in IT doing nothing but security. Half an hour, a good conversation, and by the end of it he had turned down the role I'd called about.

The job was a strong one on paper. A small health-tech start-up in Berlin wants one person to own security and compliance end to end: AWS and GCP, the BSI C5 and ISO certifications, threat modelling, vulnerability management. Hybrid, two days from home, virtual equity on top.

The base was listed as €50,000 to €100,000.

He is looking for €120,000 to €135,000, and for a company further along, with a hundred-plus people and a proper engineering floor behind him. Both reasons were real. Only one of them was inside the company's control, and it was the one he heard first.

What a wide band actually says

Founders tend to write a broad range for sensible reasons. They want to stay open, they don't want to scare off a strong junior, and they'd rather negotiate than commit. All fair.

A senior candidate doesn't read it that way. When the top of a band is double the bottom, the message that comes across is that the company hasn't yet decided who it is hiring. Is this a second-year engineer who will grow into the remit, or someone who has already carried two certifications through audit? Those are different people, at different prices, and they ask different questions in the first five minutes.

Worse, the experienced candidate assumes you'll anchor near the floor, because that is where offers usually start. So €50,000 to €100,000 sounds like seventy-five with a following wind, and the conversation ends politely.

Set the scope against the market

The scope in that brief is not junior. One person owning cloud security, certification and risk for a regulated health product is the job a head of information security or a senior cloud security architect does in a larger company. Barclay Simpson's 2026 guide to cyber security pay in Germany puts a head of information security with a team of under ten at €100,000 to €160,000 in Berlin, Munich and Frankfurt, and a cloud security architect at €110,000 to €150,000. Even a cloud security engineer sits at €90,000 to €120,000.

So the brief asked for a head of security and priced the floor below an individual engineer. Candidates notice that gap far faster than hiring teams do.

Equity rarely closes it. Virtual shares in a ten-person company are a genuine upside, but a senior hire with a mortgage in Berlin or a family in Johannesburg weighs them as a bonus, not as rent.

The rules are moving your way anyway

The EU Pay Transparency Directive expects employers to give applicants the starting pay, or its range, in the advert or before the interview, and it stops them asking about current salary. Germany missed the June 2026 deadline to write this into law, and as of late October there was still no government draft. It will come, though, and when it does, a range like €50,000 to €100,000 will be printed for everyone to compare against the work you describe. Better to fix it now, on your own terms.

The five-minute band test

Before the role goes out, or before your recruiter makes a single call, sit down with the brief and answer five questions.

1. Who is this, in one line? Write the job as a title you could look up: "senior cloud security engineer", not "security person who does everything".

2. What does the market pay that title? Take one current salary guide for your city and write down its range. If your ceiling sits below its midpoint, you have found the problem.

3. How wide is your band? If the top is more than about a third above the bottom, decide which half you are really hiring for and cut the other.

4. Which part could you move? Base, title, team size, working pattern or start date. Pick one in advance, so the first "no" isn't the last word.

5. Would you say it out loud? Put the number in the first message to the candidate. If you wince typing it, a senior person will wince reading it.

If question two or three shows a gap, you have two honest choices. Raise the band to match the scope, or shrink the scope to match the band and hire someone earlier in their career who will grow into it. Both work. What fails is keeping a head-of-security brief and a junior floor, and hoping the right person won't do the maths.

The engineer from Thursday will find his next role, probably within weeks. The start-up will keep looking. The shame is that a fifteen-minute rewrite of one line might have kept that conversation going.

If you're hiring for a hard-to-fill technical role in DACH or South Africa and want a second view on the brief before it goes out, book a 30-minute call.

Next
Next

The Blue Card line for IT in 2026, and who clears it