Templates

Interview scorecard for UX designers, with anchors for each competency

On this page
  1. The six competencies this scorecard covers
  2. The scorecard at a glance: weights and anchors
  3. The scorecard template
  4. Anchors for each competency
  5. Two work samples to use in the interview
  6. A filled example
  7. Adjusting for role and level
  8. Mistakes specific to scoring UX designers
  9. Where this fits in the hiring process
  10. Questions people ask

A UX designer interview scorecard should score six things: how the candidate frames a problem and uses research, interaction design craft, the reasoning behind their trade-offs, accessibility, collaboration with product and engineering, and how they give and take critique. Below is a copy-ready scorecard with example weights, what a 1, 3 and 5 look like on a 1–5 scale, two work samples and a filled example. Score the decisions a designer made and can explain, not the visual polish of the portfolio.

The five points follow the 1–5 interview rating scale: 1 is no evidence or evidence of the opposite, 3 is a clear example that meets the bar for the level, 5 is rare. The layout comes from the interview scorecard template. The full loop, with a portfolio review and a live design exercise, is in the interview guide for designers; this page adds the anchors each row is scored against and a different exercise, a critique of an existing flow. The scorecard builder prints a 1–4 version if your team uses four points.

The six competencies this scorecard covers

  • Problem framing and use of research. Do they find out who the users are, how often the problem happens and what goes wrong today before drawing anything?
  • Interaction design craft. Are flows short for the common case, with clear states for errors, empty screens, loading and edge cases?
  • Design reasoning and trade-offs. Can they say why they chose one approach over another, and what they gave up?
  • Accessibility. Do they design for contrast, labels, keyboard focus, color-independent states and target size from the start, not as a fix at the end?
  • Collaboration with product and engineering. Do they work within constraints, hand off designs engineers can build, and adjust when something cannot be built?
  • Giving and receiving critique. Is their feedback specific and kind, and do they change their own work when the critique is right?

The scorecard at a glance: weights and anchors

Weights are an example for a mid-level product designer. Agree yours with the design manager at intake and lock them before the first interview.

CompetencyWeight1 looks like3 looks like5 looks like
Problem framing and use of research20%Starts drawing at once; the portfolio shows final screens with no problem statement or user evidence.States the problem and who has it, names the research or data used (interviews, analytics, support tickets) and one thing it changed in the design.Reframed the problem after research showed the brief was wrong, and can show the decision that followed.
Interaction design craft20%Designs only the happy path; no error, empty or loading states.Common case is short, error and edge states are designed, defaults are sensible.All of a 3, plus a flow measurably simplified after launch (fewer steps, fewer support tickets) with how they knew.
Design reasoning and trade-offs15%"It looked cleaner" or "the stakeholder wanted it" is the only reason given.Explains at least one real trade-off (speed versus flexibility, consistency versus a special case) and why they chose as they did.Revises the design when a constraint changes in the interview and explains exactly what had to change and why.
Accessibility15%Cannot name an accessibility consideration, or calls it engineering's job.Applies the basics by habit (contrast, text labels, focus order, states not shown by color alone) and knows WCAG is the standard.Has shipped work tested with assistive technology or disabled users, and cites specific WCAG 2.2 criteria such as target size.
Collaboration with product and engineering15%Describes engineers as the obstacle, or handed off files with no specs or states.Involves engineers early, hands off states and behavior, and adjusted a design when something could not be built.Changed how the team works together (a shared component, a review ritual) and can describe the result.
Giving and receiving critique15%Feedback in the exercise is vague taste ("I don't love it"), or becomes defensive when challenged.Gives specific feedback tied to the user's goal, and gives an example of changing their own work after critique.Separates blocking issues from preferences unprompted, and describes running critiques that improved others' work.

Visual design is not a row here because it varies so much by seat; add it for UI-heavy roles (see the adjustments below). How to set weights is in weighted interview scorecard.

The scorecard template

Candidate: [name]                     Role: [product / UX / UI designer], [level]
Interviewer: [name]                   Stage: [screen / portfolio review / critique exercise / cross-functional]

Pass/fail (checked before scoring)
  Portfolio walkthrough confirms the candidate's own role in the work:  [ ] yes  [ ] unclear
  Work location and hours as stated in the job description:           [ ] meets [ ] does not

Problem framing and use of research (20%)        Score 1-5: [ ]
Evidence: [problem stated, research used, what it changed]

Interaction design craft (20%)                   Score 1-5: [ ]
Evidence: [states designed, steps for the common case]

Design reasoning and trade-offs (15%)            Score 1-5: [ ]
Evidence: [trade-off named, response to a changed constraint]

Accessibility (15%)                              Score 1-5: [ ]
Evidence: [issues found in the critique exercise: _ of 4; practice described]

Collaboration with product and engineering (15%) Score 1-5: [ ]
Evidence: [handoff, a design changed for a constraint]

Giving and receiving critique (15%)              Score 1-5: [ ]
Evidence: [quality of feedback in the exercise; example of changing own work]

Weighted score: sum of (weight x score) / sum of weights scored = [   ]
Recommendation: [Strong yes / Yes / No / Strong no]

Anchors for each competency

The table gives the 1, 3 and 5. Here is the question that tests each row and what a 2 and a 4 sound like.

Problem framing and use of research

Ask: "Pick one project. Before you designed anything, what did you know about the users and the problem, and how did you find out?"

  • 2: Research was done by someone else and the candidate cannot say what it changed.
  • 4: Ran or shaped the research, and can point to a design decision it reversed.

Interaction design craft

Ask: "Show me the error and empty states for that flow. Which edge case was hardest?"

  • 2: Some states exist but were added late, after engineering asked.
  • 4: States were part of the first design, and the candidate can describe an edge case that changed the main flow.

Design reasoning and trade-offs

Ask: "What was the other option you seriously considered, and why did you not ship it?"

  • 2: Names an alternative but the reason for rejecting it is preference.
  • 4: Clear trade-off tied to the user or the business, and what they would watch to know if they were wrong.

Accessibility

Ask: "How did accessibility show up in that project, specifically?" Then the critique exercise below.

  • 2: Mentions contrast only, or says the design system "handles it".
  • 4: Applies the basics by habit and finds most of the planted issues in the exercise, with the reason each matters to a user.

Collaboration with product and engineering

Ask: "Tell me about a design that engineering said could not be built as drawn. What happened?" More in interview questions for cross-functional collaboration.

  • 2: Accepted the cut without exploring alternatives, or escalated instead of talking to the engineer.
  • 4: Found a version that kept the user goal within the constraint, worked out with the engineer.

Giving and receiving critique

Ask: "Tell me about critique that changed your design. What did you disagree with at first?" More in interview questions for receiving feedback.

  • 2: Accepts critique but cannot name a change it caused, or gives feedback that is accurate but blunt to the point of unhelpful.
  • 4: Specific, kind feedback in the exercise, and a real example of changing their mind.

Two work samples to use in the interview

Both are invented and the same for every candidate. Neither uses a problem from your roadmap. Tell candidates in advance and how to ask for an adjustment; see ADA accommodations in interviews.

Flow critique (20 minutes). Show three screens of an invented appointment-booking flow on a phone. Plant four issues: gray placeholder text used as the only field label, with low contrast; an icon-only button with no text label; a form error shown only by turning the field red; and small, tightly packed time-slot buttons. Brief: "You are in a design review with the designer who made this. Give them your critique: what would you change first, and why?"

What to listen for: how many issues they find and whether they explain the effect on a real user; feedback ordered by impact and phrased so a colleague could act on it; and whether they ask about the users before redesigning. The W3C's WCAG 2.2 (a W3C Recommendation, current version dated 12 December 2024, checked November 2026) covers each planted issue: 1.4.3 Contrast (Minimum) asks for a contrast ratio of at least 4.5:1 for normal text, 1.4.1 Use of Color says color is not used as the only visual means of conveying information, and 2.5.8 Target Size (Minimum) asks for pointer targets of at least 24 by 24 CSS pixels, with exceptions. A candidate does not need the numbers to score a 3; a 5 usually knows them. This scores accessibility, critique and craft.

Research plan scenario (10 minutes, verbal). "Sign-ups fell after last month's redesign of the sign-up flow. You have two weeks and no research budget. What do you do?"

What to listen for: finding where the drop happens first (which step, which devices, which traffic source) before guessing why; quick ways to watch real people use it (sessions with existing customers, support tickets, recordings if the product already collects them with consent); a hypothesis that could be tested; and a view on whether to roll back while they learn. This scores problem framing and reasoning.

Check that portfolio work is the candidate's own with the steps in how to spot a fake design portfolio; that check is pass/fail, not a scored row.

A filled example

A made-up candidate for a mid-level product designer on a business scheduling product, scored after the portfolio review, the flow critique and the cross-functional interview:

Problem framing and use of research — 4. Walked through a shift-swap feature where support tickets showed managers, not staff, were the users stuck; ran five calls with managers and moved approval into the manager's daily summary.

Interaction design craft — 3. Error and empty states were designed; the conflict case (two swaps for one shift) was handled with a clear message.

Design reasoning and trade-offs — 3. Chose a summary email over a new screen to reach managers where they already were; named lost discoverability as the cost.

Accessibility — 2. Found the contrast and the icon button in the critique but not the color-only error or the target size; said the design system handles accessibility.

Collaboration with product and engineering — 4. Reworked an animation that would have needed a new library, with the engineer, keeping the confirmation the users needed.

Giving and receiving critique — 3. Ordered the critique by impact and phrased it as suggestions with reasons.

Weighted score: 3.20 ((4×20 + 3×20 + 3×15 + 2×15 + 4×15 + 3×15) ÷ 100). Recommendation: Yes, if accessibility can be coached: ask the design manager whether the team can support that in the first quarter before deciding.

Adjusting for role and level

Role or levelAdjustment
UI or visual designerAdd a visual craft row (type, spacing, hierarchy, consistency with the design system) at 15–20% and lower framing.
UX researcherReplace interaction craft with research method choice and synthesis; see the UX researcher job description template.
Content designerReplace interaction craft with a writing row scored on microcopy in the critique exercise.
Junior or career changerAccept school, bootcamp or volunteer projects; score reasoning and critique at full weight and accept smaller scope for a 3.
Senior or lead designerAdd a row for influence on product direction; a 3 on collaboration needs a change to how the team works, not one project.

Mistakes specific to scoring UX designers

MistakeWhy it failsFix
Scoring the portfolio's polishPolish reflects tools, time and the last employer's brand as much as the designer's decisionsScore what they decided and why, row by row
Scoring taste that matches the interviewer'sRewards similarity, not skillAsk for the reason behind a choice and score the reason
"Digital native" or "fresh eyes" as a plusBoth are proxies for age, which the EEOC lists among protected bases (40 or older)Score current practice and learning shown in the work
Penalizing NDA-limited portfoliosGood designers in regulated or enterprise work often cannot show screensAccept a redacted walkthrough and score the decisions described
Using a real roadmap problem as the exerciseReads as free work and favors candidates who know your productUse an invented problem in a nearby domain

Where this fits in the hiring process

The UX designer phone screen places the candidate (product, UX research, UI or content design) and runs a first portfolio walkthrough. The portfolio review, the critique exercise and the cross-functional interview fill in the six rows. Keep the rows consistent with the must-haves in the UX designer job description template, and carry the weakest scored row into the first month of the 30-60-90 day plan for UX designers.

If you interview with Interview Signal, the desktop app we make, these rows can become the scorecard areas in its kit, each with a weight of 1, 2 or 3 and rubric lines on a 1–10 scale; each score carries the candidate's own quotes, checked word for word against the transcript (see how the scorecard with verified quotes works). It reads only the words spoken, so a portfolio shown on screen is scored from what the candidate says about it. Whatever you use, have each interviewer score before reading the others, then compare in a calibration session.

Questions people ask

What should a UX designer interview scorecard measure?

Six things for most product design roles: how the candidate frames a problem and uses research, interaction design craft, the reasoning behind their trade-offs, accessibility, collaboration with product managers and engineers, and how they give and receive critique. Weight them for the seat, and write what a 1, 3 and 5 sound like for each before the first portfolio review.

How do you score a UX portfolio fairly?

Score the decisions, not the polish. Ask the candidate to walk through one project and score what they personally decided, why, what evidence they used and what changed after launch. Visual finish belongs in its own lower-weighted row for UI-heavy roles, and candidates whose best work is under NDA can walk through a redacted version or a smaller public project.

Should accessibility be a separate row on a UX designer scorecard?

Yes for most product roles. Folded into general craft, it tends to be skipped. A separate row makes interviewers ask about contrast, labels, focus, states that do not rely on color alone and touch target size, and lets a candidate who applies the W3C's WCAG 2.2 in real work score higher than one who only names it.

Is an unpaid design exercise fair for UX designer candidates?

A short exercise on an invented problem, run live or capped at a few hours, is common and fair if every candidate gets the same one. Avoid problems from your real roadmap, which can read as free work, and tell candidates in advance how it will be scored and how to ask for an adjustment.