Why include overhead time at all?

Because skipping it is the most common reason people’s practice pacing does not match the real interview — a 60-minute slot rarely means 60 minutes of questions.

What if my round has very different question types mixed together?

Run the calculation once per question type with its own expected count, rather than averaging technical and behavioural questions together.

Is less time per question always bad?

Not necessarily — a phone screen with five quick questions is meant to be fast. Use the guidance line as a sanity check against the round type, not an absolute rule.

Interview prep timer

A round that is sixty minutes long is not sixty minutes of question time — introductions, a bit of small talk and wrap-up eat into it, and most people do not budget for that when they practice.

Set your round length, how many questions you expect, and how much of that time is genuinely spoken versus overhead, and this works out how long you actually have per question.

Time per question

12.5 minutes

Split roughly: behavioural answers run short, technical and system design questions run long — do not divide the time evenly across very different question types.

Total round length: 60 minutes
Overhead (intro, wrap-up): 10 minutes
Time available for questions: 50 minutes
Questions expected: 4
Average time per question: 12.5 minutes
For a 90-second practice answer: Fits comfortably within budget

Everything above is worked out in your browser. Nothing you type is sent to us or saved anywhere.

How this is worked out

Available time is the round length minus the overhead you set aside for introductions and wrap-up.
Time per question is that available time divided evenly across the number of questions you expect.
The guidance line below the headline changes with the round type, since a behavioural answer and a system design question do not take the same amount of time by nature.

What this does not cover

This assumes questions get roughly equal time, which real interviews rarely do exactly — use it to set a practice budget, not a strict interview-day rule.
It does not simulate or time you live; it is a planning calculation, not a stopwatch.
A system design or deep technical round with very few questions is normal — do not force this into more questions than the round actually asks.

Questions people ask

Why include overhead time at all?: Because skipping it is the most common reason people’s practice pacing does not match the real interview — a 60-minute slot rarely means 60 minutes of questions.
What if my round has very different question types mixed together?: Run the calculation once per question type with its own expected count, rather than averaging technical and behavioural questions together.
Is less time per question always bad?: Not necessarily — a phone screen with five quick questions is meant to be fast. Use the guidance line as a sanity check against the round type, not an absolute rule.

Where these figures come from

Rates and rules on this page were last checked against the source on 31 August 2026. Tax law changes; check the source before you rely on a number for a decision.

Related calculators

Running these numbers because you are weighing a move? See what is open right now.