Part 2 of 8 · 1 min read
Plan
Time for each phase.
Think of a short race with fixed checkpoints. Reaching each checkpoint on time matters more than speed in one stretch.
The time plan.
| Minutes | Phase | Goal |
|---|---|---|
| 0 to 5 | Scope | Agree what to build and what not to build |
| 5 to 10 | Numbers | Estimate the load and the data |
| 10 to 20 | First design | A simple, complete design with a numbered flow |
| 20 to 35 | Deep dive | Fix the bottleneck, design the hard part |
| 35 to 42 | Failures and trade-offs | What breaks, what is given up |
| 42 to 45 | Close | Summary, and questions |
Roles. The candidate leads. The interviewer answers scope questions, gives hints, and picks the deep dive if the candidate does not. A good candidate does not wait for the interviewer to drive.
What is judged (the rubric of section 5).
- Structure and communication.
- Scoping and requirements.
- Numbers.
- Design quality and correctness.
- Depth in one or two areas.
- Trade-offs.
- Reliability and failure thinking.
- Handling hints and follow-ups.
Think aloud. The interviewer cannot see inside your head. Say what you are choosing and why in one sentence: "I choose a message queue here because the work is slow and can be done later."
Mock interview
A mock interview is a practice interview held with a friend or alone, with the same time limit and rubric as a real one.
Example: two learners swap roles. One plays the interviewer with a prompt and the rubric, and the other designs a ticket booking service in 45 minutes.
Check yourself: 1. How long should the scope phase take? 2. Who leads the interview? 3. Why think aloud?