You joined as SDE-1 two years ago. You ship features on time, your code reviews are clean, your manager says 'great work' in 1:1s. But promotion season came and went — and you're still SDE-1. Sound familiar? Here's what nobody told you about the SDE-1 to SDE-2 jump in India.
It's May 2026. Appraisal letters are landing in inboxes across Bangalore, Hyderabad, and Gurugram. Some of your batchmates from college just got bumped to SDE-2 at Flipkart, Razorpay, or Atlassian. You didn't. And the worst part? Nobody can clearly tell you why.
The SDE-1 to SDE-2 promotion is the single most misunderstood jump in Indian tech. It's not about how hard you work. It's not about how many tickets you close. It's about a very specific shift that most engineers figure out 6-12 months too late.
Let me break it down.
What SDE-1 to SDE-2 Actually Means in 2026
First, let's get the definitions right. The titles are roughly standardized across product companies in India now:
| Level | Years of Experience | Typical CTC Range (India, 2026) | Scope | |-------|---------------------|----------------------------------|-------| | SDE-1 | 0-2.5 years | ₹18-35 LPA | Owns features, executes well-defined tasks | | SDE-2 | 2.5-5 years | ₹35-65 LPA | Owns systems/modules, makes design decisions | | SDE-3 | 5-8 years | ₹65 LPA - ₹1.2 Cr | Owns products, mentors, influences roadmap |
The salary jump from SDE-1 to SDE-2 in 2026 is significant — typically a 40-70% increase in total compensation. At Flipkart, an SDE-1 at ₹28 LPA usually moves to ₹45-50 LPA on promotion. At Atlassian or Microsoft IDC, the jump can be even higher because of RSU refreshers kicking in.
But here's the thing nobody says out loud: the title change isn't a reward for past work. It's a bet on future work. Your manager has to convince a promotion committee that you're already operating at SDE-2 level. Which means by the time you're "ready" for promotion, you've actually been doing the job for 6+ months.
The Real Difference Between SDE-1 and SDE-2
Forget what your HR portal says. Here's the unspoken difference, learned the hard way from hundreds of Indian engineers who made (or missed) the jump:
SDE-1 thinks in tasks. SDE-2 thinks in systems.
An SDE-1 gets a JIRA ticket that says "Add a coupon code field to checkout." They build it, test it, ship it. Done. Promotion-ready, right?
An SDE-2 gets the same ticket and asks:
- How will this scale when we have 10,000 coupon types?
- What's the impact on our payment service's p99 latency?
- Should this be a separate microservice or a column in the orders table?
- What's the rollback plan if something breaks on Big Billion Day?
- Have we considered fraud vectors?
The SDE-1 ships in 3 days. The SDE-2 ships in 5 days — but their code doesn't wake anyone up at 2 AM six months later.
The "Glue Work" Trap
Here's where many Indian engineers, especially women engineers, get stuck. You spend your time:
- Onboarding new joiners
- Fixing production bugs nobody else wants to touch
- Writing documentation
- Coordinating between 3 teams
This is called glue work. It's essential. It makes the team function. And it will get you a "Meets Expectations" rating but almost never a promotion.
Promotion committees want to see visible technical impact. Not "kept the team running." That's a brutal reality of Indian tech in 2026.
The 5 Things Promotion Committees Actually Look For
I've talked to engineering managers at Razorpay, Swiggy, PhonePe, Microsoft IDC, and Atlassian about what gets discussed in promotion calibration meetings. Here's the actual checklist:
1. Scope of Ownership
Can you point to a system, service, or significant module and say "I own this"? Not "I work on this" — I own this. The auth service. The notification pipeline. The pricing engine.
If you can't name something you own, you're not getting promoted. Period.
2. Technical Decisions, Not Just Execution
Have you made architectural decisions that affected the team? Did you choose PostgreSQL over MongoDB for a feature and document why? Did you propose moving from REST to gRPC for an internal service?
Pull requests are execution. Design documents are SDE-2 currency.
3. Cross-Team Impact
SDE-1s impact their team. SDE-2s impact multiple teams. Have you:
- Built a library other teams now use?
- Driven a migration that touched 3+ services?
- Resolved an issue that was blocking another team?
4. Mentorship
Have you onboarded an intern or new joiner? Reviewed their PRs? Run a lunch-and-learn session on Kafka or system design?
This shows your manager you're not just a senior IC in waiting — you're already acting like one.
5. Reliability and Operational Excellence
Have you reduced on-call pages by improving a flaky service? Cut down deployment time? Improved test coverage on a critical path?
In 2026, with AI taking over a lot of routine coding, operational maturity is what separates senior engineers from juniors. Anyone can vibe-code a feature with Cursor. Fewer people can debug a memory leak in production at midnight.
Build Your Promotion Case 6 Months in Advance
Here's the timeline that actually works in Indian tech companies:
Month 1-2: The Conversation
Schedule a 1:1 with your manager. Don't make it about a raise. Make it about growth. Use these exact words:
"I want to understand what specifically I need to demonstrate to be considered for SDE-2 in the next cycle. Can we identify 2-3 concrete projects or behaviors I should focus on?"
Then write down what they say. Email them a summary. "Thanks for the chat. As I understood, the path forward involves [X], [Y], and [Z]. Let me know if I missed anything."
This document becomes your promotion contract.
Month 3-4: The Visible Project
Volunteer for or propose a project that has:
- Cross-team impact
- A design component (you write the doc)
- A measurable outcome (latency, cost, conversion)
If nothing like this exists on your team, create one. "I noticed our deploy pipeline takes 22 minutes. I think I can get it under 8. Can I take 2 weeks to scope this?"
Month 5-6: The Brag Document
Indian engineers are terrible at this. We're taught humility is a virtue. In promotion cycles, it's a career killer.
Maintain a running doc with:
- Projects shipped (with measurable impact)
- PRs that improved quality/reliability
- People you mentored
- Decisions you made
- Bugs you found in design reviews
- Tech talks or documentation you wrote
When promotion time comes, your manager has to argue your case in a room full of skeptics. Make their job easy.
The Salary Math: Is Promotion Even Worth It?
Brutal truth: internal promotion almost always pays less than switching companies.
Let's run the numbers. SDE-1 at ₹28 LPA in 2024 batch:
| Path | Outcome by May 2026 | |------|---------------------| | Stay, get strong rating, no promotion | ₹32-34 LPA (10-15% hike) | | Stay, get SDE-2 promotion | ₹42-48 LPA (50-70% jump) | | Switch to similar-tier company as SDE-2 | ₹48-60 LPA (70-110% jump) | | Switch to higher-tier company (FAANG) as SDE-2 | ₹55-80 LPA (95-185% jump) |
So why bother with internal promotion at all?
Three reasons:
- The title matters when you switch later. Going from SDE-1 to SDE-2 externally is way harder than negotiating SDE-2 to SDE-2.
- RSU vesting. If you've been at a place for 2 years, your stock is just starting to vest meaningfully. Leaving forfeits unvested equity.
- You actually like the work. Don't underrate this.
The smartest play in 2026? Optimize for promotion, then evaluate offers externally. You can check your salary benchmark on CareerLens to see what SDE-2s at your target companies are actually making, and use that data either to negotiate internally or to make a clean switch.
The Mistakes That Keep Engineers Stuck at SDE-1
I've seen these patterns dozens of times. Don't be these people:
The Quiet Achiever. Does great work. Never talks about it. Manager has nothing to write in the promo doc. Stays SDE-1.
The Ticket Closer. Closes 40 tickets a sprint. All small. None visible. Looks productive in dashboards. Invisible in promotion committee. Stays SDE-1.
The Hero Firefighter. Always on Slack at 11 PM solving prod issues. Manager loves them. Promotion committee asks "what did they build?" — silence. Stays SDE-1.
The Tech-Stack Tourist. Switches teams every 8 months chasing "interesting tech." Never owns anything long enough to show impact. Stays SDE-1.
The Refactor Obsessive. Spends 3 months rewriting the auth service in Rust because "the old code is bad." No business impact. Manager can't justify it in committee. Stays SDE-1.
What to Do If You're Stuck
If you've been SDE-1 for 2.5+ years and there's no clear promotion path, you're in dangerous territory. The longer you stay, the more the market questions why.
Here's the decision tree:
Step 1: Have the conversation with your manager. Direct: "What's preventing me from being promoted in the next cycle? I want specifics, not generalities."
Step 2: If the answer is fuzzy ("you need more impact," "just keep doing what you're doing"), that's a red flag. Your manager either can't or won't advocate for you.
Step 3: Give it one more cycle (6 months) with a written plan. If still no movement, start interviewing externally.
Step 4: Even if you plan to stay, interview externally anyway. Nothing motivates an internal promotion like a competing offer letter.
FAQ
How long does it take to get promoted from SDE-1 to SDE-2 in India?
The typical timeline is 2 to 3 years at most product companies. Anything faster than 18 months is rare and usually requires exceptional impact. Anything beyond 3.5 years suggests either company-specific issues or a need to switch.
Is SDE-2 the same across companies like Flipkart, Razorpay, and Microsoft?
Roughly yes, but with caveats. SDE-2 at Microsoft IDC or Google typically equals SDE-3 at smaller startups in terms of scope. Salary varies wildly: SDE-2 at Razorpay might be ₹45 LPA while SDE-2 at a smaller startup might be ₹30 LPA for similar work. Use CareerLens to benchmark levels across companies.
Should I switch companies if I'm not getting promoted?
If you've spent 2.5+ years as SDE-1 with no clear path forward, yes. The Indian tech market in 2026 still rewards external switching with 50-80% hikes for strong engineers. But don't switch just for money — make sure the new role has a clearer growth path.
Do I need to know System Design to get promoted to SDE-2?
Absolutely. SDE-2 promotion almost always involves either a design round in the internal promotion process or expectations to lead design reviews. If you can't explain why you'd use Redis vs Memcached or when to denormalize a database, you're not SDE-2 ready.
Bottom Line
- SDE-1 to SDE-2 is a mindset shift, not a tenure milestone. You get promoted when you're already operating at the next level, not after you "earn" it.
- Glue work won't get you promoted. Visible technical impact will. Pick projects with cross-team scope and measurable outcomes.
- Document everything. A brag doc isn't bragging — it's giving your manager ammunition to fight for you in calibration meetings.
- Have the explicit conversation with your manager 6 months before promotion cycle. Don't assume they know your goals.
- Internal promotion pays less than switching — but the title compounds. Optimize for promotion, then evaluate the market with full information.
The engineers getting promoted to SDE-2 this May aren't smarter than you. They're just clearer about what the game actually is. Now you are too.