On preparing for coding interviews

Q: How should I prepare for coding interviews of a certain standard sort ("algorithms and data structures interviews," "whiteboard interviews," "Leetcode interviews")?


  1. Do your best to mimic the actual environment of your interview:
    a. If possible, drill in the same IDE that you'll use in the interview.
    b. Practice talking through the question (literally, out loud, at least sometimes).
    c. If you won't be able to execute the code you write, don't let yourself do this as you write the code in practice.
    d. But do go back and make sure you wrote code that actually works, whether or not you'll be allowed to run the code during the interview.
    e. Do at least some of your practice in clothes like the ones you'll be wearing.
  2. Choose a few problems that (i) are a bit harder than will typically be asked and (ii) exercise a few essential skills (graph traversal, binary search, whatever). Do them repeatedly, as drills.
  3. LeetCode is better as a question repository and discussion forum than as a platform for testing your answers. The platform will confront you with overflow / underflow cases and other edge cases that your interviewers will overlook, guide you through, or happily leave underspecified. It's good to know about (e.g.) overflow, but it's inefficient to spend so much practice time on it.
  4. Definitely try to learn all the essentials, but not at the expense of becoming more fluent in areas you know pretty well. People sometimes spend 10 to 25 hours struggling with the tricker parts of dynamic programming or XOR hacks when they would be better off using that time to absolutely nail down basic graph search algorithms.
  5. Practice the skill of plugging away at a problem when you're stuck, but treat it as one skill among many. So: don't spend too much time struggling when you're stuck. It's more important to learn all the basic question types.
  6. Cracking the Coding Interview is an excellent question repository (and a bit underrated as an instruction / reference book). The Algorithm Design Manual is a pleasant and very different sort of reference, with plenty of "aha" moments. But beware of the trap of substituting passive reading for active preparation.
  7. Email me if you have other questions.

Subscribe to Nate Meyvis

You'll get email when I post new essays and notes.