What this guide replaces
A traditional resume is a marketing document for outsiders. A promotion packet is an evidence document for insiders. The audience already knows who you are and what you do; the job is to prove you have been operating one level above for 12 to 18 months. This guide gives you the Promotion Case Doc framework plus 5 real examples across IC, Staff, Manager, lateral, and cross-functional moves.
Internal promotions fail for 4 reasons in my tracking across 60 packets over the last 3 years: weak sponsorship (manager not in your corner), no paper trail (claiming you already operate at the next level with no evidence), unclear forward thesis (asking for a title with no proposal for what changes), and bad timing (submitting in a cycle where the org is not promoting). This guide covers the 3 you can control.
The document you build is called a Promotion Case Doc in most companies. Amazon calls it a PD doc, Google calls it a packet, and Meta calls it a promo doc. The shape is the same across companies: 2 to 4 pages, 5 sections, heavy on evidence and light on adjectives.
The Promotion Case Doc framework
5 sections, each with a distinct job. Do not reorder them; the logic builds from scope to behaviour to impact to signals to forward plan.
1. Scope expansion
Quantify how your scope grew in the last 12 to 18 months. Team size (direct and dotted line), budget, revenue under your ownership, number of customers, number of systems touched. Before and after numbers, not adjectives.
2. Level-above behaviours
List 3 to 5 specific projects where you already operated at the target level. For IC-to-Senior: projects where you set direction instead of executing someone else's plan. For Senior-to-Staff: cross-team efforts you drove without a manager title.
3. Impact metrics
Revenue moved, cost saved, latency cut, team velocity lifted, customers retained, incidents reduced. Each number tagged to a timeframe. Lifetime numbers are cheating; use rolling 12 months where possible.
4. Peer and stakeholder signals
Who supports the promotion and why. Direct quotes from peer reviews, 360 feedback, customer references. HR wants evidence that the level change is already visible to the people who work with you.
5. Forward thesis
What you will do with the new level in the next 2 quarters. This is the part most promotion packets skip. Without it, you are asking for a title; with it, you are proposing a trade where the company also wins.
5 worked examples
Names and numbers are changed; structure and tone are preserved. Each example is a trimmed version of a real packet that resulted in a promotion or internal move.
Example 1: IC-to-Senior Software Engineer (SDE-2 to SDE-3 at a product company)
Name: Arjun M. Current role: SDE-2, Checkout platform (2.5 years) Target role: SDE-3, same team Scope expansion (12 months): - Owned 2 additional services (payments retry queue, fraud score fallback). Services now: 5 (was 3). - Mentored 2 SDE-1s to first production launch; both now own a service each. - Represented the team in the quarterly architecture review board (previously my manager's seat). Level-above behaviours: - Drove the migration off the in-house rate limiter to envoy. Wrote the design doc, ran the RFC process across 4 teams, shipped in 9 weeks with zero customer-facing incidents. My manager signed off; he did not drive. - Caught and proposed the fix for the long-standing double-charge bug that had been open for 14 months. Estimated financial exposure resolved: 42 lakh INR annually. - Ran the on-call training for 6 new engineers. Avg p0 MTTR on this service dropped from 38 min to 21 min quarter-over-quarter. Impact (last 4 quarters): - Checkout success rate: 97.8 percent to 99.1 percent. - Median checkout latency: 820 ms to 340 ms. - Infra cost for the 3 services I owned most of the year: 18 percent reduction (11 lakh INR annually). Peer signals: - 9 of 11 peer reviewers rated me at SDE-3 on the "direction setting" dimension in the spring calibration. - Customer team lead: "Arjun is the person we escalate to when a payments partner acts up. He owns it." Forward thesis: - Next 2 quarters: drive the refactor of the subscription billing system. The current manager has already approved scope. I will need SDE-3 authority to commit design decisions without his review on every step.
Example 2: Senior-to-Staff Engineer
Name: Priya V. Current role: Senior Software Engineer, Data Platform (3 years) Target role: Staff Engineer, same platform Scope expansion (18 months): - Technical lead for 3 teams (data ingestion, warehouse, query layer). 14 engineers in orbit, 6 direct collaborators. - Budget influence: annual infra spend 2.3 crore INR. Cut 41 percent over 4 quarters via columnar format migration and cold-storage tiering. - Cross-org: led the data contract working group across platform, ML, and analytics engineering. Level-above behaviours: - Authored the north star architecture for real-time joins across domains. Adopted by all 3 teams, now in staged rollout. - Represented the company at 2 Data Council events and one internal deep-dive with the VP of Engineering. - Mentored 4 Senior Engineers through their quarterly goals; 2 were promoted in the last cycle. Impact: - Fresh data latency for analytics: 6 hours to 9 minutes end to end. - Query p95 on the warehouse: 14 seconds to 2.1 seconds. - Incident rate on ingestion: 3.2 per month to 0.4 per month. Stakeholder signals: - VP Engineering, 1:1 notes: "Priya already owns the Staff scope. The title is catch-up." - Analytics Director: "She is the person I think of when someone asks me what good data engineering looks like here." Forward thesis: - Take over the data-platform technical strategy doc from the current Staff (moving to a new org). Propose and drive the 2-year consolidation plan for the 3 warehouses we still run.
Example 3: IC-to-Manager (Senior Engineer to Engineering Manager)
Name: Rohit S. Current role: Senior Engineer, Growth team (3 years IC, 8 months dotted-line mentor) Target role: Engineering Manager, same team Scope expansion (12 months): - Grew the mentor circle from 1 to 4 direct-line mentees over the year. Ran weekly 1:1s with each. - Owned the team hiring loop: designed 2 interview questions now in the standard set, conducted 18 interviews, 3 hires closed. - Led the team's annual planning exercise (2025 Q4 planning doc). My manager stepped back. Level-above behaviours: - Ran the last 2 retros; identified and drove the switch from Jira to Linear that cut planning meeting time by 40 percent per sprint. - Handled a peer-conflict situation between 2 engineers with HR partnership. Both remain engaged; neither has left. - Built the team's career development template, now used by 2 other growth-adjacent teams. Impact (team-level): - Team velocity (shipped roadmap items): 14 to 23 per quarter. - 1:1 skip-level satisfaction score: 6.8 to 8.4 out of 10. - Team attrition: 2 in 2024, 0 in 2025 YTD. Peer signals: - 5 of 6 team members independently told my manager they would prefer me as their next manager. - Product counterpart on team: "Rohit is already acting as the EM; the title is the last piece." Forward thesis: - Next 2 quarters: stabilise the team headcount at 8, own hiring for 2 more Senior Engineers, and drive the team through the Q1 OKRs independently.
Example 4: Lateral transfer (Product to Platform team, same level)
Name: Kavya L. Current role: Senior Engineer, Mobile product team (2 years) Target role: Senior Engineer, Core Platform team This is a lateral move, not a promotion. The document is still needed because the receiving team has to justify the internal transfer to HR. Why this team: - Over 40 percent of my last 4 quarterly goals touched the platform layer (auth, notifications, analytics SDK). I know the codebase. - I filed 9 PRs to platform repos in 12 months; 7 merged. The top committer on the platform side was the EM of that team. Scope I bring: - Deep product-team empathy that platform teams often lack. Every platform API we shipped in the last year had at least one sharp edge for product engineers. I can be the bridge. - iOS and Android parity experience. Current platform team skews Android-heavy. Impact in current role: - Notification tap-to-open rate: 6.2 percent to 11.8 percent. - Cold start time on iOS: 1.8 seconds to 0.9 seconds. - Shipped the analytics-SDK v2 across both platforms, now used by 6 internal teams. Forward thesis: - First 90 days: shadow platform on-call, pick up 2 existing projects. Q2: own the cross-platform SDK consolidation effort end to end. No compensation or level change requested. Signals gathered: - Platform EM agreed to the transfer in principle. - Current manager agreed to a 6-week handover.
Example 5: Cross-functional promotion (Engineering to Product Engineering Lead)
Name: Vikram R. Current role: Staff Software Engineer, Payments (4 years) Target role: Product Engineering Lead, Payments (new role, hybrid of Staff + junior PM) Why this role exists and why me: - Payments product team has been running without a dedicated engineer-PM bridge for 8 months. Roadmap slippage is 23 percent quarter-over-quarter. A dedicated bridge is the fix, and I have been playing it unofficially. - In the last 4 quarters, I authored 11 PRFAQs alongside the PM team. 8 shipped. Scope expansion (12 months): - Co-owned the payments product roadmap with the PM lead. Ran 6 of the last 10 roadmap reviews. - Interviewed 14 enterprise customers alongside the Sales Engineering team. Converted 4 of those into case studies. - Led the pricing-model redesign: new model rolled out in March, driving 18 percent increase in ARPU. Level-above behaviours: - Built the payments analytics dashboard used weekly by the CRO, CPO, and VP Eng. Before this, the data lived in 4 different dashboards and reports. - Represented engineering at the monthly exec review. My manager stopped attending in January. Impact: - Payment success rate: 98.2 to 99.4 percent. - Chargeback rate: 0.8 to 0.3 percent. - Revenue attributable to payments improvements in 2025 YTD: 4.1 crore INR. Forward thesis: - Take over roadmap ownership for the payments product in full, reporting to the VP Eng with a dotted line to the CPO. First 2 quarters: deliver the stablecoin-payments experiment plus the unified reconciliation dashboard.
What HR looks for
HR is not your manager. In the calibration meeting they need artifacts they can point to when the conversation gets political.
Written record of level-above work
HR wants a paper trail. Screenshots of 1:1 notes, quarterly goals, peer reviews, and slack threads where you drove decisions across teams. Verbal "I do it already" does not survive calibration.
Peer and stakeholder endorsements
3 to 5 peer-level colleagues, 1 cross-functional stakeholder (PM, design, data), 1 skip-level. Direct quotes, not generic praise. HR filters out anything that could apply to anyone.
Quantified business impact
Money, time, or risk moved. If you cannot connect your work to a number, you are not ready for the next level. Recruit a finance partner or your PM to help translate.
Gap analysis against the next-level rubric
Most companies publish a level rubric internally. Print it, highlight evidence for each competency at the target level, flag the 1 or 2 gaps you are actively closing. Honesty wins here; HR trusts candidates who name their gaps.
Manager sponsorship
A promotion packet without your manager as a sponsor is dead on arrival. If your manager is neutral, fix that first before writing anything else. The packet is the artifact; the sponsorship is the decision.
Timing the promotion packet
Promotion cycles run on a fixed cadence at most mid-size and large companies: every 6 months or every 12 months. Submitting late in the cycle is worse than submitting in the next one. Here is the timeline that works.
6 months before
Start tracking. Keep a running doc of level-above work, quantified wins, and stakeholder moments. Memory fails; the doc does not.
3 months before
Draft the first version of the promotion case doc. Share with your manager in the next 1:1. Ask for explicit feedback: gaps, weak spots, counter-examples.
6 weeks before
Gather peer and stakeholder quotes. Send a short email asking: "I am putting together my promotion case. Would you write 2 sentences on a specific example where we worked together?" Most people say yes.
2 weeks before
Final polish. Cut anything that is not load-bearing. Verify every number with the actual dashboard or tool. Send to manager with a requested submission date.
Calibration week
Be reachable. Your manager may need a data point or quote. Do not ask for updates; they will tell you when it is decided.
If your company runs annual cycles, double every interval above. The rule is: 6 months of evidence gathering, 2 months of drafting and sponsor alignment, 2 weeks of final polish.
External references
Frequently asked questions
Do I need a resume for an internal promotion?+
How long should the Promotion Case Doc be?+
Can I skip the manager and go to HR?+
What if my manager is neutral on my promotion?+
How do I handle peer jealousy or internal politics?+
Is it ok to ask for a level check instead of a full promotion?+
What if I get rejected?+
Can I use this framework for an internal transfer, not a promotion?+
Build the resume behind your promotion case
Even an internal move benefits from a clean, quantified resume attached to the packet. ResumeBuildz gives you scope-and-impact prompts so every bullet pulls its weight.