UX/UI Designer
Interview Questions & Prep
Design interviews run differently from most technology loops because the portfolio, not the resume, decides whether you advance — the interview's real job is to test whether the thinking behind your portfolio is as strong as the pixels. Panels probe process as hard as outcome: how you scoped the problem, what research grounded the decision, what you'd change with more time. Expect at least one live critique or whiteboard exercise, and expect to defend decisions you made months or years ago in the moment, not just describe them.
These aren't leaked question lists, and no page can predict your interview verbatim — they're the patterns these interviews reliably follow. Use them to build your own stories, not to memorize someone else's.
How UX/UI Designer interviews are typically structured
Typical loop: recruiter screen, a portfolio presentation or walkthrough with the hiring manager or design lead (usually 45-60 minutes on 2-3 projects), a design exercise or whiteboard challenge (sometimes a take-home, increasingly live to see real-time thinking), and cross-functional rounds with engineering or product partners. Accessibility and design-systems fluency are now near-universal topics somewhere in the loop, not specialist add-ons.
The questions — with a practice tracker
Open a question to see what it's really probing and what a strong answer covers, then build your notes right there. Mark each one ready as your story firms up.
Ready to practice your interview responses out loud?
The free AI coach asks you these questions one at a time and gives honest feedback on what you actually write.
Your prep tracker: 0 of 10 questions marked ready
Notes and progress are saved in this browser only — nothing you type here leaves your device, with one exception that's always in your control: requesting the emailed PDF prep pack below sends your statuses and notes once to build the PDF (never stored, like our live preview). Clearing your browser data clears your notes too.
Take these results with you — your Interview Prep Pack (PDF)
A branded PDF of exactly what this run computed — nothing added, nothing invented. Emailed to you and downloaded here.
Your ready/needs-work statuses and typed notes are sent once to build the PDF — never stored, never used for anything else.
Opening & motivation questions
Walk me through your background and how you'd describe your design practice.
What they're really asking
Sets calibration for seniority and specialization — generalist product designer versus a research- or systems-leaning specialist — before the portfolio deep-dive begins.
A strong answer covers
- A concise arc of your design path and current focus
- Tools and depth named specifically — Figma variables, Dev Mode, component libraries
- One recent project teed up as your strongest portfolio piece
- A sentence connecting your practice to what the role appears to need
Your talking points
Why this company, and why does this product interest you as a designer?
What they're really asking
Filters candidates applying broadly from people who've actually used or studied the product, and checks whether your sensibility fits the product's stage and audience.
A strong answer covers
- Something specific you noticed using or researching their product — a flow, a design decision, an accessibility gap
- An honest read on what you'd want to work on if hired
- Awareness of their design maturity — early-stage versus an established design system — and how you'd fit it
Your talking points
Portfolio, process & critique questions
Walk me through this project in your portfolio — the problem, your process, and the outcome.
What they're really asking
The centerpiece of any design interview; tests whether the thinking behind the artifact is as strong as the artifact itself.
A strong answer covers
- The problem framed in the user's and the business's terms, not just 'I redesigned X'
- The research that grounded the direction, named specifically — user interviews, usability testing, analytics
- Key decisions defended with reasoning, not just described
- A quantified outcome if one exists, and honest acknowledgment if it doesn't
Your talking points
What would you change about this project if you had more time or did it again?
What they're really asking
The retrospective test — designers who claim a project was perfect read as either inexperienced or not genuinely reflective.
A strong answer covers
- A real limitation or compromise — timeline, technical constraint, insufficient research
- What you'd do differently and why
- What you learned that shows up in later work
Your talking points
Walk me through how you'd approach this design exercise — what would you want to know first?
What they're really asking
Live exercises test process under time pressure and whether research instinct survives a compressed timeline; the panel watches the questions asked as much as the output.
A strong answer covers
- Clarifying questions before jumping to solutions — the users, the constraints, the success metric
- A rough structure stated aloud: define, explore options, narrow, prototype
- At least one alternative considered and rejected, with a reason
- An honest acknowledgment of what you'd validate with real users given more time
Your talking points
How do you think about accessibility in your design process, and can you give a real example?
What they're really asking
WCAG 2.2 and regional accessibility law are now hard filters at many enterprises; tests whether accessibility is integrated into your process or an afterthought.
A strong answer covers
- A specific standard named — WCAG 2.2, Section 508/ADA, or the European Accessibility Act, depending on region
- Where it enters your process — design tokens, contrast checks, keyboard navigation, screen-reader testing
- A real project where an accessibility consideration changed a design decision
Your talking points
Behavioral questions — answer these with STAR
STAR = Situation, Task, Action, Result — the structure interviewers are trained to score. The scaffold under each question saves your story as you build it.
Tell me about a time engineering pushed back on a design as technically infeasible. What happened?
What they're really asking
Designer-engineer friction is near-universal; tests collaboration skill and whether you can find a workable middle ground rather than capitulating or digging in.
A strong answer covers
- The specific constraint raised, and whether it held up on investigation
- How you responded — a compromise, an alternative solution, or holding the line with reasoning
- The outcome and the relationship afterward
Build your STAR story
Describe a time your design decision was contradicted by usability testing or data. What did you do?
What they're really asking
Tests whether you follow evidence over ego — a core signal of research-grounded design maturity.
A strong answer covers
- The original hypothesis and why it seemed reasonable
- What the data or testing actually showed
- How you responded — a redesign, further investigation, or a documented trade-off if you kept the original direction
Build your STAR story
Tell me about giving or receiving difficult design critique.
What they're really asking
Critique culture is central to how design teams function; tests whether you engage substantively with feedback rather than defensively or superficially.
A strong answer covers
- The specific critique and what made it hard to hear or give
- How you separated feedback on the work from feedback on you
- What changed in the design — or your reasoning for holding your position — as a result
Build your STAR story
Describe a project where you used AI-assisted tools in your workflow. What worked, and where did you still need to do the thinking yourself?
What they're really asking
AI-assisted prototyping is a fast-rising 2026 differentiator; tests genuine hands-on use versus resume language, and whether you understand its limits.
A strong answer covers
- The specific tool and task — AI-assisted prototyping, Figma AI/Make, v0
- What it accelerated honestly, without overselling it
- Where craft or judgment still required manual work, told with an honest take on its current limitations
Build your STAR story
Your next step
The free AI coach asks them one at a time and gives honest, structured feedback on your actual answers — including a STAR check on the behavioral ones.
- Track this interview in your pipeline → Move the application to "Interview" in the free tracker so the thank-you note and follow-up happen on time — it's private to your browser.
- Stuck on a specific question? → ask the free AI career assistant — answers grounded in our published guides, with sources.
Preparation tips for this role
- Bring 2-3 portfolio projects you can walk through in real depth for 15-20 minutes each, with the research, the decisions, and an honest retrospective — depth on a few real projects beats breadth across many shallow ones.
- Practice narrating a design exercise out loud, including the clarifying questions you'd ask first — panels watching a live exercise are grading your process as much as your final screen.
- Prepare a real accessibility example, not a general statement — WCAG 2.2 fluency with one concrete project is now expected at most enterprises, not a specialist bonus.
- Have an honest 'what I'd change' answer ready for your strongest project — claiming a perfect outcome undermines credibility more than admitting a real trade-off.
- Research the company's current design maturity — an established design system versus an early-stage product — before the interview, and match your process answers to it.
Strong questions to ask them
"Do you have any questions for us?" is scored too. These show judgment — and get you information you genuinely need.
- How mature is the design system today, and how much of the team's time goes toward it versus new feature work?
- What does the collaboration model with engineering and product actually look like day to day?
- How is design research resourced — is there a dedicated researcher, or do designers run their own studies?
- What AI-assisted tools has the team adopted into the workflow, and how's that actually going?
- What would success look like for this role in the first six months?
And when the interview works: the offer
The conversation after "we'd like to make you an offer" is worth preparing too — often thousands' worth. Structure the offer with the free evaluator, or read how (and when) to counter.
First, make sure you get the interview
Interview prep only matters once a recruiter actually calls — and for most ux/ui designer applications, an ATS decides that first. Check where your resume stands before the interview questions ever come up.
Related pages for UX/UI Designer
Get more interviews to prep for
We rewrite your resume and LinkedIn profile around how ux/ui designer hiring is actually screened — human-delivered, verified by an expert ATS reviewer, in 72 hours.
Optimize my resume