Staff promotion · Calibration playbook
01 / 08
How I built a case the committee couldn't argue with

Write a Staff-Engineer case
like a calibration-committee insider

A real packet from Payments Platform — the scope, the proof, and the artifacts that cleared the bar.

Committees don't promote potential.
They promote evidence that reads as already Staff.
White paper | Bold highlights | Editorial layoutCover · 01
Chapter · 01
02 / 08
Chapter One

First, the scope

Maya Chen, senior engineer on Payments Platform — three teams, one outage, and a system nobody wanted to own.

Section Divider02 / 08
Four moments the committee circled twice
03 / 08

The proof moments that carried the packet

Incident
Led the ledger-drift recovery
Zero customer-facing loss across 3 teams in 11 hours
Architecture
Proposed the idempotency-key redesign
Adopted by 4 squads before the RFC even closed
Mentoring
Grew two engineers to senior in one cycle
Both cite her 1:1 notes as the turning point
Cross-team
Aligned Payments and Risk on a shared schema
Ended an 8-month stalemate in one working session
Content · Grid 2x203 / 08
How the packet is built
04 / 08

One scope statement, the whole packet out

1
Scope memo: one page naming the system, the blast radius, and who now depends on her
2
Incident retro: the ledger-drift timeline, decisions made under pressure, and the fix that stuck
3
Design doc: the idempotency-key RFC, with the counter-proposal it beat
4
Peer packet: six calibrated quotes from partner teams, not just her manager — settle the doubt
Every artifact backs the same claim —
it doesn't ask for trust, it shows the receipts.
Content · Steps04 / 08
The packet the committee skimmed in 6 minutes
05 / 08

Not an essay —
just one SCOPE.md

# promotion/maya-chen/SCOPE.md
level: L7 (Staff)
scope: "Payments Platform — ledger, idempotency, settlement retries"

evidence:
  - incident:   "Ledger-drift recovery, zero customer loss, 11h, 3 teams"
  - design:     "Idempotency-key RFC — adopted by 4 squads pre-approval"
  - mentoring: "2 engineers promoted to senior in one cycle"
  - alignment: "Payments/Risk schema agreement after 8-month stalemate"
Content · Code Block05 / 08
The numbers the committee actually checked
06 / 08

How far the scope grew, how deep the impact reached

Incidents owned end-to-end 6 RFCs adopted without rework 3 Engineers leveled up to senior 2 Cross-team peers in calibration 9 Revenue at risk, ledger-drift $4.2M
Chart · Horizontal Bars06 / 08
Three things she did before submitting
07 / 08

Don't just gather evidence —
frame the ask

Learning
Named her one miss
the schema rollout slip
Owning a gap made every other claim more credible
Sponsorship
Got her skip-level
to co-sign the packet
A manager alone reads as advocacy; a skip-level reads as calibration
The ask
Requested Staff
this cycle, not "eventually"
A specific ask forces a specific answer from the committee
The packet doesn't ask the committee to imagine Staff.
It shows them she's already operating there.
CTA07 / 08
Thanks for reading
08 / 08
L7 · the ask

If you're building your own case: name the scope, collect the receipts, get a skip-level to sign —
and ask for the level directly, not "whenever you think I'm ready."

Scope · Proof · Artifacts · Impact · Ask Staff Engineer Promotion Calibration-Committee Playbook
End08 / 08