The Individual Contributor Path
summary
Argues the staff‑plus role is undefined but actionable, centering on three pillars: big picture, execution, leveling up and concrete practices like impact/effort prioritization, locator/topographical/treasure maps for org strategy, and cross‑org guilds. Cites company scale (Usabilla ~30–60 engineers vs SurveyMonkey ~300–400) and a real product shutdown (GetFeedback) to show career risk. Recommends open channels, nemawashi prebriefing, and a staff guild (built and used) to spread standards and mentoring. Advises focusing on measurable impact, not busywork.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 2:32Career path as IC
- 3:58Staff engineer role
- 5:42Staff vs senior duties
- 6:44Three pillars of staff engineer
- 13:43Impact versus visibility
- 14:05Big picture vision
- 19:29Company maps
- 21:55Communication challenges
- 25:24Business context
- 26:49Vision and strategy
- 30:42High-impact projects
- 36:18Leading teams
- 39:53Admitting ignorance
- 41:37Empowering individual contributors
- 43:44Influence across org
- 45:28Designing IC future
related talks
58mBeing Staff Plus
51mCongratulations, You're Staff. Now Why Are You Still Stuck?
25mThe staff engineer vs manager path A window over the tech career paths
25mCareer Growth: A Journey to Zen
30mBuilding a better bridge
29mStarting a new job as a Staff+
33mShaping Product Strategy as an Individual Contributor
36mEveryone is HR. Careers in Agile organizations