Gayle Laakmann McDowell Technical Interview Practice

Practice coding problems using this technical interview practice routine based on Gayle Laakmann McDowell's method. Work out loud, write code by hand, and verify manually before running in an editor.

5 time blocks, 50 minutes in total.

Time blocks

Problem Breakdown and Edge Cases: 5 min
Read problem statement and clarify assumptions out loud
Out-Loud Solution Design: 10 min
Work through small examples on paper while speaking thoughts
Paper Code Drafting: 15 min
Write line-by-line code on paper without an IDE or auto-complete
Manual Line-by-Line Tracing: 10 min
Dry-run code on paper using sample inputs and edge cases
IDE Verification and Big O Audit: 10 min
Type code into editor, run test cases, and check complexity

About this routine

Gayle Laakmann McDowell, former Google engineer and author of Cracking the Coding Interview, advocates for a structured technical interview practice routine that mimics real interview conditions. Rather than typing directly into an IDE with syntax highlighting and auto-completion, candidates practice solving problems on paper or a whiteboard while speaking their thoughts aloud.

The core of this practice cycle involves breaking down the problem, designing an algorithm visually, writing out code by hand, and dry running it with edge cases before ever touching a computer keyboard. This forces deep understanding of data structures and logic without relying on compiler error messages to catch mistakes.

Finally, the handwritten code is transcribed into an editor to test edge cases and measure efficiency. Running through this 50-minute practice block regularly builds clear communication habits and technical confidence for live engineering interviews.

Why this routine works

Builds muscle memory for whiteboard coding without IDE assistance
Improves ability to communicate thought process clearly under time pressure
Helps identify edge cases and logic errors before running code

FAQ

What is Gayle Laakmann McDowell's technical interview practice method?

It is a pen-and-paper problem-solving cycle where engineers speak out loud, write code by hand without IDE help, manually test edge cases, and then verify the code in an editor.

Why should you write code on paper during interview practice?

Writing code by hand eliminates auto-complete and compiler hints, forcing you to think through syntax, logic, and edge cases before running the program.

How long does a technical interview practice block take?

A single practice problem block takes 50 minutes, divided between paper problem-solving, manual tracing, and IDE validation.

Sources

Cracking the Coding Interview by Gayle Laakmann McDowell