Promotion Tool

Turn your wins into a promotion case

A calibration committee is going to read 30 promo packets in an afternoon. They'll spend two minutes on yours. This tool turns your raw achievements into a tight, structured packet they can actually skim and remember.

✓ 100% client-side✓ Nothing leaves your browser✓ Free, no signup
About You
Scope Expansion

What you're actually responsible for — systems, teams, surfaces.

Evidence you're working at the bar of the level above. This is the heart of the case.

Key Achievements

Lead with the outcome, not the project. Use numbers wherever you can — revenue, latency, headcount unblocked, time saved.

Achievement 1
Achievement 2
Achievement 3
Cross-Functional Reach

Cross-team RFCs, working groups, calibrations you've sat on, internal talks given.

Closing Statement (Optional)

Your Promo Packet

Fill in the form on the left. Your packet will build itself here as you type.

How to write a promo packet that actually wins

Calibration committees see dozens of cases at every cycle. The good news is they're not looking for a long document. They're looking for evidence, fast. A few things that consistently separate strong cases from weak ones:

Lead with outcomes, not activities

"Built a new dashboard" is an activity. "Cut on-call alert noise by 62%, reducing engineer burnout reports by half" is an outcome. Every bullet should answer: so what? If the so-what isn't obvious, the bullet doesn't belong.

Numbers earn their place

You don't need numbers on every line, but the lines with numbers carry the case. Revenue, latency, conversion rate, MTTR, time saved per engineer per week, % of org using your tool, headcount unblocked. If you don't have numbers, get them — quietly look at dashboards, ask other teams, estimate carefully. A packet with three quantified outcomes beats a packet with ten qualitative ones.

Show you're already at the next level

The single most important framing: a promo case is not "I am ready to be promoted." It's "I am already operating at the next level — please catch up the title." Every section should reinforce that. If the committee reads your case and thinks "yeah, that's staff work," you win.

Cross-functional reach is the staff-level multiplier

The jump from senior to staff (or any IC level to the next at scale) is usually less about doing harder work and more about working across more teams. Cross-team RFCs, working groups, technical mentorship outside your immediate team, internal talks — all of these signal staff scope. Make them visible.

Keep it to two pages

If it's longer than two pages, you're padding. Cut. The clearer your case, the more confident your manager looks when defending it in calibration.

Start drafting six months out

The engineers who scramble to write a case in two weeks consistently underperform engineers who've been tracking wins in a running doc all year. Keep a simple "promo evidence" Notion page going from day one of any cycle. By the time the packet is due, you'll already have the raw material.

Frequently Asked Questions

What is a promotion case?+
A promotion case (sometimes called a promo packet or promo narrative) is a written document that argues why you should be promoted to the next level. It typically includes evidence of your scope, the impact of your work, your cross-functional reach, and a recommendation. It's the artifact your manager presents to a calibration committee — so it needs to be tight, evidence-driven, and aligned with the next level's expectations.
How long should a promotion case be?+
Most strong promo packets are one to two pages of well-structured content. Calibration committees read dozens of cases in a sitting — they reward clarity and specific evidence, not length. If your case is longer than two pages, the signal is that you're either padding or trying to compensate for thin evidence. Cut ruthlessly.
What makes a promotion case strong?+
Three things: (1) Scope expansion — clear evidence that you're already operating at the next level, not just doing your current job well; (2) Measurable impact — specific outcomes with numbers; (3) Cross-functional reach — evidence that your influence extends beyond your immediate team. Anything that doesn't speak to one of these three is filler.
When should I start building my promotion case?+
Start tracking evidence the day you're told "next cycle" — usually 6 to 12 months out. Keep a running document of wins, scope changes, cross-team collaborations, and quantifiable outcomes. When promo season arrives, you'll already have the raw material.
Should I write my own promotion case or wait for my manager?+
Always write your own draft. Your manager will appreciate the head start, and you'll have control over how your achievements are framed. The manager's role is to translate your draft into the language the calibration committee uses, vouch for your scope, and present it in committee. Yours is to give them the raw material in a form that's hard to ignore.
What if my manager won't put me up for promotion?+
Get specific about why. "Not yet ready" is not actionable feedback; "you need to ship a cross-team initiative end-to-end" is. Ask for concrete gaps you can close before the next cycle and a written commitment that closing them is sufficient. If your manager won't give you that clarity, you're hitting a leveling ceiling that won't move. Either escalate to skip-level or start interviewing.

Ready to look at what's out there?

Browse engineering, product, and design roles at companies with strong leveling and clear paths to staff.

Browse Jobs → Explore Companies →