How to Answer Salary Expectations: Three Honest Scripts and When Each One Backfires

The short answer to how to answer salary expectations: give a researched range whose bottom number you would genuinely accept, or redirect to the range the employer has already published. Never quote a figure you have not checked against market data, and never treat the question as a trap you can fail simply by answering it.

Why the question exists, and what the recruiter is actually doing with it

Almost every candidate reads this question as a negotiation opening move. For the person asking it on a first call, it usually is not. It is a filter. The recruiter has a band they are allowed to hire inside, a stack of candidates, and twenty minutes. They are checking whether talking further is a waste of everyone's time.

That reframing matters, because it changes what a good answer has to accomplish. You are not trying to win a negotiation on minute six of a screening call — you have no leverage yet, because nobody has decided they want you. You are trying to do two things at once: stay inside the band so you are not screened out, and avoid naming a number so low that it becomes the ceiling later.

• The budget check. Is this candidate affordable at the level we are hiring? If your number sits far above the band, the call ends politely and early.
• The level check. Your number tells them where you think you sit in seniority. A figure far below the band reads as a candidate who has misjudged the role's scope — that can screen you out too.
• The anchor. Whatever number enters the conversation first tends to shape the range everything else is discussed around. This is the part candidates are right to be careful about.
• The paper trail. Many applicant tracking systems store whatever you typed in the desired-salary field and surface it to the hiring manager at offer time, months later, long after you have learned the job is bigger than it looked.

The anchoring worry is real but frequently overplayed in career advice. Refusing to engage at all, three times in a row, on a screening call is itself a signal — it reads as either inexperience or difficulty, and recruiters have plenty of other candidates. The practical goal is to give an answer that is honest, researched and slightly wide, then to keep the right to revise it once the scope of the job is clear.

Build the range before anyone asks for it

You cannot answer this question well without doing about ninety minutes of research first, and the research is the part most candidates skip. You are looking for three things: a floor you will not go below, a realistic midpoint for the role as advertised, and a defensible top of range you can justify with scope rather than optimism.

Start with government wage data for the baseline

The US Bureau of Labor Statistics runs the Occupational Employment and Wage Statistics program, which publishes wage estimates by occupation at national level, by state, and for roughly 530 metropolitan and nonmetropolitan areas. The May 2025 estimates, released on 15 May 2026, put the mean annual wage across all occupations at $69,770 and the median hourly wage at $24.51. The detailed tables also publish wage percentiles for most occupations, so you can see the 10th, 25th, 75th and 90th percentile — not just the middle.

Two honest limitations. OEWS estimates combine six semiannual survey panels collected over a three-year period, and BLS itself cautions that this makes the data awkward for looking at change over short periods — so it lags a fast-moving market. And the very top of the distribution has historically been suppressed: percentiles at or above $115.00 an hour, or $239,200 a year, were published only as a footnote rather than a number. The May 2025 release publishes specific estimates for many of those previously suppressed percentiles, which is a genuine improvement, but the top end remains the weakest part of the dataset. Treat OEWS as your floor-setting instrument and your sanity check, not as the number you quote.

Then read the posted ranges, including ones you are not applying to

The single most useful salary dataset available to you right now is the set of job postings in your field that are legally required to carry a pay range. You do not have to apply to read them. Twenty postings for adjacent roles, in the same metro or at comparable remote-first employers, will tell you more about current market pricing than any aggregate average, because a posted range is what someone is actually budgeting today.

Read them for structure as well as numbers. A range of $95,000–$130,000 for a role described in your exact language tells you the employer expects to pay near the middle for a solid hire and near the top only for someone who exceeds the brief. A range of $70,000–$180,000 tells you the posting covers several levels and that the level conversation matters more than the money conversation.

Use salary-sharing sites, but know what is wrong with them

Crowd-sourced salary sites are genuinely useful and structurally biased, and you should hold both ideas at once. The bias is not a conspiracy; it is arithmetic. People self-select into reporting, and the people most motivated to report tend to be at the tails — the unusually well paid and the unusually aggrieved.

• Self-selection. The sample is whoever felt like submitting, not a representative draw from the profession.
• Staleness. Entries often carry no visible date, and a four-year-old number in a repriced market is worse than no number.
• Missing context. Company size, team scope, equity terms and bonus structure are usually absent, and those are frequently what separate two people with identical titles.
• Thin coverage outside a few industries. Some sites are dense and reliable inside large tech employers and sparse to the point of meaninglessness everywhere else.
• Base versus total. Some sites report base only, some report total; comparing across them without checking is how people end up quoting a number 25% off.

Finish with two conversations

Aggregate data tells you the shape of the market. People tell you what is happening this quarter. Two short calls — one with someone doing the job you are applying for, one with a recruiter who staffs the role regularly — will correct your range faster than another hour of spreadsheets. Ask what a role like this is going for right now, not what they personally earn. It is an easier question to answer and you will get a straighter reply.

What US pay transparency and salary history rules actually change

The legal landscape has shifted meaningfully in the candidate's favour over the past few years, but it varies by state and by city, and it is routinely overstated in career content. Nothing here is nationwide, and none of it is legal advice — if you think a rule has been broken, that is a question for a lawyer or your state labour agency, not for a blog.

Pay ranges in job postings

A growing group of states requires employers to include a good-faith pay range in job postings, generally above an employee-count threshold. As of 2026 that group includes California, Colorado, Hawaii, Illinois, Maryland, Massachusetts, Minnesota, New Jersey, New York, Vermont and Washington, plus the District of Columbia. Two more joined in mid-2026. Virginia's requirement took effect on 1 July 2026 and reaches essentially every employer in the state regardless of headcount, alongside a new restriction on salary history inquiries. Maine's followed on 29 July 2026 for employers with ten or more employees, with the useful wrinkle that current Maine employees can ask for — and must be given — the pay range of the job they already hold.

A second group requires disclosure, but not in the posting itself. Connecticut, Nevada and Rhode Island require the range to be provided on request or at a defined point in the hiring conversation rather than up front. Delaware is a third case often mislabelled in summaries: its law does require the range in the posting, but not until 26 September 2027. Thresholds vary enormously across all of these — Colorado, Rhode Island and the District of Columbia reach employers with a single employee in the jurisdiction, New York starts at four, New Jersey at ten, California, Illinois and Washington at fifteen, Massachusetts at twenty-five, Minnesota at thirty and Hawaii at fifty. Check your own state rather than assuming, because the gap between a fifteen-employee threshold and a fifty-employee one decides whether the number is on the table before you ever speak to a human.

There is decent evidence these rules do something. A November 2025 NBER working paper by David Arnold, Simon Quach and Bledi Taska found that mandates raised the share of postings containing salary information by about 30 percentage points and were associated with wage increases of roughly 1.3% to 3.6%, with no detectable effect on employment, on the number of postings, or on the skill and education requirements employers stated. The practical read for you: in covered states, the employer's range is often already on the table, which makes the redirect strategy below much easier to run.

Salary history bans

Separately, a little over twenty jurisdictions restrict private employers from asking about or relying on your prior pay — roughly twenty states plus the District of Columbia and Puerto Rico. California, Colorado, Connecticut, Delaware, Hawaii, Illinois, Maine, Maryland, Massachusetts, Minnesota, Nevada, New Jersey, New York, Oregon, Rhode Island, Vermont, Virginia and Washington are among them. A few more states restrict the practice for state government employers only, and roughly two dozen cities and counties — New York City, San Francisco, Philadelphia, Chicago, Cincinnati, Toledo and Columbus among them — have their own ordinances. Michigan and Wisconsin have gone the other direction entirely and pre-empted local bans.

Two things follow. First, salary history and salary expectations are different questions, and only the first is restricted anywhere: an employer in a ban state can still ask what you are looking for. Second, even where the ban applies, you are usually free to volunteer your history if you think it helps you — the restriction is on them asking, not on you sharing. Most of the time it does not help you, because it re-anchors the conversation to your last employer's budget rather than this one's.

The three honest answers, with wording

There are only three defensible strategies, and the right one depends on what information you already have. All three are honest; none involves a fake competing offer or a number you invented. Pick by asking one question: do I know the employer's range, and do I understand the scope of this job?

1. Give a researched range

Use this when there is no published range and you have done the research. Name a band roughly 15–20% wide, anchored so that the bottom is a number you would genuinely accept for the role as described. Then tie it to something — market data, scope, or the level you are being hired at — and stop talking.

"Based on what I'm seeing for similar roles in this market, I'm targeting $110,000 to $130,000 on base, and where I land in that range depends a lot on the scope — particularly whether this role owns the reporting line or supports it. Does that sit inside your band?"

When it backfires: when your bottom number is aspirational rather than acceptable. Assume the employer hears the bottom of your range as your price, because in practice many of them do. If you would decline $110,000, do not say $110,000. It also backfires when the range is too wide — a $90,000 to $150,000 answer tells the recruiter you have not researched the role, and invites them to treat $90,000 as your number.

2. Redirect to the posted or budgeted range

Use this when the employer has published a range, or is required to provide one on request. This is the lowest-risk answer available and it is increasingly the default, because the information genuinely is public. You are not dodging; you are pointing at the document.

"I saw the range on the posting — $115,000 to $140,000 — and that works for me. I'd want to understand the scope better before I say where in it I'd expect to land. Is that range still current for this req?"

If no range was posted and you are in a state that requires one on request, asking for it is an ordinary, unremarkable thing to do: "Before I give you a number, could you share the range budgeted for the role?" Most recruiters answer without friction, and the ones who bristle have told you something useful about the employer.

When it backfires: when you use it as a stonewall. Agreeing to the posted range without qualification effectively concedes the midpoint, so pair the redirect with a scope question rather than a flat "that works." And if you run the redirect when no range exists and no law compels one, you can look evasive — in that case, fall back to strategy one.

3. Defer until you know the scope

Use this when the role is genuinely ambiguous, when the title spans several levels, or when the conversation is a first exploratory call and the job has not been defined. Deferral is legitimate — but you can only spend it once, and you must offer something in return.

"Honestly, I don't want to give you a number that's wrong in either direction before I understand the scope — the title covers quite different jobs at different companies. Can you tell me what the band is for this level, and I'll tell you straight away whether I'm in it?"

When it backfires: when it is your answer twice. A second deferral reads as either evasion or inexperience, and some applicant tracking workflows require a number before the recruiter can advance you at all. Deferral is also weak at the late stage — by the second or third conversation, refusing to discuss compensation starts to look like a candidate who will be difficult about the offer.

When the form demands a number

The hardest version of this question is not conversational at all. It is a required numeric field on an application form, with no context, no range, and no human to ask. You cannot deflect a form. What you can do is control what you type and understand how it will be read later.

1. 1Try the non-numeric escapes first. Some forms accept text: "Negotiable", "Open", or "Market rate". If the field takes letters, this is the cleanest answer available.
2. 2If it demands digits, enter the midpoint of your researched range, not your floor and not your dream number. A midpoint is the figure you can most easily defend in a later conversation.
3. 3Never enter 0 or 1. Some systems sort or filter on this field, and a placeholder can drop you into an unexpected bucket — or make you look careless.
4. 4Use round numbers on forms, precise ones in conversation. Forms are filters; conversation is where a specific figure signals research.
5. 5Write down what you entered. If the offer arrives three months later and someone quotes your form answer back to you, you want to remember the number and the date you gave it.

If the form also asks for current or prior salary, check whether you are applying in a jurisdiction with a salary history restriction. In many covered states the field should not be there at all for private employers, and a required prior-pay field from a covered employer is a reasonable thing to raise with the recruiter — politely, and with the assumption that it is a stale form rather than bad faith.

Base salary or total compensation? Say which one you mean

A surprising share of failed salary conversations are unit mismatches. You quote total compensation; the recruiter hears base. Or you quote base; they assume it includes the bonus and build an offer that lands well under what you meant. The fix costs four words: specify the unit every single time you say a number.

In roles with meaningful variable pay, anchor on base and treat everything else as a separate conversation. Base is the number that compounds — it drives future raises, bonus percentages and the band you are hired into. Bonus is conditional, equity is contingent and often illiquid, and benefits vary enormously in cash-equivalent value.

• Base. The guaranteed annual figure. Quote this by default and say the word "base" out loud.
• Target bonus. Ask what percentage is on target and, more usefully, what it actually paid out for the last two cycles.
• Equity. Ask for the grant value, the vesting schedule and whether the value is set at grant or at some later valuation. In private companies this number is a projection, not money.
• Everything else. Employer retirement contributions, healthcare premium share, and paid leave can be worth several thousand dollars a year and are frequently invisible until you compare two offers side by side.

When you present a range, say which unit it refers to, and if you are willing to trade, say that too: "I'm targeting $130,000 base; if the bonus structure is strong I have some flexibility on that figure." That sentence gives the recruiter something to work with and costs you nothing.

The same question, answered differently at each stage

Your answer should change as your leverage changes, and your leverage changes once someone decides they want you specifically. Treat the compensation conversation as a thread that runs through the whole process rather than a single moment you either win or lose.

The screening call

Low leverage, high screen-out risk. This is where the redirect and the researched range work best, and where a hard refusal costs you most. Our guide to phone interview tips covers the rest of that call — it is a qualification conversation, and compensation is one of four or five boxes the recruiter has to tick before you advance.

The first interview with the hiring manager

Compensation usually does not belong here, and if it comes up, a short version of your screening-call answer is enough. Spend the time establishing scope instead, because scope is what justifies your number later. The way you frame your background in the first ninety seconds of an interview does more for your eventual offer than any number you name, and structured examples — the approach in our STAR method story bank guide — are what make a senior-level band feel obvious rather than argued.

The second interview and beyond

Now you have information and some leverage. If your understanding of the role has grown — more direct reports, a bigger territory, an unstaffed function you would be inheriting — this is the moment to revise upward, explicitly and with the reason attached. What changes in round two is largely scope and stakeholder alignment, which is exactly the raw material for a revised range. The questions you ask at the end of an interview are also where you can surface budget, level and band without ever making it feel like a negotiation.

After the offer

This is a different game with different rules, and it is mostly conducted in writing. Once a number is on the table the conversation moves from "am I in your band" to "what will you move, and against what evidence" — our salary negotiation email guide covers the templates and mechanics for that stage. Keep the two moments separate in your head: the expectations question is a filter, the post-offer negotiation is a trade.

After you give the number

Most of the damage in salary conversations happens in the ten seconds after the figure, not in the figure itself. Candidates name a range and then keep talking — softening it, apologising for it, or adding a qualifier that quietly lowers it. The recruiter hears the qualifier, not the number.

• Stop talking. Say the range, ask your scope question, and let the silence sit. It is four seconds and it feels like forty.
• Do not pre-negotiate against yourself. "...but I'm flexible, and honestly the role matters more than the money" hands back everything you just established.
• Write down what you said and when. You will be asked to repeat it weeks later, and inconsistency is expensive.
• Confirm in writing if the number shifts. A one-line email after a call — "just to confirm, the band we discussed was X" — prevents the most common late-stage misunderstanding.
• Keep the process moving. A clean, prompt follow-up does more for your position than another paragraph about compensation; our post-interview follow-up sequence has the wording.

One last reframe. If your researched number puts you outside the employer's band, that is not a failed answer — it is a correctly functioning filter that saved you four interviews and a disappointing offer. The purpose of answering well is not to get every job. It is to make sure the jobs you spend your time on are the ones that can actually pay for the work.