Negotiation Script: SDE-1 Role in India (2026)

Landing your first Software Development Engineer (SDE-1) offer is a huge milestone, but the conversation that comes next—negotiating your salary—can feel daunting. In India's competitive tech landscape, where initial offers can vary widely, knowing how to articulate your value is a critical skill that can set the trajectory for your early career earnings. This script is your practical guide to navigating that crucial discussion with confidence and professionalism, tailored for the 2026 hiring scene.

Understanding the SDE-1 Negotiation Landscape in India

Before you utter a word, you need to understand the playing field. For freshers and early-career professionals in India, the scope for negotiation is real but has its boundaries. Companies like TCS, Infosys, and Wipro often have standardized entry-level packages, while product-based companies like Flipkart, Razorpay, and Swiggy may have more flexibility based on your skills, internships, and competing offers.

• Know the Benchmarks: For 2026, research typical SDE-1 compensation. Use platforms like AmbitionBox and Glassdoor. A range might be ₹8-15 LPA for service-based firms and ₹15-25+ LPA for top product-based or high-growth startups like Zerodha or Freshworks, depending on the institute and role.
• The "Fresher" Factor: Recruiters often assume freshers won't negotiate. By being prepared, you immediately stand out as a professional who understands their worth.
• What's Negotiable: Beyond base salary, consider other components of your Cost to Company (CTC): joining bonus, relocation allowance, stock options (ESOPs—especially in startups), and even your job title.

Preparing Your Negotiation Toolkit

You cannot negotiate effectively without ammunition. Your preparation is what transforms an awkward ask into a collaborative conversation.

1. Quantify Your Achievements: Go beyond "I built a project." Say, "I developed a full-stack application that improved data retrieval time by 30%," or "My internship contribution at [Company] was directly integrated into the main product pipeline."
2. Gather Market Data: Have specific numbers ready. "My research on platforms like AmbitionBox shows that for SDE-1 roles in Bangalore with my skill set (Python, React, AWS), the average compensation is around ₹18 LPA."
3. Secure a BATNA: Your Best Alternative To a Negotiated Agreement is your leverage. If you have another offer, even for a different role, it strengthens your position significantly. It's not about playing companies against each other, but demonstrating your market value.
4. Practice Your Delivery: Rehearse your key points aloud. Confidence comes from familiarity.

The Step-by-Step Negotiation Script

Use this script as a framework. Adapt the bracketed [ ] information with your specifics.

When the HR Manager calls or emails with the initial offer...

Your First Response (Gratitude & Request):

"Thank you so much for the offer! I'm genuinely thrilled at the prospect of joining the team at [Company Name] and contributing to [mention a specific project or tech stack you admire]. Could you please share the detailed offer letter and the complete breakdown of the CTC? I'd like to review it thoroughly before we proceed."

• Why this works: It shows enthusiasm, buys you time, and ensures you have all the data (variable pay, bonus structure, etc.).

After Reviewing the Offer (The Collaborative Ask): Once you have the details and have done your research, schedule a call.

"Thank you for sending the details. I've reviewed everything, and I'm very excited about this opportunity. Based on my understanding of the role and the [specific skills: e.g., scalable system design, cloud expertise] I bring from my internship at [Previous Company/Project], along with the current market standards for this position in [City, e.g., Pune], I was hoping we could discuss the compensation package.

My research indicates a range of [₹X LPA to ₹Y LPA] for similar roles. Given my [mention 1-2 key achievements: e.g., published app with 10K+ downloads, contribution to an open-source project], I believe a base salary closer to [Your Target Number] LPA would be more reflective of the value I aim to bring to [Team Name, e.g., the payments team].

I am absolutely committed to accepting this offer and making an impact here. Is there any flexibility to revisit the base salary or the joining bonus component to help bridge this gap?"

• Why this works: It's data-driven, ties your ask directly to your proven skills, expresses commitment, and offers a potential alternative (joining bonus).

Handling Common HR Responses

Be ready for these replies. Stay calm and professional.

• "This is our standard package for freshers."
  • Your Response: "I understand that. However, I believe my experience with [specific technology/domain] and my [specific achievement] differentiate my profile. I'm keen to understand if there's any scope for an exceptional case review or if there are performance-based accelerators we could build into the offer."
• "We don't have any budget left for this role."
  • Your Response: "I appreciate you sharing that constraint. In that case, could we explore other components? For instance, a one-time signing bonus, an early performance review with a defined salary hike milestone in 6 months, or an increase in the ESOP grant? My primary goal is to find a structure that recognizes my initial contribution."
• "We need an answer immediately."
  • Your Response: "I'm very serious about this role, and I want to give the offer the consideration it deserves. Could I possibly have until [e.g., end of the week] to provide my final decision? This will allow me to wrap up my other ongoing processes respectfully."

What Not to Do During Negotiation

Avoid these common pitfalls that can sour the conversation.

• Don't make it personal: Never negotiate based on personal expenses. Keep the focus on market value and your professional worth.
• Don't bluff or lie: Never invent a competing offer. Your credibility is your most important asset.
• Don't be confrontational: Use "we" language. You are solving a problem together, not making demands.
• Don't negotiate over email for the main ask: The nuance of a voice or video call is crucial. Use email for follow-ups and documentation.

Next Steps

Mastering this conversation is just the beginning of managing your tech career. To build the skills that justify your ask, explore in-demand courses on our platform. Start by browsing top-rated System Design courses to ace your next technical round, or deepen your core fundamentals with our curated list of DSA and problem-solving resources. Finally, prepare for the entire journey with our guide on cracking product-based company interviews.