Everything was going fine. You nailed the introduction. You answered the competency questions without rambling. The interviewer even laughed at something you said. And then. “So, what are your salary expectations?”
Your stomach does that thing. The tiny clench. Because now you’re not talking about skills anymore. You’re talking about money. And nobody, literally nobody, taught you how to do this. Not school. Not college. Not your parents, whose advice was probably “ask for a good salary” which is roughly as useful as “drive carefully” when you’ve never been behind a wheel.
So your brain starts panicking in real time. If you say ₹8 Lacs and they were willing to go to ₹10, you just cost yourself ₹2 Lacs a year. If you say ₹10 and their budget was ₹7, maybe they drop you and call the next person. And you can’t exactly say “what’s your budget?” because you read somewhere that candidates shouldn’t ask that. Or maybe they should? You can’t remember. The silence is stretching. You need to say something.
This is the moment. And most people handle it badly. Not because they’re bad at interviews. Because they walked in without the one thing this question actually requires: 45 minutes of homework the night before.
What the Recruiter Is Actually Trying to Figure Out
Not your deepest desires. Not whether you’re greedy. Not whether you’re “worth it.”
They have a budget. The hiring manager approved a salary range for this role last month. HR knows it. Finance signed off on it. The recruiter sitting in front of you knows it. The only person in the room who doesn’t know this number is you.
When they ask about salary expectations, what they’re really checking is: does this candidate’s number fall somewhere inside the bracket that already exists? If yes, great, conversation continues. If the candidate is ₹1.5 Lacs above the ceiling, there’s no point going to round 3 because the offer letter will disappoint everyone. If the candidate names a number ₹2 Lacs below the floor, the recruiter starts wondering whether the experience is thinner than the resume suggested.
That’s the whole thing. It’s a compatibility check dressed up as a personal question. Once you see it that way, half the anxiety disappears. You’re not being tested on your self-worth. You’re being asked whether a number matches another number.
The Three Ways People Blow This
“I’m flexible, whatever you think is fair.”
Sounds polite. Sounds open-minded. Actually hands the recruiter a blank cheque to pay you the minimum. Because that’s what “flexible” means from their side of the table. You just told them you’ll take whatever they offer. So they’ll offer the floor. Why wouldn’t they? You gave permission.
So many freshers say this because it feels safe. It’s the opposite of safe. It’s the fastest way to start a job already underpaid.
Quoting a number that came from nowhere.
“₹10 Lacs.” For a role that pays ₹5 to ₹6 Lacs in the market. The recruiter blinks. Doesn’t argue. Doesn’t counter. Just says “we’ll get back to you” and never does. The candidate goes home thinking the interview went well because nobody explicitly said the number was wrong. It was wrong. The conversation ended the moment they said it.
This usually happens because someone told them to “always aim high.” That advice works when you have 3 competing offers and genuine leverage. A fresher with zero alternatives quoting double the market rate doesn’t have leverage. They have a fantasy number.
Dodging the question entirely.
“I’d prefer not to discuss compensation at this time.” Fine in round 1 when the role hasn’t been explained yet. Deeply weird in round 3 when the company is clearly moving toward an offer. The recruiter has heard every version of this dodge. They know the difference between “I want to understand the role first” (reasonable) and “I’m scared to say a number” (obvious). By round 2 or 3, not answering is its own answer. And it’s not a good one.
The thread connecting all three: nobody did the research. A candidate who spent 45 minutes on AmbitionBox the night before doesn’t say “I’m flexible” and doesn’t quote ₹10 Lacs for a ₹6 Lac role and doesn’t dodge the question in round 3. They give a range. Calmly. Because they looked it up.
The 45-Minute Homework That Changes Everything
This is embarrassingly simple. And almost nobody does it.
Open AmbitionBox. Open Glassdoor. Open PayScale. Search for the exact role title you’re interviewing for. Filter by city. Filter by years of experience. Look at the range. Not the average. The range.
If you’re interviewing for a marketing executive role in Bangalore with 2 years of experience, and AmbitionBox shows the range is ₹4 to ₹8 Lacs with a median around ₹5.5, you now know something the previous version of you didn’t know. You know where the market sits. You’re not guessing anymore. You’re not relying on what your college friend said he earns (he was rounding up, by the way, everyone rounds up).
Now add your specifics. Got a certification that directly applies? Push slightly above median. Switching industries and your experience doesn’t perfectly translate? Stay closer to the middle. Got a strong portfolio piece or a really good internship? That adds weight.
Your final answer should be a range. “₹5.5 to ₹7 Lacs based on my research and experience.” Not a single number. A range. Because a range says “I’ve done my homework AND I’m flexible.” A single number says “take it or leave it.” One of those invites conversation. The other kills it.
And talk to actual people if you can. Not just portals. If you know someone in a similar role at a similar-sized company, ask what the range looks like. People will tell you. Not their exact CTC always. But they’ll say “probably ₹5 to ₹7 for someone at your level.” That’s enough.
45 minutes. The night before. That’s the entire difference between freezing in the interview and answering like you’ve done this before.
What to Actually Say (Word for Word)
Here’s the sentence:
“Based on my experience and the market data I’ve looked at for this role in [city], I’d expect something in the range of ₹X to ₹Y. But I’m open to discussing the final number depending on the overall package and role scope.”
That’s it. That single sentence does every single thing you need it to do. Shows you researched. Gives a range, not a rigid demand. Signals flexibility without revealing your floor. And invites the recruiter to share their budget, which is what you actually want, because the second they tell you the range, you’re negotiating with information instead of operating blind.
Don’t apologise for your number. “I know this might be high, but…” kills everything the research was supposed to do. If your range is grounded in market data, state it. Flat. Calm. No disclaimers. The recruiter will tell you if it works or not. Both responses are useful. Neither is personal.
For freshers the framing shifts, but only slightly. You don’t have competing offers or years of leverage. That’s fine.
“I’ve looked at the market range for this role and it seems to be between ₹X and ₹Y. I’m comfortable within that range and honestly more focused on the learning and growth at this stage.”
That’s not weak. That’s a 22-year-old who did their homework and also understands that their first job is a launchpad, not a destination. Hiring managers respect that framing way more than a fresher who quotes ₹9 Lacs for a ₹4 Lac role because they read something on Reddit about “knowing your worth.”
Know your worth, yes. But know the market’s worth too. Those are two different numbers and the gap between them is where the negotiation actually lives.
When They Won’t Let You Give a Range
Some recruiters push back. “We need a specific number for our internal system.” This happens. Don’t panic.
Give them the midpoint of your range. Upper half of midpoint, ideally. If your range is ₹5.5 to ₹7, say ₹6.2 or ₹6.5. Then add: “But there’s flexibility depending on the overall structure, incentives, and review cycle.”
That last line is load-bearing. Without it, ₹6.5 becomes a wall and if their budget is ₹6 flat, they might drop you instead of checking whether ₹6 plus a joining bonus would work. With the flexibility signal, they know there’s room. Room keeps conversations alive.
Sometimes this question hits in round 1. Before they’ve even explained the role properly. That’s annoying but it happens. And it’s completely okay to slow it down.
“I’d love to give you a well-informed answer on this. Can we revisit it once I’ve understood the role scope and expectations better?”
That’s not dodging. That’s asking for context before making a commitment. Any recruiter worth their job will say yes. If they insist on a number before telling you what the job involves, that tells you something about how this company negotiates. And you should probably remember that signal.
After the Offer Letter Is Where Real Negotiation Lives
Everything before the offer is positioning. The actual negotiation starts when they hand you the letter.
Because at that point, you’re not one of 200 anymore. You’re the one they picked. They spent interview hours on you. They ran internal approvals. They compared you against other candidates and chose you. Restarting the process would cost them 3 to 4 more weeks. They don’t want to restart. That reluctance is your leverage. Not loud leverage. Quiet leverage. The kind you use with a polite email, not a demand.
If the number on the letter is lower than your expectation:
“Thank you for the offer. I’m genuinely excited about the role and the team. I was hoping the compensation would be closer to ₹X based on our earlier discussions and the market benchmarks. Is there room to revisit, or would it be possible to discuss an earlier performance review or a different incentive structure?”
Three things happening in that response. Gratitude (so they know you’re not being combative). A specific number anchored to data (not “I feel I deserve more”). And alternatives (review timeline, bonus structure) that give the company ways to bridge the gap without busting their approved budget.
Sometimes they come up ₹30,000 to ₹50,000 on the annual. Sometimes they offer a 6-month review instead of the standard 12-month one. Sometimes they add a one-time joining bonus. Sometimes they say “this is our final number.” All useful answers. None of them are personal attacks.
The worst thing anyone does at this stage: saying yes to a number they’re unhappy with and then resenting the company for the next year and a half. If the number doesn’t work, say so. Once. Politely. With data. Then decide. Sometimes the role’s other benefits (learning, brand name, remote flexibility, team quality) make the gap worth absorbing. Sometimes they don’t. Only you know which one it is.
FAQ’S About Salary Expectations in Interviews
Is giving a range risky? Less risky than giving a rigid number. “₹6 to ₹7.5” tells the recruiter you’re flexible. “₹7.5, non-negotiable” tells them to find someone cheaper. Ranges invite discussion. Fixed numbers end it.
What if you have absolutely no idea what the market pays? 30 minutes on AmbitionBox. That’s the fix. Search the role. Filter by city. Filter by experience. The data is free. Going into a salary conversation without checking benchmarks is like walking into a negotiation without knowing the other side’s position. Technically possible. Strategically terrible.
Can you change your number after you’ve said it? Yes. Especially after learning more about the role. “When we first discussed this, I mentioned ₹X. Having understood the full scope now, I think ₹Y reflects it better.” That’s not backtracking. That’s updating based on new information. Recruiters get it.
Should freshers negotiate at all? They can. The leverage is limited without competing offers, though. For most freshers, the smarter play is accepting a fair offer from a company that offers real learning, performing well for 6 to 12 months, and then renegotiating with actual performance data. “I closed 15 deals in 6 months” gets you a raise. “I think I deserve more” doesn’t.
Will a wrong salary answer actually cost you the job? Only if it’s wildly off and you won’t budge. Quoting ₹12 Lacs for a ₹5 Lac role and refusing to discuss? Yes, that ends things. Quoting ₹7 for a ₹5 Lac role but signalling flexibility on structure? That conversation continues. Recruiters don’t reject reasonable numbers. They reject rigidity.
All the Best!
