Running the Interview Challenge
The way you run a whiteboard challenge impacts the candidate's performance and your ability to assess them fairly. It's the difference between getting a clear picture of someone's abilities and getting a stress-induced performance that doesn't reflect their actual capabilities.
Interview Setup and Logistics
Physical Space (In-Person)
Essential Elements:
- Whiteboard or writing surface: Large enough to work comfortably; full board is ideal
- Markers: Multiple colors (at least 3-4), all working with bold color
- Eraser or cleaner: Ready if they need to clear space
- Seating: Chair that allows them to stand and work comfortably
- Visibility: Everyone can see the board clearly
- Quiet: Minimal distractions or interruptions
Virtual Space (Remote)
Technical Setup:
- Test whiteboarding software beforehand (Miro, Figma, Google Jamboard, etc.)
- Ensure screen sharing works smoothly
- Have a backup tool in case of technical failure
- Test audio/video quality
- Send whiteboarding tool link and instructions ahead of time
Considerations:
- Virtual whiteboarding can feel more stilted; be extra warm and encouraging
- Candidate can't stand and move as freely; be patient if they seem uncomfortable
- Screen sharing sometimes lags; give them time to catch up
Before the Challenge Begins (10 minutes early)
- Greet candidate warmly
- Small talk to help them relax: "How was your morning?" "Found parking okay?"
- Offer water, coffee, restroom
- Mention it's okay to ask questions
- Explain the timing: "You'll have 25 minutes for the challenge, then we'll discuss"
- Brief on how you'll facilitate: "I'll watch and take notes. Feel free to think out loud"
- Ask if they have any questions before starting
Challenge Introduction (2-3 minutes)
Reading the Brief
- Read the brief clearly and completely
- Read it at a pace they can follow (not too fast)
- Don't ad-lib or change the challenge mid-read
- Pause at the end so they can process
Opening Questions
"Do you have any clarifying questions before you start?" Wait for questions. Answer them directly and clearly. Don't use questions as a test ("What do you think we should focus on?"). Just answer.
Starting the Clock
- "You have [time] for the challenge. Let's start now."
- Start your timer visibly or mention when they have X minutes left
- Be consistent about time warnings (some people appreciate "5 minutes left" warnings; some don't)
During the Challenge
Your Role: Observer, Not Facilitator
Your job is to observe their process, not to help or guide them. This is hard—resist the urge to help.
Do:
- Watch attentively and take notes
- Note the time spent on different phases
- Observe their approach and decision-making process
- Listen to how they articulate their thinking
- Note moments of hesitation or uncertainty
- Stay quiet and let them think (silence is okay)
Don't:
- Suggest ideas or approaches
- Offer affirmation ("Great idea!") that influences their thinking
- Ask them to hurry or slow down (let them self-manage)
- Distract them with your own work or phone
- Offer unnecessary information beyond the brief
If They Ask Questions During the Challenge
Clarifying Questions (Legitimate):
Candidate: "Can I assume the target user is desktop or mobile?" or "Is there a specific budget constraint?"
Answer directly: "Either is fine" or "No specific budget constraint."
Help-Seeking Questions (Don't answer these):
Candidate: "Should I focus on the UI or the flow?" or "What do you think about this direction?"
Respond: "That's up to you—whatever you think makes sense" or "Whatever direction you want to go, I'm interested to see your thinking."
When They Get Stuck
It's normal. Silence is okay. Struggling is okay. Don't rescue them.
- If they explicitly ask for help: "What are you uncertain about?"
- Let them work through it
- Don't offer suggestions unless they directly ask
If They Run Over Time
- Give a 5-minute warning if they haven't already noticed the time
- At time, say: "Time's up. Let me ask you to wrap up in the next 30 seconds"
- Don't let them continue significantly past time (it becomes unfair to compare)
What to Observe and Note
Problem Analysis Phase
- Do they start by asking clarifying questions or asking you to repeat?
- Do they immediately write down key constraints and goals?
- How do they organize information?
- Do they identify user groups? Research needs?
- Time spent on this phase (ideal: 3-5 minutes)
Research/Discovery Phase
- Do they discuss understanding the user context/needs?
- Do they consider competitive solutions?
- How systematic is their thinking?
- Time spent (ideal: 3-5 minutes)
Ideation Phase
- Do they sketch or talk through multiple ideas?
- How many concepts do they explore?
- Do they evaluate trade-offs or just pick the first idea?
- Time spent (ideal: 5-8 minutes)
Solution Development
- Are they going deep on their chosen direction?
- Are they considering details and edge cases?
- How thorough is their thinking?
- Time spent (ideal: 7-12 minutes)
Communication Throughout
- How clearly are they explaining their thinking?
- Do they check in with you ("Does this make sense?") or just proceed?
- How comfortable do they seem?
- Are they thinking out loud or silently?
Responsive Facilitation
Handling Major Misunderstandings
If candidate is clearly solving the wrong problem:
- Let them work for a few minutes if possible (gives you data on how they approach things)
- Gently clarify: "Just to check—by 'improve the booking experience,' did you understand we meant for new users?"
- Let them course-correct
- Don't penalize them for a clarification question they should have asked
Handling Off-Track Thinking
Sometimes candidates go in unusual directions. That's okay. Let them explore. You might learn something interesting about their thinking.
If They Finish Early
- Ask: "Do you feel like you're done, or is there more you'd like to develop?"
- If they're truly done, let them be done (don't pressure them to fill time)
- You'll have more time for discussion
The Final Presentation
Asking Them to Walk Through Their Solution
At the end of time: "Walk me through what you came up with."
Let them explain their solution. This is part of the assessment—how clearly can they communicate their work?
Do:
- Listen actively
- Let them finish their explanation before asking questions
- Take notes on key points and articulation quality
Don't:
- Interrupt or correct them
- Offer critique yet
- Suggest better ideas
Discussion and Follow-Up Questions (5-10 minutes)
Clarifying Your Understanding
- "Tell me more about why you chose this approach over other options"
- "How would this work for [different user type]?"
- "What would you do differently if [new constraint]?"
Exploring Their Thinking
- "What was the hardest part of this challenge?"
- "If you had more time, what would you change?"
- "How would you validate whether this works?"
Assessing Flexibility
Present a new constraint or question and see how they respond:
- "What if we learned that our main user group was on mobile, not desktop?"
- "One stakeholder thinks we should prioritize X instead of Y. How would you respond?"
Feedback in the Moment
You don't need to give detailed feedback during the interview. A simple closing works:
"Thank you for working through that thoughtfully. We'll take some time to review and get back to you with feedback."
Wrapping Up
Next Steps
- Explain what happens next: "We'll review your work and be in touch by [date]"
- Thank them for their time
- Be warm—they put themselves out there
Immediate Post-Challenge Notes
Within 15 minutes of the interview, while it's fresh:
- Write down key observations
- Note specific strengths and growth areas
- Score on your assessment rubric
- Capture quotes or specific moments that stood out
Remember
Your job running the challenge is to create an environment where someone can do their best thinking, observe their process fairly, and document what you learned. A candidate's performance in a whiteboard challenge is one data point in hiring. Combined with portfolio review, interviews, and references, it helps you make a stronger decision.