Book · 2019
An Elegant Puzzle
by Will Larson
Will Larson's field guide to engineering management, written from actual operating experience at Digg, Uber, and Stripe.
What does Reddit think of An Elegant Puzzle?
The book shows up in two contexts. First, when someone gets promoted into management and asks what to read — the ↑67 r/ExperiencedDevs comment puts it on a short list alongside The Manager's Path. Second, when someone is already managing and needs vocabulary for team health, headcount tradeoffs, and saying no to low-priority requests. r/cscareerquestions has 8 mentions. r/devops has 6. Both sit at neutral sentiment — the book appears in reading lists but doesn't generate argument outside r/ExperiencedDevs. Nobody debates against it publicly, which isn't the same as unanimous praise. Larson's blog posts draw separate citations in several threads, sometimes more than the book itself, which is a mild signal that the free writing covers similar ground. Peak volume was 2022–2023 at 12 mentions per year; 2024 dropped to 2 before a return to 4 in 2025.
Community feedback & reader fit
Themes
- · Engineering management systems and frameworks
- · Team growth stages and sizing
- · Prioritization and organizational saying-no
- · Staff-level career development
- · Engineering organization design
Common praise
- + The team growth stage model gives new managers vocabulary for diagnosing why a team feels stuck.
- + Larson writes from operating experience at Stripe and Uber, which makes the framework feel less theoretical than most management books.
- + The prioritization advice — commit only on the highest-priority items and deliver them — gets cited verbatim in r/devops threads about sprint health (↑41).
Common criticism
- − Larson's blog posts cover much of the same ground for free, which several threads cite directly rather than pointing to the book.
- − Readers who need people management depth — performance conversations, compensation, firing — will find the book thin on those topics.
Who it's for
You just got your first direct reports at a mid-size tech company and your manager handed you nothing. An Elegant Puzzle is what r/ExperiencedDevs (21 mentions) hands you first. If you're a senior IC thinking about whether to move into management, the book gives you a realistic picture of what the job involves — team health frameworks, hiring loops, and growth stage thinking that most IC career tracks never cover. Readers who want pure people skills over systems thinking will get more from The Manager's Path, which goes deeper on the interpersonal side that Larson largely leaves alone.
Mentions over time
Top subreddits
Which Reddit comments matter for An Elegant Puzzle?
Top-upvoted quotes across the subreddits where this book is mentioned. Click through to read the full thread.
“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…
“I'm an Engineering Manager and I follow a number of people with similar roles/experience: * Charity Majors - she writes a lot of great articles on tech leadership * Pat Kua ([
“Congrats for your new role. I believe senior is more about people management. So, my suggestions are 1. An Elegant Puzzle: Systems of Engineering Management 2. [The Manager\`s Path](
“>I've been assigned to manage team of ~10 software engineers - their skills level are mediocre, despite average of 5-10 years of experience each There is nothing wrong with being average. Most engineers are around there. Having a few lower performers in a 10 people team can happen, but having 10 …
“Read Will Larson’s work, his book « An Elegant Puzzle » is great and his blog posts are very insightful as well!
“Say no very often. Commit on only the highest priority items, and deliver them. Have a routine around learning from sprints, or however you organize your work. The most important thing is learning how the team can improve and making sure the work is of the highest value / priority. Show the work…
“I posted a list of my favorite books in another comment on the importance of reading to get to the next level. Here is that list for people who don't want to click a link: * [Staff Enginee…
“Yup. As much as I hate training-by-library, and I’ve made a point in my career to avoid it with new EMs on my teams, that’s just the reality at most places and sounds like OP hasn’t even gotten the courtesy of book recommendations. Managers Path is a great start - it’s a mile wide and an inch deep …
Convinced? Pick up An Elegant Puzzle
Readers also mention
Books that share discussion threads with An Elegant Puzzle — counted from the comments, not curated.
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 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.
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.
Code Complete
Steve McConnell
Steve McConnell's 900-page construction manual for software, ranked third on Reddit's canonical reading list and still cited 25 years after publication.
The Phoenix Project
Gene Kim
An IT manager inherits a failing project, a mutinous ops team, and a CEO deadline — and has to ship before the company does.
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.
An Elegant Puzzle — frequently asked
What does Reddit actually think of An Elegant Puzzle?+
Depends which sub.
Should I read An Elegant Puzzle before or after The Manager's Path?+
After. r/ExperiencedDevs threads that recommend both consistently position The Manager's Path as orientation and An Elegant Puzzle as the systems layer on top. Larson assumes you already understand the basic EM job; he's writing about how to run the function at scale. The ↑67 comment that pairs them makes this sequencing explicit.
Is An Elegant Puzzle worth reading if I'm not yet a manager?+
Probably yes if you're a senior engineer trying to understand how EMs make decisions. The r/ExperiencedDevs crowd cites it when explaining organizational behavior to ICs — the sections on headcount and roadmap prioritization demystify things that look arbitrary from the outside. Less useful if you want concrete advice on your own IC career progression.
Does An Elegant Puzzle hold up in 2026?+
Mention volume peaked in 2022–2023 and dropped to 2 in 2024, which usually signals a book settling into backlist status. The core frameworks are process-agnostic enough that the age hasn't obviously dated them.