Coding Interview Checklist
On this page
Most failed coding rounds are not lost on the algorithm. They are lost on the process: coding before the problem is clear, spending 30 minutes on a clever idea, never running an example through the code. This page is the checklist to read the day before, and to keep next to you in a remote interview. It assumes you have worked through the Pattern Recognition Cheat Sheet and the pattern pages.
The week before
- Re-solve, don't re-read. Pick 10–15 problems you solved before, two or three per pattern, and write each one again from a blank file within 25 minutes.
- One language, its standard library cold. In Python:
collections.deque,Counter,defaultdict,heapq(a min-heap; negate for max),bisect,sorted(key=...), slicing,float('inf'). - Practise out loud. Do at least two timed problems while explaining every step, ideally with a friend playing the interviewer.
- Practise in the real setting: the shared editor (often without autocomplete or a run button), or a whiteboard for on-site rounds.
- Review your own mistakes list, the bugs you actually make: off-by-one, empty input, forgetting
visited,pathvspath[:].
The hour before
- Camera, microphone, internet, a charged laptop, the editor link open.
- Water, paper and a pen for drawing small examples.
- Warm up with one easy problem you know, written once from scratch. Don't start anything new.
Try it yourself first
You have the full problem. Sketch your answer, then sign up free to read the complete walkthrough.
- The complete design, flow by flow, with pictures
- Deep dives into the hard parts
- What mid, senior and staff candidates are expected to say
- Full company question lists
Free forever. No card needed.