AI HR
Prova

Interview questions

UI/UX designer interview questions

Design interviews are mostly about your thinking, told through your portfolio. Interviewers want to hear the problem, the constraints, the decisions you rejected and what happened after launch, not a tour of polished screens.

Rehearse this interview by voice2 minutes without an account, 3 more after sign-up. No card.

Questions by stage and what a strong answer includes

  1. 01

    Tell me about your current role and the products you design for.

    Strong answer: Product type, platform (web, iOS, Android), team size and your scope: end-to-end flows, a design system, research. Name the tools you work in, typically Figma.

  2. 02

    Which project in your portfolio best represents you, and why?

    Strong answer: One case where you owned the problem, not only the visuals, with a reason that connects to the role you are applying for.

  1. 03

    Tell me about a time a PM or engineer pushed back on your design.

    Strong answer: What the pushback was, how you checked whether they were right (data, constraints, a quick test) and the version that shipped. Show you defend users without being precious.

  2. 04

    Describe a design decision you got wrong.

    Strong answer: What you assumed, how you found out (usability test, analytics, support tickets) and how you corrected it. Specific and unembarrassed.

  1. 05

    Walk me through a case study from problem to outcome.

    Strong answer: Problem and business goal, users and research, two or three directions you explored, why you chose one, constraints you hit and a measured result. Keep it to 10-15 minutes and invite questions.

  2. 06

    How do you do user research when there is no budget or researcher?

    Strong answer: Guerrilla tests with five users, support tickets, analytics, sales call recordings, quick surveys. Show you know the limits of each method.

  3. 07

    How do you hand off designs to engineering?

    Strong answer: Components from the design system, documented states and edge cases (empty, error, loading), annotations, and staying available during the build. A pairing session beats a big spec dump.

  4. 08

    How do you make sure your designs are accessible?

    Strong answer: Contrast ratios, focus states, touch targets, screen reader labels, WCAG 2.1 AA as a baseline, and testing with real assistive tech when you can.

  1. 09

    Design challenge: redesign the checkout for a grocery delivery app.

    Strong answer: Ask about goals and constraints, define the user and the main friction, sketch the flow before screens, explain trade-offs and say how you would test it. Thinking aloud matters more than pixels.

  2. 10

    How do you measure whether a design worked?

    Strong answer: Pick metrics before launch: task success, conversion, time on task, support contacts, plus qualitative feedback. Tie at least one example from your portfolio to a real number.

  1. 11

    What level and scope are you looking for?

    Strong answer: Be clear about the level you are targeting, the kind of problems you want to own and your salary range. Ask how designers are leveled and reviewed at the company.

One answer, before and after

Tell me about a time a PM or engineer pushed back on your design.

Weak answer

Engineers often say designs are too hard to build. I explain why the design is important for the user experience and usually we find a way. I'm good at collaboration.

Strong answer in STAR

Situation
I designed a new onboarding flow for a budgeting app with an animated, swipeable card for each step. The lead engineer said it would take three sprints and delay the release.
Task
I needed to keep the part of the design that drove completion without blocking a release planned in five weeks.
Action
I went back to our prototype tests: completion improved because each step asked one question, not because of the animation. I proposed a static one-question-per-screen version first, with the swipe animation as a follow-up ticket, and paired with the engineer for an afternoon to adjust spacing in the build.
Result
The simpler flow shipped in one sprint. Onboarding completion went from 54% to 71%, and the team decided the animation was not worth the extra two sprints.

Why it works

The weak answer frames engineers as an obstacle. The strong one shows the designer knew which part of the design created the value and protected it, while giving up what did not matter. Numbers are illustrative: use your own.

How a practice session works

  1. 01

    Pick a stage, paste the job posting

    Recruiter screen, HR interview, hiring manager, final round or offer talk. Add the posting and your resume so the questions are about your role, not generic.

  2. 02

    Talk it through by voice

    The interviewer speaks the language you chose, interrupts, follows up and digs into details like on a real call. If the connection drops, you pick up where you stopped.

  3. 03

    Get the review and drills

    A score, 7 skills, what you said next to a stronger way to say it, plus pace, filler words and talk share. Weak spots turn into short drills.

Rehearse this interview by voice

Related roles