How to Prepare for a UX Designer Interview With AI

Use AI for UX designer interview preparation as a skeptical reviewer, not as a substitute designer. Build a verified record for each case study, rehearse the portfolio against the role, practice unfamiliar design problems aloud, and require every critique to point to something you actually presented. The goal is to make your design judgment visible without letting a model invent research, decisions, collaboration, or impact.

This approach fits product, interaction, and user experience design interviews that combine portfolio review, a functional exercise, and behavioral questions. The exact format varies by employer, so treat the interview invitation and recruiter guidance as the specification.

What does a UX designer interview actually test?

A UX interview tests more than the polish of the final interface. Interviewers need to understand how you framed the problem, learned about users, handled constraints, generated and tested options, worked with other disciplines, and changed the design when evidence challenged an assumption.

Employer guidance makes those different signals explicit. As of July 29, 2026, Amazon's UX interview guide describes a loop with three parts: a portfolio review, an interactive functional exercise such as design whiteboarding or research planning, and one-to-one behavioral interviews. Amazon also says the interview group may include UX professionals, product managers, software development managers, and business partners. A portfolio that only makes sense to another visual designer may therefore miss part of its audience.

The Home Office designer role standard provides a useful, employer-neutral view of the work itself. It describes designers working with researchers, developers, product owners, and analysts to define problems, learn about users, map flows, prototype, test, and iterate. That is a better basis for a practice scorecard than a list of generic interview questions.

Turn the role and interview format into five evidence lanes:

Use the employer's job description to adjust the weight of those lanes. A research-heavy role may need deeper method choices and synthesis. A systems role may emphasize reusable patterns and cross-product consistency. An early-stage product role may put more weight on ambiguity, scope, and collaboration with engineering.

Build a case-study evidence trace before asking AI for feedback

AI cannot audit a case study if the source material is vague. For each portfolio project, create a compact evidence trace from artifacts you are allowed to use:

1. Context: product, users, business situation, project stage, and constraints.
2. Your responsibility: the decision or deliverable you owned, plus the boundaries of that ownership.
3. Evidence: research findings, analytics, support themes, usability observations, or documented stakeholder requirements.
4. Decision: the options considered, the tradeoff selected, and who participated.
5. Iteration: what changed after critique, testing, technical review, or new information.
6. Outcome: the result you can substantiate, the measurement window, and important limitations.
7. Reflection: what you would keep, change, or investigate next.

Keep the trace behind the presentation rather than turning every field into a slide. It is a fact base for follow-up questions and an input boundary for the AI.

Google's UX design portfolio tips recommend showing the end-to-end process, clearly identifying the user problem and final solution, and stating your role, impact, and cross-functional collaboration. Google also recommends enough context for a person to understand the work when you are not present. That last test is useful: first ask the AI to summarize the case study using only the deck, then compare its summary with your evidence trace. A wrong summary may reveal a presentation gap, but it does not prove the model's rewrite is accurate.

Protect confidential work while assembling the packet. Replace customer or participant identifiers, remove internal strategy and unreleased details, and follow any nondisclosure agreement. If the project is heavily restricted, explain the constraint and use approved abstractions rather than quietly feeding private artifacts to a model. The AI interview assistant privacy checklist can help you decide what belongs in a cloud-assisted practice workflow.

Rehearse the portfolio as a decision narrative

A portfolio presentation should show why the work moved from one state to the next. It should not be a chronological inventory of every workshop, wireframe, and design-system component.

The Figma recruiter portfolio guide says design leaders may have only minutes or seconds to assess a portfolio. It recommends making the role and medium easy to parse, focusing each project on the relevant work, and explaining the solution, iterations, personal role, and lessons. Use that advice to run two different practices.

Run a fast comprehension test

Give the AI only the material an interviewer will see and ask:

In two minutes, identify the user problem, my role, the most consequential design decision, the evidence behind it, and the outcome. For every point, cite the slide or sentence that supports it. Mark anything you cannot find as missing.

Do not treat the response as a hiring decision. Use it to locate ambiguity. If the AI attributes a team decision entirely to you, the deck may need a clearer ownership statement. If it cannot find the user need until the middle, move the problem frame earlier. If it calls a visual change the main decision when the real decision concerned workflow or scope, the narrative hierarchy may be wrong.

Run an interruption test

Real portfolio reviews are conversations. Ask the AI to stop you at decision points with one follow-up at a time:

• Why did this evidence justify that decision?
• Which alternative did you reject, and what did it do better?
• What was your contribution versus the team's?
• What would have changed your mind?
• How did you know the result was better for users?

Answer without reading a script. After the rehearsal, ask the AI to list only claims that lacked support in your trace. This is more useful than asking it to make the story “sound senior,” which often rewards confident language instead of defensible judgment.

Time the presentation with room for questions and transitions. Do not assume one employer's duration applies elsewhere; Amazon currently describes 60-minute sessions, while other loops may divide the time differently. Follow the format you were given.

Practice a functional design exercise without outsourcing the design

A whiteboard, critique, or research-planning exercise evaluates how you work with an unfamiliar problem. If AI supplies the solution during practice, you train recognition rather than design reasoning.

Separate the exercise into an interviewer phase and a critic phase.

Phase one: restrained interviewer

Give the AI a problem brief and prohibit it from proposing features. Ask it to reveal only information that a real interviewer has specified. Then work through the problem aloud:

1. Restate the decision and ask clarifying questions.
2. Identify users, context, risks, and constraints.
3. State which assumptions matter most.
4. Choose a research or validation step proportional to the uncertainty.
5. Generate at least two materially different approaches.
6. Select one using explicit tradeoffs.
7. Sketch the critical flow and define how you would test it.
8. Summarize open questions and the next iteration.

When the brief lacks data, label an assumption instead of asking the AI to fabricate a research finding. When the AI plays a participant or stakeholder, label its answers as simulation inputs, not user evidence.

The Home Office standard describes prototyping as a way to test ideas and make thinking visible, with fidelity matched to the stage and purpose. Your practice should do the same. A rough flow that exposes a risky interaction can be more useful than a polished screen that hides the unanswered question.

Phase two: evidence-bound critic

Finish the exercise before requesting evaluation. Give the AI a fixed rubric and the transcript, then require each finding to include:

• the exact moment or artifact it refers to;
• the consequence for the user, business, or delivery team;
• one alternative action;
• whether the issue is observed, inferred, or unknown.

For a reusable interview protocol, adapt the AI mock-interview scoring workflow. Keep the rubric stable across practice rounds so a more enthusiastic model response does not masquerade as improvement.

Prepare behavioral stories around design conflict and learning

Design interviews often probe the work around the artifact: disagreement, influence, prioritization, failed research, accessibility, engineering constraints, and decisions that did not produce the expected outcome.

Build a small story bank from real projects. Each record should capture:

• the design tension or decision;
• the affected users and stakeholders;
• what evidence existed at the time;
• what you personally did;
• what teammates or leaders did;
• the outcome you can support;
• what you learned or changed afterward.

The ownership boundary matters. “We” can hide your contribution; “I” can erase the team. Practice moving deliberately between the two. For example: “The research team identified the pattern. I translated it into two flow options. Engineering surfaced the latency constraint. We selected the lower-risk path and tested it.”

Ask the AI to probe causal gaps rather than polish the wording. If a story jumps from a workshop to a successful launch, it should ask what changed, who approved it, and how the result was measured. The behavioral-interview evidence-bank guide provides a fuller method for truthful follow-up preparation.

Use AI feedback without accepting invented design evidence

Generative AI can present a plausible critique, metric, research theme, or stakeholder reaction that never occurred. NIST calls this risk confabulation: confidently generated false or erroneous content. The NIST Generative AI Profile recommends fact-checking generated information and reviewing sources and citations because model output can be unreliable.

Apply a strict rule: the AI may classify, question, compare, or critique evidence, but it may not create project facts.

Reject or relabel output that:

• invents interview quotes, usability findings, adoption metrics, or accessibility results;
• upgrades a shared team outcome into your individual achievement;
• assumes that a final design shipped when it remained a prototype;
• turns an internal preference into a user need;
• creates certainty where the original work had mixed or incomplete evidence;
• recommends exposing confidential artifacts to make the story more convincing.

A simple review label keeps practice honest:

• Verified: supported by an artifact or fact you can defend.
• Inference: a reasonable interpretation that must be stated as such.
• Unknown: missing evidence or something you cannot disclose.
• Fabricated: introduced without support and removed.

Do not paste the model's improved version into your deck until every factual change passes that review.

Run one controlled UX interview practice loop

Use one portfolio project and one functional prompt for a baseline session:

1. Present the case study without AI rescue.
2. Answer five interruption questions from the evidence trace.
3. Complete a functional exercise aloud.
4. Answer two behavioral questions about conflict or iteration.
5. Ask for transcript-cited feedback under the fixed rubric.
6. Choose one behavior to improve.
7. Repeat the same session and compare that behavior only.

Useful measures are observable: time until the user problem is clear, number of decisions tied to evidence, number of ownership ambiguities, and whether the conclusion includes limitations. An AI-generated score is not an objective hiring probability.

Stop adding polish when the evidence is already clear. UX preparation can become counterproductive if every answer sounds scripted, every case study follows the same template, or the model removes the uncertainty that made the decision difficult.

Make your design judgment easier to inspect

Strong UX interview preparation connects the user problem, evidence, decision, iteration, collaboration, and outcome. AI can pressure-test that chain, simulate interruptions, and point to gaps in a transcript. It cannot create legitimate user research, ownership, or impact after the fact.

Once the evidence trace and practice loop are stable, compare the workflow requirements in the desktop AI interview assistant evaluation guide. Use any assistant only where the employer's rules, confidentiality obligations, and participant permissions allow it.