"What are your salary expectations?" is the only interview question where a suboptimal answer has a precise, countable cost — sometimes thousands per year, compounding with every future raise calculated off that base. Which is why learning how to answer salary expectations deserves more than the usual advice of "just deflect." Sometimes deflecting is right; sometimes naming a researched range is stronger; and the answer depends on when you're asked, what you know, and how much leverage you hold. This guide gives you the decision rules and the word-for-word scripts for each branch. One important note before the scripts: norms and laws around pay conversations vary by country, state, and industry — several US states and a growing number of jurisdictions now require ranges in postings or forbid asking about salary history — so part of your preparation is knowing the rules where you're applying.
Why they ask early: budget filter, not an offer
When a recruiter raises money in the first screen, they're not negotiating — they're checking compatibility. Every role has a budgeted band; the recruiter's job is to avoid running five rounds of interviews with someone whose floor is above their ceiling. Understanding this defuses the anxiety: the early salary question is a filter, and your goal is simply to pass through it without anchoring yourself low.
This reframing also explains the golden rule of timing: information you give early constrains you; information you get early empowers you. The recruiter screen is where you should be asking about the range as much as answering — a two-way version of the exchange most candidates treat as one-way. (It belongs on your list of questions to ask in an interview.)
Researching your number: sources that beat guesswork
Walk in with three numbers — your floor (below which you decline), your target, and your stretch — built from sources in roughly this order of usefulness:
- Posted ranges in your market. Pay transparency laws mean many postings now include bands. Collect ten postings for your role, level, and location; the pattern is your market.
- Aggregator data — salary platforms and government wage statistics. Use several and expect disagreement; treat them as triangulation, not gospel, and match your specific title, level, and metro area.
- Humans. Two or three people in similar roles, asked tactfully ("Is a range of X–Y realistic for this kind of role around here?" is easier to answer than "What do you make?"). Recruiters in your field, current or former colleagues, and professional communities all count.
- Your own compensation history, adjusted — relevant context, but don't let a historically underpaid salary anchor your future. That's precisely the anchor several jurisdictions banned employers from asking about.
Adjust for the total picture: bonus structure, equity, retirement match, health costs, and remote-versus-metro location can move the real value of an offer meaningfully in either direction.
Deflect or name? Decision rules by stage and leverage
There's no universally correct move — there are conditions:
Deflect (ask for their range) when:
- It's the first screen and no range has been posted
- You suspect your researched numbers are shaky for this market
- You have reason to think the band is above your expectations (bigger company, hotter market)
Name your range when:
- They've declined to share theirs and pressing further would burn goodwill
- Your research is solid and your range is deliberately ambitious
- You're senior enough that coyness reads as gamesmanship
- A posted range exists — then your "range" is really a position within theirs
Either way, never name a single number early, and never answer with your current salary. The first is an anchor with no room; the second imports your old employer's constraints into your new negotiation.
Leverage modifies everything: with a competing offer in hand or a rare skill set in demand, naming a confident, high-but-researched range early works in your favor. With neither, extracting their range first is worth one polite attempt in every conversation.
Word-for-word scripts: the range answer, the deflection, the application form field
The deflection (first attempt, recruiter screen):
"Compensation matters, of course, but I'm still learning what the role fully involves. Could you share the budgeted range for the position? That would tell me quickly whether we're aligned."
Polite, reasonable, and it works often enough to always be worth trying — many recruiters will simply tell you.
The range answer (when deflection fails or naming is right):
"Based on my research for this type of role in this market, I'm targeting somewhere in the range of $78,000 to $88,000, depending on the full package — benefits, bonus, growth. Does that fit with what you've budgeted?"
Annotations: "based on my research" frames the number as market data, not personal hope. The 10–15% spread is wide enough to negotiate, narrow enough to mean something. Put your actual target near the bottom of the stated range — companies gravitate to the low end of whatever you say, so a range of "target to stretch" protects you. The closing question returns the ball and often extracts their band anyway.
The application form field (the box that won't submit while empty):
- If it accepts text: "Negotiable" or "Market rate — happy to discuss."
- If it demands a number: enter the bottom of your researched range, and treat it as provisional — form fields are filters, not contracts. If the form allows a range, use one.
The posted-range response:
"I saw the posting lists $70,000 to $95,000. Given my six years of experience and [specific qualification], I'd expect to land in the upper portion of that band."
You're no longer guessing — you're positioning, with reasons attached.
Pay transparency laws in 2026: what postings must tell you
The transparency landscape keeps expanding, but unevenly. A number of US states and cities require salary ranges in job postings; others require disclosure on request or after an interview; the EU's pay transparency directive is pushing member states toward disclosure requirements and restricting salary-history questions; and many places also ban employers from asking what you currently earn. The practical takeaways, wherever you are:
- Check the rules for the job's location — not yours. A remote role posted from a transparency state often carries the posting requirements with it.
- A posted range changes your script from discovery to positioning (see the script above). Note that some posted ranges are stretched wide for compliance; the realistic band is usually narrower than the extremes.
- If you're asked for salary history where that question is banned, you can sidestep gracefully: "I'd rather focus on the value of this role — my expectations for it are X to Y." No confrontation required.
Since rules differ and keep changing, verify the current requirements for your jurisdiction rather than assuming — a five-minute search on your state or country's labor department site settles it.
When they push back on your range: holding without hostility
The pushback conversation, played out:
Recruiter: "That's above what we've budgeted — the band tops out at $72,000."
You (option A — hold): "I appreciate you telling me directly. My range reflects the market I'm seeing, so $72,000 would be difficult as a base — but if there's flexibility elsewhere in the package, a signing bonus or an early review, I'm open to looking at the whole picture."
You (option B — walk politely): "That's helpful clarity. I think we may be too far apart on base, and I'd rather be honest about that than waste your process. If the band changes down the line, I'd welcome another conversation."
Both responses hold your position without a trace of hostility; the difference is whether the total package could plausibly close the gap. Two things to keep in hand: silence is allowed — after they name a low number, a beat of quiet often precedes their "...but there might be some flexibility"; and never bluff a competing offer. Real leverage names itself plainly; fake leverage collapses embarrassingly.
For roles with variable compensation — sales especially, where on-target earnings and quota structure matter more than base — the same scripts apply to the OTE conversation, and your track record does the arguing (a sales resume built on attainment numbers is negotiating leverage in document form).
From expectations to negotiation: bridging to the real conversation
Everything above happens before an offer. Once an offer arrives, you graduate from expectations to negotiation, and the dynamics invert in your favor: they've chosen you, invested rounds of interviews, and the alternative to closing you is restarting the entire search for their runner-up.
The bridge move when an offer lands:
"Thank you — I'm genuinely excited about this. I'd like a couple of days to review the full package. Could you send everything in writing?"
Always take the time; never accept or counter in the moment. Then evaluate the total (base, bonus, equity, benefits, flexibility, growth) against your researched three numbers, and return with a specific, reasoned counter on the one or two dimensions that matter most to you. If you set expectations well during the process — a researched range, low anchor avoided, their band discovered early — negotiation becomes a short, calm conversation instead of a standoff. The salary question also travels with a supporting cast in interviews ("Where else are you interviewing?" "When can you start?"), all covered in our guide to the most common interview questions.
Frequently asked questions
What if they insist on a number in the very first conversation?
Give your researched range rather than fighting past one deflection attempt — refusing twice reads as evasive and sours the relationship over a question they consider administrative. The range with a low-end target protects you well enough; walking into screens without a prepared range is the actual mistake to avoid.
Should I answer differently for hourly roles?
The structure is identical; only the arithmetic changes. Research the hourly market band, prepare floor/target/stretch per hour, and account for the variables that dominate hourly work: guaranteed hours, overtime rates, shift differentials, and scheduling stability. A higher rate with unstable hours can net less than a modest one with a full schedule.
Is it ever smart to go below my researched range?
Only deliberately, and only when a role trades short-term pay for something you've consciously priced: a career change into a new field, equity you believe in, credentials or training, or work arrangements money can't buy elsewhere. Decide that trade before the conversation — conceding mid-call under pressure is how people end up resenting jobs they chose.
What if my expectations changed mid-process — can I revise a number I already gave?
Yes, with a reason attached: "Since we first spoke, I've [received another offer / learned the role's scope includes X]. My updated range is..." It's a normal professional move when justified by new information — far better than silently resenting the old number or springing a surprise at the offer stage.
Know your worth on paper too
The same research discipline that sets your salary range should shape how your resume argues for it — evidence, numbers, and scope. Run yours through Workplacea's free resume checker to see whether the document justifying your range actually shows the achievements behind it.