How do you answer "What are your salary expectations?"

Turn it back first. Politely ask what the role is budgeted for: "Do you have a range in mind for this position?" If they give you one, position yourself inside it. If they push and you have to name something, give a researched range, not a single number, and set the bottom of that range at the number you actually want. They tend to hear the low end. Tie it to the job, not your rent: "based on the scope of the role, I'd expect somewhere between X and Y." One clean deflection, then a range if pressed.

Most interview questions test whether you can do the job. This one tests whether they can afford you, and it quietly decides how much they'll pay you if they can. That's why it lands harder than it looks. A recruiter drops it early, almost offhand, usually in the first ten minutes of a phone screen, and a lot of good candidates blurt a number they picked in the shower and lock themselves into it for the rest of the process.

Here's the part nobody tells you on the way in. The number you say here doesn't just answer a question. It becomes the ceiling. From the hiring side, that first figure you name is the anchor every later conversation gets dragged toward, and they will not float higher than it on their own. So the goal isn't to have a clever line ready. It's to say as little as you can get away with, learn what they've got budgeted, and only commit to a number when you've made them want you and you know what the role is actually worth.

This is the tactical version. Word-for-word scripts for the recruiter screen, for the pushback, for the moment you genuinely have to give a number. If you want the wider set of curveballs the interview throws, we covered those in the interview trap-questions playbook where salary is one of twelve. This post is the full script for that one. For the broader set of money questions across the whole process, there's also our guide on answering salary-related questions in an interview.

Why they really ask (it's two questions wearing one coat)

Recruiters aren't asking to be nosy. The question is doing two jobs at once, and understanding both is what stops you from fumbling it.

The first job is a filter. Somebody set a budget for this seat, and the recruiter's whole afternoon is spent making sure they don't advance candidates who'll want more than that budget holds. If your number lands way over what they've got, the interview ends there, politely, and you never hear the reason. So the question is partly a knockout: are you in range or aren't you.

The second job is quieter and costs you more. Whatever you say becomes the anchor for the offer that might come weeks later. Say 70 and the offer arrives at 70 or a hair under, even if the budget went to 85. The offer rarely climbs above the first number the candidate volunteered, because from where the company sits, why would it. You told them what you'd take. They wrote it down.

Recruiters lean on this question hard because in that early moment it's about the only real card they hold. They don't yet know if you're their top pick, and you don't yet know if you want the job, but they can find out your number before you've found out theirs. That asymmetry is worth real money to their side. There's nothing shady about it. It's the game, and the people running it do this all day while you do it every few years.

The core move: turn it around before you answer

The single highest-value habit you can build is to answer the salary question with a question. Politely, warmly, no attitude, you ask what they've budgeted for the role before you offer up anything of your own.

It works because whoever names a real number first has handed over information the other side wanted, and in a negotiation the side with more of the other's information usually comes out ahead. A recruiter who tells you the range first has just shown you their ceiling. Now you can aim for the top of it. A candidate who names a figure first has shown the recruiter their floor, and the offer gets built up from there, not down from the budget.

The wording matters less than the calm. Any of these does the work:

Notice what those lines have in common. They're friendly and they never actually refuse to answer. They frame the range as a shared efficiency thing, which it genuinely is, and then they stop talking. That last part is where people lose it. You ask the question and then you sit in the silence and let them answer. Recruiters are trained to leave a gap right there so you fill it with "but if that's a stretch I could probably do a bit less." Don't. Let the quiet be their problem. The person who talks first in that pause is usually the one who gives ground.

What if they won't share their range?

Sometimes you'll deflect and get a wall back. "It depends on the candidate." "We don't disclose that." "It's flexible."

Two things are true here. One, in a growing number of places they may be legally required to give you a range if you ask, which we get to below. Two, an employer who flatly refuses to say what a job pays, at any point, is telling you something. Not always something disqualifying, but something. The roles that hide comp the hardest are often the ones betting you'll sink weeks into their process and then feel too invested to walk when the offer disappoints.

So don't dig a trench over it. Ask once. If they still won't budge and you have to keep the conversation alive, give a researched range rather than a bare number, and make that range work for you. That's the next section, and it's the part worth getting exactly right.

When you have to give a number, give a range (and rig the bottom)

Plenty of times the deflect-once approach hits a hard "we really do need a figure to move you forward." Fine. You give one. But you give a range, not a point, and you build that range on purpose.

Here's the rule that changes everything: they hear the bottom of your range. Say "80 to 95" and the number that sticks in the recruiter's notes is 80. So the bottom of whatever range you name has to be the number you'd actually be happy to sign for. Not your wildest dream, and definitely not your walk-away floor, but your genuine target, sitting at the low end, so that even the least generous reading of your answer still lands you where you want to be.

Work backward from that:

• Bottom of range = your real target. The figure you'd take and feel good about. This is where they'll aim.
• Top of range = target plus roughly 10 to 15 percent. Enough headroom to leave negotiating space, not so much you look unanchored.
• Keep the band tight. A range wider than about $20,000 to $25,000 reads like you don't know what you're worth. "90 to 150" isn't a range, it's a shrug.

Before any of this you need actual numbers, not a feeling. Pull comps for your exact role, level, and location from Levels.fyi, Glassdoor, LinkedIn Salary, Payscale, or wherever your field congregates, and if a range was posted with the job, that is the employer's own stated band, so use it. If you want a deeper walkthrough of building and defending those numbers, our salary negotiation guide covers the research side in more detail. Then say it plainly:

The phrase "based on the scope of the role" is doing quiet heavy lifting. It anchors your number to the value of the work, not to what you happen to need to cover rent, and it gives you a clean way to push the figure up later if the role turns out to be bigger than the posting let on. Which senior roles almost always do.

Never anchor on your current or past pay

Somewhere in the screen you may get the cousin of the salary question: "What are you making now?" or "What was your last salary?"

Treat your current pay as none of their business, because for the purposes of this offer it isn't. Your old salary is a fact about your last job, not a measure of what this one is worth, and letting it into the conversation drags your new number toward your old one. If you were underpaid before, answering honestly locks that underpayment in for another few years. This is exactly how pay gaps follow people from job to job.

Redirect to the role, every time:

And here's the kicker most people don't know: in a lot of the country, they can't even ask. More on the law in a moment, but the short version is that asking a candidate's salary history is now off-limits in a good chunk of states, and even recruiters who can technically ask often consider it clumsy. You're on solid ground declining to answer.

Handling the pushback without folding

You'll meet resistance. Here's how the common shoves go and how to stay standing.

"We really need a number to move forward." After one deflection, this is your cue to give the researched range. Don't turn it into a standoff, especially with a recruiter who's just trying to fill a field in their tracking system. Deflect once, then range. That's the rhythm.

"What are you currently making?" Covered above. Redirect to the role and your target range. If they press, "I keep my current compensation private, but I'm happy to tell you what I'm looking for here."

The posted-range squeeze. This one's sneaky. You aim near the top of a range the company itself posted, and they tell you that if you came in there you'd be "maxed out" and "not eligible for a raise," so you should really come in lower. That's a negotiation move dressed as helpfulness. A posted range is the employer's own declaration of what the job can pay. If the top of it genuinely maxes out the band, that's a compensation-structure problem on their end, not a reason for you to volunteer less. You can say, "I understand there's a structure, and based on the responsibilities we've discussed, the top of the posted range is where I'd expect to land. I'm open to talking through how growth works from there."

"Won't asking for more get my offer pulled?" Almost never, if you're reasonable and polite. Offers get rescinded over aggressive over-reach, going higher than a number you'd already committed to, or plain rudeness, not over one calm question about range. If a company yanks an offer because you politely asked what the role pays, it just did you the favor of showing you how it treats people before you signed. That's a different stage than this one, though. Once an actual offer is on the table, the playbook shifts to a written counter, which we walk through in how to counter a lowball offer. The number you protect here is the anchor that offer gets built on, so getting this stage right is what saves you from a painful counter later.

The recruiter screen version: be quick, give a range

The first time this question shows up is usually a recruiter phone screen, and increasingly it's an automated AI screening call where salary is literally a knockout field the bot has to check before a human ever sees you. In that context, over-cleverness backfires. A twenty-minute screen isn't the moment to fence over anchoring. The recruiter has fifteen candidates to clear and one job to do: confirm you're roughly affordable.

So keep it efficient. Try one deflection to get their range. If they give it, great, position yourself and move on. If they need your number to advance you, hand over the researched range without drama and let the process continue. You haven't shown your value yet at this stage, which means you're not in a strong position to hold the line hard, and getting screened out over a salary standoff before anyone's even met you is the worst possible trade. The recruiter screen is where the whole hiring process quietly narrows, and salary is the tripwire that ends it early. Clear the tripwire, keep moving.

One reframe that takes the stress out of it: good recruiters actually want your number early. If you're above their band, they'd rather know now than after four rounds, and plenty will keep you in mind for a better-fitting role later. Naming a well-researched range to an honest recruiter isn't weakness. It's a filter that protects your time as much as theirs. The adversarial energy only kicks in with the ones who hide their range while demanding yours.

The higher-stakes moment later on

Different rules apply once you're deep in the process, talking to a hiring manager who's clearly interested, or circling the pre-offer conversation. Now you have leverage, because they've spent time on you and started to picture you in the seat. This is where holding your anchor pays off most, because whatever you agree to here is what the written offer will echo.

Here you can afford to deflect more firmly and tie everything to scope, and once numbers are properly on the table it's worth reading up on how to negotiate a good offer during the interview. "Now that I understand what the role actually involves, and it's broader than the posting suggested, I'd put my expectation at the upper end of what we discussed." If they name a figure, don't pounce on it, and don't fold either. A little silence, a "let me think about the full package," and a considered response beat an instant yes. The instant yes tells them they could've gone lower.

The mistake is treating the early screen and the late-stage conversation the same way. Early, you're clearing a filter, so be fast and reasonable. Late, you're setting the anchor for real money, so be deliberate and a touch slower. Same question, two completely different stakes.

The pay-transparency era changes your leverage

The whole dance is shifting under everyone's feet, and mostly in your favor. Two legal trends worth knowing, framed as general information rather than legal advice, since the details vary by state and keep moving.

Salary-history bans. As of 2026, more than a dozen states plus Washington, D.C., prohibit employers from asking about your current or past pay, with some tallies running higher depending on how state and local rules are counted. Virginia's version takes effect July 1, 2026. Where these apply, "what are you making now?" isn't just awkward for them to ask, it's off-limits. You don't have to cite the statute in the room. Just know that declining to share your salary history is normal and often legally backed.

Employer-must-disclose rules. A handful of states go further and require employers to show you the pay range. California's SB 1162, in effect since January 1, 2023, requires employers with fifteen or more staff to post the pay scale in the job listing, and it goes further: an employer has to hand an applicant the pay scale for a role on reasonable request. So in California, and a growing list of other jurisdictions, your deflection has teeth: you can ask for the range and they're supposed to give it. Enforcement isn't perfect, and a determined company can still stall, but the balance has tilted toward candidates in a way it never used to be.

The practical upshot: check the posting. If a range is published, you don't have to guess or go first at all. You can anchor to their own stated band, aim for the upper-middle if your experience backs it, and skip the awkward opening volley entirely.

How to use a posted range when you have one

More postings carry ranges now than they did even two years ago. When one does, your job gets easier, but there's still a right way to read it.

A posted range is not a menu where you politely pick the middle. It's the employer signaling what the seat can hold. If you're a clean fit or slightly senior for the role, aim for the top third, not the middle, and justify it with scope. "The posting lists 90 to 110. Given the depth of what we've discussed, I'd be targeting the upper part of that, around 105 to 110." You're not being greedy. You're reading their own numbers back to them with a reason attached.

Watch for the range that's suspiciously wide. When a listing says "$70,000 to $180,000," that's a company hedging, and often the real budget lives near the bottom. In that case your deflection still matters: "I see the posted range is broad. What's actually budgeted for this specific level?" narrows it fast, and pushes the burden of the first real number back onto them.

The mindset that makes the scripts land

You can memorize every line above and still give it all away with your tone. The scripts only work if you deliver them like they're obvious, because to you they should be.

Two habits carry the most weight. First, stop negotiating against yourself before the conversation even starts. Candidates talk themselves down in their own heads, deciding a number is "probably too much" and quietly shaving it off before anyone's pushed back. You don't know the budget. Let them tell you your number's too high, if it even is. Don't do their job for them. Second, get comfortable with silence, because it's the most underrated tool in the room. After you ask for their range, or after you state yours, close your mouth. The pause will feel like an hour. It's three seconds, and the person who breaks it first tends to be the one who blinks.

None of this is about being combative. The warmest, most collaborative version of these lines beats the hard-nosed one every time, because you're not fighting the recruiter. You're just declining to hand over your leverage for free. Say it kindly, say it once, and let the number sit there and do the work.

Frequently Asked Questions

• What's the best one-line answer to "What are your salary expectations?"

  "Do you have a range in mind for this role? I want to make sure we're in the same ballpark before we go further." It's warm, it doesn't refuse, and it quietly hands them the job of naming the first number. Only if they insist you go first do you pivot to a researched range with your target sitting at the bottom.

• Should I give a number or a range?

  Range. A single number hands them a bullseye and zero room to read you generously. Build the range so its bottom is the figure you'd genuinely sign for, since that low end is what lands in their notes, and keep the whole band inside roughly $20,000 to $25,000 so you don't look like you're guessing.

• Is it true the first person to say a number loses?

  Loses ground, usually. Whatever figure you name first becomes the anchor the offer gets built around, and companies rarely climb above the number a candidate volunteered on their own. It isn't a law of physics, and plenty of people who go first still land fine. But the mechanics quietly favor the side that stays quiet longer, which is exactly why deflecting to their range first is the safer opening.

• What if the recruiter refuses to share their budget?

  Ask once. If they still won't say, give your researched range rather than stonewalling and losing the screen over it. A flat refusal to tell you what a job pays is a small yellow flag about how the place operates, and in states like California they may actually be required to disclose the scale if you ask. Either way: deflect once, range if pressed, keep moving.

• Can employers legally ask what I currently make, and do I have to answer?

  In much of the country they can't ask at all. As of 2026, more than a dozen states plus Washington, D.C., ban salary-history questions, with Virginia's taking effect July 1, 2026, and the list keeps growing (general information, not legal advice, and it varies by state). Even where it's legal, you don't have to answer. Redirect: "I'd rather focus on what this position is worth. For this role I'm targeting [range]." Anchoring a new offer to an underpaid past just extends the underpayment.

• The salary range was posted with the job. What do I say?

  You're in luck, because now you never have to go first at all. Aim for the top third if your experience backs it, and pin the number to scope: "Given what we've discussed, I'd target the upper end, around [top of range]." Watch out for the suspiciously wide posting, though. If a listing spans something like $70k to $180k, ask what's actually budgeted for your specific level, and you'll narrow it fast.

• Will asking about salary early make me look greedy?

  Not to a good recruiter, no. The honest ones would much rather learn your number in the first ten minutes than after four rounds of everyone's time, and a lot of them will file you away for a better-fitting role if you happen to be above the current band. Say it warmly, frame it as getting on the same page before you both invest, and it reads as professional every time.

• How do I handle the salary question differently in a recruiter screen versus a final interview?

  Speed early, deliberation late. In the screen you're clearing a budget filter with no leverage yet, so try one deflection and then hand over your range if they need it. By the time a hiring manager clearly wants you, the calculus flips: hold your anchor, slow down, and tie every number to the scope of the work. It's the same words carrying very different stakes.

• What if they tell me I'd be "maxed out" at the number I asked for?

  Recognize it for what it is, which is a negotiation move dressed up as a warning. The company posted or stated that range itself, so it just declared what the seat can pay. If the top of it happens to cap out their internal band, that's a structure problem on their end, not a signal for you to shave your number. Stay pleasant, hold the figure, and ask how raises work from there.

• The offer came in below the range I gave. Now what?

  You're past the expectations question and into the counter, which is a different move with its own script. Ask once, warmly, with a number you can defend, and don't panic-accept. Walk through it with our guide on countering a lowball offer, and once you're weighing the whole thing, our job offer evaluation breakdown helps you judge the full package rather than base salary alone.