Study Notes by Niladri & AI

sec11-promotion-packets

9 min read

Promotion Packets

selt career promotion staff-engineering

Status: Notes complete

Overview

Getting the Staff engineer title at your current company requires more than doing good work — it requires actively building the case for your promotion and navigating the organizational processes that govern it. Will Larson’s core argument is that most engineers who don’t get promoted are not promoted because they waited for someone to notice them, not because their work wasn’t good enough. The promotion packet is the primary tool for making your case visible, legible, and compelling to the people who decide.

Core Concepts

What Is a Promotion Packet?

A promotion packet is a written document — typically 1 to 4 pages — that makes the case for your promotion to Staff engineer. Crucially, you write it, not your manager. Your manager may help you refine it, and they will almost certainly need to present or champion it, but the work of assembling evidence and articulating the case is yours.

A strong promotion packet covers four things:

  1. What you did — Concrete work: projects led, decisions made, systems built or improved, problems solved
  2. The organizational impact — What changed because you did it? Teams unblocked, reliability improved, costs reduced, strategic options opened
  3. Alignment with the Staff-level criteria — Explicit mapping to your company’s career ladder, quoting the criteria your work satisfies
  4. Future direction — What you plan to do as a Staff engineer that you can’t do yet as a Senior

The packet is documentation of a case that already exists. You cannot write a compelling packet for work you haven’t done yet.

Do the Work First

The most important insight about promotion packets: the packet is documentation, not strategy. You need to do Staff-level work for 1 to 2 performance cycles before you write the packet — not as a result of writing it.

This means:

  • Taking on scope that crosses team boundaries
  • Driving alignment on technical direction across multiple teams
  • Owning problems end-to-end, including the organizational and communication work, not just the technical work
  • Making your impact visible in ways that others in the organization can observe and describe

If you’re waiting to be “given” Staff-level scope before you do Staff-level work, you’re likely waiting indefinitely. The work tends to come before the title, often by a year or more.

The 1-2 Year Reality

Larson is explicit that most engineers do Staff-level work for 1 to 2 years before receiving the title. This is not a failure — it is the norm. The job of that period is to:

  1. Accumulate a track record of Staff-level impact
  2. Make sure the right people (sponsors, manager, skip-level) are aware of that impact
  3. Build the organizational relationships that make your promotion credible

Expecting the title to arrive quickly after you start doing Staff-level work is a setup for frustration.

The Two-Budget Problem

Even if your work clearly meets the Staff bar, you may not get promoted. This is the two-budget problem:

  • Your performance budget — This is met when you are clearly doing Staff-level work
  • Your headcount budget — There needs to be a Staff slot available on your team or in your organization

If there is no open Staff slot (because Staff engineers are already at the target ratio on your team, or because headcount is frozen), you will not be promoted regardless of your performance. This is not a reflection of your quality — it’s an organizational constraint.

Implications:

  • Understand your organization’s current Staff engineer density on your team
  • Talk to your manager honestly about whether a slot is realistically available in the next 1-2 cycles
  • If the answer is “probably not for a long time,” that’s information about whether you should stay or find your path at another company

The Career Ladder Alignment

Every promotion decision is evaluated against your company’s career ladder — the written criteria that define what Staff-level performance looks like. The problem is that most engineers don’t study their career ladder carefully enough to write against it.

What to do:

  1. Read the Staff engineer criteria on your company’s ladder carefully
  2. Identify the 3-5 criteria that most differentiate Staff from Senior
  3. Ensure your recent work provides clear evidence for each of those criteria
  4. In your promotion packet, explicitly quote the criteria and map your work to them

Do not assume your manager or the promo committee will make the mapping for you. Make it explicit.

The Criteria Vary by Company

“Staff engineer” means different things at different companies. At some companies it requires broad technical leadership across many teams. At others it requires deep technical expertise in a specific domain. Know what your company’s bar is, not a generic definition.

Advocates and Sponsors

A promotion packet alone is not enough. Someone needs to champion your case in the promo committee meeting where decisions are made — and they need to be both credible and present.

The difference between a sponsor and an advocate:

  • Sponsor — An influential person who actively speaks up for you and puts their credibility on the line on your behalf
  • Advocate — Someone who knows your work well enough to describe it accurately when asked

You need at least one sponsor in the room during the promo discussion. Ideally this is your manager, plus at least one senior stakeholder who has worked with you and can speak to your impact.

How to develop sponsors:

  • Identify which senior engineers or managers regularly interact with your work
  • Make sure they have direct visibility into your most impactful contributions
  • Don’t rely on your manager to relay your work — if a VP-level stakeholder worked with you on something significant, they should know your name and what you did

Common Failure Modes

1. Waiting for Someone to Notice

The most common failure. The assumption is: “If I do good work, someone will see it and promote me.” At most companies, promotions require an explicit case to be made. Nobody will write the packet for you; nobody will advocate without being asked.

2. Writing About Work That Impacted You, Not the Org

A compelling promotion packet documents impact on the organization — other teams, users, the company’s strategic position. Work that was personally challenging, technically interesting, or important to your immediate team is not sufficient if it had no broader organizational footprint.

3. Not Mapping to the Specific Criteria

Generic descriptions of good work (“led the backend team,” “improved reliability”) don’t make a strong case. You must map explicitly to the language of your company’s career ladder: “Demonstrated technical leadership across teams by [specific thing] — this satisfies the ‘[criterion name]’ criteria on the ladder.”

4. No Advocates in the Room

Even a perfect packet fails if nobody who knows your work is in the room during the discussion. Promo committees ask questions; someone needs to answer them credibly. Identify your advocates early and brief them before the cycle closes.

5. Confusing Busyness with Impact

Doing many things is not Staff-level performance. Staff-level performance is doing the right things — the ones that move organizational levers — and doing them with the influence and judgment that a Staff engineer brings.

Structuring the Packet

A practical 4-section structure for the promotion packet:

Section 1: Recent work and impact (the core)
3-5 projects or initiatives from the last 1-2 cycles. For each: what you did, what the impact was (measured where possible), and what was Staff-level about your approach (scope, judgment, influence, organizational complexity).

Section 2: Criteria alignment
A table or list mapping your work to each Staff-level criterion on the career ladder. Be explicit and quote the criteria.

Section 3: Organizational visibility and influence
Evidence that other parts of the organization recognize your impact — cross-team initiatives, decisions you influenced, partners who can speak to your work. This is where sponsor relationships show up.

Section 4: Future direction
What you will do as a Staff engineer. This should not be a wish list — it should be a concrete statement of the next-level problems you’re positioned to solve. This helps the committee see the promotion as forward-looking, not just a retroactive reward.

The Relationship Between the Packet and Finding Your Sponsor

The promotion packet and the sponsor are not separate tracks — they reinforce each other. The packet gives your sponsor the language and evidence they need to champion your case credibly. The sponsor gives the packet a human voice in the room. Without both, the case is significantly weaker.

Practical sequencing:

  1. Do Staff-level work for 1-2 cycles
  2. Ensure key sponsors have direct visibility into that work
  3. Begin drafting the packet with your manager’s input
  4. Share a draft with your primary sponsor and ask: “Does this accurately capture my impact? What would you add or strengthen?”
  5. Finalize and submit with your manager as the official champion

Key Takeaways

  1. You write the packet — Do not wait for your manager to initiate this. The promotion case is yours to build and document.
  2. The packet is documentation, not strategy — Do Staff-level work first for 1-2 cycles; the packet captures a case that already exists in your track record.
  3. Expect 1-2 years of Staff-level work before the title — This is the norm, not a failure. Use that time to accumulate impact and visibility.
  4. The two-budget problem is real — Performance and headcount are separate gates. Understand whether a slot is actually available on your team.
  5. Map explicitly to your company’s criteria — Quote the career ladder. Do not assume the committee will make the mapping for you.
  6. Organizational impact is what counts — Work that was hard for you personally but had no broader footprint does not strengthen the case.
  7. Sponsors are essential — Someone credible needs to speak for you in the room. Identify them early, make sure they have direct visibility into your best work.
  8. Brief your advocates before the cycle closes — Don’t assume the people who’ve worked with you remember the details. Give them a short brief on what you did and why it mattered.
  9. The “nobody noticed” failure is the most common — At most companies, doing good work quietly is not sufficient. Making the case is an active, explicit act.
  10. Know your company’s specific bar — “Staff engineer” varies significantly across organizations. Study your company’s ladder and calibrate to it, not to a generic definition.

Last Updated: 2026-05-30

Graph View

Backlinks