Interview scorecard
UX Designer
Score each skill from 1 to 5. A 1 is below the bar for this role, a 3 meets it, and a 5 is above it. The examples show what each sounds like. Use 2 and 4 for answers that fall in between.
Interaction design
Designs how users move through a task, including each step, feedback and error state.
Questions
- Tell me about a flow you designed. How did users move from start to finish?
- Describe a time users got stuck at a step. How did you change it?
- How do you decide what happens when something goes wrong for the user?
1: Below the bar
Describes screens, not the steps between them. Ignores errors and feedback, and can't say why choices were made.
3: Meets the bar
Walks through a clear flow and explains key choices. Covers common errors but misses edge cases or evidence it worked.
5: Above the bar
Explains each step's purpose, plans for errors and edge cases, and shows how real user behavior changed the design.
User research
Gathers evidence from real users and turns it into clear findings that shape design decisions.
Questions
- Tell me about a time user research changed your design direction. What did you learn?
- How do you decide which research method to use and how many users to talk to?
- Tell me about a time findings surprised you or the team. What did you do next?
1: Below the bar
Relies on opinions or assumptions. Describes research vaguely, with no clear method, and can't point to a decision it changed.
3: Meets the bar
Picks a sensible method and talks to real users. Shares findings with the team, though the link to design changes is loose.
5: Above the bar
Matches method to the question, spots bias in their own approach, and shows a clear line from findings to a design change.
Information architecture
Organizes content and navigation so users can find what they need without thinking.
Questions
- Tell me about a time you organized a large amount of content. How did you start?
- How have you checked whether people could find things in a structure you built?
- Tell me about a time you restructured navigation or labels. What prompted the change?
1: Below the bar
Groups content by how the company is organized. Cannot say how they know users would find things.
3: Meets the bar
Groups content by user tasks and uses clear labels. Tests the structure with some users but changes little afterward.
5: Above the bar
Builds structure from how users think, tests it early, and changes labels or groups based on what people got wrong.
Prototyping
Builds quick, testable prototypes and uses what they learn to improve the design.
Questions
- Tell me about a prototype you built. What question was it meant to answer?
- How do you decide how detailed a prototype needs to be?
- Tell me about a time a prototype changed your design. What happened?
1: Below the bar
Treats a prototype as a polished mockup to show off. Can't say what it was meant to test or what changed.
3: Meets the bar
Picks a sensible fidelity and tests with a few people. Makes some changes but the learning goal was loose.
5: Above the bar
Starts with a clear question, picks the cheapest prototype that answers it, and explains the design change the results drove.
Product thinking
Connects design choices to user needs, business goals and constraints, and decides what to build first.
Questions
- Tell me about a time you decided what not to design. How did you decide?
- Describe a design you shipped. How did you know it worked for users and the business?
- Tell me about a time a business goal and a user need pulled in different directions.
1: Below the bar
Talks only about screens and visuals. Can't say what goal the design served or how success was checked.
3: Meets the bar
Links designs to a user need and a business goal. Can explain a priority call but gives limited evidence of results.
5: Above the bar
Frames the problem before the solution, weighs user, business and cost trade-offs, and backs decisions with results they tracked.
Overall recommendation
Decide on your own, before you compare notes with the rest of the panel.