top of page

The Biggest Salary Negotiation Mistakes That Keep You Underpaid

Updated: May 12

You worked hard. You cleared four gruelling technical rounds. You finally got the HR call.

And then the HR asks the "million-dollar" question: "What are your salary expectations?"

You panic. You blur out a number. They agree instantly. You feel great until six months later when you realize your teammate with the same experience is earning ₹3 Lakhs more than you.

Why? Because they negotiated. You didn't.

In this guide, I’ll break down the exact mistakes developers make during salary negotiations and what to do instead.


Let's get into it.

Professional illustration showing a developer successfully navigating a salary discussion. The image highlights the contrast between an initial low offer and a final negotiated high-salary package, featuring elements like market research reports and a confident handshake."

Mistake 1: Being the First to Name a Price


This is the most expensive mistake in the book. When HR asks for your expectation and you say "18 LPA," but their budget was "22 LPA," they won't correct you. You just handed them a 4-Lakh discount on your talent.


What to do instead: The "Reverse" Strategy Throw the question back professionally.

"I’d love to understand the budget for this role first. What is the range the company has benchmarked for a candidate with my profile?"

Now you negotiate from their ceiling, not your guess.


Mistake 2: Negotiating on CTC, Not In-Hand


In India, a 20 LPA CTC can be a trap. Between PF deductions, unrealistic variable pay, and "hidden" allowances, your monthly take-home might be lower than someone with an 18 LPA offer.

Key questions to ask before signing:

  • What is the fixed component (Basic + HRA + Special Allowance)?

  • What percentage is variable, and what is the historical payout frequency?

  • Is the PF calculated on Basic or Gross?

  • What are the Joining Bonus clawback conditions?


Mistake 3: Accepting the First Offer Immediately


Companies almost always have a 10-15% "buffer" kept aside. If you accept the first number, that buffer stays in the company’s pocket.

What to say instead:

"Thank you for the offer. I'm genuinely excited about the role. However, based on my research and current interviews, I was expecting something closer to ₹X. Is there some flexibility here?"

They won't withdraw the offer just because you asked. The worst they can say is no. The best? An extra 1-2 lakhs for a single sentence.


Mistake 4: You Walk In Without Market Data

"I think I deserve around 18 LPA."

"I think" is not a negotiation strategy.

Before any salary conversation, get real numbers.

Check Glassdoor, Ambition Box, LinkedIn salary insights, Levels.fyi . Talk to people in similar roles. Know what the market pays at the 50th percentile and at the 75th percentile.

Then target the 75th.

When you say "based on current market data for this role in this city, the range is X to Y and I'm targeting the upper end because of my experience in Z" that's a different conversation entirely.


A software developer confidently discusses an offer with an HR manager, using printed market compensation data (Levels.fyi, AmbitionBox) to cross out an initial 18 Lakhs figure and highlight a higher 22 Lakhs CTC.

Mistake 5: Waiting for the Appraisal Letter to Negotiate

By the time you receive your appraisal letter in April, the budgets are already locked. Your manager’s hands are tied.

The Pro Tip: Start the conversation 3 months before the cycle closes. Show your impact, share the market data, and plant the seed early.

"I want to discuss my compensation before the numbers are frozen. Based on my contributions this year, I’m looking at a correction to match the current market standard."

Mistake 6: Sounding Apologetic

"I was hoping, if possible, maybe I could get a little more..."

Negotiation is not a favour; it’s a business transaction. If you sound like you’re asking for a "gift," you’ve already lost your leverage.

Master the Silence: State your number. Give one logical reason. Stop talking. Silence creates pressure. Let the HR be the one to break it.


Quick Checklist Before Your Next Negotiation


  • Never say a number first. Ask for their range.

  • Calculate the in-hand salary, not just CTC.

  • Counter-offer at least once. Always.

  • Come with market data, not feelings.

  • Start the appraisal conversation 2 to 3 months early.

  • Be confident, not aggressive, not apologetic.


Final Thoughts


Nobody teaches you this in college. Nobody teaches you this in your first job either.

So you figure it out by watching others. Most of whom are also figuring it out by watching others.

The result is a generation of technically strong developers who undersell themselves every time money comes up.

This is a learnable skill. Once you learn it, you keep the money you earn.

You worked hard to get the offer. Work a little harder to make sure it's the right number.



 
 
 

Comments


bottom of page