UI/UX Designer Interview Questions and Answers

Questions and model answers

9 questions you are likely to hear.

1. 1

   Walk me through your design process.

   Why they ask: Interviewers want a flexible, evidence-based process, not a rigid textbook sequence.

   Sample answer: I start by understanding the problem with the PM and stakeholders: the business goal, the users and constraints. Then I look at existing data, analytics and support tickets, and run quick user interviews if needed. I define the problem clearly and map the user flow. I sketch several directions, pick one or two with the team and build prototypes in Figma. I test with five or so users, iterate and then work closely with developers during build. The depth of each step depends on risk: a small UI fix might skip research, while a new onboarding flow gets full discovery.

2. 2

   Tell me about a design decision you made based on user research.

   Why they ask: This tests whether research actually shapes your work.

   Sample answer: At a fintech startup, we planned to add more features to the dashboard because users said they wanted more insights. In usability sessions with eight users, I noticed most of them struggled to find their account balance among the existing widgets. I proposed simplifying the dashboard instead: a clear balance and recent transactions at the top, with insights moved to a separate tab. We A/B tested it, and the simplified version had better task success in tests and fewer support questions about balances after launch. The research changed our roadmap direction.

3. 3

   How do you handle feedback from a stakeholder you disagree with?

   Why they ask: Collaboration and diplomacy are key to a designer's effectiveness.

   Sample answer: I first make sure I understand the concern behind the feedback, because a request like make the button bigger often hides a real goal, such as more sign-ups. Then I bring evidence: research findings, analytics or design principles, and propose a way to test if we still disagree. A sales director once wanted a long sign-up form to capture more lead data. I suggested a test with a short form and progressive profiling after sign-up. The short form converted much better, and we still collected most of the data later. Framing it as a test kept the relationship positive.

4. 4

   How do you design for accessibility?

   Why they ask: Accessibility is now a baseline expectation and often a legal requirement.

   Sample answer: I build accessibility in from the start rather than auditing at the end. I check colour contrast against WCAG AA, never rely on colour alone to convey meaning, design visible focus states, keep touch targets at least 44 pixels and write clear labels and error messages. I annotate designs for developers with heading order, alt text and focus order. I test with screen readers like VoiceOver and with keyboard only during design QA. On a government services project, these practices helped us pass an accessibility audit on the first round.

5. 5

   How have you worked with or built a design system?

   Why they ask: Design systems are central to scaling design work.

   Sample answer: At a SaaS company with three product teams, designs had drifted into dozens of button and input styles. I audited the product, consolidated components and built a Figma library with variants, auto layout and variables for colour, spacing and typography tokens. I worked with a frontend lead to mirror the tokens in code and documented usage guidelines and do's and don'ts. We set up a weekly review for new component requests. Within a few months, new feature designs reused most components, design-to-development handoff got faster and visual inconsistencies dropped sharply.

6. 6

   How do you measure the success of a design?

   Why they ask: Interviewers want designers who think about outcomes, not just outputs.

   Sample answer: I agree success metrics with the PM before designing, tied to the goal. Behavioural metrics include task completion, conversion, time on task, error rates and retention. Attitudinal metrics include satisfaction scores like SUS or CSAT and qualitative feedback. I compare before and after where possible, or run A/B tests. For a checkout redesign at an ecommerce company, we tracked completion rate, payment errors and time to complete. Completion improved noticeably, and we also saw fewer support tickets about failed payments, which we had not expected.

7. 7

   Design a smart home app for elderly users. How would you approach it?

   Why they ask: Design exercises test problem framing, empathy and trade-offs.

   Sample answer: I would clarify goals first: is it for safety, comfort or independence, and are family members also users? I would focus on elderly users living alone and their key needs, such as controlling lights and temperature and getting help quickly. Design choices would include large touch targets, high contrast, simple language, few options per screen and voice control as an alternative. A prominent help button would alert family members. I would include a family setup mode so relatives can configure devices remotely. I would test with real elderly users early, because assumptions about this group are often wrong.

8. 8

   How do you work with developers during implementation?

   Why they ask: Strong collaboration with engineering ensures designs ship well.

   Sample answer: I involve developers early, sharing rough concepts so they can flag technical constraints before I polish designs. I use consistent components and tokens, annotate interactions, states and edge cases, and walk the team through designs in a handoff session. During build, I am available for questions and do design QA on staging, logging issues by priority. I am flexible when something is expensive to build and look for a simpler solution with similar value. Developers on my last team said the edge-case annotations, such as empty, error and loading states, saved them the most time.

9. 9

   Tell me about a design that failed and what you learned.

   Why they ask: Interviewers value honesty and learning over perfect stories.

   Sample answer: I redesigned the navigation of a B2B product to use a new icon-only sidebar, which looked clean in reviews. After launch, support tickets increased because users could not find features they used rarely, and analytics showed lower use of some modules. I had tested only with internal users who knew the product well. We quickly added text labels and a search shortcut, and usage recovered. Since then I always test with real customers, including less frequent users, before shipping navigation changes, even if it is a short remote test.

Keep going.

• Frontend Developer Interview Questions and Answers
• Product Manager Interview Questions and Answers
• How to Answer "Tell Me About Yourself" in an Interview
• How to Answer "What Are Your Strengths and Weaknesses?"
• Behavioral Coach
• Resume AI