Of every awkward question in the loop, this one costs the most money when you fumble it. A blurted number on a recruiter screen can quietly cap your offer ten weeks before you ever see the comp sheet. And the rules changed: by 2026, sixteen states plus DC require salary ranges on job posts, which means recruiters are now sitting on a published band while still asking you to anchor first. This guide walks through why interviewers ask, the three-part answer that works in transparency and non-transparency states alike, fifteen real-world sample answers, and the phrases that quietly torch leverage.
Why interviewers ask this
Two things are happening at once when a recruiter asks for your salary expectations on the first call. First, it’s a budget calibration. The role has an internal band — usually a published one in CA, CO, NY, WA, IL, MD, MA, NJ, MN, and DC — and they want to confirm you fit inside it before spending forty hours on loops. If you’re 30% over, they save everyone time. If you’re 30% under, they save the company money. Either way, the question filters.
Second, it’s an alignment signal. They’re testing whether you’ve done research, whether you negotiate professionally, and whether you’ll be a difficult close at offer time. Recruiters get bonused on filling reqs, not on minimizing comp, but they answer to hiring managers who notice when someone joins $20K over band.
The trap is anchoring. Patrick McKenzie’s classic essay points out that whoever names a number first sets the gravitational center of the negotiation — and McKenzie estimates his own writing on the topic has produced over $2.3M in added salary for readers who learned to not name it first. If you say “I was thinking 110,” the offer comes in at 112 and they call it generous. If you make them name it, the offer comes in at 135 because that’s actually the middle of the band you didn’t know existed.
The Three-Part framework
Use this any time someone asks for a number — recruiter screen, manager round, final loop, written form, whatever.
Part 1 — Reframe to a range. Never offer a single point. A point is a ceiling; a range is a floor. Say “I’m targeting a range” and immediately move to part two.
Part 2 — Anchor with market data. Cite a credible source. Levels.fyi for tech, BLS or Glassdoor for non-tech, the posted band itself if the state requires one. The phrase that works: “Based on [source] for this role and level in [location/market], comparable positions are landing in the [X to Y] range.” X and Y should be the 60th and 90th percentile, not the median — you’re describing where strong candidates land, not the average hire.
Part 3 — Bridge to total comp. End by widening the conversation. Salary is one lever; equity, bonus, sign-on, PTO, remote flexibility, and review timing are others. Try: “But I’d rather understand the full structure — base, equity, bonus target, sign-on — before locking in a number. What does the band look like on your end?”
That last sentence is the whole game. You’ve shown you’ve done homework, given a defensible range, and turned the question back to them. Now they anchor.
15 sample answers
Each of these works because it reframes, cites, and redirects. Steal the structure, swap in your numbers.
1. Software engineer, mid-level, recruiter screen (non-transparency state):
“I’m targeting a range based on Levels.fyi data for senior engineers in this market — roughly $165K to $195K base, with total comp depending on equity. But I’d want to understand your full package before pinning a specific number. What range did you have budgeted?”
2. Software engineer, California (transparency state, band posted):
“I saw the posted band is $180K to $230K. I’m looking at the upper half given my five years of distributed-systems work, so realistically $210K to $230K base, plus whatever the equity refresh looks like. Does that align with what you’re seeing for this level?”
3. Product manager, final-round, asked again:
“I gave the recruiter a range of $175K to $210K based on Glassdoor and friends at similar-stage Series C companies. After meeting the team, I’m more confident this is the right fit, so I’d land in the upper half of that — but I want to see the offer holistically before committing to a target.”
4. Designer, asked by hiring manager mid-loop:
“I’d rather not lock in a number before I see the full offer structure, since equity and bonus mix vary a lot. Based on market data for senior product designers, I’ve been looking at $150K to $180K base. Is that in your range?”
5. Marketing director, agency switch:
“Comparable director roles in this market are running $170K to $210K base with a 15-20% bonus target. I’m looking to stay competitive within that range, but I’d weigh the full package — including equity and PTO — before naming a specific figure.”
6. Asked to disclose current salary (illegal in many states):
“I’d rather focus on the value I’d bring to this role and what comparable positions are paying today. Based on market research, I’m targeting $X to $Y. Can you share the budgeted range for the role?”
7. New York, board-level role:
“The posted range is $250K to $320K. Given my track record scaling teams from 20 to 200, I’m looking at the top third — $290K to $320K — plus a meaningful equity grant. Happy to walk through specifics once we’re aligned on fit.”
8. Career switcher (out-of-industry):
“I know I’m coming from a different track, so I’ve calibrated against entry-mid analyst comp in this market — $95K to $115K. That said, my prior experience compresses the ramp, so I’d want to revisit the band at first review. What’s your structure for that?”
9. Remote-first company, location ambiguous:
“Since this is remote, I’d assume you have a national or zone-based band. I’ve been targeting $140K to $170K based on Levels.fyi for senior remote roles. Where does your band land for my zone?”
10. Contract-to-hire, asked about hourly:
“For contract, I’m looking at $90 to $110 per hour depending on scope. For the conversion to full-time, I’d benchmark against equivalent FTE base — roughly $175K to $200K. Which structure are you optimizing for?”
11. Asked in a written application form:
“Open to discussion based on full compensation structure. Targeting $X to $Y base based on market data, flexible on the mix.” (If the form requires a single number, enter the top of your range, not the middle. Single numbers anchor down, not up.)
12. Senior engineer who already has a competing offer:
“I have an active offer at $220K base plus equity, so I’m anchored around that. To make a move worth it, I’d be looking at $235K to $250K base. Does that fit your band?”
13. Asked early on Zoom by a junior recruiter who insists on a number:
“I genuinely don’t have one specific number — I’m targeting $130K to $155K based on the market. If you need a single figure for your tracker, put $145K, but I’d want the conversation to stay open as we get into specifics.”
14. Internal transfer or boomerang:
“I’d want to benchmark against the external market for this level, not my prior internal band. Based on what I’m seeing externally, $X to $Y feels right. Can you share where the team’s current comp lands for that role?”
15. After the offer drops below your range:
“Thanks for the offer. Based on the market research I’ve done and the scope we discussed, I was targeting $X to $Y base — your number is $Z. Is there flexibility on base, or should we look at sign-on or equity to close the gap?”
What NOT to say
These are the phrases that quietly cost candidates five figures every year. Practice the answers above out loud so none of these slip out under pressure.
- “Whatever you think is fair.” Translates to: I have no leverage and I’ll accept anything. Recruiters don’t reward this.
- “My current salary is $X.” In states with salary-history bans (CA, NY, CO, WA, IL, MA, NJ, and a dozen more), they can’t even ask — and offering it unprompted anchors you to your old market value, not your new one.
- “I’d want $150K.” A single number is a ceiling. They’ll match it or shave it; they won’t exceed it.
- “I’m looking for something competitive.” This is filler. It signals you haven’t done research. Recruiters mentally downgrade you when they hear it.
- “I’d take less for the right opportunity.” Now you’ve told them the right opportunity is worth a discount. Don’t volunteer concessions before you’ve seen the offer.
- “Whatever the band is.” Same problem — you’ve given up your half of the negotiation before it started.
- “$200K is my hard minimum.” Hard floors backfire if the band is $190K to $215K. Always frame as a range, never as a floor.
Closing move and practice routine
The single most expensive moment in any negotiation is the four seconds after someone asks for a number. Most candidates fill that silence with the first figure that comes to mind. The fix is mechanical: rehearse your three-part answer until it comes out without thinking.
Sit down this week with a timer. Write your range based on Levels.fyi, the posted band (if any), and the 75th-percentile Glassdoor data for your role and metro. Then record yourself saying the answer out loud, three times, until it sounds conversational instead of memorized. Do this for the recruiter-screen version, the final-round version, and the “what’s your current salary” deflection. That’s fifteen minutes of work that routinely returns $10K to $30K on an offer.
Then track every interview where the question came up — what you said, what they offered, what the gap was. After three or four loops, patterns emerge: maybe you anchor too low in tech, maybe you fold under pressure on final rounds. OfferFlow’s job tracker captures interview rounds, salary asks, and offer outcomes side by side so you can see your own negotiation history and stop repeating the same $15K mistake. The candidates who get paid aren’t the ones with the best resumes — they’re the ones who said the same well-rehearsed sentence on the recruiter call when everyone else was guessing.
Sources: