AI Summary
5 min readNeetCode, the creator of the coding preparation platform of the same name, joined The Pragmatic Engineer for a wide-ranging conversation that started with a puzzle: if AI can now write most code, why haven't tech companies abandoned the data-structures-and-algorithms interview? The answer, he argues, has less to do with the algorithms themselves and more with what the process reveals about a candidate's thinking, communication, and willingness to do hard things. Across the episode, NeetCode returns again and again to a single theme: in an era where AI makes coding cheap, the scarce resource is the human ability to care, to explain, and to defend choices.
Why the coding interview survives
NeetCode is direct: "Companies just have no idea how to evaluate. And they probably never did." The DSA interview never predicted job performance well, but it is standardized, scalable, and simple to administer. Changing it—say, to an AI-assisted format—requires retraining thousands of interviewers and introduces new variables like prompt quality. "Any time you try to change something, you risk making it worse," he says. The format persists not because it is perfect, but because it is the least bad option at scale. Meanwhile, smaller companies can use trial periods or work-sample tests, but for big tech, the inertia of the existing system is immense.
Continue reading the full summary in the app — free to try.
Read Full Summary →Free • No credit card required
Never miss an episode of The Pragmatic Engineer
Get every new episode summarized in your inbox — free, ~5 minutes to read.
No spam. Unsubscribe anytime.
What you'll learn
- 1 (02:06) **Neet joins and opening discussion** - Why DSA coding interviews remain unchanged despite AI coding tools
- 2 (05:51) **Neet's path into programming** - Electrical engineering background and when programming clicked
- 3 (08:19) **CAP theorem and going deep** - Why the standard framing felt incomplete and preference for PACELC
- 4 (12:25) **Amazon experience** - Joining Alexa org, intense culture, and quitting after two months
- 5 (17:35) **Joining Google** - Culture contrast with Amazon and rapid L4 to L5 promotion
- 6 (21:49) **Starting NeetCode** - Tutorial videos made while jobless, then exploding after Google offer
- 7 (24:34) **Leaving Google for full-time NeetCode** - Weighing structured career vs building own thing
+ Full timestamped outline available in the app
Show Notes
Brought to You By:
• Antithesis – verify your system’s correctness without human review or traditional integration tests – and avoid bugs or outages.
• Sentry – application monitoring software considered “not bad” by millions of developers
• Google Cloud Run – run your code and host LLMs directly on top of Google’s scalable infrastructure, without having to worry about managing infra.
—
Navdeep Singh – oftentimes better known as NeetCode – is the creator of NeetCode.io, one of the most popular coding interview preparation platforms and YouTube channels for software engineers. Before building NeetCode full-time, he worked as a software engineer at Amazon and Google.
In this episode of The Pragmatic Engineer, I sit down with Neet to discuss his path from Amazon and Google to building his own startup, why he left Amazon after just two months, what he learned at Google, and the decision to leave a stable engineering career to bet on himself. We also discuss what coding interview preparation teaches beyond passing interviews, the value of going deep on difficult problems, and why systems thinking and domain expertise remain essential engineering skills in the age of AI.
Throughout the conversation, NeetCode makes the case that learning hard things is one of the single best investments an engineer can make, helping build the judgment and expertise that remain valuable no matter how the tools change.
—
Timestamps
00:00 Intro
02:57 Neet’s take on coding interviews
06:41 Getting into tech
08:56 Why Neet isn't a fan of the CAP theorem
13:12 Quitting Amazon after two months
18:22 Google vs Amazon
22:26 The origins of NeetCode
25:27 Leaving Google to go all in on NeetCode
32:02 Why Neet doesn't fix every bug
39:26 The value of coding interview prep
42:57 Systems thinking and domain expertise
47:28 Hiring at Big Tech
52:15 Tech stack at Neetcode
57:57 The NeetCode redesign contest
1:01:46 The future of software engineers
1:09:04 Hot takes: AGI, AI skill erosion, personality traits
1:22:49 “Maybe some people should just give up”
1:24:39 How to be a standout engineer
1:27:55 Book recommendation
—
The Pragmatic Engineer deepdives relevant for this episode: