How long is a whiteboard design challenge?

Across product design and UX interviews at most tech companies, the whiteboard challenge — sometimes called a whiteboard exercise, an app critique, or a design exercise — is scheduled for 45 minutes. That window usually breaks down as a few minutes of prompt and setup, roughly 35 to 40 minutes of you working, and a few minutes at the end for the interviewer’s questions. Do not treat 45 minutes as 45 minutes of solo work: the interviewer will interrupt, probe, and occasionally redirect you, and that is part of the exercise.

A recruiter or phone screen runs 20 to 30 minutes — an initial recruiter screen that typically lasts about 30 minutes, a lightweight and often verbal version testing whether you can structure a problem at all. The standard virtual or onsite round is 45 minutes, often closer to an hour once setup and context are included, with a real prompt and a real interviewer watching you think — so practise with a clear time limit. An extended onsite can reach 60 minutes, and senior-role versions stretch to 90 minutes when the whiteboard challenge is folded together with an app critique or a follow-on design question. If you are not sure which you are getting, ask your recruiter: how long is the design exercise, and will it use a physical or digital board, or collaborative tools like FigJam or Miro?

Almost nobody fails a whiteboard challenge for running out of time — they fail for spending the time in the wrong proportions, because interviewers assess problem definition and solution-finding skills more than output. Twenty minutes drawing screens and four minutes understanding the problem, when the scorecard weights those the other way round.

The split strong candidates converge on maps to three beats — understanding the prompt, brainstorming, and execution:

• 0–5 min: clarify the problem statement, constrain the problem, and write the constraints on the board.
• 5–10 min: pick a user and a moment, define their user needs, and say why.
• 10–20 min: map the current journey and mark where it breaks.
• 20–30 min: generate multiple ideas and possible solutions quickly, weigh the promising options, then converge on one idea.
• 30–45 min: sketch, name trade-offs, and state how you would measure success.

It is a default, not a rule. In many interviews the working portion is only 20 to 30 minutes to map workflows or sketch wireframes, which is exactly why a clear design process and a repeatable step-by-step process matter. The split keeps you out of the two things that sink answers: designing before you have framed the problem, and running dry before you have named a single trade-off.

You will sometimes run out of time. Stop and summarise: say what you would have done next and what you would want to validate first. Say your reasoning out loud so the interviewer can follow your thought process. Interviewers expect unfinished work — a whiteboard design challenge is a thinking sample, not a deliverable. If you get feedback or a redirect, acknowledge the interviewer feedback and adapt; pushing ahead unchanged can hurt your performance. Finishing badly, in a rush, reads far worse than stopping cleanly with a clear plan for where you would go next.

The fix for time management is practice under a real clock, out loud, with a structured framework instead of only repeating prompts. Run timed product design exercises on an actual whiteboard with a five-phase timer that tells you what to do in each phase, use design thinking as you work, score your attempt against the rubric interviewers use, then read a worked answer for the same prompt and compare — to learn the process, not to copy patterns, because overfitting existing answers can miss the next design problem. A simple role play with a friend helps too, and plenty of free resources make it easier. After about five timed runs the format stops being scary and the 45 minutes stops feeling short. That is the entire difference between candidates who freeze and candidates who finish clean.