Staff Engineer: Leadership beyond the management track — Notes
selt staff-engineering career leadership ic-track
Author: Will Larson
Publisher: Self-published (Leanpub), 2020
Source: staffeng.com + interviews with 14+ Staff-plus engineers
EPUB: K:/Books/Will Larson - Staff Engineer - Leadership beyond the management track.epub
What This Book Is About
“Staff Engineer” fills a gap that nearly every practitioner in the field had noticed: the engineering management track has been extensively written about (First 90 Days, High Output Management, The Manager’s Path), but the technical leadership track above Senior had almost no dedicated literature. The book assembles Larson’s own frameworks, shaped during his time running Digg and working at Stripe and Calm, with interview material from 14+ engineers who hold Staff, Principal, or Distinguished titles at companies including Stripe, Mailchimp, Fastly, Dropbox, and Slack.
The central argument is that the Staff-plus role is under-defined and under-documented because organizations each invent it differently. There is no canonical job description, no obvious promotion formula, and no shared vocabulary. Larson proposes a framework to replace that ambiguity: four archetypes that describe how the role manifests, five activities that describe what the work actually is, and a set of practical mechanics for attaining and operating at the level.
The book is organized in four parts. The Overview section establishes vocabulary and context. Part I (Operating at Staff) covers what effective Staff-plus work looks like in practice — how to set direction, manage quality, communicate, build influence, and create space for others. Part II (Getting the Title Where You Are) covers the promotion mechanics — promotion packets, sponsorship, Staff projects, visibility, and access to decision-making rooms. Part III (Deciding to Switch Companies) covers how to find a company where Staff-level work is possible, how to interview, and how to negotiate. A final Stories section presents edited transcripts from the 14+ engineers interviewed.
Note Style
Each section file follows this structure:
- Overview — what challenge/topic the section addresses
- Core Concepts — key terms introduced (where applicable)
- Main Content — frameworks, practical advice (section-specific)
- Key Takeaways — 7–10 condensed points
- Related Resources — wiki-links to related notes
Flashcards use Obsidian Spaced Repetition format with tag #flashcards #selt.
Section Progress
Overview
| # | Section | Notes | Flashcards |
|---|---|---|---|
| sec01 | Overview (archetypes, what they do, does title matter) | ✅ | ✅ |
Part I: Operating at Staff
| # | Section | Notes | Flashcards |
|---|---|---|---|
| sec02 | Work on what matters | ⬜ | ⬜ |
| sec03 | Writing engineering strategy | ⬜ | ⬜ |
| sec04 | Managing technical quality | ⬜ | ⬜ |
| sec05 | Stay aligned with authority | ⬜ | ⬜ |
| sec06 | To lead, you have to follow | ⬜ | ⬜ |
| sec07 | Learn to never be wrong | ⬜ | ⬜ |
| sec08 | Create space for others | ⬜ | ⬜ |
| sec09 | Build a network of peers | ⬜ | ⬜ |
| sec10 | Present to executives | ⬜ | ⬜ |
Part II: Getting the Title Where You Are
| # | Section | Notes | Flashcards |
|---|---|---|---|
| sec11 | Promotion packets | ⬜ | ⬜ |
| sec12 | Find your sponsor | ⬜ | ⬜ |
| sec13 | Staff projects | ⬜ | ⬜ |
| sec14 | Get in the room, and stay there | ⬜ | ⬜ |
| sec15 | Being visible | ⬜ | ⬜ |
Part III: Deciding to Switch Companies
| # | Section | Notes | Flashcards |
|---|---|---|---|
| sec16 | Finding the right company | ⬜ | ⬜ |
| sec17 | Interviewing for Staff-plus roles | ⬜ | ⬜ |
| sec18 | Negotiating your offer | ⬜ | ⬜ |
Stories
| # | Section | Notes | Flashcards |
|---|---|---|---|
| sec19 | Stories — key themes and patterns | ⬜ | ⬜ |
Key Concepts Reference
| Term | Definition |
|---|---|
| Staff-plus | Umbrella term for Staff Engineer, Principal Engineer, Distinguished Engineer, and Fellow — all titles above Senior Engineer on the IC track |
| Dual-track ladder | The career structure offering both an engineering management track and a technical individual contributor track above Senior |
| Tech Lead (archetype) | A Staff engineer who guides a team’s approach and execution, partners closely with 1–3 managers; most common archetype |
| Architect (archetype) | A Staff engineer responsible for technical direction and quality within a critical domain; requires deep knowledge + cross-org leadership |
| Solver (archetype) | A Staff engineer who digs into arbitrarily complex problems; may stay in a single area long-term or move between hotspots |
| Right Hand (archetype) | A Staff engineer who extends an executive’s (VP/CTO) attention and authority; provides leadership bandwidth at scale |
| Setting technical direction | Acting as the “Lorax” for your technical domain — speaking for the long-term health of the systems even when no one else is |
| Mentorship | Sharing knowledge and experience to help someone develop; a two-way relationship that grows over time |
| Sponsorship | Actively advocating for someone’s promotion, visibility, or inclusion in high-stakes work; requires using your political capital |
| Being glue | Tanya Reilly’s term for the coordination, documentation, onboarding, and unblocking work that keeps teams moving |
| Exploration | Taking on ill-defined, high-risk work to evaluate whether a technical direction is viable; analogous to R&D scouting |
| Snacking | Doing easy, low-impact tasks that feel productive but don’t move the needle on important work |
| Preening | Doing high-visibility low-impact work primarily to look good, at the expense of more important but less visible work |
| Chasing ghosts | Pursuing a problem or initiative that doesn’t have real organizational buy-in, often after being advised to drop it |
| Staff project | A large, ambiguous, cross-cutting project that serves as evidence of Staff-level impact during a promotion cycle |
| Promotion packet | A written document summarizing a Staff engineer candidate’s impact, scope, and advocacy for promotion review |
| Sponsor | A senior person who advocates for your advancement with their own credibility; different from a mentor |
| Engineering strategy | A written document (Strategy + Vision) that explains how engineering decisions will be made in a domain going forward |
| Low-context communication | Communication that is explicit and complete enough to be understood without prior context; important at broader scope |
| High-context communication | Communication that relies on shared assumptions; efficient within a team but breaks down at org scale |
Last Updated: 2026-05-30