Gergely Orosz · 5 min read · Growth
Tech interviews with NeetCode
Read the original on newsletter.pragmaticengineer.com →
This Pragmatic Engineer episode features Navdeep Singh (NeetCode) discussing his journey from Amazon and Google to building NeetCode, why he left a stable engineering role, and the value of deep problem solving and systems thinking in the AI era. The conversation also covers what coding interview prep teaches beyond passing interviews and how sharing career milestones can drive audience growth.
Key Takeaways
- Engineering interviews lack a robust evaluative method; leetcode-style screens scale well for large teams but don’t necessarily predict performance.
- The CAP theorem’s two-of-three framing is widely taught but incomplete; think critically and don’t accept theorems at face value.
- Amazon’s intense culture fostered independence, which helped NeetCode succeed at Google and aided his career progression.
- NeetCode’s growth was boosted when he publicly shared his Google job, illustrating how transparency about milestones can drive audience engagement.
- Cheating tools are influencing Google to revisit onsite whiteboard interviews, highlighting how assessment formats evolve with tools and strategies.
Excerpt
Stream the latest episode Listen and watch now on YouTube , Spotify , and Apple . See the episode transcript at the top of this page, and timestamps for the episode at the bottom. Brought to You by • Antithesis – If you’re using agents to code, the problem isn’t writing the code but making sure it didn’t break anything. Antithesis runs your whole system in a hostile environment and identifies hard-to-find bugs before users hit them in production. With Antithesis, teams like Jane Street, Fly.io, and the etcd community use agents safely and ship better code, faster. Learn more.…