The Promotion Packet & the Interview Loop

⏱ ~10 min read · 🎧 8 min listen · ✎ 3 quizzes · 🧪 ~60 min lab

Everything you've written in this course — the scope map, the ADR, the strategy memo — was never homework. It was ammunition. This lesson is where the evidence trail gets loaded into the two weapons that actually make the move: the promotion packet for the internal path, and the interview loop for the external one. Your mission brief says both paths, so we build both — from the same eleven lessons of material.

Start the packet before the work

Will Larson's core insight about promotion packets is one of those ideas that looks obvious only after you hear it: write the packet before you do the work, not after.¹ Written at the end, a packet is an inventory — a scramble to remember what you did and dress it up. Started early, it's a map: the empty sections tell you exactly which evidence doesn't exist yet, so you can go create it deliberately. You've been running this play for eleven lessons without the name — every lab was an evidence slot being filled in advance.

Structure the packet as one high-level claim per focus area, with evidence beneath each claim. Not "I did these forty things" but "I operate at org-level scope — here are three exhibits." And understand who it's for: your manager, and behind them your sponsor — the senior person who will argue your case in a room you're not in. Committees promote based on what advocates can say on your behalf, so the packet is literally your sponsor's ammunition: crisp claims they can repeat, evidence they can point to.¹ Larson's workflow is blunt about this — share the packet with your manager in a 1:1, ask what's missing, and revise it together every cycle.¹

Now the timeline reality, so it doesn't demoralize you later: staff+ promotions move in quarters, halves, and years, not weeks — often landing a cycle or two later than the work deserved, and for roughly a third of the engineers Larson surveyed, only by changing companies.² Three months of this course positions you; the org's calendar decides when it pays out. That's not a verdict on you — it's headcount, budget, and committee mechanics. Keep pursuing it anyway — Reilly's point about titles is that they anchor expectations and grant scope you'd otherwise re-argue in every room⁵ — but it's also exactly why you're building the external path in parallel.

Eleven lessons, ten exhibits

Here's the mapping this course was designed around. Each artifact you've produced evidences a specific Principal-level claim — and feeds a specific interview round:

Before any artifact goes into the packet, run it through five quality tests: is the impact org-level, not team-level? Is it narratable in ninety seconds? Does it end in a named outcome? Is your framing of the problem visible — not just your execution of someone else's? And would a stranger on a committee understand it without context? The full tests, packet skeleton, and this mapping table live in a printable promotion-packet checklist — keep it next to the packet as you assemble.

The external loop: what Principal interviews measure

External Principal loops typically run three kinds of rounds: system design at staff depth, an architecture deep-dive on your own past work, and behavioral/leadership rounds.³ The shape looks like a senior loop; what's measured changes completely. And the more senior the role, the more your real operating history — not rehearsed material — is what's being probed.⁴

In system design, the differentiator at this level is trade-off narration. Interviewing.io's guide is explicit: listing options with pros and cons is mid-level; committing — "given these trade-offs, I'd choose that, and here's what it costs us" — is what senior-plus candidates do, while driving the interview themselves rather than waiting to be led.³ That's Lesson 02, spoken aloud. The deep-dive round inverts it: they pick your system and drill into why. Your ADRs and design docs are pre-written answers — you've already articulated the alternatives you rejected and why.

For behavioral rounds, convert artifacts into stories with a four-part spine: situation → your framing of the problem → the decision and its trade-offs → org-level outcome. The second beat is the one seniors miss: what did you see that others didn't? And remember Lesson 01 — every "Principal Engineer" ad conceals one specific archetype. Use your questions to probe which shape this role really is: which team, which fire, which executive? Interviewing for the wrong shape wastes a loop you can't rerun.

🧪 Lab: load the ammunition

Two artifacts this time — one per path. Budget ninety minutes total; you're assembling, not inventing.

1. Promo-packet outline. Write three high-level claims about your Principal-readiness. Claims about org-level impact, not effort — "I set technical direction for X" beats "I worked hard on X".
2. Evidence slots. Under each claim, list 2–3 evidence slots. Fill what you can from the mapping table above; where a slot is empty, don't pad — name it honestly as "evidence to create next quarter". Those gaps are your work plan.
3. Three interview stories. Pick three pieces of real work (course artifacts count). Write each in the four-part structure — situation, your framing, the decision and its trade-offs, org-level outcome — at 150 words or fewer. That's the ninety-second spoken version.
4. Stress-test. Run every claim and story through the five tests on the checklist. Cut anything that fails the stranger test.

Feedback loop: bring both artifacts back to me in chat. I'll review against a Principal-level rubric — are the claims about org-level impact rather than effort, does every story end with an outcome a VP would care about, and are the gaps honest rather than papered over. This outline is the packet you'll refine in the capstone and carry into your real cycle.

You are a seasoned Principal Engineer reviewing my work: a promotion-packet outline (three high-level claims with evidence slots) and three Principal-level interview stories. Review them against this rubric:

- Claims are about org-level impact, not effort — "I set technical direction for X" beats "I worked hard on X".
- Evidence slots are honest: real artifacts where they exist, and empty slots named plainly as "evidence to create next quarter" rather than papered over with padding.
- Each story follows the four-part spine — situation, my framing of the problem, the decision and its trade-offs, org-level outcome — and ends with an outcome a VP would care about, not effort or volume.
- Each story is 150 words or fewer (the ninety-second spoken version) and would make sense to a stranger on a committee with no context.

Grade each criterion Strong / Adequate / Missing, with one sentence of evidence per grade. Be skeptical — challenge the weakest claim first. Then ask me 2–3 follow-up questions a promotion committee or a staff+ interviewer would ask. Finish with the single highest-leverage improvement.

My promo-packet outline and interview stories follow below.

Check yourself — diagnose the move

Three scenarios. Diagnose from the mental model — don't scroll up. Wrong picks stay live.