Subreddit

Top books from r/cscareerquestions

r/cscareerquestions is a subreddit for software engineers and CS students discussing job hunting, interviews, salaries, and career progression in tech.

Updated September 2026 — rankings refresh with each new pull of comment data.

Books ranked

1,398

Published mentions

sum of exact per-book subreddit rows

2.4M

Members

Years tracked

About this ranking

The number tells the story: Cracking the Coding Interview gets 525 mentions here, more than three times its count in r/ExperiencedDevs (76), making it the single most dominant book recommendation on the site relative to any sub's own canon. Beyond interview prep, Designing Data-Intensive Applications (171) and The Pragmatic Programmer (95) round out the top three — the same titles r/ExperiencedDevs favors, but driven by different motives. Where r/ExperiencedDevs reaches for system design and management books because it's already past the gate, r/cscareerquestions treats them as credentials to acquire. The Manager's Path (34 mentions) and The Phoenix Project (40) also appear, suggesting a slice of the sub is thinking past the first job.

Guides built from this community

Ranked best-of lists and editorial guides that draw on r/cscareerquestions's tracked mentions.

By year

2026 2025 2024 2023 2022 2021 2020 2019

Most-mentioned in r/cscareerquestions

Ordered by tracked mention count across all published years. Sentiment is shown as context and does not change the order. The Upvotes toggle re-sorts by comment-score weight — display only, the canonical order stays mention-count.

Sort by upvotes = sum of comment scores on recognized mentions

Cracking the Coding Interview

Gayle Laakmann McDowell

The book credited with inventing the modern coding interview, argued about like it's also on trial for it.

391 in this sub mixed

Clean Code

Robert C. Martin

Robert Martin's case that unreadable functions are a discipline failure, not an inevitability, argued one renamed variable and one extracted method at a time.

176 in this sub positive

Designing Data-Intensive Applications

Martin Kleppmann

Martin Kleppmann walks backend engineers through every database, queue, and consistency tradeoff they'll eventually get paged about.

124 in this sub positive

Design Patterns

Erich Gamma

Four authors catalog twenty-three recurring object-oriented problems in 1994 and hand every future code review the same argument to have.

71 in this sub positive

The Pragmatic Programmer

Andy Hunt

Two working programmers write down the shop habits senior engineers use so junior ones stop reinventing them badly.

68 in this sub positive

The Mythical Man-Month

Frederick P. Brooks Jr.

Fred Brooks managed IBM's late-1960s OS/360 project, then wrote the book explaining why adding more programmers only made it later.

47 in this sub positive

Code Complete

Steve McConnell

Steve McConnell's seven-hundred-page argument that construction, not design or testing, is where most software quality is actually won or lost.

43 in this sub positive

Introduction to Algorithms

Thomas H. Cormen

A course syllabus gets posted, and a Redditor recognizes it as nothing but this book's chapter headings in disguise.

41 in this sub positive

Elements of Programming Interviews in Python

Adnan Aziz

Three hundred coding-interview problems, an online judge, and a study guide, all built to answer a shorthand Reddit already assumes you know: EPI.

33 in this sub positive

#10

System Design Interview

Alex Xu

You get handed a whiteboard and forty-five minutes to design something like TinyURL, and this is the crash course for surviving that conversation.

33 in this sub positive

#11

The Phoenix Project

Gene Kim

A struggling IT VP inherits a doomed project, a company on the edge of collapse, and one coworker who has quietly become the company's entire bottleneck.

29 in this sub positive

#12

Refactoring

Martin Fowler

Martin Fowler's method for restructuring code's internals without anyone outside noticing that anything changed at all.

24 in this sub positive

#13

The Manager's Path

Camille Fournier

A software engineer becomes a tech lead, then a manager, then a director, and the book insists on teaching you each rung separately.

24 in this sub positive

#14

Staff Engineer

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.

21 in this sub positive

#15

Structure and Interpretation of Computer Programs

Harold Abelson

Six chapters into Scheme, you're writing an interpreter for a language you invented an hour ago.

19 in this sub mixed

#16

The C Programming Language

Brian W. Kernighan

Two authors write the book that becomes 'K&R,' and forty years later Reddit still uses it as shorthand for programmers who had to know everything themselves.

19 in this sub positive

#17

Clean Architecture

Robert C. Martin

Robert Martin's rule: business logic sits at the center of the system, frameworks and databases plug in at the edges, never the other way around.

18 in this sub positive

#18

Modern Software Engineering

David Farley

Dave Farley argues the real gap between a 10x engineer and everyone else is how much rework they eliminate before it ever happens.

16 in this sub Not scored

#19

Effective Java

Joshua Bloch

Joshua Bloch turns fifty-plus Java gotchas into itemized rules, and one of them — favor composition over inheritance — outgrew the book entirely.

15 in this sub positive

#20

The Clean Coder

Robert C. Martin

Uncle Bob's professionalism manual: say no to bad estimates, refuse death marches, and work the 40 hours then study on your own time.

15 in this sub positive

#21

The Effective Engineer

Edmond Lau

Edmond Lau argues the engineers everyone calls 10x aren't working ten times the hours; they're choosing higher-impact work, chapter by chapter through why.

15 in this sub Not scored

#22

Head First Design Patterns

Eric Freeman

A junior dev dreads every requirement change until a book full of cartoon ducks and strategy patterns rewires how they see the problem.

12 in this sub positive

#23

Working Effectively with Legacy Code

Michael C. Feathers

A consultant walks into a five-year-old codebase with zero tests and a deadline, and writes the manual for surviving exactly that.

12 in this sub positive

#24

Peopleware

Tom DeMarco

DeMarco and Lister time how long it takes a programmer to get back into the zone after one interruption, then build a whole management argument around that number.

11 in this sub Not scored

Looking for more? Similar subreddits

Subs whose top-mentioned books overlap most with this one.

r/ExperiencedDevs 55 r/learnprogramming 51 r/programming 46 r/webdev 36 r/devops 36