How to Negotiate Your Salary in India in 2026 — With Actual Data

Most salary negotiations in India fail before they start — not because the engineer is wrong about their value, but because they are using feelings instead of data.

"I feel I deserve more" loses to "the market pays ₹28–32 LPA for this role in Pune, and my current CTC is ₹22 LPA." Both are saying the same thing. Only one is a negotiation. The other is a request.

Here is how to do it properly in 2026.

First — know your position before you open your mouth

The single biggest negotiation mistake Indian tech professionals make is entering the conversation without knowing their percentile.

If you are at P38 for your role and city, your negotiation is a market correction conversation — you have data on your side and significant room to ask. If you are at P72, your negotiation is a performance and retention conversation — different framing, different ask.

These require completely different approaches. Using the wrong one weakens your position.

Before any salary conversation — appraisal or job offer — run a benchmark. Know your P25, P50, and P75 for your exact role, experience band, and city. Then figure out where you sit.

Framework 1 — The appraisal hike conversation

When to use: Annual review, asking for a correction outside cycle, post-promotion negotiation

The setup:

Come in with three things prepared: 1. Your market percentile (from a benchmarking tool or recent offer data) 2. Your quantified achievements from the last 12 months (with numbers — users, revenue, uptime, speed) 3. The specific ask — a number, not a percentage

What to say:

"I have been looking at market data for my role — Senior [X] in [city] with [Y] years of experience. The market range is ₹[P50] to ₹[P75] LPA for this profile. My current CTC of ₹[X] puts me significantly below that band. Based on the work I have delivered this year — [achievement 1, achievement 2] — I am requesting a revision to ₹[ask]."

Anchor high. Open at P75 or above. If they negotiate down to P65, that is still a meaningful correction. Whoever names the number first anchors the conversation.

Do not say: "I want a 30% hike." Percentages invite a percentage counter. A specific number invites a specific conversation.

Framework 2 — The job offer negotiation

When to use: You have received an offer and want to negotiate before accepting

The setup:

You have more leverage here than in an appraisal. The company has already decided they want you. Offers are almost always negotiable — the first number is rarely the final number.

What to say (email or call):

"Thank you for the offer — I am genuinely excited about the role and the team. I do want to share one consideration. Based on my research and current market data for this role in [city], the range is ₹[P75–P90] LPA. The offer of ₹[X] is below that band. I am hoping we can get closer to ₹[ask]. Is there flexibility there?"

Key principles: - Express genuine interest before negotiating — companies rescind offers from people who seem transactional - Name a specific number, not a range (ranges anchor to the lower end) - If they cannot move on base, ask about joining bonus, earlier review cycle, ESOPs, or remote flexibility — all have real monetary value

Framework 3 — The counter-offer conversation

When to use: You have an external offer and want to use it to negotiate internally

This is the highest-leverage conversation in salary negotiation — and the most frequently mishandled.

What not to do: Walk in and say "I have another offer, match it or I leave." This creates defensiveness and often ends with you leaving anyway.

What to do:

"I have been approached for a role externally and I have received a formal offer of ₹[X] LPA. I want to be honest with you because I prefer to stay — the team and the work here matter to me. But there is a significant gap between where I am and what the market is offering. I wanted to give you the chance to address that before I make a decision."

Critical: Only use this if you are genuinely willing to leave. Do not bluff with a counter-offer conversation. If they call the bluff and you back down, you have permanently weakened your position at that company.

The 2026 data that gives you the most leverage

These are the market facts most useful in an Indian tech salary negotiation this year:

• Aon 2026 Salary Survey: Average India Inc hike is 9.1% — anything below this for a performing engineer is below market
• TCS and Infosys broad base: 4.5–8%, top performers 10%+ — useful baseline to reference
• GCC average increment: 10.4% — significantly above IT services average
• Dual-platform mobile premium (Android + Flutter): 15–25% above single-platform peers
• KMP and Compose Multiplatform: 20–30% premium for engineers with production experience
• AI/LLM integration experience: 25–40% premium in 2026

If any of these apply to you — and especially if more than one does — they are legitimate data points in your conversation, not boasts.

When not to negotiate

There are real situations where negotiating is the wrong move:

• You have just joined in the last 6 months — negotiate at the offer stage, not inside probation
• You received a significant hike in the last 6 months — asking again immediately damages trust
• Your performance genuinely was below expectations — market data does not override performance context
• You have no data and are negotiating on emotion — prepare first, negotiate second

The preparation that takes 10 minutes and changes the conversation

Run your salary benchmark before your next appraisal or offer. Know your percentile. Know the gap in rupees, not just percentage. Bring a number, not a feeling.

The engineers who negotiate the best outcomes in 2026 are not more assertive or more entitled. They are more prepared.

Run your free salary benchmark → Get your full career intelligence report — ₹49 →