How to Answer 'What Are Your Salary Expectations?'

Give a researched salary range, not a single number, and let the employer name their budget first when you can. A working script: "Based on my research for this role and market, I'm targeting a range of $X to $Y, though I'm flexible depending on the full package." Make the bottom of that range a number you would genuinely accept, because that is the number they will hear.

The question is a budget screen. Every role has an approved compensation band before the first interview happens, and the recruiter's job is to avoid spending four rounds on a candidate the band cannot reach. When they ask in the first call, they are checking whether your number and their number live on the same planet.

There is a second motive: anchoring. Whoever states a figure first sets the reference point for the whole negotiation, and the recruiter would rather that figure come from you. If you name a number below their band, most companies will not volunteer the difference. If you name one far above it, you can get screened out before anyone evaluates your actual work.

The asymmetry matters. The recruiter knows the band, your competition, and how urgent the hire is. You know none of that yet. Answering with a hard number in minute five means negotiating with the least information you will have at any point in the process.

Your default move is to get their range before you give yours. A growing number of US states and cities now require employers to post salary ranges, so in many cases the band is already public. When it is, read it before the call and skip the guessing entirely.

When it is not public, ask. Most recruiters will share the band if you ask directly and politely, because it saves them time too. Something like: "I want to make sure we're aligned. Could you share the range budgeted for this role?" works in the majority of screens.

One caveat from watching this play out: do not turn it into a standoff. If you deflect once and the recruiter asks again, deflecting a third time reads as evasive and can sour the call. Deflect once, ask for their range once, and if they insist, give your researched range with confidence. The goal is information advantage, not a power struggle with the person who decides whether you advance.

Deflection works best early in the process, when you genuinely do not know enough to price the job. A title tells you little. "Marketing manager" at one company means running a team and a seven-figure budget; at another it means writing the newsletter. Pricing those the same is how people underprice themselves.

Deflection scripts that work in a real screen:

Notice what these have in common. Each one gives the recruiter something to respond to instead of a flat refusal. "I'd rather not say" ends the conversation awkwardly; "what's the budgeted range?" moves it forward and often gets you the band.

When deflection has run its course, or when you are talking to a hiring manager rather than a recruiter, a researched range is the strong answer. The key word is researched. A range you invented under pressure sounds like one, and a recruiter who negotiates salaries all day can hear the difference.

Build the range before the interview, not during it:

Then deliver it plainly and stop talking. "Based on my research for senior roles like this one in this market, I'm targeting $95,000 to $105,000, and I'm open to discussing the full package." The pause after the range is part of the technique. Candidates who keep talking tend to negotiate against themselves in the silence.

"I've been operating at a senior level for the past four years, most recently owning [specific scope]. Based on the market for that scope in [city or remote], I'm targeting $X to $Y. I'm flexible on the mix between base and bonus if the total lands in that range."

The structure matters more than the words. You justify the range with scope before you state it, which makes the number sound like a market fact rather than a wish.

"As someone earlier in my career, I've researched what this role typically pays at the entry level in this market, and I'm seeing $X to $Y. Does that align with what's budgeted?"

With no track record to price, market data is your entire case, so lean on it explicitly. The closing question hands the conversation back to them, which is exactly where you want it when your negotiating position is thin.

Anchor inside the posted band, in the upper portion you can defend. "I saw the posted range of $X to $Y. Given my experience with [the two or three requirements you match best], I'd be targeting the upper part of that band."

Do not anchor at the absolute top unless you clear every requirement and then some. The top of a band is usually reserved for candidates who exceed the spec, and claiming it without the evidence invites pushback you cannot answer.

Some companies will not schedule interviews without a figure on file. Fighting that policy costs you the interview, so give your researched range and add one line of protection: "$X to $Y based on my research, with the understanding that I'd want to refine that once I know the full scope and package." That sentence keeps the door open to negotiate up later if the role turns out bigger than the posting suggested.

Online applications often force the issue with a mandatory salary field, and the field type dictates your move. If it accepts text, write "Negotiable" or your researched range. If it demands a single number, enter the midpoint of your range, not your floor. The midpoint leaves room to negotiate in both directions once a human is involved.

Skip the gimmicks. Entering $0 or $999,999 to dodge the filter can get your application auto-rejected or flagged as careless, and a number wildly above the band can screen you out before anyone reads your experience. The field is a filter; your job is to pass it with a defensible market number, then do the real negotiating with a person.

One more thing on the same screen: the resume you attach should go in as a PDF unless the employer explicitly asks for something else. PDF preserves your formatting through the applicant tracking system (ATS), the software that parses and stores your application.

Never accept or reject on the call. The right response to any offer, good or disappointing, is the same: thank them, express genuine enthusiasm for the role, and ask for the full offer in writing plus a day or two to review it. No reasonable employer refuses that, and the pause converts a pressured reaction into a considered response.

Then counter once, with reasons. A counter that works names the gap and justifies it: "I'm excited about this role. Based on the market data I shared and the scope we discussed, especially [specific responsibility], I was expecting something closer to $X. Is there flexibility to get there?" A counter without a reason is a haggle; a counter tied to scope is a business conversation.

If base salary is genuinely fixed, negotiate the rest. Signing bonuses, extra vacation days, equity, a remote arrangement, a professional development budget, and an early compensation review at six months are all routinely negotiable even when the band is not. And know your walk-away number before the call, because the worst outcomes I have seen came from people deciding their floor mid-conversation.

Here is the part most salary advice skips: the range you can credibly ask for was largely decided before the interview started, by your resume. Recruiters calibrate offers against perceived level. If your resume reads as "barely meets the bar," you negotiate from below the band no matter how polished your script is. If it reads as "already doing this job at this level," the conversation starts higher and your counter carries weight.

That perception is mostly a tailoring problem. A generic resume buries the exact evidence this posting is screening for, so the recruiter fills the gap with a conservative guess about your level. A resume tailored to the specific posting puts the matching scope, skills, and outcomes where they cannot be missed, which changes the level you are perceived at and therefore the number you can defend.

This is where checking your match before the interview pays off in dollars, not only in callbacks. In Roleframe, you duplicate your base resume for the job and get a fit report: an ATS score against that posting, the exact keywords recruiters filter on that you are missing, and a prioritized plan of what to change. You make the edits yourself, with Remi, the career copilot, suggesting rewrites you approve line by line. A resume that scores strongly against the posting is the concrete version of "they don't want to lose this candidate," and that is the entire foundation of a negotiation.

The logic runs the other way too. If your fit report shows major gaps, close them before you anchor high. Asking for the top of the band with a resume that visibly misses three core requirements gets you a polite no, or worse, a quiet exit from the process.

Salary scripts fail in delivery, not in wording. A researched range delivered with a wobble in your voice reads as "flexible downward," and recruiters respond to the wobble, not the words. The fix is rehearsal, out loud, until stating your range feels as neutral as stating your start date.

Practice the hard variants specifically: the recruiter who asks twice, the numeric application field, the offer that lands under your floor. Run them with a friend playing the recruiter, or record yourself and listen for hedging. If you are already working in Roleframe, you can ask Remi to run an interview practice round built from your actual resume and, on a tailored version, the posting you are applying to. It asks a question at a time, scores your answers, and flags the thin ones, which is a low-stakes way to hear your own hesitation before a recruiter does.

Whatever method you pick, rehearse the pause. State the range, then say nothing. The first time the silence stretches in a real call, you will be glad it is not the first time you have felt it.