Understanding How Promotions Actually Work in India
At most Indian product companies (Flipkart, PhonePe, Razorpay, CRED, Zepto, Swiggy, etc.), promotions are decided in a calibration meeting attended by your manager, skip-level manager, and peer managers from other teams. Your manager advocates for you in this room. Your self-review is input — not the decision.
| Company Type | Who Decides Promotion | Where Self-Review Matters |
|---|---|---|
| Indian product company | Calibration committee (your manager + peers) | Evidence for your manager to use in calibration; doesn't go to committee directly |
| FAANG India office | Promotion committee (peers + seniors outside your team) | Packet reviewed directly — quality of writing matters significantly |
| Indian IT services | BU head + HR, based on project billing and utilization | Less relevant; billing utilization and project ratings dominate |
| Funded startup (50–200 person) | Founder/CTO directly for senior roles | Visibility and relationship with founders matters most |
The Year-Round Promotion Preparation Calendar
How to Write a Self-Review That Actually Helps You Get Promoted
Most self-reviews are written in one of two failing patterns:
The Activity List: "I built the payment retry feature, fixed 12 bugs, participated in on-call rotation..." — lists what you did, not what changed because of what you did.
The Humble Minimizer: "I could have done better at communication. I'd like to improve my documentation." — volunteering negatives without being asked. This is not humility; it's evidence against yourself.
The Impact-First Self-Review Structure
| Section | What to Write | What Not to Write |
|---|---|---|
| Top Impact | "My refactoring of the checkout module reduced P95 latency 43% and unblocked 2 dependent teams from shipping their features." | "I worked on the checkout refactoring project." |
| Scope | "I led the design and delivered execution for X — coordinating 3 engineers and presenting to the Director of Payments." | "I contributed to the design of X." |
| Business Impact | "This change directly improved payment conversion by 1.2% which at our scale means ~₹8Cr/month in additional successful transactions." | "This improved performance." |
| Growth Areas | Only address if explicitly asked. If asked, pick one real area and frame it as actively improving: "I've been working on communicating technical decisions earlier to cross-functional stakeholders." | Volunteering multiple weaknesses unprompted. |
Self-Review Template (Copy This)
What I did: [1-2 sentences describing what you actually built/changed/led]
Impact: This resulted in [specific metric improvement — latency, conversion, revenue, engineering efficiency]. At our current scale, this translates to [business outcome: ₹X saved/earned, Y% improvement in user metric, Z fewer incidents per month].
Scope I operated at: I [led / was the primary owner / coordinated across] [teams/stakeholders], which required me to [specific next-level behavior: make architectural tradeoffs, prioritize competing requirements, influence without authority, etc.].
I also [secondary contribution #1] and [secondary contribution #2].
Feedback received: [Quote or paraphrase specific positive feedback from stakeholders, if you have it.]
Managing Your Manager Before the Appraisal
The 1:1 Before the Review (60 Days Out)
From what you've seen this year — what's the strongest case for me? And is there anything you think the calibration committee might push back on?
I want to use the next 8 weeks to strengthen the evidence where there are gaps."
The Sponsorship Conversation
A sponsor is someone senior — ideally your skip-level manager or a tech lead who has visibility into calibration — who will say your name positively in the room where the decision is made. This is different from a mentor who gives you advice.
[After they engage positively:]
"I'm working toward a promotion this cycle. If you think the work I've done on [X] demonstrates [next level behavior], I'd really appreciate you sharing that perspective in the calibration discussion."
Visibility Tactics That Actually Work in Indian Companies
| Tactic | Why It Works | How to Do It |
|---|---|---|
| Written impact updates | Managers can copy-paste your updates into calibration slides | Send a weekly 3-bullet Slack message: "This week I did X, impact was Y, next week I'll do Z." |
| Present in team meetings | Skip-level visibility; you become associated with your work's success | Volunteer to present demos, retros, or design reviews in all-hands or multi-team meetings. |
| Cross-team projects | Multiple managers know your work → multiple advocates in calibration | Say yes to projects that touch other teams; document your contribution clearly. |
| Document your decisions | RFC/design docs are promotion artifacts — they show next-level thinking | Write a short design doc (even 1 page) for any significant decision you own. |
| Onboard and help others | Shows leadership and is explicitly noted at senior+ levels | Be the person who helps new joiners ramp up. Mention this in your self-review. |
Promotion Traps to Avoid
Most Indian managers won't proactively say "you're ready for promotion — let me push for it." You need to initiate the conversation. Managers who advocate most strongly are the ones whose engineers made the ask explicit.
Strong individual execution is necessary but not sufficient for promotion beyond SDE2. Calibration committees look for evidence that you operate at the next level — which usually involves cross-team impact, influence without authority, or technical leadership beyond your own tickets.
Tenure does not create promotion entitlement at Indian product companies. The question is not "how long have you been at this level?" but "are you already operating at the next level?" Show evidence of next-level behaviors, not a time count.
Your manager is managing 5–8 other engineers and doesn't track every win you have. If you don't document your impact, it doesn't exist for them. A win you don't communicate is a win that doesn't count in calibration.
If your manager says "not this cycle," get specifics: "What would I need to demonstrate in the next cycle? Can you name one project or one behavior change that would shift your assessment?" Vague feedback is not actionable. Push for the specific gap.
After the Review: Salary Negotiation at Raise Time
Even when you get promoted, the default raise offered is often below market. Appraisal time is one of the two best moments to negotiate salary (the other is during an external offer process).
I've been looking at market data for [SDE3 / Senior Engineer] roles at companies like [Razorpay / PhonePe / Zepto], and the band I'm seeing is ₹[X–Y]L. The raise to ₹[current] puts me at ₹[amount], which is [below/at the lower end of] that range.
Is there room to get closer to ₹[target]? I want to continue building here long-term, and I want the compensation to reflect that commitment on both sides."