Maps for the unmarked trails — promo packets, mass rebases, oncall survival, and the management question nobody answers straight.
Your manager won't hand you a template. Here's the exact structure — impact framing, scope signals, and the three paragraphs that make or break your case at calibration.
Bootcamp didn't cover 3am PagerDuty alerts. A structured runbook, a blameless mindset, and knowing exactly when to escalate — these are the skills that separate IC3 from IC4.
Three engineers who made the switch, hated it, and came back. One who stayed and made VP. The actual data on reversibility — and why your fear of it is based on a 2015 org chart.
The plateau isn't about skill — it's about visibility surface area. Here's a concrete 90-day plan that got 11 engineers unstuck, with the specific artifacts each one shipped.
The exact doc structure used to make Staff at Stripe, Shopify, and three unnamed FAANG orgs. 847 engineers have shipped it.
"I used the promo packet template and made Staff in 14 months. The impact framing section alone changed how my manager talked about me in calibration."
"The oncall guide got me through my first P0 without spiraling. Knowing when to escalate vs. dig is a skill nobody explicitly teaches."
"$42k comp increase using the negotiation framework. The part about competing offers as leverage signals, not ultimatums, was the unlock."
After 60+ mock sessions and 12 real Staff-level loops, I mapped every signal interviewers actually score. Spoiler: it's not whether you chose Kafka over SQS. It's how you reason about failure modes under constraints you've never seen before.
Every senior engineer you admire was once stuck exactly where you are. The difference is they found the right map.
$ git clone career.git→