Congratulations, You're Staff. Now Why Are You Still Stuck?
summary
Explains why the habits that made someone indispensable as Staff — owning work, being the “hero” and single point of failure — block promotion and gives concrete fixes: delegate to avoid being loadbearing, make technical wins visible (one attendee saved $3M by changing a library), expand scope to run multi-team platforms and backend systems, build cross‑org influence with monthly one-on-ones, and get into other teams’ code by writing tests and documentation so you become the reliable right-hand/umbrella decision maker that VPs and CTOs will fund.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 3:55Hidden burdens of staff role
- 9:25Effort versus promotion
- 13:30Politics of staff promotions
- 18:02Campaigning for visibility
- 24:08Technical depth to business impact
- 30:21Building cross-team trust
- 33:53Future planning as futurist
- 37:29Barriers to upward mobility
- 41:48Q&A
related talks
58mBeing Staff Plus
29mStarting a new job as a Staff+
42mHow to Hit the Ground Running as a Staff + Software Engineer at a New Company
35mSo you've become a Docs Lead. Now what?
30mBuilding a better bridge
47mThe Individual Contributor Path
28mBuilding happier engineering teams
27mMind the gap: Navigating the staff+ performance cliff