Promotion-Ready Packets and Promo Docs at FAANG

Promotions at FAANG and engineering-mature companies aren’t earned through tenure; they’re earned through documented impact. The “promo packet” — a written document presenting your case for promotion — is the central artifact in the process. Done well, it’s the difference between getting promoted on schedule and stalling at the same level for years. This guide covers what a promo packet looks like, when to start preparing, what hiring committees look for, and how to navigate the political dynamics of the promotion process.

How Promotions Actually Work at FAANG

Standard structure across major companies:

Manager initiates. Your manager decides you’re ready for promotion (or you advocate strongly for it).
Packet preparation. Either you or your manager (depending on company) drafts a promo packet documenting your impact.
Calibration meeting. Multiple managers / senior engineers review packets across many candidates and decide who’s promoted in the cycle.
Approval. Higher-level approval (director, VP) finalizes promotions.
Communication. Decisions communicated; promotions effective at next compensation cycle.

The committee is the bottleneck. Even if your manager advocates strongly, the committee can deny. Strong packets help your manager advocate effectively.

What a Promo Packet Contains

Executive summary

2–3 sentences. “I’m requesting promotion to [target level] based on [scope evidence]: I’ve owned [systems], delivered [outcomes], and demonstrated [next-level signals] over the past [time period].”

Impact stories (3–5)

The core of the packet. Each story:

Title: short, descriptive (e.g., “Led migration of payments service to async architecture”)
Context: 2–3 sentences setting up the situation
Your role: specifically what YOU did (not the team)
Outcome: measurable impact, with numbers
Scope signal: why this exercises next-level scope

Stories should collectively cover the dimensions the next level expects: technical depth, scope, leadership, cross-functional impact.

Self-assessment

How you measure against the next-level rubric. Each company has explicit promotion criteria; your packet should map your work against them point by point.

Manager’s case

Your manager’s view of your readiness. Sometimes part of the packet, sometimes separate. Includes their advocacy and any nuance about your performance.

Peer feedback

Calibration committees often want feedback from multiple peers and cross-functional partners. Sometimes solicited as part of the packet; sometimes via separate 360 process.

What Calibration Committees Look For

Sustained impact at the higher level

Committees promote engineers who’ve already been operating at the next level. The signal is consistent: 6+ months of demonstrably next-level work. Single big projects don’t count if your typical work is at the current level.

Specific scope expansion

How has your scope grown? Multiple new responsibilities, larger systems, more cross-team work. The committee wants to see “this person has outgrown their current level.”

Multiplier impact

For senior+ promotions especially, the question is: how have you made others more productive? Mentorship, tooling, process improvements, technical leadership. Senior+ levels are about leverage, not just personal output.

Calibration vs cohort

Committees promote against cohort: are you stronger than other candidates being considered? Some cycles have many strong candidates; some have few. Calibration is partially independent of your effort.

When to Start Preparing

6–12 months before target promotion cycle

Start tracking impact systematically. Maintain a brag doc with each project’s:

Scope and your specific role
Outcomes with metrics
Cross-team / cross-functional dimensions
Lessons learned

Update monthly so details don’t fade. By promo time, you have 12+ project entries to draw from.

3 months before submission

Discuss readiness with your manager. “I’m targeting promotion in [next cycle]. What signals would they look for? What gaps should I address?” Their answer tells you whether to push for the cycle or wait.

1 month before submission

Draft the packet. Iterate with your manager. Get peer feedback. Make sure the packet’s narrative is coherent: clear thesis, supporting stories, alignment with rubric.

Submission

Final packet delivered to your manager. They synthesize their case and yours, present at calibration.

Common Promo Packet Mistakes

Listing every project

Quantity isn’t quality. 3–5 strong stories beat 12 weak ones. Calibration committees skim; the strongest stories must land in the first 30 seconds.

Vague impact

“Improved system performance” — by how much? “Led the team” — what specifically did you do? Calibration committees discount vague claims; specifics are signal.

Using “we” instead of “I”

The packet evaluates YOUR impact. Use “I” consistently. “We” hides whether you contributed substantially or just participated.

Narrative that doesn’t match the level rubric

If the next level requires “owns multi-team initiatives,” your packet must include multi-team initiative work. Mismatch between claimed scope and rubric scope kills packets.

Relying on manager advocacy without strong packet

Your manager argues your case to the committee. A weak packet limits how effectively they can advocate. Strong packet enables strong advocacy.

Submitting too early

Submitting before you’re ready leads to rejection, which makes the next cycle harder. Wait until 6+ months of consistent next-level work has been observed.

Submitting too late

Waiting “one more cycle” to be sure leaves promotion years behind your work. If you’ve been operating at the level for 12+ months, push for the promo even if not perfect.

The Politics of Promo Cycles

Manager advocacy strength

How hard your manager pushes for you matters. A new manager may be less invested; a manager who’s leaving has less leverage. Build the relationship; don’t assume default advocacy.

Committee composition

Who’s on the calibration committee for your level? Their domain expertise and biases affect outcomes. Some committees favor specific work types (e.g., technical depth) over others (e.g., cross-functional).

Cycle dynamics

Some cycles are “tight” (few promotions due to budget); others are “loose” (more promotions). Timing matters; ask your manager about cycle dynamics before submitting.

Sponsor effect

Senior engineers and managers who advocate for you in calibration outside your direct chain of command help. Build relationships with engineers above your manager who’ve seen your work.

What to Do If Denied

Get specific feedback

“What specific gaps led to the denial?” Manager should have specific feedback from the committee. Vague feedback (“you’re not quite ready”) is unhelpful; push for specifics.

Address the gaps explicitly

If feedback is “needs more cross-team scope,” seek cross-team projects. If “needs more technical depth,” push for harder technical work. Make the next packet’s improvements visible.

Consider external moves

Repeated denials despite strong work may signal systemic issues at the company. External offers often come with level bumps that internal promo cycles don’t provide.

Don’t give up on the company immediately

One denied cycle isn’t fatal. Two denied cycles is a stronger signal. Three is “leaving is faster than staying.”

Frequently Asked Questions

How long does promotion typically take at FAANG?

L3 to L4: 1–2 years. L4 to L5: 2–4 years. L5 to L6: 3–5+ years. L6 to L7: variable, often 5+ years. Each level represents real scope expansion. Tenure-based promotions are rare; you have to earn each level.

What’s the right level of self-promotion in the packet?

Confident, specific, evidence-based. “I led the migration that reduced p99 latency 60%” is appropriate. “I’m the best engineer on the team” is too much. Let the data speak; provide quotes from peer feedback that support your case rather than self-praise.

Should I argue with denied promotion decisions?

Carefully. Asking for specific feedback is appropriate; pushing back on the decision rarely changes outcomes and damages relationships. Use the feedback to improve for next cycle. If the feedback feels unjust, escalate to skip-level (your manager’s manager) once professionally; don’t litigate repeatedly.

How does promo work at startups vs FAANG?

Less formal at startups. Often manager-driven decisions without explicit committee process. Compensation adjustments may be more flexible; promotions less rigorously calibrated. Both have pros and cons: FAANG is more predictable but slower; startups are faster but more arbitrary.

What’s the relationship between promo packets and behavioral interview stories?

The same source material. Your brag doc feeds both. The framing differs: promo packets emphasize next-level scope and rubric alignment; behavioral stories emphasize STAR + reflection. The underlying projects are the same. Strong engineers maintain a brag doc that powers both promo cycles and external interviews simultaneously.