Most UX designers apply for jobs with a reasonable understanding of what their portfolio should contain and a vague dread about what happens after the portfolio is submitted. The interview process for design roles is less standardized than it is for engineering — there are no LeetCode-style exercises with objectively correct answers, no universally agreed-on question banks, and no consistent stage count across companies. A process at a startup might be three conversations. A process at Google or Airbnb might be eight stages across six weeks, including multiple design exercises and a presentation to a panel of senior designers.
What is consistent across virtually all UX design interviews is the portfolio review — and the design challenge that accompanies it. These two stages are where most candidates succeed or fail, and where the gap between good interview performance and great interview performance is almost entirely explained by preparation and self-awareness rather than raw design skill.
This article maps the complete UX design interview process: the stages most candidates encounter, what each stage evaluates, how to walk through a case study effectively, how to approach design challenges, what interviewers are really looking for beneath the questions they ask, and the red flags that should make a candidate reconsider an offer.
'In a portfolio review, I am not evaluating the final design. I am evaluating how the designer makes decisions under constraint, and whether they are honest about what they do not know. Confident uncertainty is much more persuasive than false conviction.' — Aarron Walter, VP of Design Education at InVision, in a 2023 design leadership podcast
Key Definitions
Portfolio Review: A structured interview stage in which a candidate presents two or three case studies from their portfolio, walking the interviewer through their design process, decisions, and outcomes. Typically 45-90 minutes.
Design Challenge (Take-Home): An open-ended brief sent to a candidate to complete independently before an interview. Legitimate challenges are scoped for 4-8 hours of work. The presentation and critique of take-home work typically forms a full interview stage.
Whiteboard Challenge (Live Design Exercise): A design problem presented to the candidate during an interview and solved in real-time. Evaluates structured thinking, communication, and comfort with ambiguity more than final design quality.
Behavioral Interview: An interview round using structured questions based on past experience — 'Tell me about a time when...' — to assess collaboration skills, conflict resolution, feedback reception, and strategic judgment.
Design Critique Interview: A stage in which the candidate is asked to review an existing product or design artifact and provide structured feedback, demonstrating analytical and communication skill.
Interview Process by Company Type
| Company Type | Typical Duration | Stages | Design Challenge Format | What Differentiates Candidates |
|---|---|---|---|---|
| FAANG / Large Tech | 5–8 weeks | 5–8 stages | Take-home + panel presentation | Structured process thinking |
| Series B–D Startup | 2–4 weeks | 3–5 stages | Take-home or live exercise | Breadth of craft, speed |
| Enterprise / Non-Tech | 4–8 weeks | 4–6 stages | Portfolio review + exercise | Stakeholder communication |
| Agency / Studio | 1–3 weeks | 2–4 stages | Portfolio + skills test | Execution speed, visual range |
| Government / Public Sector | 4–10 weeks | Variable | Structured exercise | Process documentation |
Stage 1: Recruiter Screen
The recruiter screen is typically a 30-minute phone or video call covering role expectations, basic background questions, and a mutual logistics check — timeline, location requirements, compensation expectations. The recruiter is filtering for coherent work history, basic communication quality, and whether the candidate's stated expectations are compatible with the role.
Preparation for the recruiter screen is minimal but important: know your headline (a two-sentence summary of who you are and what you do), know what type of role you are looking for and why this one fits, and know your current or expected compensation range.
One common mistake at this stage is failing to ask any questions. Asking one or two thoughtful questions — 'What design challenges is the team working on most actively right now?' or 'How large is the design team and what is its relationship with product?' — signals genuine interest and starts gathering the information you need to evaluate the opportunity.
Stage 2: Portfolio Review
The portfolio review is the central stage of the UX design interview process and the one on which hiring decisions most heavily weight. Most candidates underperform their actual ability at this stage by making structural errors in how they present their work.
The Framing Problem
Most candidates begin portfolio presentations with the solution: they open Figma and show the final design. Strong candidates begin with the problem: they explain who the users were, what they were struggling with, and why the problem was worth solving. The difference between these two opening moves signals immediately whether the designer is solution-oriented or problem-oriented — and product teams want problem-oriented designers.
Pacing and Detail
Candidates routinely try to show too much in too little time. If you have 45 minutes and two case studies, you have approximately 18 minutes per case study plus transition time. Practice your presentation to fit this constraint.
For each case study, structure your walk-through around four moments:
- The problem and context (3-4 minutes)
- The research and what you learned (4-5 minutes)
- The design decisions and why you made them (5-7 minutes)
- The outcome and reflection (3-4 minutes)
Invite questions at each stage rather than presenting as a monologue.
Handling Questions About What You Did Not Do
Interviewers will probe the boundaries of your involvement: 'Why did you not test with more participants?' 'Why was this approach chosen over an alternative?' Strong candidates answer these questions honestly and specifically. Not knowing the answer to a specific question is not a failure — fabricating an answer is.
Stage 3: Design Challenge
Take-Home Format
Take-home challenges are the most common format at product companies. A legitimate challenge brief includes: a context description, a specific design problem to address, available information about the users and business constraints, and a time expectation scoped to 4-8 hours.
Candidates should resist the temptation to over-invest. A design challenge is a sample of your thinking, not a shipped product. A clearly documented decision process with rough wireframes and honest constraints analysis will outperform a polished but unexamined final design.
Structure your take-home response to explicitly address: how you understood the problem, any research you referenced, the alternatives you considered, the approach you chose and why, what you would validate with users before building, and what assumptions you made that require testing.
Live Whiteboard / Design Exercise
Live design exercises evaluate real-time problem structuring more than design execution. The most effective approach:
- Ask clarifying questions before picking up a pen. 'Who are the users? What is the business goal? Are there existing patterns I should be consistent with?'
- State your assumptions explicitly.
- Structure your thinking out loud: 'I am going to start with the user journey rather than jumping to individual screens.'
- Seek feedback as you go. Treating the exercise as a collaborative conversation rather than a solo performance demonstrates cross-functional collaboration skill.
Stage 4: Behavioral Interviews
Behavioral interviews use past experience to predict future behaviour. Common behavioral questions for UX designers include:
- 'Tell me about a time when you disagreed with a product manager's decision about a design.'
- 'Describe a project where your initial design direction was significantly changed based on user research.'
- 'Give me an example of a time you had to deliver difficult feedback to a colleague about their design work.'
- 'Tell me about a project that shipped and did not achieve the outcome you expected. What did you do next?'
Prepare specific answers using the STAR format (Situation, Task, Action, Result) before interviews begin. Avoid generic answers that could apply to any designer in any company. Specific examples are dramatically more persuasive than general statements about your approach.
Stage 5: Cross-Functional Partner Interviews
Many companies include interviews with engineers, product managers, data analysts, and researchers who would work closely with the designer being hired. These interviews evaluate cross-functional communication and collaboration.
The most important thing to demonstrate in cross-functional interviews is genuine curiosity about and respect for the other function's perspective. Engineers want to know that a designer understands technical constraints. Product managers want to know that a designer can think about business metrics. Data partners want to know that a designer values quantitative evidence.
What Interviewers Are Really Evaluating
Underneath the specific questions and exercise formats, experienced design interviewers are consistently evaluating three things:
Thinking quality: Does this designer identify the right problems? Do they understand user behavior, not just user preferences? Can they reason through trade-offs clearly?
Communication quality: Can this designer explain their work to people who are not designers? Can they give and receive feedback productively? Can they influence without authority?
Self-awareness: Does this designer know what they are good at and what they need to develop? Are they honest about failures and genuinely curious about feedback? Designers who present an unbroken record of success are early-stage warning signs.
Visual quality matters, but it is evaluated through these three lenses rather than independently. A visually mediocre portfolio from a designer who clearly thinks carefully, communicates well, and is honest about uncertainty will consistently advance over a visually polished portfolio from someone who cannot explain their design decisions.
Red Flags in the Interview Process
Red flags from the company side that candidates should take seriously:
Take-home challenges exceeding 8 hours of work, or with a brief that reads like a real business deliverable. Companies that use candidates for free work during the interview process have a documented pattern of undervaluing design time post-hire.
No design team involvement in the interview process. If the only people you speak to are a recruiter and a hiring manager with no design background, you cannot assess the design culture. Request to speak with other designers before accepting an offer.
Inability to describe the design process or team structure clearly. Interviewers who cannot explain how design decisions are made, how designers interact with product management, or how design quality is evaluated are describing a dysfunctional design organization.
'We move fast and break things' culture descriptions that lack any quality process. Companies that pride themselves on moving fast without mentioning any user research, design review, or quality standards will likely ask designers to ship work that has not been validated.
Practical Takeaways
Practice your portfolio presentation out loud before the interview, not just by reviewing your slides. The gap between how a presentation feels when reviewing it silently and how it lands when spoken aloud is enormous. Record yourself presenting once; you will identify pacing problems, filler words, and unclear transitions that silent review never surfaces.
Prepare questions that evaluate the company as much as they demonstrate interest. 'What was the last design recommendation that significantly changed a product direction?' and 'How do you handle disagreements between design and engineering about what gets built?' surface more about culture than any amount of company research.
Ask for feedback after rejections whenever possible. 'I would be grateful for any specific feedback about how my portfolio or interview performance could be stronger' is a professionally appropriate request. Even partial feedback accelerates improvement faster than self-assessment alone.
References
- Walter, A. (2023). Design Hiring and Portfolio Evaluation. Design Leadership Podcast Series.
- Nielsen Norman Group. (2024). UX Designer Interview Process: What to Expect. nngroup.com/articles
- UXPA International. (2024). UX Practitioner Survey: Interview Experiences 2024. uxpa.org
- Springboard. (2024). The Complete Guide to UX Design Interviews. springboard.com/blog
- Zhuo, J. (2019). The Making of a Manager. Portfolio/Penguin.
- Dovetail. (2024). Research-Backed Design Interview Preparation. dovetail.com
- CareerFoundry. (2024). How to Ace Your UX Design Interview. careerfoundry.com
- Interaction Design Foundation. (2024). UX Design Interview Questions and Answers. interaction-design.org
- Glassdoor. (2024). UX Designer Interview Questions: Community Reports. glassdoor.com
- LinkedIn. (2024). Design Interview Process Reports: Community Insights. linkedin.com
- Buley, L. (2013). The User Experience Team of One. Rosenfeld Media.
- Knapp, J., Zeratsky, J., & Kowitz, B. (2016). Sprint. Simon & Schuster.
Frequently Asked Questions
What happens in a UX design interview?
Most processes include a recruiter screen, portfolio presentation, design challenge (take-home or whiteboard), behavioral interviews, and cross-functional partner interviews. Some companies also include a critique session where you review an existing product.
How long is a typical UX take-home design challenge?
Legitimate challenges are scoped for 4-8 hours of work. Any brief asking for a polished deliverable-ready prototype is exploiting candidates' time and is a red flag about how the company values design work.
How should I walk through a case study in an interview?
Lead with the problem and business context, not the solution. Cover the problem, research findings, design decisions with rationale, outcome, and reflection — keeping each case study to 10-15 minutes and inviting questions throughout.
What do interviewers look for in UX design candidates?
Thinking quality (structured problem-solving), communication quality (explaining decisions to non-designers), and self-awareness (honesty about what worked and what did not). Visual execution quality matters but rarely decides hiring at mid-level and above.
What are red flags in a UX design interview process?
Take-home challenges exceeding 8 hours, no design team involvement in interviews, vague answers about how design influences product decisions, and culture descriptions emphasizing speed without any quality or research process.