How do I prepare for a UX interview?

Work backwards from the rounds you'll face: rebuild two or three case studies around your decisions, rehearse behavioural answers out loud, practise critiquing a live interface against a few clear lenses, and be ready to name the UX laws and research methods behind your choices. Prepare your own questions for them too. A week of focused, spaced practice beats a panicked all-nighter.

How long does it take to prepare for a UX interview?

A focused week is enough for most people if you already have projects to talk about. Spread it out - an hour or two a day across seven days - so the material actually sticks, rather than cramming the night before. If you're rebuilding a portfolio from scratch, give yourself two to three weeks.

What should I do the day before a UX interview?

Stop learning new things. Re-read your own case studies, rehearse your two-minute and ten-minute walkthroughs out loud, prepare three questions to ask them, check the logistics (link, time zone, names), and sleep. Cramming new frameworks the night before just adds noise.

What are the rounds in a UX interview?

Most UX loops include a recruiter screen, a portfolio walkthrough, a behavioural round, a design critique or whiteboard exercise, and sometimes a take-home or product-sense round. Each tests a different thing, so preparing for one is not preparing for all - plan for each.

How to prepare for a UX interview: a 7-day plan

Most people prepare for a UX interview by re-reading their portfolio the night before and hoping. This is the other way: a focused, day-by-day plan that rehearses each round so you walk in ready instead of cramming. It assumes you already have projects to talk about - if you don't yet, start with the portfolio guide first.

The single most useful idea: prepare for the rounds, not the topic. A UX loop is not one conversation - it's a recruiter screen, a portfolio walkthrough, a behavioural round, a live critique or whiteboard, and often a take-home or product-sense round. Preparing for one is not preparing for all. Spread the work across a week so it actually sticks.

Day 1 - Map the loop and your stories

Find out the exact rounds (ask the recruiter - they'll usually tell you). List your two or three strongest projects and, for each, the one decision you're proudest of and the one thing you'd change.

Day 2 - Rebuild your case studies around decisions

For each project, write the problem, the options you weighed, what you decided and why, and the measurable result. Frame it as the job the user was trying to do, and tie the outcome to a metric - conversion, task success, a north-star metric.

Day 3 - Rehearse behavioural answers out loud

Draft real "tell me about a time" stories - a disagreement, a failure, shipping under constraint - using a simple situation-action-result shape. Say them out loud. The gap between knowing a story and telling it well is the whole game.

Day 4 - Practise the live critique

Take any app and critique it against clear lenses: Nielsen's heuristics, accessibility, the user's goal, and "what would I test first?" A structured heuristic evaluation beats scattered opinions and calms the nerves.

Day 5 - Whiteboard and research method drills

Practise a design prompt: define the user and goal before touching the UI. Rehearse choosing the right research method for a question - usability testing, card sorting, first-click tests - and why.

Day 6 - Their questions, and the UX laws worth naming

Prepare three sharp questions to ask them (how decisions get made, how success is measured, the hardest current problem). Refresh a handful of UX laws you can name naturally to show depth. See the full UX interview questions bank to drill the answers.

Day 7 - Dress rehearsal, then rest

Do a full run-through of your strongest case study, timed. Check logistics. Then stop - new material the night before adds noise, not confidence.

Keep preparing, free

One UX term a week, explained by example, straight to your inbox - the easiest way to keep the vocabulary fresh between now and the interview: