The CTC Trap: How to Legally Dodge Salary History Questions in 2026

"What's your current CTC?" It sounds like small talk. It is not. It is the single most financially damaging question in the entire Indian hiring process, and 93% of recruiters ask it in the very first screening call before they've even decided if you're a fit for the role.

You are not legally or ethically obligated to disclose your current or past salary in most hiring conversations — and in a growing number of jurisdictions, the recruiter isn't even allowed to ask. This guide gives you the exact scripts, legal context, and negotiation logic to handle this question without lying, without sounding evasive, and without losing the offer.

• Whether asking for your CTC is actually legal in India and abroad.
• Exactly how much a single unguarded answer can cost you over a 5-year career window.
• Five ready-to-use scripts, ranked from softest to firmest, that redirect the conversation to role value.
• How to adjust your approach depending on whether you're talking to a service giant, a product company, or a startup founder.

The first person to name a number in a negotiation almost always loses value — the goal isn't to hide your salary, it's to never let it become the anchor.

In an ideal hiring process, offers are based on role value, market rate, and your skills — not on what your previous employer happened to pay you three years ago. But asking for CTC persists in Indian hiring because it is the single fastest way for a recruiter to control the budget and speed up an offer approval internally.

• Budget anchoring: Your current CTC lets the recruiter calculate the minimum hike (usually 20-40%) needed to make you say yes, instead of paying the role's true market value.
• Speed: A number lets them skip a longer conversation about your skills, market rate, and the role's actual budget band.
• Internal approvals: HR often needs to justify a new hire's package against their last drawn salary to finance and leadership.
• Habit, not policy: Most recruiters ask because it's always been asked — not because a lawyer or compliance officer told them to.

This matters because it means the question is almost never a hard requirement — it's a default script. And default scripts can be redirected.

There is no single central law in India that bans employers from asking for your current CTC, unlike in over 20 U.S. states (including California, New York, and Colorado) and cities where salary history bans are now standard employment law. That said, "legal to ask" does not mean "you're obligated to answer with a specific number."

If you're applying to a global capability centre (GCC), remote-first startup, or a company headquartered in a salary-history-ban jurisdiction, you can directly and politely mention that their hiring policy (or their home jurisdiction's law) doesn't require salary history disclosure. This alone often ends the conversation in your favour.

1. 1.Massachusetts became the first US state to ban salary history questions in 2016, and over 20 states have since followed.
2. 2.The UK does not have a formal ban, but the 2026 push toward mandatory salary-band disclosure in job postings is reducing reliance on the question entirely.
3. 3.India has no equivalent law yet, but large product companies and GCCs are voluntarily adopting range-based hiring to compete for talent with global employers.

Pay transparency laws exist because salary history perpetuates old pay gaps into every future job — the fix isn't more disclosure, it's less reliance on the past.

Let's put actual rupee figures on this, because the abstract advice to "negotiate confidently" doesn't land until you see the compounding damage.

Say you're a 3-year experienced backend developer currently at ₹8 LPA at a service company, interviewing for a product-based fintech role budgeted at ₹16-18 LPA for your exact skill level. If you disclose ₹8 LPA early, most recruiters will anchor your offer at ₹10.5-11.5 LPA — a "generous-sounding" 35-40% hike that is still ₹5-6 lakhs below the role's actual budget, every single year, compounding across every future hike calculated as a percentage of that lower base.

1. 1.Year 1 shortfall: ₹5-6 LPA below market rate.
2. 2.Year 2 (assuming a standard 15% annual hike on the lower base): the gap widens to roughly ₹6.5-7.5 LPA.
3. 3.Over a 5-year window, compounded, this single unguarded answer can cost a mid-level professional ₹30-40 lakhs in lifetime earnings from one job change alone.

The damage doesn't stop at the first hike either. Most companies calculate your next appraisal cycle's increment as a percentage of your existing base, which means an anchored, underpriced starting offer keeps compounding a percentage-point shortfall against the true market rate for every year you stay. Switch jobs again in three years, and recruiters at your *next company will anchor off this already-discounted number, repeating the entire cycle. This is precisely why career coaches describe the CTC question as a compounding tax on your entire career*, not a one-time inconvenience.

The goal isn't to refuse rudely or lie about your salary — both backfire. The goal is to redirect the conversation to role value and market rate, confidently and without apology. Here are five field-tested responses, ranked from softest to firmest.

1. 1.The redirect: "I'd rather focus on the value I can bring to this role. Based on my research, roles like this at [company/industry] typically pay ₹X-Y LPA — does that align with your budget?"
2. 2.The range-only: "My compensation has multiple components including variable pay and ESOPs, so a single CTC number wouldn't be an apples-to-apples comparison. What I can share is my expected range for this role: ₹X-Y LPA."
3. 3.The company-policy mirror: "I generally keep my current compensation confidential per my current employer's policy, but I'm happy to discuss my expectations for this role in detail."
4. 4.The delay-to-offer: "I think that conversation is most useful once we're both confident this is a mutual fit — can we revisit compensation once we've discussed the role in more depth?"
5. 5.The direct ask-back: "Before I share a number, could you tell me the budgeted range for this position? That'll help me give you a realistic expectation."

Whoever gives a number first in a negotiation gives up information; whoever asks the better question keeps control of it.

Delivery matters as much as wording. Practise saying your chosen script out loud, at normal conversational pace, until it stops sounding rehearsed. A script read in a flat, defensive tone signals discomfort; the exact same words said with a small smile and steady eye contact (or a relaxed tone on a call) signal that this is simply how you operate — not a confrontation. Recruiters mirror the energy you bring to the conversation, so calm confidence tends to de-escalate any pushback far more effectively than a firmer refusal would.

Your deflection strategy needs to change depending on who's asking. Treating a TCS HR interview the same way you'd treat a Series B startup founder call will backfire in both directions.

• Service giants (TCS, Infosys, Wipro, HCL): HR processes are standardised and often require a formal CTC breakup document before an offer letter is generated. Here, focus on negotiating the structure (fixed vs. variable, joining bonus, relocation) rather than refusing to share the topline number outright.
• Mid-size product companies: HR has more discretion. The range-only script (#2 above) works especially well here since these companies are used to candidates who've researched market bands on Glassdoor and AmbitionBox.
• Startups & unicorns (Razorpay, CRED, Meesho, Zepto): Compensation conversations often happen directly with the founder or hiring manager, not HR. These conversations reward confidence and market data far more than policy language — lead with your expected range and back it with specific comparable roles.
• Global Capability Centres (GCCs): Increasingly following the parent company's home-country policy (US/UK), meaning salary history questions may already be officially banned internally — worth asking directly.

Every script above only works if you can back it up with a real, specific number. Vague confidence gets exposed in the first follow-up question. Specific, sourced confidence closes the conversation.

Before any interview where compensation might come up, spend 30 minutes building your range using at least three independent sources — never rely on a single site, since self-reported data can skew high or low.

• AmbitionBox / Glassdoor: Filter by exact role, experience band, and city — a Bengaluru SDE-2 number is meaningless for a Pune role.
• LinkedIn Salary / LinkedIn posts: Search for recent posts from people in comparable roles who've openly shared their band after a switch.
• Naukri Salary Insights: Useful for service-sector roles specifically, where AmbitionBox data can be thinner.
• Direct network: A single DM to a former colleague who switched roles recently is often more accurate than any aggregator.

When your sources disagree — and they often will, sometimes by several lakhs — resolve the gap by weighting recency over volume. A single data point from someone who switched jobs last month carries more signal than fifty two-year-old self-reported entries on an aggregator site, since compensation bands in Indian tech have moved fast enough that even 18-month-old figures can undersell your true market value. When in doubt, quote the lower end of your most recent, most specific data point rather than the midpoint of a stale aggregate — it's a number you can defend with confidence if challenged.

The same AI tools reshaping how you write code and resumes can sharpen your negotiation prep. This isn't about generating a script and reading it robotically — it's about compressing hours of research into minutes.

1. 1.Market range synthesis: Paste your role, years of experience, city, and stack into an AI assistant and ask it to cross-reference typical ranges across service vs. product companies, then sanity-check the output against AmbitionBox and Naukri directly.
2. 2.Objection rehearsal: Ask the AI to role-play as a pushy recruiter who keeps insisting on a number, so you can practise holding your script calmly across three or four follow-up pushes.
3. 3.Email/message drafting: If a recruiter asks for CTC over email or a hiring portal form, have the AI help you draft a concise, professional range-only response rather than typing a rushed reply under pressure.
4. 4.Tools like Claude Code or Cursor, while built for engineering work, are increasingly used by developers to quickly script small personal calculators — for instance, a simple script to model take-home pay across two competing offers with different fixed/variable splits.

There's a broader trend worth noting here: as AI-assisted coding tools compress how long engineering work takes, hiring managers at product companies are increasingly benchmarking candidates on output and judgement rather than raw years of experience, which is shifting salary bands upward for developers who can demonstrate strong AI-assisted workflows. Mentioning fluency with tools like Claude Code or Cursor during a negotiation — backed by a concrete example of faster delivery — can itself become a point of leverage, separate from your CTC history entirely.

Even candidates who know these scripts still lose ground by making one of these avoidable errors under pressure. Interview adrenaline has a way of erasing careful preparation the moment a recruiter raises an eyebrow or goes quiet on the line, so it's worth rehearsing not just what to say but how to recover if you slip and say too much anyway — a simple recovery line like "that figure includes some one-time components, so my expected range for this role is still ₹X-Y LPA" can undo an accidental overshare within the same conversation.

• Blurting a number to end an awkward silence — recruiters are trained to let silence sit; don't fill it with your CTC.
• Lying about your current salary — this is discoverable via offer letters, Form 16, or reference checks, and can get an offer rescinded even after joining.
• Giving a range so wide it's useless — "₹10-25 LPA" signals you haven't done your research; a tight, sourced range like "₹18-21 LPA" signals confidence.
• Negotiating only the fixed component — ignoring variable pay, ESOPs, and joining bonus structure can leave real money on the table even after "winning" the base number.
• Accepting the first counter-offer immediately — most recruiters build in room to move; a polite one-more-ask ("is there any flexibility here?") frequently gets 5-8% more with zero risk.

Silence is one of the most powerful negotiation tools — and one of the most underused.

The salary history question feels like a formality, but treating it that way is exactly what costs Indian professionals lakhs in lifetime earnings, year after year, offer after offer. You are allowed to redirect the question to role value. You are allowed to quote a researched range instead of an exact figure. And in a growing number of hiring contexts, you're not even required to answer at all.

The candidates who negotiate best aren't the ones with the most experience — they're the ones who walked in with a number they could defend and a script they'd rehearsed enough to say calmly, without flinching, three times if needed.

1. 1.Your current CTC is information you control, not information you owe anyone by default.
2. 2.A researched, specific range beats a vague refusal every single time.
3. 3.The best time to practise your script is before the interview, not during it.

Negotiation isn't a fight to win — it's a conversation to steer toward a number you can defend.