Blank editor, someone watching. The graded thing is as much HOW you work as the final code.
~36 min · run it top to bottom
- 1. Clarify3 min3:00
Restate the problem in one sentence. Ask for an example input/output. Confirm constraints + name the edge cases yourself.
Interviewer grades: Do you understand before coding, and do you surface edge cases without being asked?
“Let me make sure I understand the problem, then I'll walk through my approach.”
checking microphone…
- 2. Approach3 min3:00
Say the brute force, then the better one. State time/space. Get a nod before you type.
Interviewer grades: Can you reason about complexity and choose, instead of jumping straight to code?
- 3. Data model2 min2:00
Pick the data structure and say WHY (fast lookup / ordering / dedup).
Interviewer grades: Do your structure choices have reasons attached?
- 4. Code + narrate18 min18:00
Write the simplest correct version, talking the whole time. Clear names. Small steps.
Interviewer grades: Communication while coding, clean correct code, steady progress without hints.
“What I'm doing here is”
checking microphone…
- 5. Test6 min6:00
Write a quick test in main, run it, walk one example by hand, then handle the edges.
Interviewer grades: Do you verify your own code? Testing discipline before you claim it works.
- 6. Complexity + tradeoffs4 min4:00
State final time/space. Then: “it's simple now — in production I'd …”.
Interviewer grades: Production sense and honest tradeoffs, not just a passing function.