Five recurring brief types
UX whiteboard briefs in 2026 cluster into five recurring types. Knowing the type lets the candidate map their preparation onto the brief in the first 60 seconds, which saves time and improves response quality. The five types: improve an existing flow, design for a new user group, add a feature, solve an abstract problem, critique an existing product.
The brief is intentionally underspecified. The interviewer is watching what assumptions the candidate names, what constraints they ask about, and how they structure ambiguity. Candidates who treat the brief as a literal instruction usually underperform; candidates who treat it as a starting point for inquiry usually convert.
The response structure that converts
How to spend the time
- Clarifying questions (3–5 min). What's the goal? What's the constraint? Who's the user? What's the time horizon? Two or three questions, not ten.
- Problem framing (5 min). Restate the problem in one sentence. Name the tension. State the assumption you're proceeding on.
- User and scenario (5 min). Identify the primary user, the scenario, the moment of friction.
- Candidate solutions (8 min). Two or three candidate solutions. Name what each does well and what it trades off.
- Sketch (5 min). Sketch the preferred solution at a low fidelity. Communicate, don't design.
- Self-critique (3 min). What you'd want to validate. What you're not sure about. What you'd test first.
For 45-minute briefs, expand framing and solutions. For 60-minute briefs, add a second scenario.
Brief 1 — Improve an existing flow
"Design a better checkout flow for [retail/SaaS/fintech] product." The most common brief type. The interviewer is testing whether the candidate can identify friction points, prioritise improvements, and articulate why their proposal moves the metric the team cares about.
Response pattern that works: clarify the user (new vs returning), clarify the constraint (mobile vs desktop, time-boxed for shipping or longer rebuild), name three to five friction points you'd interrogate, pick the highest-leverage one, propose a change, name the trade-off. Candidates who try to redesign the entire flow usually lose; candidates who pick one decisive change and defend it usually win.
Brief 2 — Design for a new user group
"Design [product feature] for [an underserved population]." Testing whether the candidate can apply inclusive design thinking without slipping into stereotype.
Response pattern: name what you'd want to research before designing (the most important move — it signals you don't assume), state the assumptions you're proceeding on if research isn't possible in 30 minutes, identify the constraints that group might face (technical, cultural, accessibility), and design around those. Candidates who design as if they know the user group's needs in detail tend to lose; candidates who explicitly name the limits of their knowledge tend to win.
Brief 3 — Add a feature
"How would you add [feature] to [existing product]?" Testing whether the candidate can think about feature integration, surface placement, and the cost of adding complexity.
Response pattern: clarify the goal (what does adding this feature achieve for the user and the business), assess whether the feature should be added at all (the strongest candidates often push back here — "I'd want to validate the assumption that this is the right intervention"), identify candidate surfaces, name the cost of each, propose a placement, sketch.
Brief 4 — Solve an abstract problem
"Design a way for people to [do something low-tech, e.g., wake up on time / drink more water / find a parking space]." The most ambiguous brief type. Testing whether the candidate can decompose ambiguity and frame a tractable problem.
Response pattern: explicitly narrow the problem. "I'm going to design for [specific user group], in [specific scenario], optimising for [specific outcome]." The candidate's choice of narrowing is the most predictive moment of the whole round. Strong narrowings reveal judgement; weak narrowings (e.g., "everyone, in any scenario") read as evasive.
Brief 5 — Critique an existing product
"What would you change about [the interviewer's product / Twitter / Amazon]?" Testing whether the candidate can structure a critique without descending into opinion.
Response pattern: pick one specific user journey rather than critiquing the whole product. Walk through the journey with named friction points. Pick the most decisive one. Propose a change. Name what you'd want to validate. Candidates who try to critique the whole product in 30 minutes lose; candidates who pick one journey and go deep usually win.
What interviewers watch for
The whiteboard rounds I ran as a hiring manager, the candidates who converted were almost always the ones who paused before answering, asked the question that actually mattered (not the question that sounded thoughtful), and then articulated their reasoning out loud as they sketched. The candidates who failed were almost always the ones who started sketching before they'd named what they were solving.
Four diagnostic signals interviewers consistently watch for:
Pace. Strong candidates manage the time visibly — naming when they're moving from framing to solutions, checking the clock without anxiety, giving themselves room for self-critique. Weak candidates either rush or run out.
Pushback handling. Interviewers will challenge a decision midway. The strong response: acknowledge the challenge specifically, restate the assumption you were proceeding on, decide whether to revise or defend. The weak response: collapse and rework everything, or defend without engagement.
Honest self-critique. The self-critique section at the end is often what separates strong from average. Strong candidates name what they'd validate, what they're uncertain about, what the trade-off cost is. Average candidates skip the self-critique or treat it as a victory lap.
Communication clarity. The thinking is half the round. Strong candidates narrate their reasoning out loud, write key decisions on the board, and check in with the interviewer about whether the framing makes sense before going deep.
For the full interview pipeline view, see interview preparation guide. For interview question patterns, see UX interview questions. The take-home alternative is covered in take-home assignment guide. The presentation round is in interview presentation guide.
For the broader portfolio defence — which often comes up in whiteboard preamble — see portfolio examples and case study examples.
Frequently asked questions
How long is a UX whiteboard challenge?
Typically 30 to 60 minutes. 30 for screening, 45 to 60 for final-stage rounds. Some companies have moved to take-home alternatives in 2026, but whiteboards remain common at FAANG, fintech and consultancies.
What does a UX whiteboard interviewer watch for?
Problem framing, clarifying questions, structured thinking, trade-off communication. The output sketch matters far less than the thinking process.
Can I use a framework in a UX whiteboard challenge?
Yes, sparingly. A loose framework provides scaffolding under time pressure. Detailed rehearsed frameworks tend to read as performative.