interviewing.io Recorded Mock Interviews
by Aline Lerner · interviewing.io
Full-length recordings of anonymous mock interviews between real candidates and engineers from Google, Meta and Amazon, each ending with the interviewer's unfiltered verdict. Shows pacing, hint-taking and communication failures that written guides describe but never demonstrate.
More resources on Coding Interview Preparation
Intro to Behavioural Interviews
A former Facebook engineer who ran roughly a thousand interviews explains what the behavioural round actually scores: signal on conflict, ownership and self-awareness. Explains the round from the grader's side - what the interviewer is writing down and how a story is scored - rather than handing over a list of questions. That inversion is what makes it transferable to any company's behavioural loop.
Beyond Cracking the Coding Interview
The 2025 sequel to Cracking the Coding Interview, built around thirteen recurring problem patterns such as sliding window and topological sort. Adds 150+ worked problems, a spaced practice plan, behavioural preparation and salary negotiation guidance.
System Design in a Hurry
A structured delivery framework for the 35-minute system design round: requirements, API, high-level design, deep dives. Written by former Meta and Amazon staff engineers who ran the loops, with breakdowns of commonly asked designs and levelling expectations.
Cracking the Coding Interview, 6th Edition
189 problems with full solutions, preceded by chapters on how interviews are actually scored, the big-O refresher most candidates need, and an explicit five-step approach for attacking an unseen problem at the whiteboard. Its value now is the meta-content — how the round is graded, how to structure an answer aloud — more than the problem set, which online judges cover better.
Tech Interview Handbook
Free end-to-end guide covering resume, application strategy, algorithm cheatsheets by data structure, behavioural questions and negotiation. Includes the Grind 75 practice list, which orders problems by pattern coverage rather than raw problem count.