Salary Expectation Question in Interviews: Exact Scripts That Protect Your Leverage

Salary Expectation Question in Interviews: Exact Scripts That Protect Your Leverage

"What are your salary expectations?" is the question most job seekers handle worst — and losing it costs thousands, sometimes tens of thousands, of dollars per year. The moment you name a number without the right context, you've anchored the negotiation in the company's favor. This guide gives you exact scripts for every scenario, so you protect your leverage and maximize your offer.

Why This Question Is a Negotiation Trap

When a company asks about your salary expectations early in the process, they have a structural advantage: they already know their budget. You don't. Naming a number too low shortchanges you. Naming one too high can eliminate you before you've had a chance to prove your value.

The goal is not to refuse to answer — it's to defer the number until you have more information and the company has more investment in you.

What's Legal (And What You Should Know First)

In many US states (California, New York, Colorado, and others), employers are prohibited from asking about your current salary history. However, asking about your expectations is still legal nearly everywhere.

Know the difference: - "What are you currently making?" → You are NOT required to answer in salary-history ban states - "What are your salary expectations?" → You can deflect, but you can't refuse entirely

The 4 Best Response Strategies (With Exact Scripts)

### Strategy 1: The Redirect (Earliest Stage) Use this when asked before an offer seems imminent — typically in screening or early rounds.

"I'm still learning about the full scope of the role. I'd love to understand more about the responsibilities and what success looks like before I land on a specific number. Is there a range the company has budgeted for this position?"

This does two things: delays your number, and puts the ball back in their court.

### Strategy 2: The Range (When You Must Give a Number) When pressed for a specific number after deflecting, give a range — anchored high.

"Based on my research into market rates for this role and the scope we've discussed, I'm targeting somewhere in the $[X] to $[Y] range — with the understanding that the full package matters too."

The anchoring rule: Your low number should be what you actually want. Your high number should be 15–20% above that. Negotiations almost always land in the lower half of a range.

### Strategy 3: The Flip (Probing for Their Budget) Before giving any number, try to extract theirs.

"I want to make sure we're aligned before we go further — do you have a budget range for this position that you can share?"

Many recruiters will share it. When they do, you have the information advantage.

### Strategy 4: The Research-Backed Number (For Final Rounds) Once you're in late rounds and it's time to commit, lead with data.

"I've done some research using [Glassdoor / LinkedIn Salary / levels.fyi / industry surveys], and the market for this type of role in this location is typically in the $[X]–$[Y] range. Given my [specific experience/achievement], I'd target the upper half of that range — around $[Y]."

This positions your ask as logical, not personal — which makes it much easier to defend.

Real Example: How Amit Protected $18K in Salary

Amit was a data engineer interviewing for a role he genuinely wanted. In the first screening call, the recruiter asked, "What are you expecting salary-wise?"

Instead of naming a number, he said: *"I'm still learning about the scope of the role — can you share the range you've budgeted?"*

The recruiter shared a range of $110K–$130K. Amit had been ready to ask for $108K. He negotiated to $125K using that information. The deflection alone was worth $17,000 per year.

What If They Say "We Need a Number Before We Proceed"?

Occasionally, companies or recruiters will push hard for a number and suggest they can't move forward without one. In that case:

"I understand. To give you a number with confidence, I'd find it helpful to know the budget range so I can assess fit. If that's not possible, I can share my expectations after our next conversation when I have a clearer picture of the role's full scope."

If they continue to pressure: give a range anchored high, with the explicit caveat that it could shift based on the full compensation picture (bonus, equity, benefits).

Handling the "What Are You Currently Making?" Version

In salary-history-ban states, you are legally protected from answering. Use this:

"I understand that [State] has salary history disclosure laws, and I'd prefer to keep the conversation focused on what's right for this role rather than my previous compensation. What's the range you have in mind?"

In states without such laws, you can still deflect: *"I'd prefer to focus on what's competitive for this role and market, rather than my current package — can you share the budget range?"*

Use ReSuGrow's Salary Negotiation Coach

ReSuGrow's Salary Negotiation Coach provides personalized scripts for every stage of the compensation conversation — from early screening through final offer negotiation. It takes into account your role, industry, experience level, and location to help you anchor and defend your number confidently.

Conclusion

The salary expectation question is a negotiation, not a form to fill in. The candidate who names a number first, without information, gives away leverage they can never get back.

Deflect early. Get their range first. Anchor high when you must commit. Back your number with data.

Your first salary at a new company sets the base for years of future raises. Protect it accordingly.

---