Book · 2008
Cracking the Coding Interview
by Gayle Laakmann McDowell
The book credited with inventing the modern coding interview, argued about like it's also on trial for it.
What does Reddit think of Cracking the Coding Interview?
r/cscareerquestions carries the overwhelming majority of the mentions here, and what it's arguing about is genealogy, not quality. One heavily upvoted comment (↑348) states it as history: this book is where the era of 'preparing' for algorithm interviews actually started. Another (↑263) sharpens the blame, crediting Gayle Laakmann McDowell's book with introducing programming challenges to hiring, and Meta with weaponizing that format into LeetCode grinding. A third (↑272) calls the material outdated outright, 'the algorithms have expired,' brush up on AI prompting instead. The most specific citation (↑278) is McDowell's own advice, tell the interviewer if you've seen the problem before, recounted the way people recount advice that didn't pay off. r/programming's canon-ranking thread (↑655) seats it alongside Clean Code and Pragmatic Programmer, for scale, not agreement. Being credited with inventing a genre reads, across this sample, like a charge sheet as often as a compliment.
Community feedback & reader fit
Themes
- · credited with inventing interview-prep culture
- · blamed for the LeetCode grind culture
- · the 'admit you've seen it before' advice
- · called outdated by 2026 posters
Common praise
- + One commenter (↑348) credits it with literally starting the era of interview preparation — origin-story status, not just a recommendation.
- + The canon-ranking thread (↑655) keeps it in rotation next to Clean Code and Pragmatic Programmer years after publication.
Common criticism
- − Another commenter (↑263) blames the book's format, amplified by Meta's hiring practices, for the LeetCode grind culture that followed.
- − A recent comment (↑272) calls the material outdated outright, arguing the algorithms 'have expired' and telling readers to focus on AI prompting instead.
- − The specific advice about admitting you've seen a problem before (↑278) gets recounted like a cautionary tale, not a technique that worked.
Who it's for
Read this if you want the book that codified the modern coding interview, for better or worse, per the poster (↑348) who calls it the start of the whole 'preparing for interviews' era. Interviewing somewhere that's moved past algorithm puzzles? One recent commenter (↑272) says the material has already expired, and to spend your time elsewhere. McDowell's specific advice on flagging a memorized problem is in here, but at least one Redditor's retelling (↑278) reads like a warning rather than an endorsement, so weigh that before following it verbatim.
Mentions over time
Which Reddit comments matter for Cracking the Coding Interview?
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 think it's interesting that at he says to not try get good at interviewing, but to get good at being a SWE. In my experience, this is the exact wrong approach to the Google interview. The Google interview tests almost no real…
“Here's the list, for anyone interested in just that: 1. The Pragmatic Programmer by David Thomas & Andrew Hunt (67% recommended) 2. Clean Code by Robert C. Martin (66% recommended) 3. Code Complete by Steve McConnell (42% recommended) 4. Refactoring by Martin Fowler (35% recommended) 5. Hea…
“HackerRank + LeetCode for SQL interview questions, LeetCode easy gets you past coding rounds at most companies, Cracking the PM Interview is good for product data science questions and more open-ended business-y DS case problems. For ML interview questions, just knowing the most important concepts +…
“Read about the JVM and the implications it has as far as running and compiling code. Understand pass by reference and value and how those relate to java. Learn the difference between an interface and an abstract class I feel like that always comes up when talking about Java. As far as syntax go…
“Big companies started asking simple algorithm questions as a language agnostic way to Guage candidates coding and critical thinking ability. Then a book was published called 'cracking the coding interview'. This was a beginning of Era where candidates started to 'prepare' for these interview. As av…
“In the book "cracking the coding interview", the author tells you to inform the interviewer immediately if you've seen the problem before. She claims you'll get rewarded for your honesty and that the interviewer can immediately tell if you're just regurgitating a memorized solution. I had a Faceboo…
“No it is not relevant. Coding has changed drastically in the past few years. You wouldn't be able to recognize what code looks like. The algorithms have expired. You need to brush up on AI prompting and quantum computing. You need to become one with a cloud. The companies mentioned in CTCI don't eve…
“Meta / Facebook actually ruined it for all by pushing Leetcode as text-book prep for interviews in this diverse field. Let me explain why. Gayle Laakmann McDowell, the ex-Googler who actually introduced programming challenges as a part of the hiring process, described it better in her book "Crackin…
“Here's my list of the classics: **General Computing** * But How Do It Know? - The Basic Principles of Computers for Everyone * The Elements of Computing Systems: Building a Modern Computer from First Principles * […
“F*** the woman who wrote CTCI. She single-handedly changed the tech interview process to be like how only google’s was at the time, i.e. an algorithm memorization test. I’m surprised google was even ok with her monetizing their interview process in the first place. Imagine writing a book dedicated t…
“I miss the days when even knowing what CTCI was gave you a distinct edge.
“Delete Facebook Hit the Gym Get Cracking the Coding Interview
“there is a book I bought called cracking the coding interview that really helped me, it's worth a read, but overtime you begin to realize these problems are virtually the same just rehashed to look like something else, once you pick up that pattern you'll begin to see it. I NEVER CODE RIGHT AWAY T…
“when I first got my cs degree I had a mini crisis. I recommend getting cracking the coding interview and starting slow. Remember hackerrank style questions are very different from your day job and if you haven’t done them in years you’ll definitely be slow to change gears. Give yourself time to …
“They popularized it but it became ubiquitous with every Tom, Dick, and Harry "startup" out of the Bay Area and Seattle copying this approach, because if Google and Amazon are doing it then it sure is the only correct way to hire strong engineers. Equally to blame is Gayle McDowell who popularized t…
Convinced? Pick up Cracking the Coding Interview
Readers also mention
Books that share discussion threads with Cracking the Coding Interview — counted from the comments, not curated.
Guides featuring Cracking the Coding Interview
Ranked best-of lists and editorial guides where this book's tracked mentions place it.
Cracking the Coding Interview — frequently asked
Did Cracking the Coding Interview actually start the LeetCode interview culture?+
That's the claim in this sample, not a settled fact. r/cscareerquestions (↑348) calls it the beginning of the era where candidates started 'preparing' for algorithm interviews, and a separate comment (↑263) blames Meta for weaponizing the format Cracking the Coding Interview popularized into today's LeetCode grind.
Is Cracking the Coding Interview still relevant in 2026?+
Not according to one pointed r/cscareerquestions comment (↑272), which says coding has changed drastically and 'the algorithms have expired,' suggesting readers focus on newer skills instead. That's one voice in the sample, but it's the most direct verdict on the book's current relevance.
Should I follow Cracking the Coding Interview's advice to tell the interviewer I've seen a problem before?+
The book's own advice, per one retelling (↑278), is that honesty gets rewarded because interviewers can tell when you're regurgitating a memorized solution. The Redditor's own story that follows the citation reads like it didn't go well, so treat the advice as debated rather than proven.
Who wrote Cracking the Coding Interview, according to Reddit's discussion of it?+
Gayle Laakmann McDowell, described in one comment (↑263) as the ex-Googler credited with introducing programming challenges into hiring, a detail raised specifically to explain how her book's format ended up driving the LeetCode-style interview that followed.