Skip to main content

Guide · behavioral-prep

How to Handle the 'What Are Your Salary Expectations?' Question

Anchor on a researched range, not a single number. Quote the 75th-to-90th percentile for your role, level, and metro, frame total comp not just base, and defer the final number until after you have an offer in hand.

By Sam K., Founder, InterviewChamp.AI · Last updated

How do you answer the salary expectations question in an interview?

Answer with a researched range, not a single number, and try to defer once before you commit. Anchor on the 75th-to-90th percentile for your role, level, and metro. Frame it as total compensation (base plus equity plus signing) rather than base alone. If the recruiter accepts a deferral, push the final number until you have a written offer in hand.

That one habit, a range tied to market data instead of a number off the top of your head, is often the gap between an offer that matches your last paycheck and the offer that ends the search. The salary question is really a behavioral interview moment in disguise: they're testing your judgment, not just your math.

The defer-then-range script

Most candidates hand the recruiter a single number on the first ask. That's almost always a losing move. Use this two-step instead.

Step 1, defer (try this first). "I'm still learning about the scope here. I'd love to talk total compensation once we're sure the role's a fit. Is that okay?" Roughly half the time, recruiters will accept this and move on. The other half push back politely, and that's fine; you've signaled you take the conversation seriously.

Step 2, range framed as research. If they push: "Based on what I'm seeing for this level in this metro, total comp in the X-Y range. I'm focused on the right team and the right work, happy to go deeper on what I'm seeing if it's useful." The "research" framing matters: you're not asserting your worth, you're reporting the market.

An anchor is the first number named in a negotiation; whoever sets it pulls every later number toward it, which is exactly why you want it to be a researched range rather than a recruiter's lowball.

The Indeed Career Guide on salary negotiation consistently finds that candidates who anchor on a researched range, not their last salary or a personal target, secure measurably higher offers than those who give a single number off the cuff.

How to answer salary expectations: the 5-step method

If you want the whole thing as a checklist you can run the morning of the interview, here it is in order.

  1. Research the real range first. Triangulate three sources and write down the 75th-to-90th percentile band for your exact role, level, and metro. That band is your entire script; everything else is delivery.
  2. Try to defer once. On the first ask, deflect to "let's talk total comp once we know it's a fit." Half of recruiters accept it; the rest will push back, and you'll be ready.
  3. Anchor on total compensation, not base. Quote base plus equity plus signing as one number. A base-only figure invites the recruiter to under-count everything else.
  4. Frame the range as market data. Lead with "based on what I'm seeing for this level in this metro." You're reporting the market, not asserting your worth, which is much harder to argue down.
  5. Hold the final number until the written offer. Defer the precise commitment until the offer letter arrives, then counter on the movable levers. The expectations question is not the negotiation.

Walking in with these five beats rehearsed means you say the answer in your own voice instead of freezing and blurting a number, the single most expensive thing a new grad does in this conversation.

Research the right range

Three sources, triangulated. Never trust just one.

  1. A public salary aggregator for the company and level. Look at the median and the 75th percentile for your specific role title and your specific metro. Total compensation is base plus equity plus signing plus bonus, the number you actually care about, not base alone.
  2. A jobs board with reported ranges. Many U.S. states now require employers to post a range on the job listing under pay transparency laws, rules that force the employer to publish a salary band before you ever apply. Read it. The top of that range is your floor for the conversation.
  3. One or two real-world data points. Find someone at the company, your level, your metro. A 5-minute LinkedIn message asking "would you be willing to share what the comp band looks like?" succeeds more often than candidates expect.

Per the LinkedIn Talent Blog's negotiation research, candidates who cite specific market data in their first comp conversation receive offers 8-12% higher than those who don't, even when the cited data is publicly available.

As of 2026, the standard public sources CS new grads triangulate are Levels.fyi for company-and-level total-comp bands, Glassdoor and Indeed for metro medians, and the Bureau of Labor Statistics for the broad entry-level floor. Three named sources beat one guess. FAANG and other Big Tech employers publish tighter, more public bands than startups, so the research is easier the higher up the brand ladder you go.

Salary range vs. single number: what each one does to your offer

The most common new-grad mistake is naming one number. Here's why a range wins in the 2026 hiring cycle.

| What you say | What the recruiter hears | What it does to your offer | |---|---|---| | A single number ("$145,000") | A ceiling | Offer can only move down from there | | "Whatever's fair" | "Guess low to protect budget" | You hand control to the other side | | Your current salary | "Last-paycheck-plus-a-bit is fine" | Anchors your new offer to your old one | | A researched range, total comp | "This candidate knows the market" | Negotiation starts inside your band, not below it | | A deferral, then a range | "Serious, not desperate" | Recruiter often names a number first |

The pattern is simple: every row except the last two hands your anchor to the company. A range framed as market data keeps it with you.

What to never say

Three answers that quietly tank your leverage:

  • Your current salary. In most U.S. states the employer can't legally ask, and even where they can, sharing anchors your next offer to your last. Redirect to expectations.
  • "Whatever's fair." This is the worst answer. The recruiter now has to guess your range, and they'll guess low to protect the budget. You've moved control to the other side of the table.
  • A single specific number. "I'm looking for $145,000." Now the only direction the offer can move is down. Always a range. If I had to pick the one line that costs new grads the most money, it's this one said too early.

After you have the offer

The expectations conversation isn't the negotiation. The real negotiation happens after the offer letter arrives. Wait for it in writing. Read it twice. Identify the levers that are actually movable (often: signing bonus, equity refresh, start date) versus the ones that aren't (often: base, in companies with strict bands).

A counter-offer is your researched ask back to the company after the written offer lands: specific, evidence-backed, and tied to one or two movable levers. Then come back with that counter, not a vague "is there room to move?" Recruiters respond to data, not to vibes.

For the full mechanics of the counter itself, read how to negotiate a CS new-grad offer, and if the recruiter says base is locked, the signing-bonus negotiation guide covers the most flexible lever in a new-grad package.

Practice saying it out loud before the call

Reading a script is not the same as delivering it when a recruiter is staring at you. The expectations question lands in the first phone screen, so rehearse it in a realistic tech interview phone screen setting, not just in your head.

The reason this matters: the answer only works if it sounds like you, not like a memorized line. A live practice run, where you actually hear yourself name the range out loud, is what turns a script into something you can say under pressure. You can do that in a free practice interview and hear the answer in your own voice before it counts, or see how full live-interview support works on the pricing page.

Key terms

Anchor
The first number named in a negotiation. It pulls every later number toward it, which is why you want a researched range, not a recruiter's opening lowball, to set it.
Total compensation
Base salary plus equity plus signing bonus plus any annual bonus. The number that actually matters; quoting base alone lets the recruiter under-count the rest.
Pay transparency laws
State rules (live in much of the U.S. as of 2026) that require employers to publish a salary range on the job posting and bar them from asking your salary history.
Counter-offer
Your researched ask back to the company after the written offer arrives: specific, evidence-backed, and aimed at one or two movable levers.
Equity refresh
Additional stock granted after your initial grant, often a movable lever in a counter even when base is locked to a level band.

About the author: Sam K. is the founder of InterviewChamp.AI and writes about the modern tech interview from the inside: what changed, what works for new grads, and where the old playbook fails.

Frequently asked questions

Should I give a number when asked for my salary expectations?
Give a researched range, not a single number, and not until you've tried to defer once. The first number on the table tends to anchor the rest of the negotiation, and the candidate is almost never the right party to set that anchor.
What if the recruiter pushes for a specific number?
Reframe to total compensation and to a range. 'Based on what I've seen for this level in this metro, I'm seeing total comp in the X-Y range, and I'm focused on the right fit.' Most recruiters accept this; if yours doesn't, give the higher end of your range.
Is it bad to share my current salary?
Yes. In most U.S. states it's now illegal for the employer to ask, and even where it isn't, sharing anchors your next offer to your last one. If asked, redirect to expectations for this role at this level.
How do I research what a fair range is?
Use three sources: a public salary database for the company and level, an aggregator for the metro, and one or two real-world data points from people at your target level. Triangulate; don't trust one source.
What if I'm a new grad with no negotiation experience?
You still have a range; the entry-level band for your role and metro is public. Anchor on that band's 75th-to-90th percentile, frame it as research-based, and accept that the recruiter will counter. The worst outcome of asking for more is matching the offer they would've made.
What is a good salary expectations answer for an entry-level CS role in 2026?
A strong 2026 entry-level answer sounds like: 'For new-grad software roles at this level in this metro, public data puts total comp in roughly the X-Y range, and that's where my expectations sit. I'm most focused on the fit and the team.' It names a researched range, frames it as market data, and keeps the door open: three things recruiters reward.
How is answering salary expectations different from negotiating the offer?
The expectations question happens before any offer exists, so your goal is to set a researched range and protect your anchor, not to close a number. The negotiation happens after the written offer arrives, where you counter on specific movable levers. Treating the expectations question as the negotiation is the most common new-grad mistake; it commits you to a number with zero leverage.