Spoken answer template
Technical rounds are not only a test of what you know. They test whether you can be understood while you are thinking. Say this out loud. Reading it silently does not build the same skill.
Target: 60 to 90 seconds.
The shape
I would first prove [one operational fact].
The first evidence I would check is [command or query], because it tells me [what it proves].
If the output shows [result], I know [confirmed fact].
If it does not, I would check [alternate layer] next.
My safe next step would be [read-only or reversible action].
For the customer, I would say: [plain-English update and next check-in].
When you do not know
Saying this well is worth more than a confident wrong answer. Interviewers are listening for whether you can narrow uncertainty rather than perform certainty.
I would not want to overstate the root cause yet.
I would narrow it by proving [specific fact] first.
That tells me whether this is more likely [layer A] or [layer B].
Once I have that evidence, I can choose the least risky fix.
Things that cost candidates offers
- Naming a fix before naming a proof.
- Presenting a hypothesis in the grammar of a fact.
- Reaching for a destructive or irreversible action in a production-flavored question when a read-only one would answer it.
- Explaining what a command does instead of what its output proved.
- Going silent while thinking. Narrate the search, not just the result.