Part 3 of 7 · 1 min read
What the round looks like
A short prompt, a lot of talking, some code.
The prompt is usually one line: "Design a parking lot", "Design an elevator", "Design a movie ticket booking system". The interviewer expects questions first. The rest of the time goes on classes and code, and the interviewer interrupts with changes such as "now add a new vehicle type" or "now two users book the same seat at once".
Formats vary: - Whiteboard or document. Classes, fields and method names, with little code. - Editor. Compilable code for the core flow, often in the language of the candidate's choice. - Mixed. A class sketch first, then code for one or two methods.
A made-up time plan for 45 minutes:
| Minutes | Step |
|---|---|
| 0 to 5 | Questions and requirements |
| 5 to 10 | Entities and a first class list |
| 10 to 25 | Classes, links and key methods |
| 25 to 38 | Code for the main flow and one rule |
| 38 to 45 | Edge cases, a change request, tests |
Check yourself: 1. Why does the interviewer change the requirements mid-round? 2. How many minutes of the plan go to questions? 3. What is the difference between the whiteboard and the editor format?