How to assess · For hiring teams

How to Assess UX Design Skills When Hiring

The test formats that actually work for UX Design, what a strong answer looks like, sample questions and a scoring rubric you can use as-is.

The short answer

Assess UX Design with a task, not a conversation: timed design exercise with a constraint, critique exercise, ai-scored assessment (e.g. cohesyve) or portfolio interrogation. Score it against written criteria you fix before you see any submissions, and weight the criteria that the role actually depends on.

Frames the problem in terms of the user's task and context before designing anything
Structures flows so the next step is obvious and the number of steps is minimal
Designs every state — empty, loading, error, success — not only the happy path
Makes trade-offs explicit: what was sacrificed for what, and why

Build a UX Design assessment →Read the full article ↓

Paste a job description; Cohesyve generates a role-specific assessment and rubric. Ten candidates free, no card.

UX design is easy to assess badly, because portfolios show polished outcomes and hide the reasoning that produced them. The skill you are hiring for is the reasoning: understanding the user's task, structuring a flow so it is obvious, making trade-offs between competing needs, and knowing what to test. This page covers how to assess UX design for product designer, UX designer and design lead roles: problem framing, flow and structure, interaction judgement, and the ability to explain and defend decisions.

Why UX Design is worth testing

Weak UX produces products that look fine in a screenshot and frustrate people in use — flows with extra steps, states nobody designed, and decisions made for the stakeholder rather than the user. A short design exercise with a real constraint shows whether a candidate reasons from the user's task and can explain their choices, and that predicts whether the product gets easier or busier.

What strong UX Design looks like

Frames the problem in terms of the user's task and context before designing anything
Structures flows so the next step is obvious and the number of steps is minimal
Designs every state — empty, loading, error, success — not only the happy path
Makes trade-offs explicit: what was sacrificed for what, and why
Uses established patterns where they fit and departs from them with reasons
Knows what to test and how, and changes the design based on findings
Explains decisions to non-designers and takes critique without defensiveness

Ways to assess UX Design

Timed design exercise with a constraint

Give a small, specific problem — a flow for cancelling a subscription that retains fairly, an onboarding step for a described product — with a real constraint (mobile only, no new backend). Ask for low-fidelity screens and a written rationale. Ninety minutes.

Pros

Tests reasoning and structure directly; the rationale is comparable.

Cons

Time pressure; keep fidelity low so speed of tooling does not decide it.

Best for Any UX role.

Critique exercise

Show a flawed flow — extra steps, missing states, unclear next action — and ask what is wrong and what they would change first.

Pros

Tests judgement fast; no tooling.

Cons

Passive.

Best for Screening.

AI-scored assessment (e.g. Cohesyve)

Generate a UX design task from the job description — a flow design with rationale, a critique, a trade-off scenario — with a rubric. Each candidate receives a different variant; the work and the reasoning behind it are scored together.

Pros

Asynchronous and consistent across a large pool; a different brief per candidate removes recycled portfolio work; scores the reasoning, which is where design and product judgement show.

Cons

Cannot observe live collaboration or critique; keep a working session for shortlisted finalists.

Best for Screening an applicant pool fairly before interview time is spent.

Portfolio interrogation

Pick one piece and ask what the problem was, what they considered and rejected, and what they would change now.

Pros

Reveals ownership and reasoning behind polished work.

Cons

Talk-based.

Best for Mid and senior roles.

Cohesyve

Run a UX Design assessment on your next opening

Cohesyve generates a unique UX Design task per candidate from your job description, with the scoring rubric attached. Questions are different for every applicant, so they cannot be shared or looked up.

Try it free →Book a 30-min demo

What to test

Problem framing

Whether design starts from the user.

State the user's task and context before sketchingIdentify what the brief assumesSay what success looks like for the user

Flow and structure

Whether the path is obvious and short.

Reduce a flow by two stepsDesign the next-action hierarchy on a screenHandle a decision point without a dead end

States and edge cases

Whether the whole experience is designed.

Design empty, error and loading statesHandle a user who returns mid-taskDesign for a slow connection

Reasoning and communication

Whether decisions are explained.

Write a rationale a PM could act onRespond to critique that is partly rightExplain a trade-off to an engineer

Sample UX Design questions

Before you design a screen, what do you need to know?

Entry

Look for Who the user is, what they are trying to do, where they came from, what happens next, constraints.

What states does a list screen need?

Entry

Look for Empty, loading, error, partial, success; each designed, not defaulted.

This checkout has seven steps. Which would you remove and how?

Mid

Look for Identifies steps that collect nothing essential, combines where sensible, keeps what protects the user.

A stakeholder wants a feature that will clutter the main screen. What do you do?

Mid

Look for Understand the need, propose placement that serves it without cost to the main task, show the trade-off, test if contested.

Tell me about a design you shipped that was wrong, and how you found out.

Senior

Look for Honest account, evidence from testing or data, what changed.

Red flags

Designs the happy path only
Cannot explain why a screen is structured as it is
Portfolio work with no rationale
Defensive under critique
Adds steps to solve problems

Scoring rubric

Criterion	Weight	What strong looks like
Problem framing	25%	Starts from the user's task.
Flow and structure	30%	Obvious, minimal, complete.
States and edge cases	20%	Every state designed.
Reasoning	25%	Decisions explained; trade-offs explicit.

Mistakes hiring teams make

Judging on visual polish
Not giving a real constraint
Scoring the screens without the rationale
Skipping states
Accepting portfolio work without interrogation

Roles that need UX Design

UX DesignerProduct DesignerInteraction DesignerDesign LeadUX ResearcherProduct Manager

Common questions

Should I ask for high-fidelity work?

No. Low fidelity keeps the exercise about reasoning and structure, and stops tool speed from deciding the outcome.

What is the best single UX question?

Show a seven-step flow and ask which steps to remove. Structural judgement shows immediately.

How long should a UX assessment take?

Ninety minutes for a design exercise with rationale; thirty for a critique.

Is a take-home design test fair?

Keep it under two hours, clearly not usable work, and score the rationale as much as the screens. For longer briefs, pay.

Cohesyve · Skill assessments for hiring

Test UX Design before the first interview

Generate a role-specific UX Design assessment from your job description and see who can do the work before you spend interview time on them.

1,500+

assessments completed

50%

faster time-to-hire

90%

completion rate

5 min

from JD to assessment

No credit card · 10 free candidates · Plans sized to your hiring volume

From the blog

Related skill guides