Most live coding interviews test how well someone performs under pressure, not how well they code. A short, structured round fixes most of that, and gives you a better signal in less time.
The 30-minute structure
| Time | What happens |
|---|---|
| 0–5 min | Explain the problem, let the candidate ask questions |
| 5–20 min | Candidate codes, runs and tests |
| 20–27 min | Follow-up questions on their solution |
| 27–30 min | Candidate asks you questions |
1. Pick a small, realistic problem
Skip puzzles. Choose something close to the real job: parse a log file, paginate an API response, fix a buggy function. It should be solvable in 15 minutes by someone good.
2. Let them use a real environment
Let candidates run code and look things up the way they would at work. Remembering syntax isn't the skill you're hiring for.
3. Spend the most effort on follow-ups
The solution tells you what. The follow-ups tell you why:
- Why did you choose this approach?
- What breaks if the input is 100x larger?
- What edge case aren't you handling yet?
- What would you change before shipping?
Follow-ups are also the hardest part to fake with memorised or AI-generated answers.
4. Score against one rubric
| Score | Meaning |
|---|---|
| 1 | Can't explain their own code |
| 2 | Explains what, not why |
| 3 | Explains why and names a trade-off |
| 4 | Compares options and adapts when the constraint changes |
Write evidence, not adjectives. Free template: technical interview rubric.
5. Keep it consistent
Same problem, same time limit and same follow-ups for every candidate in the role. That's what makes it fair, and comparable.
Common mistakes
- Problems that need a trick to solve
- Silent interviewers (talk with the candidate)
- Penalising a candidate for looking something up
- Deciding in the first 5 minutes
Scaling it
If you're hiring several engineers, running this for every candidate takes a lot of senior time. Some teams use conversational AI interviews for the first round. The AI runs live coding with follow-up questions, saves a full transcript, and your engineers review it and run the final round.
More follow-up ideas: 30 technical interview follow-up questions
Top comments (0)