How to Answer the Expected CTC Question in an Interview

The expected CTC question — "What are your salary expectations?" — shows up in almost every Indian interview, usually from HR, and most freshers either blurt out a number they haven't researched or undersell themselves out of nervousness. The right approach is to quote a researched range tied to the role and market, not a single figure, and to hold that range until you have a firm offer in front of you. This article gives you the actual wording to use, how to research the number beforehand using Naukri, Glassdoor and AmbitionBox, and how to handle the specific traps recruiters set — like being asked for your current CTC first, or being pushed for an exact figure on the spot.

Why This Question Trips Up Freshers Specifically

Experienced candidates usually have a current CTC to anchor from and a clear sense of market rate for their skill level. Freshers and people with 0–2 years of experience often don't — campus placement packages vary wildly by college tier, and off-campus offers vary even more, so there's no reliable personal benchmark to quote. That gap is exactly why an unprepared answer costs you money: quote too low and the company will happily pay you less than they budgeted; quote too high without justification and you risk getting screened out before a human even discusses it with you.

Research the Number Before the Interview, Not During It

Walking in without a number is worse than walking in with a slightly wrong one. Spend twenty minutes before the interview checking:

• AmbitionBox and Glassdoor salary pages for the specific company and role — these are self-reported but useful for a ballpark, especially for large employers like TCS, Infosys, Wipro or Accenture where sample sizes are large.
• Naukri's salary insights or recent job postings for the same role and experience band in your city, since compensation for the same title can differ by 30–40% between a metro and a tier-2 city.
• Your own college's placement cell data or seniors who joined similar roles in the last one to two hiring cycles — this is often the most accurate signal for entry-level packages, more reliable than aggregator sites.

Once you have three or four data points, take the median, not the highest number you found — a single outlier posting skews your anchor and makes your ask look uninformed if the interviewer knows the real range.

What to Actually Say

Use a range, anchored slightly above the median you researched, and tie it explicitly to the role rather than a personal need.

"Based on my research for this role and experience level in [city], I'm looking at something in the ₹6–7.5 LPA range. I'm flexible depending on the full compensation structure and the role itself."

This works because it signals you've done homework, it gives the recruiter room to negotiate within a band you've already accepted, and it doesn't box you into a number you'll regret if the role turns out to include better benefits, a signing bonus, or faster growth than you expected. If you're asked to narrow it to one figure, give the midpoint of your range and stop talking — resist the urge to justify it further unless asked.

Handling the Specific Traps

"What is your current CTC?"

If you're a fresher with no prior CTC, say so plainly — there's nothing to hide. If you have a current job and don't want to anchor the new offer too closely to your old, low salary, you're allowed to keep the focus on the number you're seeking rather than disclosing the old one in detail: "My current compensation isn't directly comparable given the role and scope here, but I'm targeting ₹X–Y for this position." Several large employers still ask for payslips to verify current CTC during background checks, so don't misstate the number outright — keep the framing about the new role's scope, not the old figure's accuracy.

"Just give me one number."

If pushed, give the midpoint of your researched range and add one sentence of context: "If I had to pick one figure, I'd say ₹6.75 LPA, based on what similar roles at comparable companies are paying in this city." A single justified number beats a vague range delivered nervously.

"Can you take less because you're a fresher?"

This is a common pressure tactic, especially in off-campus drives and smaller companies. It's fine to hold your range if you've researched it properly — being a fresher doesn't mean your market value is arbitrary, it means your market value is at the entry-level band, which you should already have priced in.

What a Realistic Range Actually Looks Like by Experience Level

Ranges vary enormously by role, company tier and city, but here's a rough shape freshers and early-career candidates can use as a starting anchor before adjusting for their specific situation.

Profile	Typical CTC Range (Non-Metro)	Typical CTC Range (Metro)
Fresher, mass IT recruiter (TCS/Infosys/Wipro-scale)	₹3.5–4.5 LPA	₹3.5–4.5 LPA
Fresher, product/startup, technical role	₹4–7 LPA	₹6–10 LPA
0–1 year experience, non-technical (ops, support)	₹3–4.5 LPA	₹4–5.5 LPA
1–2 years experience, technical role	₹5–8 LPA	₹7–12 LPA

These figures are directional, not guaranteed — always adjust against the specific company and role you're interviewing for using the research steps above, and check what portion is fixed vs variable, since a headline number with a large bonus or ESOP component isn't the same as an equal fixed CTC. Once you have an offer in hand, run the actual numbers through the in-hand salary calculator before comparing two offers, since take-home pay can differ meaningfully even at the same CTC depending on structure and city.

After the Number: What to Check Before You Accept

Getting the expected-CTC conversation right is only half the negotiation. Once an offer comes through:

• Ask for the full CTC breakup, not just the headline figure — see our guide to salary slip components for what each line should represent.
• Compare the offer against your current or previous CTC properly, not just the headline number, since the actual jump matters more in in-hand terms than CTC terms.
• If there's room to push further, structure it as a specific ask tied to market data or a competing offer, rather than a general "can you do better" — see our broader guide on how to negotiate salary for the actual scripts.

What Not to Do

Don't quote a number you found once on a random forum and haven't cross-checked. Don't lowball yourself because you're worried about seeming greedy — recruiters expect a researched range, not a modest guess, and an unnaturally low number can even raise doubts about your confidence or self-assessment. And don't treat the first number you're offered as final if it's meaningfully below the range you researched and stated — a polite "I was expecting closer to my stated range given [specific reason]" is a normal part of the process, not a confrontation.

How Much of a Hike Is Reasonable When You're Switching Jobs?

If you're already employed and moving, recruiters and career forums frequently repeat a "20–40% hike" figure as the norm for a job switch. Treat that as a commonly repeated industry rule of thumb rather than a confirmed, sourced statistic — the real number depends heavily on how underpaid you currently are, the role's market rate, and how badly the new company wants you specifically. A more reliable way to set your own number is still the research method above: median market rate for the new role, compared honestly against your current CTC, not a flat percentage applied blindly.

If your current CTC is already below market rate

In this case, don't anchor your ask to a percentage hike over your current pay at all — anchor it to the market rate for the new role. If similar roles are paying ₹6 LPA and you're currently on ₹3.8 LPA, asking for "a 40% hike" undersells you; asking for something close to the ₹6 LPA market rate is the more defensible number, and you can say exactly that if asked to justify it.

If you're moving for a promotion in scope, not just a lateral move

A role with meaningfully more responsibility — say, moving from a support role to an analyst role, or from an individual contributor track to leading a small process — justifies a larger jump than a same-level lateral move. Frame this explicitly in your answer: "Given the scope of this role compared to my current one, I'm targeting ₹X, which reflects the added responsibility" reads as reasoned, not greedy.

What Recruiters Are Actually Assessing With This Question

HR isn't just collecting a number — they're also reading how you handle a slightly uncomfortable, high-stakes question. A candidate who freezes, gives a wildly unresearched figure, or immediately caves when pushed signals the same behaviour they'll likely show later when negotiating a raise, a project deadline, or a client conversation. Conversely, a calm, specific, well-justified range signals exactly the kind of preparation and self-advocacy that's genuinely useful on the job. Keep this in mind, because it also means how you say your range often matters as much as the number itself — steady pacing and a brief justification land better than a rushed, apologetic answer.

A Realistic Example Conversation

Here's roughly how this plays out for a fresher applying to a product company for a support/associate role, having researched a median of ₹4.8 LPA for the role in their city:

Recruiter: "What are your salary expectations?"

Candidate: "Based on what I've seen for this role and experience level in the market, I'm looking at somewhere in the ₹4.5–5.5 LPA range. I'm flexible depending on the complete structure — fixed versus variable, and any other benefits."

Recruiter: "Our budget for this role tops out at ₹4.2 LPA fixed, with a small variable component."

Candidate: "I appreciate you being upfront. Could you walk me through what the variable component typically pays out at, and whether there's a review point in the first year where this could be revisited?"

Notice the candidate doesn't immediately accept or immediately walk away — they ask a clarifying, specific follow-up that could still make the lower number acceptable, without sounding either desperate or difficult.