Book · 2022
The Staff Engineer's Path
by Tanya Reilly
A staff engineer's actual job — navigating ambiguity, protecting your team from org chaos, and delivering on projects nobody owns — laid out by someone who did it.
What does Reddit think of The Staff Engineer's Path?
Eleven mentions across r/ExperiencedDevs (8), r/devops (2), and r/cscareerquestions (1), with peak activity in 2023 and a steady trickle since. The tone in r/ExperiencedDevs is consistently instrumental: this shows up in resource lists alongside Designing Data-Intensive Applications as the pair you actually need, not the pair someone recommends to sound credible. One ↑83 comment distills the community's position cleanly: "yes, tanya reilly actually knows what she's talking about." That's high praise from a sub that opens most book threads with "skip most of those honestly." The Will Larson Staff Engineer comparison surfaces occasionally — r/ExperiencedDevs notes both, treating them as complements rather than rivals. Reilly wins on structure; Larson wins on interviews. r/devops offered the most useful honest take: a commenter who expected to know everything already didn't. r/cscareerquestions cited Reilly's "glue work" essay rather than the book directly, which suggests her reputation extends past the text itself.
Community feedback & reader fit
Themes
- · Navigating the staff engineer role without a management title
- · Glue work, visibility, and the hidden cost of keeping teams functional
- · Staff-level system design judgment vs. architecture book theory
- · Organizational influence without direct authority
- · Career clarity for senior ICs who don't want to manage
Common praise
- + The glue-work framing gave r/cscareerquestions commenters a named concept they immediately applied to gender dynamics in engineering orgs.
- + r/devops commenter expected to already know everything covered and was wrong — a rare admission.
- + Shows up in r/ExperiencedDevs resource lists next to DDIA, which is the recommended-book equivalent of a strong endorsement.
- + The ↑83 comment singles it out specifically while dismissing the rest of the list.
Common criticism
- − Only 11 total mentions across tracked subs — it gets cited rather than discussed, which limits how much Reddit actually unpacks its arguments.
- − The Will Larson comparison comes up enough that readers feel they need to justify choosing one; the books may cover more of the same ground than their proponents admit.
- − No commenter quotes a specific chapter or framework by name, which suggests the overall arc lands better than any individual piece.
Who it's for
You've been senior for two years and the promotions committee keeps telling you to demonstrate "scope and influence" without specifying what that means in practice. This book names that problem. It's also worth your time if you're already staff and realizing the job you thought you were getting is mostly calendar management and invisible coordination work — Reilly has a term for that and it's not flattering to the org. If the Will Larson Staff Engineer is already on your shelf, r/ExperiencedDevs treats them as a pair, not substitutes.
Mentions over time
Top subreddits
Which Reddit comments matter for The Staff Engineer's Path?
Top-upvoted quotes across the subreddits where this book is mentioned. Click through to read the full thread.
“I'm a seasoned backend engineer, sharing some resources you will find useful. ##### Books Designing Data-Intensive Applications by Martin Kleppmann The Pragmatic Programmer by Andy Hunt The Staff Engineer's Path by Tanya Reilly ##### Talks
“skip most of those honestly **actually useful for staff-level:** * "the staff engineer's path" - yes, tanya reilly actually knows what she's talking about * "designing data-intensive applications" by kleppmann - will make you mass more useful in system design than any "architecture" book * "an e…
“You'll likely benefit from reading this book, or at least skimming it and focusing on sections that stand out to you: The Staff Engineer's Path: A Guide for... by Reilly, Tanya (amazon.com) It really is a good book…
“Read The Staff Engineer's Path and / or Staff Engineer: Leadership beyond the management track
“Tanya Reilly, who wrote The Staff Engineer's Path, has written about women volunteering to do work that aligns with PM duties more than coding - and how managers are 44% more likely to ask a women to do those kinds of duties Anecdotally many female…
“There's another book which some people like better: Tanya Reilly - The Staff Engineer's Path.
“Recent books: * The staff engineer's path - I thought I already knew all the things, and I was wrong! * The field guide to understanding human error - truly excellent, and something anyone involved in incident management should read. Here's a preview:
“Lots of great advice given so I'll just drop two resources for further learning: Will Larson's "Staff Engineer's Path" is full of interviews and advice. The defunct, but evergreen companion podcast full of even more interviews from other p…
Convinced? Pick up The Staff Engineer's Path
What else does r/ExperiencedDevs read?
Other books mentioned in the same sub, ranked. Shared-sub overlap with this title breaks ties.
Designing Data-Intensive Applications
Martin Kleppmann
A backend engineer's field guide to the tradeoffs behind every database, queue, and distributed system you will ever touch.
The Pragmatic Programmer
Andy Hunt
Two veterans hand you a checklist for the craft: don't write code you don't need, own your tools, and fix the broken window before someone else does.
The Mythical Man-Month
Frederick P. Brooks Jr.
Fred Brooks spent the 1960s building IBM's OS/360 and wrote down everything that went wrong — in 1975, and it still lands.
A Philosophy of Software Design
John Ousterhout
A Stanford professor's 200-page rebuttal to Clean Code, built on interface depth rather than method length.
The Manager's Path
Camille Fournier
A software engineer picks up a management role and finds out — via 142 Reddit mentions — that nobody told them about the crying, the firings, or the 90-day onboarding clock.
Staff Engineer
Will Larson
Will Larson interviews the staff engineers Reddit wishes it had access to and explains what they actually do after they stop writing code all day.
The Staff Engineer's Path — frequently asked
Is The Staff Engineer's Path better than Will Larson's Staff Engineer?+
Depends on what you want. r/ExperiencedDevs recommends both and treats them as complements: Larson's book leans on interviews with practicing staff engineers, Reilly's leans on structure and frameworks. The ↑28 comment notes some readers prefer Reilly's; nobody argues you should skip one entirely. Read both if the role is new to you.
What does Reddit actually think of The Staff Engineer's Path?+
Broadly positive, though understated. The ↑83 endorsement — "yes, tanya reilly actually knows what she's talking about" — is about as direct as r/ExperiencedDevs gets. The r/devops commenter who expected to already know everything reported they were wrong, which is the review that actually means something.
Should I read The Staff Engineer's Path if I'm not staff yet?+
Yes, probably. The ↑78 r/ExperiencedDevs comment says to at least skim it and focus on sections that stand out — the framing on glue work and organizational influence applies earlier than the title implies. If you're senior and wondering why promotions keep not landing, the book names the gap more directly than most managers will.
Does The Staff Engineer's Path hold up in 2026?+
The mention data runs through January 2026 with no sign of the book aging out of recommendations. It still appears in r/ExperiencedDevs resource lists alongside DDIA — a pairing that's been stable since 2023. The org-dynamics content is structural enough that it doesn't depend on any particular tech moment.