The Staff Engineer’s Path — Notes
tsep staff-engineering career leadership ic-track
Author: Tanya Reilly
Publisher: O’Reilly Media, 2022
Pages: 359 PDF pages (Introduction + 9 chapters)
PDF: K:/Books/The staff engineers path.pdf
What This Book Is About
A practical guide for software engineers who want to grow as individual contributors rather than move into people management. The book argues that staff engineering is a distinct discipline — not “senior engineer plus more code” — that requires three interconnected skill sets called the Three Pillars:
- Part I — Big-Picture Thinking: Understanding where your organization is, where it’s going, and how to help navigate it there
- Part II — Execution: How to take on and drive large ambiguous projects to completion
- Part III — Leveling Up: How to make the engineers around you better
The central theme is that scope, not depth, is the defining characteristic of staff work. A staff engineer’s value comes from having broad context and using it to make good decisions and help others make good decisions.
Note Style
Each chapter file follows this structure:
- Overview — what the chapter is about and its central argument
- Core Concepts — key terminology introduced
- Main Content — frameworks, models, practical advice (chapter-specific structure)
- Key Takeaways — 7–10 condensed points
- Related Resources — wiki-links to related notes
Flashcards use Obsidian Spaced Repetition format with tag #flashcards #tsep.
Chapter Progress
Introduction
| # | Title | Notes | Flashcards |
|---|---|---|---|
| 0 | Introduction: The Staff Engineer’s Path | ✅ | ✅ |
Part I: Big-Picture Thinking
| # | Title | Notes | Flashcards |
|---|---|---|---|
| 1 | What Would You Say You Do Here? | ✅ | ✅ |
| 2 | Three Maps | ✅ | ✅ |
| 3 | Creating the Big Picture | ✅ | ✅ |
Part II: Execution
| # | Title | Notes | Flashcards |
|---|---|---|---|
| 4 | Finite Time | ✅ | ✅ |
| 5 | Leading Big Projects | ✅ | ✅ |
| 6 | Why Have We Stopped? | ✅ | ✅ |
Part III: Leveling Up
| # | Title | Notes | Flashcards |
|---|---|---|---|
| 7 | You’re a Role Model Now (Sorry) | ✅ | ✅ |
| 8 | Good Influence at Scale | ✅ | ✅ |
| 9 | What’s Next? | ✅ | ✅ |
Key Concepts Reference
| Term | Definition |
|---|---|
| Staff engineer | A senior IC who exercises technical leadership at broad scope without managing people |
| Three pillars | Big-Picture Thinking, Execution, Leveling Up — the three skill domains of staff engineering |
| Locator map | Understanding how your team/project fits in the broader organizational context |
| Topographical map | Understanding your organization’s culture, power structures, and terrain |
| Treasure map | Understanding where the organization is headed technically and why |
| Technical vision | The “north star” — what good looks like in 3–5 years |
| Technical strategy | The actionable plan to reach the vision (Rumelt’s kernel: diagnosis + guiding policy + coherent actions) |
| RACI | Responsible, Accountable, Consulted, Informed — a responsibility assignment matrix |
| RFC | Request for Comment — a design document used to drive consensus |
| ”Even over” | A format for explicit trade-off statements: “We value X even over Y” |
| Nemawashi | Japanese concept: laying informal groundwork before a formal decision |
| Westrum typology | Pathological / Bureaucratic / Generative — organizational culture classification |
| Local maximum | Optimizing within a small scope while missing larger opportunities |
| Sponsorship ABCDs | Amplifying, Boosting, Connecting, Defending — four ways to sponsor someone |
| Glue work | Vital non-technical coordination work that often falls to junior engineers unfairly |
| Radiating intent | Signaling what you’re about to do before doing it, rather than seeking permission |
| CYAE | Cover Your Ass Engineering — avoiding ownership and accountability |
Last Updated: 2026-05-30