The most common career question from early-career Indian engineers: "I've been SDE-1 for 18 months — how do I get promoted?" The answer isn't to work harder at your current level. It's to consistently demonstrate you're already operating at the next level.
This guide demystifies promotion at India's top product companies — from what your manager actually writes in your promotion packet, to how to have the conversation without sounding entitled.
Promotion Timelines at Major Indian Tech Companies
| Company | Typical SDE-1 → SDE-2 Timeline | Process | Salary Jump |
|---|---|---|---|
| Amazon India (L4 → L5) | 18–30 months | Promotion brief, bar raiser calibration, VP approval | +40–60% |
| Google India (L3 → L4) | 18–24 months | Peer/self review, manager nomination, promotion committee | +35–50% |
| Microsoft India (SDE-1 → SDE-2) | 18–30 months | Annual review cycle, manager + skip-level nomination | +30–45% |
| Flipkart (SDE-1 → SDE-2) | 18–24 months | Half-yearly reviews, calibration panel | +35–55% |
| Swiggy (SDE-1 → SDE-2) | 15–24 months | Quarterly OKR reviews, manager nomination | +30–50% |
| CRED / Razorpay | 12–20 months | Manager + peer review, promotion bar set per cycle | +35–55% |
| Series A/B Startups | 9–18 months | Often informal; manager decides based on impact | +25–45% |
What Your Manager Actually Evaluates
In most Indian product companies, promotion packets cover 4–6 dimensions. Here's what they are and what "SDE-2 level" looks like for each:
| Dimension | SDE-1 (Current Level) | SDE-2 (Target Level) |
|---|---|---|
| Technical Scope | Owns a component; implements features defined by seniors | Owns a module end-to-end; defines technical approach for medium-complexity features |
| Independence | Needs frequent check-ins; asks for direction on ambiguous tasks | Takes an ambiguous requirement, breaks it down, and drives it to completion independently |
| Quality of Work | Code works; occasional edge cases missed; design needs review | Code is production-ready first time; proactively handles edge cases; design docs are thorough |
| Team Impact | Good individual contributor | Actively helps teammates; unblocks peers; improves team processes (runbooks, documentation) |
| Execution & Delivery | Meets deadlines when requirements are clear | Estimates accurately; flags risks early; delivers even when requirements shift |
| Communication | Updates manager when asked | Proactively communicates status, risks, and decisions; writes clear design docs |
The 6-Step Promotion Playbook
Step 1: Have the Explicit Conversation (Month 1–3)
Most Indian engineers never explicitly ask their manager what SDE-2 looks like for them specifically. Schedule a 1:1 specifically to ask: "What would SDE-2-level performance look like for me in the next 6–12 months?" Write down the answer. This conversation also signals ambition without entitlement.
Step 2: Pick a Signature Project (Month 2–4)
Promotion packets need concrete evidence. Pick one project in the next quarter that you'll own end-to-end — from requirements clarification to design, implementation, testing, rollout, and post-launch monitoring. This becomes the centrepiece of your promotion case. Don't spread thin across 5 medium tasks; go deep on one high-impact one.
Step 3: Build Visible Breadth (Ongoing)
Promotions require "cross-team visibility" at most companies. Ways to build this: review design docs from adjacent teams, contribute to on-call rotation even if not required, present in team or org-wide tech talks, write internal wiki docs that others use. Your manager needs to be able to cite examples from people who aren't your direct teammates.
Step 4: Document Your Impact (Ongoing, Every 2 Weeks)
Keep a running "brag document" — a private record of: features shipped and their business impact, bugs caught in code review that would have caused incidents, documentation and tooling you improved, junior engineers you helped, processes you improved. Most engineers forget their own wins by review time. Your manager can't advocate for you if they can't remember specifics.
Step 5: Get Peer Signals Aligned (Month 10–14)
In most Indian product companies, peer reviews are part of the promotion process. Ensure you have at least 2–3 cross-team peers who have directly observed your SDE-2-level contributions. Don't just wait to be reviewed — proactively help others in ways that are visible and memorable. Ask if you can contribute to their design docs or review their architecture choices.
Step 6: Close the Loop Before Review Season (Month 14–18)
Two months before the review cycle, have a direct conversation with your manager: "Based on what we discussed earlier, I believe I've been operating at SDE-2 level. What's your assessment, and what should I do differently before the cycle closes?" This gives your manager the cue to write your promotion packet and gives you time to fill any gaps.
The Brag Document — Build This Now
Every engineer promoted in India has (knowingly or unknowingly) built a version of this. Here's what to track:
-
Features shipped: Name, impact (users affected, latency reduced, revenue unlocked), and your specific contribution beyond just "I coded it"
-
Incidents prevented: Bugs you caught in PR review that would have caused customer-facing issues or downtime
-
Team leverage: Documentation, runbooks, tooling, test frameworks you created that your teammates now use regularly
-
Technical decisions: Times you drove the technical approach decision (even if small), got buy-in, and it worked well
-
Mentorship moments: Junior engineers you helped get unblocked or ramp up faster
-
Cross-team collaboration: Any work you did with teams outside your immediate team — even small contributions count
-
Quantified metrics: Wherever possible: "reduced P95 latency from 400ms to 150ms", "reduced on-call alerts by 60%", "shipped feature used by 2M users"
The Promotion Conversation — Word-for-Word Scripts
Things That Kill Promotions in India
| Mistake | Why It Kills Your Promotion | Fix |
|---|---|---|
| Only visible to your direct manager | Calibration panels ask for cross-team evidence; your manager can't invent it | Actively create opportunities for adjacent teams and senior engineers to observe your work |
| Excellent individual contributor, zero team multiplier | SDE-2 requires demonstrable leverage beyond your own output | Proactively help, write docs, review others' designs even when it's not required |
| Delivering in isolation with no communication | "Delivery" without visibility = no promotion evidence; managers can't advocate for work they didn't observe | Send short updates proactively; share design docs before they're finished to get input |
| Waiting to be "ready" before asking for promotion scope | You'll be stuck doing SDE-1 tasks with SDE-1 impact | Ask your manager for one SDE-2-scope project in the next quarter, explicitly |
| Avoiding ownership of messy/risky problems | Promotions go to people who take on hard, ambiguous things — not just clean features | Volunteer for on-call, legacy system cleanup, or cross-team migration projects others avoid |
| Not understanding company-specific promotion criteria | Amazon's Leadership Principles, Google's BOLD criteria, Flipkart's competency bars are different | Study your company's official SDE-2 criteria; ask your manager or HR for the rubric |
If You're Stuck: The 18-Month Rule
Here's the honest truth that Indian career advice rarely says out loud:
SDE-1 at Company A → SDE-2 at Company B: How to Position It
| On your resume | In the interview | In the offer negotiation |
|---|---|---|
| Lead with impact, not title: "Led end-to-end implementation of [X] feature, reducing latency by 40%" | "I've been operating at SDE-2 scope for the past 8 months — [examples]. I'm looking to have that formalized in a new role." | "My current comp is ₹[X] and I'm targeting SDE-2 roles; based on market rates, I'm looking at ₹[Y] as a base." |
Promotion Checklist — Self-Assessment
Rate yourself honestly on each dimension before your review cycle:
| Criterion | Check |
|---|---|
| I have owned at least one feature end-to-end (design → prod → monitoring) in the last 6 months | ☐ Yes / ☐ No |
| I have written at least one design doc that was reviewed by senior engineers | ☐ Yes / ☐ No |
| I can cite 2+ specific instances where I helped unblock a teammate or improved team velocity | ☐ Yes / ☐ No |
| I have at least 2 peers from other teams who have directly observed my SDE-2-level work | ☐ Yes / ☐ No |
| I have had an explicit conversation with my manager about promotion criteria and received specific feedback | ☐ Yes / ☐ No |
| My brag document has 5+ concrete examples with quantified impact from the last 6 months | ☐ Yes / ☐ No |
| I have proactively taken on something messy or risky that others avoided | ☐ Yes / ☐ No |
| I know the specific SDE-2 rubric at my company (not just "general leadership" but company-specific criteria) | ☐ Yes / ☐ No |