How to Answer 'What Are Your Salary Expectations?' Without Losing Money

Why the question is asked at all

Recruiters ask salary expectations to solve three problems at once: filter out candidates who are outside their band, avoid wasting a hiring manager's time, and — quietly — get you to anchor first so they have a ceiling to negotiate against. Most recruiters have a defined salary band for the role before the first screen and know within $10–15k where an offer will land. When you name a number below that band, they don't correct you; they mark it in their notes and it becomes the base rate for the offer conversation. When you name a number above the band, they either counter with the band or, if it's close, keep talking. The strategic answer, therefore, is almost never a number — it's a range paired with a condition.

Do your research before you ever answer

Never enter a salary conversation without three pieces of data: the market range for the role in your city or remote market, the company's specific band if you can find it, and your own floor (the number below which you would walk away). Use Levels.fyi for tech, Payscale and Glassdoor for a broader view, Blind for candid comp data, and the Bureau of Labor Statistics for regulated roles. For public companies, check H-1B disclosures on H1BData.info — they publish actual salaries paid. Talk to two or three people currently doing the job at similar companies. Do all of this before the first recruiter screen, not after.

What to say in the recruiter screen (script 1: deflect politely)

'I want to be respectful of your time and I'm still learning about the scope of the role, so it would be premature for me to give you a hard number. What's the range budgeted for this position?' This puts the ball back in the recruiter's court, which is where it belongs. About 40% of recruiters will just tell you the range. If yours does, thank them, then say 'That sounds reasonable — let's keep talking' and move on. You've given up nothing and you now know the ceiling.

What to say if the recruiter pushes back (script 2: broad range with a floor)

If the recruiter insists — 'I do need a rough number to move forward' — give a broad range anchored to your research: 'Based on the roles I'm considering, I'm targeting somewhere in the $145k–$175k range for total comp, though I'm open depending on the full package.' Two rules for this range: the bottom of your range should be at or above the middle of the market band, and the top should be about 20% above the bottom. Never give a single number and never say 'negotiable' without a floor.

What to say when the recruiter names a range first

If the recruiter opens with a range, don't accept the midpoint — that's what they expect. Instead, tie your response to the top of their range: 'The top of that range feels aligned with what I'm targeting, especially given the scope of what we've discussed around the platform team.' You've now anchored to the top without a fight, and you've named a specific piece of scope that justifies it. In offer negotiations, that scope reference matters.

Handling the 'current salary' question

Some states and cities (California, New York, Colorado, Washington, and others) prohibit employers from asking your current or prior salary. If you're asked anyway, or if you're outside those jurisdictions, don't answer it — respond with your target range instead. 'I'd rather focus on what the market is paying for the scope of this role and what I'm targeting next, which is $145k–$175k.' If the recruiter presses, you can say 'My prior comp isn't the best proxy for this role because [it was a smaller company / different scope / longer ago / different market].' You don't owe them the number.

How the conversation shifts at the hiring manager stage

By the hiring manager round, the question changes: they're not filtering, they're calibrating. If salary comes up here, you can go slightly more specific — the same range, but with a preferred number attached to a specific level of scope. 'For an IC role at this level, $160k is where I'd expect to land; if the scope grows to include the roadmap ownership we discussed, $175k feels right.' You're now selling into scope, which is a much better negotiation than selling into your salary history.

What to do when the offer arrives

The single highest-leverage negotiation move is the pause. When the recruiter reads the offer, take a breath, thank them, and say some version of: 'Thank you for the offer. I need to look at the full package and I'll come back to you within 48 hours.' Then actually take the 48 hours. In that time, look at every lever: base, sign-on, equity, bonus target, PTO, remote flexibility, start date, title. Come back with a specific counter that names two or three levers, not just base. 'I'd like to accept if we can move base to $175k, sign-on to $20k, and start date to March 3.' Most recruiters can move at least one of the levers you name.

What levers actually move at each level

• Base salary: usually 3–7% movement, more in a hot market.
• Sign-on bonus: often the easiest lever — recruiters have discretion here.
• Equity (RSUs or options): 10–25% movement is common at senior levels.
• Bonus target: rarely moves, but the target percentage sometimes does.
• PTO: hard to move at most companies; unlimited PTO is not always better.
• Start date: freely negotiable — use it to negotiate for a sign-on.
• Remote flexibility: increasingly hard to move in 2026; ask early, not at offer stage.
• Title: sometimes movable, especially at smaller companies.

Word-for-word: how to counter a lowball offer

'Thanks for the offer — I really enjoyed the conversations and I want to work with this team. Based on the scope we've discussed and where the market is for this role, I'd like to see base at $175k, with a $20k sign-on. Everything else in the package looks great. Can we make that work?' This script is short, specific, doesn't apologize, doesn't threaten to walk, and names exact numbers. Recruiters respond to it because it's easy to bring back to the hiring manager.

What to say if they say no

If the recruiter comes back and says the numbers aren't possible, don't collapse. Ask which lever is possible: 'Understood on base — how much can we move on the sign-on side?' You may end up with a slightly higher base and no sign-on, or the reverse. Either way, you've cleared out the ambiguity and moved the total comp up. If they can't move anything, that's real information; decide whether the offer at that number is still worth taking.

Common mistakes that cost tens of thousands

• Answering the salary question in the first five minutes of the recruiter screen.
• Giving a single number instead of a range.
• Anchoring at your current salary instead of the market rate.
• Accepting the first offer verbally on the phone.
• Countering only on base and ignoring sign-on and equity.
• Comparing offers by base only instead of total comp.
• Using another offer as leverage without being willing to actually take it.
• Under-negotiating because you feel grateful — the offer means they picked you, which is the moment your leverage is highest.

How this integrates with Resumeva's tools

Before the first conversation, use the Resume Builder to make sure your resume shows scope and ownership, not just tasks — the more scope your resume communicates, the higher the initial band the recruiter will offer. Run your resume through the ATS Resume Checker to make sure the recruiter can quickly see the seniority signals (people managed, budget owned, systems shipped) that justify the higher end of the range.

Why this matters

The advice in this guide is drawn from real recruiter conversations and analysis of what actually moves candidates forward. Apply it as a checklist on your next application.

Put it into practice

Don't try to apply everything at once. Pick the one or two changes that feel most relevant to your situation, ship the update, and measure the response over your next 10 applications.

Common mistakes to avoid

• Treating advice as universal — context always matters
• Over-editing until your voice disappears
• Skipping the proofread because you've read it 30 times
• Forgetting that recruiters are people, not algorithms