Promotions Are Legal Cases, Not Gifts
At most large tech companies (Google, Meta, Amazon, Microsoft, etc.), promotions are not decisions made by your manager. They are decisions made by a calibration committee — a group of senior engineers and managers who have never worked with you, reviewing a written document about your work.
Your manager is your advocate, not your judge. And like any advocate, they can only argue as well as the evidence you give them.
Anatomy of a Promotion Packet
A typical packet contains three components:
1. Impact Statement
A structured narrative of your contributions over the past 6–12 months, written at the level you are being promoted to, not the level you are at. This is the most important section. It should answer: "Why is this person already operating at the next level?"
2. Peer Feedback
Quotes from 3–5 colleagues who can speak to your technical leadership, cross-team influence, and judgment. The committee discounts generic praise ("great to work with") and weights specific, technical observations ("She identified a race condition in our distributed lock implementation that would have caused data corruption under load").
3. Gap Analysis / Level Rubric Alignment
Most companies publish internal engineering level rubrics (e.g., "Staff engineers drive technical direction across multiple teams"). Your packet should explicitly map your work to each rubric dimension. Do not make the committee infer the connection — state it directly.
How to Help Your Manager Win
Draft the packet yourself. Your manager is busy. If you hand them a first draft of your impact statement, they will refine it rather than write it from scratch. This also ensures your framing is accurate — you know your work better than anyone.
Select peer reviewers strategically. Choose peers who:
- Have worked with you on technically complex problems (not just pleasant interactions).
- Are at or above the level you are targeting (their credibility matters to the committee).
- Can speak to cross-team impact, not just within-team contributions.
Start 6 months early. The most common reason promotion packets fail is insufficient evidence of operating at the next level. If you want to be promoted in December, you need to be doing Staff-level work in June — and documenting it. Talk to your manager in Q2 about what "Staff-level" looks like for your specific team and org.
Interviewers at Staff+ levels often ask: "How do you think about your own career growth?" The weak answer describes courses taken or certifications earned. The strong answer demonstrates self-awareness about scope: "I track my impact against the Staff rubric quarterly. Right now I'm strong on technical execution but I'm deliberately taking on more cross-team coordination work to close the gap on organizational influence." This signals that you understand the difference between Senior and Staff, and that you manage your career with the same rigor you apply to engineering problems.