The EU Pay Transparency Directive 2026: How to Negotiate When the Salary Range Is Already Posted

Why a Posted Range Rewires the Whole Negotiation

For as long as most people have been job hunting, salary negotiation was a game of hidden information. The employer knew their budget. You didn't. They often knew your last salary, because they asked, and that number became the low anchor for the entire conversation regardless of what the role was actually worth. Your job was to guess at their ceiling while they tried to guess at your floor, and whoever blinked first — whoever named a number, or answered the "what are you currently earning" question honestly — usually lost some leverage.

A posted range changes the shape of that game entirely. The employer has already told you their floor and their ceiling. They can't use your salary history to anchor you low, because in jurisdictions where the ban applies, they're not legally allowed to ask. So the negotiation stops being "what's the number" and becomes something much more specific: where in this band do I land, and what's my evidence for landing higher than the midpoint.

That's a fundamentally different skill than the "always counter, never accept the first offer" advice that fills most negotiation content. When the number was invisible, negotiating was partly about extraction — trying to find out what was actually available and claw toward it. When the number is visible, negotiating is about positioning — proving you belong at the top of a range the employer has already committed to publicly. This is a subtler, more evidence-driven conversation, and most candidates aren't ready for it because they've spent years training for the old game.

Step One: Work Out Where You'd Actually Land

Before you can negotiate a range, you need a working theory of where in it you currently sit. Most candidates skip this and go straight to "can you go higher," which reads as generic and is easy for a recruiter to deflect. Instead, do the diagnostic work first.

Look at the posting itself for signals. A range that starts low and tops out high is usually spanning multiple seniority bands within one nominal title — the company hasn't fully separated a "Senior Analyst I" from a "Senior Analyst III" in the posting, but the pay structure behind it has. Job descriptions that list a long spread of required years of experience ("4–9 years") alongside a wide salary range are telling you the same thing: they're fishing across a seniority spread, and where you land depends on which end of that experience spread you actually match.

Then look at your own profile against what you know the role needs. Three things reliably push you toward the top of a posted band:

Scope overlap with the senior end of the range. If the posting's upper band implies people who've managed budgets, led teams, or owned a full function, and you've done that even at smaller scale, say so explicitly and early.
Specific, named achievements that map to the role's stated priorities. Not "I increased efficiency" — "I cut deployment time from six weeks to nine days for a twelve-person engineering team," tied directly to something the posting says the role needs to fix.
Scarce skills the posting flags as "nice to have" but that you know, from the market, are actually hard to find. If the listing casually mentions a skill that's genuinely in short supply for that function, that's not a nice-to-have from your side of the table — it's leverage.

The mistake to avoid is asking for the top of the range because you want it. Every candidate wants the top of the range. What moves a recruiter or hiring manager is a specific, evidenced case for why your profile matches the top rather than the middle — and building that case requires you to actually diagnose, honestly, where your experience currently sits before you open your mouth.

Reading Wide, Narrow, and Suspicious Ranges

Not all posted ranges mean the same thing, and treating them all identically is a mistake.

A wide range — one where the ceiling is 60% or more above the floor, so something like €70,000–€115,000 — usually means the company hasn't tightly banded this role, or is genuinely open on seniority and letting the market sort candidates into the right level. Don't treat a wide range as "ask for the top and see." Treat it as a signal to ask a direct clarifying question in your first real conversation: "This range spans a fairly wide band — can you tell me what typically separates someone who lands near the floor from someone who lands near the ceiling?" That question does two things. It shows you're thinking like someone who plans to be in the upper half, and it gets the hiring manager to hand you, unprompted, the exact criteria you need to build your case against.

A narrow range — floor and ceiling within 10–15% of each other — usually means the band is genuinely fixed by policy, often at larger, more structured employers with formal pay grades. Here, pushing hard on base salary itself is usually low-yield; the recruiter frequently doesn't have discretion to move it regardless of how good your pitch is. This is your signal to shift the entire negotiation toward the things around the base number, which we'll get to below.

A suspiciously low or oddly narrow range for the seniority implied by the title is worth probing rather than walking away from immediately. Sometimes it means the company under-leveled the posting relative to what the role actually requires. Sometimes it means the budget is genuinely constrained and the title is inflated to attract applicants. Either way, a polite, direct question — "the range listed feels tighter than I'd expect for a role with this scope, can you help me understand how it was set" — gets you real information and costs you nothing. Employers who bristle at that question are telling you something useful about how they'll handle every future compensation conversation with you.

A Worked Example: Reading a Range and Building Your Ask

Say you're looking at a posting for a Senior Product Marketing Manager role in the Netherlands, listed at €68,000–€98,000. That's a 44% spread — wide, not extreme. The listing asks for "5+ years in B2B SaaS marketing" and lists cross-functional leadership and pricing strategy as "preferred" rather than required.

Here's how you'd work it:

Diagnose the spread. A 44% spread with a loosely defined "preferred" section usually means the company is open to hiring anywhere from a strong individual contributor to someone functioning close to a Director. Your job is to figure out which side of that they actually need filled right now.
Ask the clarifying question early, ideally in the recruiter screen: "Is the team currently looking for someone to execute an existing strategy, or to help build the pricing and positioning function from scratch?" The answer tells you almost exactly where the real budget sits, regardless of what the posting says.
Match your evidence to whichever answer you get. If they say "build from scratch," and you've led a pricing overhaul even at a smaller company, that's your opening: "I led exactly that at [Company] — rebuilt our tiered pricing model, which lifted expansion revenue by [X]%. That's the scope I'd expect to operate at here, which is why I'd be looking at the upper half of your range."
Anchor your ask to the band, not to a number you pulled from nowhere. "Based on the scope we've discussed, I'd expect to land around €90,000–€95,000" reads completely differently from "I was hoping for €95,000." One is evidenced positioning inside a range the employer already committed to. The other is a wish.

That's the whole shift in miniature: you're not negotiating against the company's secret budget anymore, you're negotiating your position inside a number they've already made public, using specifics they told you themselves.

What to Negotiate When the Base Is Genuinely Fixed

Plenty of employers, especially larger ones with formal pay bands, will tell you plainly that the base salary number is not negotiable — it's set by a job architecture system and moving it requires a re-leveling that's simply not happening for this hire. Believe them when they say this; fighting a policy-locked number is usually wasted energy. But a fixed base doesn't mean a fixed offer. It means the negotiation moves to everything else:

Sign-on bonus. Often the single most flexible line item precisely because it's a one-time cost, not a change to the ongoing pay band.
Annual bonus target and structure. Ask what the target percentage is, what it's historically paid out at, and whether it's negotiable even if base isn't.
Equity or stock grants, where applicable — vesting schedule, refresh grant policy, and total grant size are all frequently more movable than base pay.
Start date and initial review timing. Pulling your first compensation review forward from twelve months to six, in writing, is a real financial lever if you're confident in your ability to perform.
Remote or hybrid flexibility, which has real monetary value in commuting cost and time even though it doesn't show up in the salary line.
Professional development budget, certifications, and conference spend, particularly relevant if you're moving into a role where a credential or specialization pays off later.
Extra vacation days or a compressed schedule, which some employers will grant more readily than cash because it doesn't hit the same budget line.

The tactical point here is sequencing. If a recruiter tells you the base is fixed, don't keep pushing on base — you'll read as not listening, and you'll burn goodwill you need for the rest of the negotiation. Instead, say something like: "Understood on the base — given that, I'd like to talk through the bonus structure and start date for the first review," and move the conversation there immediately. That's a candidate who's negotiating skillfully, not one who's stuck relitigating a number that was never going to move.

How the Salary History Ban Changes Your Screening Call

Where salary-history bans apply, recruiters are not supposed to ask what you currently earn, full stop. In practice, this shows up as questions like "what are your salary expectations" instead of "what do you currently make" — a subtler version of the same fishing expedition, and one that's still completely legal to ask even where the history ban applies.

Here's how to handle it. You are not obligated to volunteer your current salary, and in a jurisdiction where the ban is in force, the recruiter isn't supposed to press you on it directly. If they ask anyway — sometimes out of habit, sometimes because the person on the call hasn't caught up with the law yet — you have a clean, professional way to redirect: "I'd rather focus on the value I'd bring to this specific role and the range you've posted, since that's a better basis for the conversation than what I've earned elsewhere." That's not confrontational. It's a factual redirect that most recruiters will simply accept, because you're right and they usually know it.

What you should volunteer instead is your expectation, anchored to their posted range and your evidence — not your history, and not a number pulled from a salary survey with no connection to the specific job. "Based on the scope we've discussed, I'd expect to be in the €85,000–€92,000 range" is the sentence that does the work. It uses their own number, positions you inside it with a reason, and gives them nothing to anchor you low with.

If the Range Wasn't Posted and Should Have Been

You'll run into postings, especially over the next year or two while implementation across the EU is still catching up, where a range legally should be disclosed but isn't — maybe the country's law is already in force and the employer hasn't updated its hiring process, or the recruiter genuinely doesn't know the rules changed. Don't assume bad faith and don't open with an accusation. Ask directly and professionally, early in the process: "Could you share the salary range for this role? I believe that's required for postings in [country] under the current transparency rules." Framing it as a request for information, not a callout, gets you the number in almost every case without creating friction, and it signals you're informed without being adversarial.

If you get pushback or a non-answer, it's worth deciding early — before you've invested three interview rounds — whether you're willing to proceed without that information. You're allowed to say, plainly, that you'd like the range before moving to a first interview. Companies that are serious about the process will provide it. The ones that dodge repeatedly are giving you useful information about how the rest of the relationship might go.

What Pay Transparency Doesn't Fix

It's worth being honest about the limits here, because overselling what these laws do you a disservice. A posted range narrows information asymmetry — you know the floor and ceiling instead of guessing blind. It does not eliminate negotiation as a skill, and it does not guarantee two equally qualified candidates land at the same point in the band.

Two people applying for the identical posted range, with genuinely comparable experience, can still end up 15–20% apart within that same band based entirely on how they handle the conversation — whether they diagnosed where they sit, whether they asked the clarifying question about what separates floor from ceiling, whether they anchored their ask to evidence instead of vague deservingness, whether they held their ground when told the base was fixed and moved the conversation to what wasn't. Transparency laws are a floor under fairness, not a ceiling on how much negotiation still matters. If anything, because the crude old leverage — anchoring you to a low past salary — has been taken off the table in jurisdictions where these bans apply, the leverage that's left is almost entirely about how well you can build and present a case for where you belong in the band. That rewards preparation more, not less.

A Straightforward Disclaimer

Everything above is career and negotiation guidance, not legal advice. Pay transparency law is genuinely in flux right now — the EU directive's transposition deadline has passed, but most large member states missed it and are still finalizing their own national versions, US state laws vary significantly in scope and enforcement, and the specific obligations that apply to any given job posting depend on the country or state, the size of the employer, and the exact date you're reading this. Before you rely on any specific right described here — the salary-history ban, the requirement to disclose a range, the right to request pay data broken down by sex — confirm what's actually in force where you're applying. If you think an employer is violating a real legal obligation, that's a conversation for a lawyer or your local labor authority, not a negotiation tactic.

Getting Ready to Actually Use This

None of this works if you walk into the conversation without having done the diagnostic work first — reading the range, mapping your evidence to the top of it, and having a clear, specific answer ready for "why should you land above the midpoint." That's genuinely a rehearsal problem as much as a research problem; the difference between knowing the theory and actually delivering "here's why I belong at the top of your range" cleanly, under a bit of pressure, in real time, is practice. ClavePrep's <a href="/tools/salary-negotiation-script">salary negotiation script tool</a> helps you build that specific case — evidence, phrasing, and sequencing — for the exact range and role in front of you, rather than a generic script that ignores the number the employer already posted.

If the harder part for you is the interview itself, not just the compensation conversation at the end of it, ClavePrep's AI mock interview product, covered in full at <a href="/how-it-works">how it works</a>, gives you a realistic run-through before the real thing, so the negotiation conversation is happening after you've already made the strongest possible case for the role. And if you're at the stage of figuring out which postings are even worth this level of preparation, <a href="/live-roles">live roles</a> is where you can see current openings, several of which already carry the posted ranges this whole guide is about.

Frequently Asked Questions

Does the EU Pay Transparency Directive apply to all job postings in Europe right now, in every country? No. The directive's transposition deadline was June 7, 2026, but as of that date only Italy, Slovakia, Lithuania, and Malta had complete national legislation in force. Larger economies including Germany, France, Spain, the Netherlands, Sweden, and Denmark missed the deadline and are working toward their own national laws, some not landing until 2027 or later. Whether a specific posting is legally required to disclose a range depends entirely on which country you're applying in and how far along that country's implementation is.

Can an employer still ask me what I currently earn? Where a salary-history ban is in force — which is the case in an increasing number of EU countries as they implement the directive, and in several US states independently — employers are not supposed to ask about your salary history directly. Some will still ask about your "salary expectations" instead, which remains legal; the difference is subtle but matters, and you're generally free to answer with an expectation anchored to the posted range rather than disclosing your actual current pay.

If a range is posted, is it always negotiable? Not necessarily the floor and ceiling themselves — some companies operate on fixed, policy-driven pay bands where the range as posted genuinely can't move for a given level. What's almost always negotiable is where you land within that range, plus the items around it: sign-on bonus, annual bonus target, equity, start date, remote flexibility, and development budget.

What should I do if a posted range seems unusually wide? Treat a wide range, generally one spanning 60% or more from floor to ceiling, as a signal to ask directly what separates a floor-level hire from a ceiling-level one. That question usually gets you the exact criteria the employer is using to sort candidates, which you can then build your case against.

What if the job posting doesn't have a range at all, and I think it legally should? Ask for it directly and professionally, early in the process — something like "could you share the salary range for this role, I believe that's required under current rules in [location]." Don't lead with an accusation; many employers are still catching up to new requirements rather than deliberately avoiding them. If they consistently avoid giving you a number, that's useful information about the process ahead.

Do salary transparency laws mean everyone in the same posted range gets paid the same? No. The range sets the floor and ceiling that apply to the role, but individual placement within that band still depends heavily on your experience, the scope you'll actually own, and how well you negotiate. Two candidates with similar backgrounds can land meaningfully apart within the same disclosed range.

Is this legal advice I can rely on in a dispute with an employer? No. This is career and negotiation guidance based on publicly known facts about the EU directive and the broader global trend toward posted salary ranges. Implementation is uneven and still evolving as of 2026. If you believe a specific legal right is being violated, consult a lawyer or your local labor authority rather than relying on general guidance like this.

What the Directive Actually Requires, in Plain Terms