How Freshers Can Negotiate Salary in India 2026

Negotiable at most product companies and startups:

• Base salary (within a band): A 10–20% increase from the initial offer is possible if you have a competing offer or demonstrably strong profile.
• Joining bonus: Even if base is fixed, a one-time joining bonus is often more flexible because it does not permanently raise the salary band.
• Start date: Negotiating your joining date to accommodate exam results, project completion, or family events is almost always feasible.
• Role level: If you have exceptional experience (strong internships, competitive programming achievements), requesting to be evaluated at a higher level is legitimate.
• Performance review timing: Asking for an early performance review (at 6 months instead of 12) is a valid ask that some companies agree to.

Not negotiable at most companies:

• Band-level fixed packages: TCS NQT Ninja (₹3.5 LPA), Infosys fixed tracks, Wipro Elite (₹3.5 LPA). These are batch-wide fixed amounts. The only exception is if you have a competing offer from another company: some companies will match within their next band.
• Equity/ESOPs in the first round: Freshers rarely receive ESOP grants upfront. This becomes negotiable once you have the offer and are genuinely weighing it against an equity-rich startup offer.

The fear of 'losing the offer if I negotiate' is largely unfounded at reputable companies. A company would never rescind an offer because a candidate professionally asked about compensation: this would be illegal in many jurisdictions and deeply reputation-damaging.

The script for negotiating a fresher offer at a product company:

'Thank you so much for the offer: I am genuinely excited about this opportunity and the team. I did want to ask: is there any flexibility in the compensation? I have been comparing this offer with [mention a competing offer range if you have one, or reference market data], and I was hoping we could explore whether there is room to move to [specific target].'

If you do not have a competing offer: 'I have done some research on the market range for this role and location, and the current offer is slightly below what I was hoping for. I am committed to joining and contributing quickly: would there be any room to adjust?'

If they say no: 'I appreciate you checking. I am still very interested in this role: can we discuss the timeline for my first performance review?' This pivots to a different negotiation lever.

A competing offer is the single strongest negotiation tool at any career stage, including for freshers. How to use it:

Timing: Mention the competing offer after you have received the current offer (not before). 'I am in the final stages with one other company and expect to receive an offer next week. I would love to join you and want to see if we can make that happen.'

Honesty: Only mention a competing offer if you genuinely have one or expect to receive one imminently. Fabricating competing offers is a career risk: the Indian tech industry is small, and recruiters from competing companies know each other.

Specifics without full disclosure: You do not need to name the competing company. You can say 'another product company' or 'a Series B fintech startup.' You do not need to disclose the exact offer amount: 'slightly higher' is specific enough.

Do not use it as a bluff: If you say you have another offer and then do not receive it, your leverage collapses. Only use it when it is real.

Freshers who focus exclusively on salary often miss the factors that matter more for long-term career trajectory:

Learning quality: A ₹14 LPA role at a product company where you write real code and own systems will outperform a ₹18 LPA service IT role where you maintain legacy code, within 3 years. The salary premium compounds from the learning.

Manager quality: Your first manager has a disproportionate impact on your first 2 years. Ask in the interview: 'What is your management style?' and 'How do you typically support juniors in their first 6 months?' The quality of the answer tells you more than the answer itself.

Team culture: A team that does code reviews, writes tests, and has engineering standards will make you a better engineer faster than a team that ships code without any review process.

Growth trajectory: Ask about the growth of people who joined at your level 2–3 years ago. What is their current role? If senior engineers of 2–3 years of tenure are still at SDE-1, the growth trajectory is slow regardless of what HR says.