DESIGN NOTES / Design interviews
Prepare for a UX design interview without a script.
Prepare evidence, project discussions, and collaborative exercises for a design interview. Confirm the format, practise honest answers, and protect confidential work.
Confirm the process instead of guessing the test
Ask the recruiter or coordinator about the format, duration, audience, expected materials, and any preparation instructions. A portfolio discussion, a collaborative exercise, and a behavioural conversation need different preparation. Read current official guidance for the employer when available, but do not assume every role uses the same sequence. Public preparation material does not provide confidential questions or a guaranteed route through an interview.
Clarify presentation technology, permitted tools, recording arrangements, and any restrictions on AI assistance. Request accessibility accommodations through the stated channel when needed; you do not have to turn an accommodation request into a public portfolio story. If the format remains unclear, prepare a flexible project summary and a few questions rather than guessing at a rigid script.
Build an evidence map for the role
List the role’s core responsibilities and match each with something you can discuss honestly. For each example, note the context, your responsibility, a consequential decision, the evidence available, and the limitation. Include collaboration and changes of direction as well as finished outputs. A useful example does not require a dramatic success story; it requires enough detail to explain your thinking and contribution.
Keep team achievements distinct from your work. If you cannot disclose an artifact, seek permission for a sanitised version or choose another example. Do not upload restricted material into public presentation tools or interview-preparation services. Label personal concepts, coursework, and untested proposals accurately. Record genuine gaps in experience so you can answer questions about them directly rather than improvising credentials.
Rehearse a project at more than one depth
Practise a short overview, a fuller walkthrough, and one detailed decision discussion. Start with the problem and your role, then explain the constraint, alternatives, decision, evidence, and remaining uncertainty. Make it possible to skip ahead when asked. Keep supporting artifacts available without forcing the interviewer through every process step. Rehearsal should make the structure familiar, not make every sentence sound memorised.
Practise collaboration when the brief is incomplete
In a practice exercise, clarify the user, task, constraints, and desired outcome before drawing screens. State assumptions and invite correction. Explore a small number of plausible directions, describe trade-offs, and identify what evidence would help choose between them. Manage time explicitly so you can summarise your reasoning rather than ending mid-screen. Avoid performing a memorised framework when it does not answer the brief.
Ask a practice partner to challenge one assumption and interrupt with a constraint. Respond by revising your reasoning, not by defending the original idea at all costs. For take-home work, clarify scope, time expectations, confidentiality, evaluation criteria, and ownership before starting. You can raise concerns about excessive or production-like assignments without making claims about an employer’s intentions.
Prepare questions and a realistic reflection loop
Bring questions that help you assess the role: how design decisions are made, how research access works, what collaboration looks like, and how responsibilities are shared. Ask about the actual team rather than assuming a public company story describes every group. Check your links, presentation readability, and an offline backup beforehand. Keep confidential material out of any backup you may send.
After practice, note where your explanation became vague, where evidence was missing, and which answers overclaimed. Improve one weakness at a time. After a real interview, record your own impressions without distributing confidential prompts or other people’s personal details. A thoughtful follow-up can clarify something you discussed, but it should not pressure anyone for a decision. Preparation improves readiness; it cannot guarantee selection or an offer.