Summary
Most advice on answering salary expectations was written before pay transparency. With roughly 60% of postings now publishing a range, deflecting reads as evasive and gains nothing. The stronger move is anchoring to the top third of the published range rather than the midpoint, because employers budget to the midpoint expecting negotiation. Prepare three numbers: a floor, a target, and an anchor set 10 to 15 percent above the target.
The standard salary expectations answer is to never give a number first. Deflect, redirect, make them go first.
That advice suited a world where you had no idea what the role paid. Roughly 60% of postings now include a salary range, either voluntarily or because of transparency laws in more than a dozen US states. When the posting prints the range you both just read, deflecting protects nothing. It reads as evasive, and it wastes the leverage that publication just handed you.
Here is the salary expectations answer that fits the information you now actually have.
Why has the old salary expectations answer stopped working?
Because the information asymmetry it protected against has largely gone. Around 60% of postings now publish a range, and salary history bans in states including California, New York, Massachusetts, Illinois and Colorado stop employers anchoring you to what you used to earn. Deflecting a question you can already answer with published data reads as evasion.
In short, two changes did this, and both favour you.
Published ranges. More than half of listings on major boards now disclose at least a band. Research on pay transparency laws found they raise disclosed salaries by about 3.6% and actual earnings by roughly 1.3% — modest on their own, but they hand you an anchor you previously had to guess at.
Salary history bans. In a growing list of states, employers cannot ask what you earned before. That severs the mechanism that used to drag every new offer toward your old one, which mattered most to anyone underpaid in a previous role.
Europe is moving the same way: Directive 2023/970 required transposition across EU member states by June 2026, obliging employers to disclose pay information to applicants.
The practical upshot is a reversal. The question used to be a trap because you were guessing. Now it is usually a test of whether you did five minutes of research.
What is the best salary expectations answer when a range is published?
Anchor to the top third of the published range, not the midpoint. Employers budget to the midpoint expecting negotiation, so candidates who name the midpoint receive it. Reference the range explicitly and tie your number to scope rather than to need.
Above all, this is the single most costly mistake in the whole topic, and it is invisible while you make it.
A posted range of $80,000 to $110,000 has a midpoint of $95,000. That midpoint is what the company expects to pay someone of moderate experience, and it already assumes negotiation. Say $95,000 and you have accepted the opening position of a negotiation that never happened.
The salary expectations answer that works references the range and justifies your position within it:
“I saw the range posted at 80 to 110. Based on the scope you’ve described — particularly owning the reporting layer end to end — I’d be targeting the upper part of that, around 102 to 108.”
Three things make that work: it acknowledges their published number rather than ignoring it, it justifies the position with role scope rather than personal need, and it names a range whose bottom is still a number you would happily accept.
Justify with scope, never with need
"I need 105 because of my mortgage" and "I'd be targeting 105 given the scope you've described" ask for the same money and land completely differently. The first invites the employer to assess whether your need is their problem. The second frames the number as a property of the job, which is the only framing where they can agree with you without feeling generous.
What if no range is published?
Ask for it once, then answer. "Could you share the range budgeted for this role?" is a normal question and in transparency states some employers must answer it. If they press you first, give a range anchored at the top of what you would genuinely accept with enthusiasm.
Here, one redirect is professional. Two is a standoff.
The redirect: “Could you share the range budgeted for this role? That’ll help me confirm we’re aligned before we go further.” In transparency jurisdictions, the law obliges some employers to provide it when asked.
If they press: answer with a range, not a point. Anchor its bottom at the top of what you would accept happily — because in practice, employers hear the bottom of your range as your real number.
That last point deserves emphasis. If you say “90 to 110” you have effectively said 90. Set the bottom where you would sign without hesitation.
What three numbers should you prepare?
A floor, a target, and an anchor. The floor is the minimum you would accept and still want the job. The target is where you realistically expect to land, ideally between the 50th and 75th percentile for the role and location. The anchor is what you say out loud, set 10 to 15 percent above the target.
| Number | What it is | How to set it |
|---|---|---|
| Floor | The minimum you would accept and still be glad | Your actual budget plus a margin, never disclosed |
| Target | Where you expect to land | 50th–75th percentile for role, level and location |
| Anchor | What you say when asked | 10–15% above target, or the top third of a posted range |
Preparing these three takes twenty minutes and removes the improvisation that costs people the most. Research from APEC found that naming a range without calculating it first costs roughly 12% at signing — which compounds, because every future raise and every next offer builds off that base.
The number worth internalising is that gap. Not negotiating at all, or negotiating from an uncalculated number, is not a neutral choice — it is a permanent discount applied to everything that follows.
Uncalculated: "I'm looking for something around 90, but I'm flexible."
Prepared: "Based on the range you posted and the scope we've discussed, I'm targeting 102 to 108. I'd want to understand the bonus structure and equity before treating base alone as the whole picture."
The first names a number and immediately discounts it. The second anchors high, justifies with scope, and opens total compensation as a second lever — which matters where base budgets hold firm but signing bonuses do not.
When does the question actually come up?
Early, in most processes. The question lands in the first stage of roughly six out of ten interviews, usually during the recruiter screen. That is a filtering conversation rather than a negotiation, so the goal there is alignment rather than maximisation.
Meanwhile, timing changes what you are trying to achieve.
At the phone screen, the recruiter is checking whether you fit the budget. This is a knockout question — one of the five that eliminate candidates at that stage — so a clear range prevents an unnecessary rejection. Vagueness here often triggers a follow-up loop that consumes your best minutes.
In later rounds, the same question is confirming alignment before they build an offer package.
After a written offer is where actual negotiation happens, and where the leverage is highest, because they have now spent real hours choosing you.
What if the posted range is below what you need?
Say so early, plainly, and without apology. Discovering a mismatch at offer stage wastes weeks for both sides. Naming it in the first conversation occasionally moves the range, and always saves the time.
Admittedly, this is the scenario most articles skip, and it comes up constantly.
The professional version is short:
“Thanks for sharing that. The range is below what I’m targeting based on my research and the scope of the role. Is there flexibility, or should we be honest that this may not be the right fit on compensation?”
Two outcomes, both better than the alternative. Sometimes the range moves, because posted bands often have room above them for the right candidate. Sometimes it does not, and you have reclaimed three weeks of process for a role you would have turned down anyway.
Treat base as one component. Signing bonuses jumped from 20% to 42% of offers between two quarters of 2025, so a capped base often leaves movement elsewhere.
Say "I'm flexible" or "whatever's fair". It reads as unprepared, gives the recruiter nothing to work with, and hands them the anchoring position you were trying to protect.
What should you never do?
Give a single number rather than a range, justify your ask with personal expenses, name a figure before researching the market, or accept the first offer without asking. Around 64% of candidates who negotiate receive more than the initial offer.
Four reliable ways to weaken a salary expectations answer:
A single number. It has no room and reads as a demand. A range gives both sides somewhere to move.
Personal justification. Rent, childcare and debt are real, and they are not arguments an employer can act on.
Answering before researching. Five minutes on posted ranges for the same title in the same city is the difference between an anchor and a guess.
Accepting immediately. Roughly 64% of people who negotiate get more than the first offer. Asking once, politely, is close to free.
Companies budget to the midpoint expecting negotiation; candidates who anchor to the top of the range leave with a better outcome.
Finally, before any of this matters, the process has to reach you — which means a resume that parses and matches the posting. Running yours through an AI resume checker against the specific role is the step upstream of every conversation here. And once you are in the room, signs an interview went well explains why a question about your salary expectations is itself one of the more reliable positive signals — it costs the interviewer something to ask.
Frequently asked questions
How do you answer "what are your salary expectations"?
Give a range anchored to market data, justified by the scope of the role. If a range is posted, target its top third and reference it explicitly rather than naming an unrelated figure.
Should you say a number first?
When the range is published, yes — deflecting a question you can answer from the posting reads as evasive. When nothing is published, ask for their range once, then answer if they press.
What salary range should I give?
One whose bottom is a number you would accept happily, since employers hear the bottom as your real figure. Set your anchor 10 to 15 percent above your target, or in the top third of a posted range.
Why shouldn't I say the midpoint of a posted range?
Because companies budget to the midpoint expecting negotiation. Naming it accepts the opening position of a negotiation that never took place.
Can employers ask my current salary?
Not in a growing number of US states, including California, New York, Massachusetts, Illinois, New Jersey, Colorado and Washington. Salary history bans exist to stop new offers anchoring to old pay.
What if the range is lower than I need?
Say so in the first conversation, plainly. Sometimes the band has room above it for the right candidate; when it does not, you have saved weeks on a role you would have declined.
When is the best time to negotiate?
After a written offer, when the company has invested in choosing you. Earlier conversations are alignment checks rather than negotiations.
Does negotiating actually work?
For most people. Around 64% of candidates who negotiate receive more than the initial offer, and research found that naming an uncalculated range costs roughly 12% at signing.
Comments