Interview Preparation
The interview isn't a test you cram for the night before - it's a performance you've already rehearsed by the time you walk in.
Learn on the move: press play and turn your commute, walk or drive into time that grows your design career.
Listen to the full Interview Preparation course on DesignPath
Most of what decides the outcome happens before you speak: whether you prepared the test task, whether your stories are ready, whether your camera even works.
Preparation is the confidence. By the time you're in the room the work is done, and you arrive to show your thinking rather than survive an exam. And when you hit a gap, be sincere - a calm "I don't know, but here's how I'd find out" reads as trust and judgment, not weakness.
This module is about that preparation, and the interview itself in order - the design challenge, your portfolio walkthrough, the behavioral questions, and the day itself.
Design Challenges
Most companies test your craft with one of two formats: a take-home you complete on your own time, or a live exercise (whiteboard or app critique) you work through in the room. Both are scoring the same thing - how you think - and most candidates sink the same way: by jumping to UI before they understand the problem.
Take-Homes: Research Before You Design
Spend the first chunk of time not designing. Skim App Store reviews, Reddit threads, and one or two competitors. Half an hour of this changes everything - it shows you solve the right problem instead of just producing screens, and it signals you'd do the same on the job. Write down, in a sentence, the real user problem you're solving before you open Figma.
Prioritize Like the Business Would
Use the Kano Model to separate must-haves from nice-to-haves. The candidate who polishes a dark-mode toggle while leaving the core requirement half-built is broadcasting misaligned priorities - exactly what a hiring team screens against. Nail the essential job first; treat delighters as bonus, clearly labeled as such.
Scope and Present the Take-Home
You're not expected to ship a product - you're expected to show judgment. Do the core flow well, and add a short note on what you'd explore next given more time.
Crucially, don't just hand over screens: include a few lines (or a 2-3 minute Loom) explaining your research, the decisions you made, and the trade-offs. A focused, well-reasoned slice with rationale beats a sprawling, silent one.
Live and Whiteboard Exercises
A live exercise is a collaboration, not a test you suffer through silently. Use a visible structure:
- Clarify the problem and constraints. Restate the prompt, ask who the user is, what success means, and what's out of scope. Interviewers want you to ask.
- State your assumptions out loud so they can correct you early.
- Diverge - sketch a few directions before committing; show you can generate options.
- Converge - pick one, and say why (the trade-off you made).
- Critique your own work - name what you'd test or where it might break down.
To get reps before the real thing, have an AI pose a whiteboard prompt and play the interviewer - the cheapest way to rehearse the live format.
Throughout, think aloud. They're scoring your reasoning, and silent brilliance reads as no brilliance at all. Treat the interviewer as a teammate - react to their nudges.
Common Pitfalls
- Jumping straight to UI with no problem framing.
- No research, no rationale - decisions that look arbitrary.
- Ignoring the stated constraints (time, platform, audience).
- Gold-plating vanity features while the core is unfinished.
- Going quiet - leaving the interviewer unable to follow your thinking.
