UX designer interviews blend craft review with collaboration and impact. Hiring managers want to see how you think, not only polished screens: problem framing, research choices, tradeoffs, validation, and partnership with product and engineering.
Whether the role is generalist, product-focused, or research-leaning, preparation should connect user needs to business outcomes—and you should be ready to discuss what you would do differently today.
Most companies score:
Process — Discovery, definition, ideation, prototyping, testing, iteration—not skipping straight to UI.
Craft — Interaction design, visual hierarchy, accessibility awareness, design system literacy.
Research judgment — When to run interviews vs surveys vs analytics; how you synthesize insights.
Collaboration — Working with PMs and engineers; handling pushback; aligning on scope.
Impact — Metrics or qualitative evidence that your work changed behavior or outcomes.
Senior loops add mentorship, critique facilitation, and strategy—how you raise the bar for other designers and influence roadmap.
Portfolio review — Walk through two to three projects with depth; expect interruptions.
App critique — Redesign or improve a known product flow; explain your reasoning aloud.
Whiteboard or take-home — Time-boxed problem; focus on process visibility.
Behavioral — Conflict with PM, tight deadline, ambiguous requirements, accessibility advocacy.
Cross-functional — Engineer or PM conversation on feasibility and prioritization.
Know which stages your target company uses so you do not over-invest in take-homes when they primarily do live critiques.
Select two flagship projects and one supporting project:
Flagship — End-to-end ownership, messy problem, clear before/after, your specific contributions labeled.
Supporting — Different skill proof: research-heavy, mobile, design system, zero-to-one vs redesign.
For each case study, structure slides or narrative as:
Context — Business and user problem (one slide, no fluff).
Your role — Team size, what you owned vs others.
Process — Research, personas or jobs-to-be-done, journey maps, sketches—not only finals.
Exploration — Alternatives you rejected and why.
Solution — Key flows, prototypes, design system alignment.
Validation — Usability tests, analytics, shipped learnings.
Impact — Conversion, task success, support tickets, NPS—honest if impact was indirect.
Reflection — What you would change with hindsight.
Remove NDA-sensitive details; use blurbs and synthetic data when needed. Interviewers forgive confidentiality; they do not forgive vague "we improved UX" claims.
"This project was checkout redesign for a B2B marketplace where cart abandonment was 38% and support tickets about billing errors spiked every month. I was the lead product designer with one researcher and two engineers over six weeks. I started with twelve moderated sessions on failed checkouts, mapped failure points to a service blueprint, and learned that tax and PO number fields—not payment UI—caused most drops. I prototyped three flows in Figma, tested with eight users, and shipped a phased release behind a flag. Abandonment fell to 24% in eight weeks, and billing-related tickets dropped 31%. I would push harder today for earlier engineering pairing on validation rules—but the research-first bet was right for this problem."
Use that pattern: problem, role, method, decision, outcome, reflection.
UX hires are rejected for brilliant portfolios and weak teamwork. Prepare stories for:
| Theme | Prove |
|---|---|
| Disagreement with PM on scope | User evidence, options, alignment |
| Engineer said not feasible | Tradeoffs, phased delivery, technical empathy |
| Ambiguous problem | How you framed and constrained |
| Accessibility fix or advocacy | Standards, user impact, prioritization |
| Fast deadline | What you cut without harming core UX |
| Research changed direction | Intellectual honesty |
| Mentoring or critique | If senior or lead track |
| Stakeholder presentation | Executive communication, not jargon |
Keep behavioral answers under 90 seconds first pass; interviewers will dig into craft details in portfolio rounds.
App critique: State users and goals first; note assumptions; walk through current flow pain; propose iterative improvements, not a fantasy full redesign in 45 minutes.
Whiteboard: Think aloud—"I would interview five users on X before locking this nav." Show structure over pixel perfection.
Take-home: Follow the brief exactly; document decisions; include accessibility notes (focus order, contrast, screen reader labels); deliver on time. Optional: short Loom if allowed.
Practice thinking aloud daily for three days before onsite. UX interviews fail when candidates go silent and draw beautiful but unexplained screens.
Prepare for:
Tie "why this company" to their product problems you understand—not color palette praise.
Answers expose craft maturity vs feature factory environments.
Days 7–5: Finalize case studies; rehearse two timed walkthroughs (20 minutes each).
Days 4–3: Run behavioral questions on voice—many UX candidates under-practice spoken answers because they focus on Figma. Parker mock interviews help with pacing, fillers, and landing a clear "result" line when nervous.
Days 2–1: App critique practice on a competitor; sleep; test screen share and file permissions.
Interview day: Water, charger, backup PDF of portfolio; for virtual, close notifications and use presenter notes sparingly.
Pixel-only narrative — No problem, research, or impact.
Credit blur — Unclear individual contribution on team projects.
Defensiveness — Critique is a collaboration simulation; welcome it.
Tool worship — Figma skill without decision rationale.
Ignoring business constraints — Beautiful flows that ignore eng cost or GTM timing.
Skipping accessibility — Treating a11y as optional "if we have time."
Behavioral rounds trip candidates who ace portfolio but ramble or hedge under pressure. Voice practice surfaces "um," uptalk, and answers that never reach outcomes.
Product designer: Shipping, metrics, iteration speed. UX researcher: Methods rigor, synthesis, influence without mockups. Design systems: Tokens, components, adoption, governance. Service design: Blueprints, ops touchpoints, org alignment.
Mirror the job description's seniority—IC vs lead—and adjust how much mentorship and strategy you emphasize.
More interview prep from Parker
