Book · 2021
Staff Engineer
by Will Larson
A senior engineer hits the ceiling of writing code alone and has to learn how influence works without a manager's title attached to it.
Catalogue record: Open Library
What does Reddit think of Staff Engineer?
r/cscareerquestions treats this as close to mandatory: one top comment (↑125) calls it "required reading for all engineers really," and that subreddit's scored excerpts back the enthusiasm up. r/ExperiencedDevs, where most of the mention volume actually sits, also scores positive overall, just less emphatically so. The most common construction in that sub isn't a solo recommendation, it's a paired one: Will Larson's Staff Engineer and Tanya Reilly's Staff Engineer's Path get named in the same breath so often ("the books from Tanya Reilly and Will Larson. Read them.") that Reddit seems to treat the two as one reading assignment rather than competitors. The top-upvoted quote (↑242) is direct about this specific book, calling it "very good" on the gap between senior and staff-level work. Mention volume climbed through 2022 and 2023 before easing off in the last two years, which tracks with a book that answers a question most engineers only need to ask once.
Community feedback & reader fit
Themes
- · The technical-leadership path as an alternative to people-management
- · Distinguishing senior-level scope from staff-level influence
- · Reddit's tendency to pair this book with The Staff Engineer's Path
- · Building influence through relationships and domain expertise
Common praise
- + r/cscareerquestions calls it "required reading for all engineers really" (↑125), the strongest unqualified endorsement in the tracked data.
- + The top r/ExperiencedDevs comment (↑242) credits it specifically with explaining why staff-level work stops being about slinging code.
- + r/ExperiencedDevs keeps recommending it alongside Tanya Reilly's book as a package deal, not as a fallback pick for people who didn't like the other one.
Common criticism
- − r/ExperiencedDevs' scored excerpts read positive but far more narrowly than r/cscareerquestions', so the warmest reception comes from the sub with the least career-advice mileage.
- − Several of the highest-upvoted threads that surface this book actually spend their word count recommending Reilly's Staff Engineer's Path instead, suggesting some readers reach for that one first.
- − Mention volume has roughly halved since its 2022-2023 peak, per the yearly counts, which could just as easily mean the conversation moved elsewhere as mean anything about the book.
Who it's for
You're past senior and can't tell if the next step is management or something else entirely; that's the exact fork r/cscareerquestions' top comment points at. Pair it with Reilly's Staff Engineer's Path rather than choosing one, since that's how r/ExperiencedDevs actually recommends them. Still early-career? The ↑242 comment is blunt that the influence-building content here assumes you're already past just writing code well. Devops and platform engineers show up too, just at a fraction of the volume from application-side developers.
Mentions over time
Top subreddits
Which Reddit comments matter for Staff Engineer?
The most relevant excerpts across the subreddits where this book is mentioned — opinionated, argued takes first, then top-upvoted mentions. 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.
“Some books can be consumed in audiobook form, which can be done while doing chores, e.g. washing dishes, or while driving. This is the primary way I have time for books. Here are some good ones: * Pragmatic Programmer (2nd edition) * Designing Data-Intensive Applications * Meltdown: Why Our Systems …
“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.
“My first company was like this, I was a "staff engineer" after 2 years while senior engineers were the ones who had been working for 10+ years. Somewhat off topic, I highly recommend the book "Staff Engineer" by Will Larson if you want to understand what the industry expectation for a staff enginee…
“I would recommend reading the book Staff Engineer by Will Larson! Lots of really cool stories about how many staff engineers at some well known companies got into their roles
“**Titles are (mostly) bullshit.** There’s no universal definition for “Staff” or “Principal” or even “Senior.” Not even Will Larson’s book can save you here. Every company has its own leveling system, and none of them are standard. What actually matters is **what your team needs right now.** …
“My goal is to focus on organizational skills. In both senses: being more personally organized and contributing more successfully at the organizational level. I've been reading Staff Engineer (by Will Larson) and it has made me want to be a lot more deliberate about how I do the (increasingly domina…
“By the book? Staff engs "make impact" If that sounds vague, that's because it is lol. I've been at Staff for about 1.5 years and I didn't read that book … first but I came to realize that it's basically by design: Moreso than writing awesome code, or delivering difficult features, or whatever a real…
“Staff eng here. Here is what helped me: Resources: I recommend Staff Engineer by Will Larson (it also has a collection of interviews with other staff engineers) and leaddev.com Coming from outside directly on the Staff position vs getting promoted means that you are at a disa…
“What content have you read or listened to, what coaching have you received, regarding the topic of becoming a staff+ engineer? It’s a topic that is very challenging to offer “general” advice on. If you haven’t read Will Larson’s book on the topic, I highly recommend it: …
“One of the reasons "Staff Engineer" by Will Larson is so good is that it explains the different staff eng archetypes. It's not one thing at all, Staff is more like a level than a role description.
Convinced? Pick up Staff Engineer
Readers also mention
Books that share discussion threads with Staff Engineer — counted from the comments, not curated.
Guides featuring Staff Engineer
Ranked best-of lists and editorial guides where this book's tracked mentions place it.
Staff Engineer — frequently asked
Is Staff Engineer by Will Larson required reading, according to Reddit?+
r/cscareerquestions' top comment (↑125) says so in almost those words: "required reading for all engineers really." r/ExperiencedDevs is warmer in tone than in raw enthusiasm, with its top comment (↑242) calling it specifically good on why staff-level work differs from senior-level code output. Both scored subreddits land positive overall.
Should I read Staff Engineer or The Staff Engineer's Path first?+
Reddit mostly refuses to pick. The highest-upvoted r/ExperiencedDevs comments on this topic name both Larson's Staff Engineer and Reilly's Staff Engineer's Path together (↑84: "the books from Tanya Reilly and Will Larson. Read them."), treating them as a matched pair rather than either being the clear starting point.
Is Staff Engineer still relevant in 2026?+
The mentions are still current, last tracked in January 2026, but the volume has cooled from its 2022-2023 peak. Nothing in the displayed excerpts argues the content has dated; the drop looks more like the conversation moving on than the book losing relevance.
Who is Staff Engineer for?+
Engineers who've hit senior level and are deciding whether to go into management or stay technical at a higher scope. r/cscareerquestions' top comment (↑125) frames it as near-universal reading, while r/ExperiencedDevs' top comment (↑242) specifically targets people wondering why staff-level work looks so different from what got them promoted to senior.