The salary expectations question, and four ways to answer it

On 6 September 2026 I pulled our Search Console data for salary queries. The phrase “ctc to in hand salary calculator” had brought 23 impressions at an average position of 62.8 across three checks in 45 days. Nobody clicked, because page six of Google may as well not exist. But people are clearly running the numbers before they walk into a room and get asked about salary expectations, which is the one question in a hiring process where a bad sentence costs real money.

The question sounds like a request for information. It isn’t. It’s a negotiation opening disguised as an HR formality, and the person asking usually already knows the band.

What the recruiter asking about salary expectations really wants

When a recruiter asks about your salary expectations, they’re checking whether you fit an approved range that was set before you applied. A number far above it ends the process quietly. A number below it gets you hired cheaply and, in a lot of companies, permanently, because internal raises are percentages of a bad starting point.

That’s the whole mechanism. Recruiters aren’t being cute about it. Most of them are working a requisition with a floor and a ceiling and a hiring manager who will approve the middle without escalation.

Which means the question has three possible good answers and one bad one, and the bad one is a single number said early.

Four answers, roughly in order of how well they hold up

1. Deflect once, politely. “I’d rather understand the scope first. Do you have a band approved for this role?” About half the time you’ll get the band. Recruiters in the US increasingly have to state it anyway, because pay transparency laws in Colorado, California, New York and Washington require posted ranges for roles that can be performed in those states.

If they give you the band, you’re done. Say the top third of it sounds right and move on.

2. Anchor with a range you can defend. Not a wish. A range built from two or three real comparables, with the bottom of it being a number you would genuinely accept. “Based on what similar backend roles are paying in Bangalore right now, I’m looking at 34 to 41 lakh total.” The specificity is what makes it survive a follow-up.

3. Give a number, but tie it to a structure. Useful when the recruiter pushes twice and you want to stay agreeable. “42 fixed, and I’m flexible on the equity split.” You’ve now moved the conversation to composition rather than size, which is a friendlier fight.

4. Answer with your current comp, adjusted. Weakest of the four, and illegal for them to ask in several US states, but if you’re a fresher with no comparables it’s honest and it works: “I’m at 8.2 now and I’m targeting 12 to 14 for a role with this much ownership.”

The bad answer is “I’m flexible” or “whatever is standard for the role”. It reads as unprepared, and it hands the range to the other side of the table.

Picking a range you can actually defend

Start from a public reference point rather than a feeling. The US Bureau of Labor Statistics puts the median annual wage for software developers at $135,980 as of May 2025, with employment projected to grow 10 percent through 2035. That’s a national median across every level and city, so it’s a floor for reasoning, not a target.

Level and geography move it far more than the median suggests. The 2025 Stack Overflow Developer Survey put engineering managers at a $200,000 median in the US against $118,335 in Germany and $52,308 in India. Same title, roughly four times the spread. Whatever number you say has to be anchored to a market, or it’s noise.

Three sources are enough: one aggregator, one person who does the job at that company, and the posted range if there is one. If two of the three agree, use that band. If they don’t, widen your range and say so out loud, which is more credible than false precision anyway.

Run your target through an actual take-home calculation before you commit to it. A 40 lakh offer with a big variable component and a 30 percent bonus that pays out at 60 percent is a different job from a 34 lakh offer that’s all fixed. Our CTC to in-hand calculator does the boring part, and the offer comparator is for when you have two of them on the table.

In India the question is really about CTC

Indian recruiters almost always ask for current CTC and expected CTC as a pair, often in the first screening call, sometimes in the application form itself. The honest framing is that expected CTC is a hike percentage, not a salary. A 30 percent hike on a switch is normal. Fifty is achievable moving from services to product. Beyond that you need a competing offer or a title change to justify it, and saying so plainly is better than pretending the number is arbitrary.

One thing worth knowing: the CTC you quote gets recorded and follows you through the background check. Inflating it is a bad trade for a small short-term gain. Companies do verify it against payslips.

We wrote up the arithmetic in more detail in CTC vs in-hand salary, and the switching side in tech salary negotiation.

Scripts you can adapt

I’m not sure the fresher script is right, honestly. It gives away the anchor. But pretending to hold cards you don’t have tends to read worse than admitting it, and freshers who over-anchor get screened out rather than negotiated with.

One opinion that might be wrong

I think the standard advice to never say a number first is oversold. It comes from sales negotiation research where both sides have similar information. Hiring isn’t that. The company knows the band, the market rate, and what the last three people accepted. You know one of those things. Refusing to name salary expectations in that situation mostly signals that you read a LinkedIn post about anchoring, and it burns goodwill with a recruiter who has forty other candidates and a quota.

Give your salary expectations as a researched range early, sound like you’ve done the work, and spend your energy on the part that actually moves: the offer conversation after they’ve decided they want you. That’s where the number changes. If you’re prepping the rest of the loop too, our final round questions post covers what usually comes right before the offer call.

What would change my mind is data showing that candidates who deflect end up with better offers at the same company. I haven’t seen that data. If you have it, I’d like to read it.