How to Answer "What Are Your Salary Expectations" in an Interview
Almost every interview reaches the moment where the recruiter leans back and asks, "So, what are your salary expectations?" It sounds simple. It is not. Answer too low and you leave money on the table for the next two years. Answer too high and you risk being screened out before the technical round even happens. And if you fumble with an "I don't know," you look like someone who has not thought about their own worth.
This is not a piece about how to negotiate a final offer. That is a different conversation, usually after the company already wants you. This is about the interview question itself, often asked in the very first HR call in India, sometimes before anyone has confirmed you can do the job. The goal here is to answer in a way that keeps you in the running and protects your number. Let us break it down.
Why they ask it, and why timing matters
Recruiters ask about salary early for two reasons. First, to filter. If their band tops out at 8 lakh per annum and you want 15, they would rather find out on a ten minute call than after four rounds. Second, to anchor. Whoever names a number first often sets the frame for the rest of the discussion.
That is why the smartest move, when the question comes very early, is to gently deflect rather than blurt a figure. You are not being evasive. You are buying time to understand the role, the responsibilities, and the level before you commit to a price. Once you have that context, a specific range lands far better.
Do your homework on the market rate first
You cannot answer well if you do not know what the role pays. Before any interview, spend an hour finding the real number for your city and experience level. In India that means checking a few sources and comparing, because a single site is often skewed.
Look at AmbitionBox and Glassdoor for role and company specific ranges. Cross check with LinkedIn Salary and with what peers in your network actually earn, which is the most honest data you will get. Factor in your city. A backend developer role in Bengaluru or Gurugram pays differently from the same title in Indore or Coimbatore. Factor in the company type too. A funded startup, a services giant like Infosys or TCS, and a product company like Razorpay or Zoho will structure pay very differently, especially the fixed versus variable split.
Once you have a realistic band, add your own logic. Where do you sit inside it based on your skills, your current pay, and how much the new role stretches you? That becomes the range you will quote.
The fresher answer
If you are a fresher or have under a year of experience, you have less leverage and less data, so keep it clean and slightly flexible. You do not want to price yourself out of a first job, but you also should not say "anything you offer."
A solid fresher answer sounds like this: "Based on my research for this role and the current market for someone with my skills in this city, I am looking at somewhere between 4.5 and 6 lakh per annum. That said, I care most about the learning and growth this role offers, so I am open to discussing the full package." This shows you did research, gives a real range, and signals you are reasonable without sounding desperate.
If they push for one number, name the middle of your range, not the bottom. And never quote a figure below the market floor just to seem safe. It reads as low confidence, not good value.
The experienced answer
With a few years behind you, your current salary and a clear market rate give you a stronger footing. Here you can be more direct and lead with value.
Try this: "In my current role I am at around 12 lakh fixed. For a position at this level with the added responsibility you have described, I am targeting the 16 to 19 lakh range. I am happy to talk through the full structure including fixed, variable, and benefits." Notice what this does. It states your base honestly, it justifies the jump with responsibility rather than greed, and it invites a real conversation instead of a yes or no.
For candidates weighing an offer against a counteroffer, or trying to time a switch for the biggest jump, it helps to talk strategy with someone who has sat on the hiring side. Goodspace runs a career program where you can work with a mentor to sharpen your offer and salary strategy through Goodspace Accelerate before you ever walk into the room. Going in with a plan beats improvising every time.
How to deflect early without sounding cagey
When the number comes up too soon, use a bridge that turns it back into a question about the role. Something like: "I would love to understand the responsibilities and the level a bit more before I put a number to it. Could you share the band you have allocated for this position?" Roughly half the time, they will tell you their range, which is exactly the information you wanted.
If they insist you go first, give a range, never a single figure, and make it wide enough to negotiate inside. A range says "here is my thinking," while a single number says "this is my line," and you rarely want a hard line this early.
Frequently asked questions
Should I ever say my current salary? If you are comfortable and it helps your case, yes, especially when your current pay is already healthy and justifies your target. If your current pay is low and would drag down the offer, pivot to a market based range instead and talk about the value you bring rather than what you earn today.
What if the range they give is below what I want? Stay calm and probe. Ask about the variable component, joining bonus, review cycle, and other benefits. Sometimes the fixed number is firm but the total package has room. If the gap is genuinely too large, it is better to know now than after four rounds.
Is it fine to say I am flexible? A little flexibility is good, total flexibility is not. "I am open to discussing the full package" is flexible. "Whatever you think is fair" hands them all the power and signals you have not valued yourself.
Can I refuse to answer entirely? You can defer, but refusing outright reads as difficult. Deflect politely, then give a range once you have enough context. Full refusal usually just delays the same question by one round.
Final thoughts
The salary expectations question is not a trap, it is a test of preparation. Research the real market number for your role and city, decide your range before you walk in, deflect gracefully if the question comes too early, and quote a band rather than a single figure. Do that, and you turn an awkward moment into a signal that you know exactly what you are worth.
