Book · 2021
Staff Engineer
by 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.
What does Reddit think of Staff Engineer?
r/ExperiencedDevs accounts for 78 of those mentions — which is exactly the audience the book was written for. Sentiment lands broadly positive but not effusive; people recommend it because it fills a gap, not because it's a page-turner. The core use case, repeated across threads: someone asks how to grow beyond senior without going into management, and multiple commenters drop the staffeng.com link or the paperback title. The Tanya Reilly comparison comes up organically. Several r/ExperiencedDevs threads recommend both together — an ↑84 comment names Larson and Reilly side by side and tells readers to start at staffeng.com. r/devops and r/programming barely register at 4 and 1 mentions respectively, both neutral. Mention volume peaked in 2022 and 2023 at 23 and 29, holding at 15 to 16 since — no collapse, just stabilization.
Community feedback & reader fit
Themes
- · technical leadership without people management
- · staff archetypes: Tech Lead, Architect, Solver, Right Hand
- · organizational influence and navigating company politics
- · career ladders and title inflation across companies
- · mentorship and building cross-functional relationships
Common praise
- + The staffeng.com interviews give the abstractions actual faces — you stop wondering what a principal engineer does all day.
- + r/cscareerquestions threads keep citing it as the clearest map of what industry expects at the staff level.
- + Covers the management-track alternative without arguing one path is superior.
- + The section on operating at the right altitude gives senior engineers language for a transition they're feeling but can't name.
Common criticism
- − The book skews heavily toward large-company archetypes; engineers at startups report that half the org-chart advice doesn't translate.
- − Light on day-to-day technical work — some readers finish it still unclear on what staff engineers actually ship.
- − The interview format means advice varies chapter to chapter in ways that can feel contradictory rather than synthesized.
Who it's for
If you're a senior engineer who keeps getting told to "have more impact" without anyone explaining what that means, this is the book they should have handed you. Engineers at large orgs — post-Series B, FAANG scale — get the most from it; the archetypes and org-navigation chapters assume a company big enough to have politics. At a ten-person startup, some chapters read like anthropology. The Tanya Reilly book covers similar terrain with more structured frameworks — read both if you're serious about the transition.
Mentions over time
Top subreddits
Which Reddit comments matter for Staff Engineer?
Top-upvoted quotes across the subreddits where this book is mentioned. Click through to read the full thread.
“I’m sorry, I don’t think you’re actually experienced enough for a tech lead role. This is the job. Will larson’s _staff engineer_ book is very good on this topic. People progress in their early part of their career by just slinging code. By the time you’re a senior, you’re writing a ton of code. It…
“I have had the most success expanding my influence by building relationships with people. A pre-requisite is being able to bring something of value to the relationship. Expertise in a domain in the company is a common one. I have one-on-ones with around 30 people across the company each month (this…
“No, but you will probably never rise above that level. Becoming staff+ requires more than just coding. If you are curious, check out the book *Staff Engineer's Path*.
“Check out the Staff Engineer: Leadership beyond the management track book. It talks about the various ways you can progress your career down a technical path as opposed to a management path. It should be required reading for all engineers really.
“Starting with a single dev or a small team, then hiring a more experienced manager when the company grows is not uncommon. The hard truth is that you being a good engineer does not make you a good CTO. The current company does not provide you mentoring. Look for mentors and people who went through…
“The best source of info on Staff Engineer roles are the books from Tanya Reilly and Will Larson. Read them. Most of Larson's thoughts are available at his website staffeng.com, start there. Lots of interviews with folks about the role, too.
“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…
Convinced? Pick up Staff Engineer
Readers also mention
Books that share discussion threads with Staff Engineer — counted from the comments, not curated.
An Elegant Puzzle
Will Larson
Will Larson's field guide to engineering management, written from actual operating experience at Digg, Uber, and Stripe.
The Staff Engineer's Path
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.
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.
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.
System Design Interview
Alex Xu
Alex Xu's interview prep guide that one r/cscareerquestions commenter credits with landing his current job.
The Unicorn Project
Gene Kim
The Phoenix Project retold from the developer's chair: same burning company, different seat at the fire.
Staff Engineer — frequently asked
Should I read Staff Engineer if I'm not at staff level yet?+
Yes. Multiple r/ExperiencedDevs threads recommend it to senior engineers specifically, and the ↑125 r/cscareerquestions comment calls it "required reading for all engineers" who want to understand where the technical track leads. Reading it early means you stop optimizing purely for code output before the promotion conversation starts.
How does Staff Engineer compare to The Staff Engineer's Path by Tanya Reilly?+
Reddit treats them as a pair. r/ExperiencedDevs threads with ↑84 upvotes explicitly name both Larson and Reilly together. Larson's book is interview-driven and more narrative; Reilly's is more structured and framework-heavy.
What does Reddit actually think of Staff Engineer?+
Broadly positive but not ecstatic. Nobody calls it life-changing; plenty call it the only book that clearly maps the technical leadership track. That's a reliable signal.
Is Staff Engineer still relevant in 2026?+
Yes. The 2024 and 2025 mention counts — 15 and 16 — hold steady against the 2022 and 2023 peak of 23 and 29. The org-navigation advice is more durable than any technology-specific book, and r/ExperiencedDevs was still citing it as recently as January 2026.