Why pre-screen UI/UX designers before the portfolio review
Portfolio reviews reward presentation, and presentation is a real skill that is not the one you are buying. A case study can be constructed after the fact around a design that shipped in a compromised form and moved nothing. What separates candidates is whether they know what happened after release, and whether they can name a decision that was overruled and why. Both are quick to establish and largely absent from the artefacts a review puts in front of you.
What actually matters when screening UI/UX Designer candidates
- 01
Portfolio
Ask them to walk through two case studies end to end: problem framing, wireframes, Figma prototypes, final UI, and what the metrics did after launch.
- 02
Craft and rationale
Probe component libraries, auto layout, variants, tokens, accessibility choices (WCAG contrast, focus order, tap targets) and why they picked a pattern over alternatives.
- 03
Feedback and iteration
Test how they handle usability test findings and stakeholder critique: what they changed after moderated sessions, Maze or Hotjar data, or a failed A/B variant.
- 04
Working with the brief
Check how they run intake with product and engineering: clarifying requirements, edge cases, handoff specs, dev QA of built screens, and scope negotiation under deadlines.
Pre-screening questions to ask UI/UX Designer candidates
12 questions grouped by what they test. Ask the same set in every screen and score answers on a consistent scale, or send them as an async video screen and compare answers side by side.
Work that shipped
3 questions01Can you describe a project where you made a significant improvement to the user experience?
Listen forWork that shipped with their own contribution named, plus what the design looked like after engineering and scope constraints landed on it.
Concept work presented as shipped, or a case study whose final state differs from what users actually received.
02Do you have experience designing for both mobile and web?
Listen forGenuine platform differences named in interaction and constraint, rather than the same layout adapted across breakpoints.
Claims both with examples from one, or responsive resizing described as designing for mobile.
03Do you have experience working with product managers and developers?
Listen forWorking relationships during build rather than at handover, with a design changed because an engineer explained the cost.
Hands over files and moves on, or describes engineering as failing to implement the design correctly.
Defending decisions
3 questions04What is your approach to resolving usability problems in a design?
Listen forProblems identified from evidence such as testing or support data, with the fix reasoned rather than chosen from a pattern library.
Usability judged by personal opinion, or fixes applied because a competitor does it that way.
05What is your process for conducting user research?
Listen forResearch they ran themselves with recruitment described, and an instance where findings contradicted what the team expected.
Research handed to another team entirely, or findings that only ever confirmed the existing plan.
06What is your approach to creating personas and journey maps?
Listen forArtefacts built from collected evidence and actually used in decisions, with a view on when they are not worth producing.
Personas assembled from assumptions, or artefacts produced for the case study rather than for the work.
Measured after launch
3 questions07How do you measure the success of your designs?
Listen forA metric agreed before the work with the result known afterwards, including a design that did not move what it was meant to.
Success measured by launch or by stakeholder approval, with no post-release measurement at all.
08What is your approach to testing design changes before rolling them out?
Listen forReal testing with sample size considered, and a willingness to accept a losing result rather than shipping the preferred design anyway.
Tests stopped when the preferred variant is ahead, or results overridden by preference with no reasoning.
09Which of your projects are you most proud of, and why?
Listen forPride attached to a problem solved or a constraint navigated, rather than to visual outcome or the profile of the client.
Pride based on how the work looks, or a project where their contribution cannot be separated from the team's.
Holding a position
3 questions10How would you handle a stakeholder disagreeing with your design proposal?
Listen forBoth moves in one answer: a design changed after a fair challenge, and one held with evidence rather than with preference.
Defers automatically to seniority, or holds every position regardless of the argument against it.
11Can you describe a situation where your design was not approved? How did you handle it?
Listen forAn honest account of why it was rejected, including cases where the objection was right and what they learned from it.
Every rejection attributed to stakeholders not understanding design, or no design of theirs ever rejected.
12How do you work within brand guidelines while solving a design problem?
Listen forWorking inside a system with a case where they proposed extending it, and how that change was reviewed and agreed.
Treats guidelines as an obstacle, or departs from a design system without raising it with whoever owns it.
How to score responses
Score every candidate on the same four criteria immediately after the screen. At this stage you are shortlisting for panel interviews, not making the final call.
Portfolio
35%5Shows shipped product screens with before and after states, plus measured lifts in task completion, activation, or support ticket volume.
Craft and rationale
25%5Explains type scale, spacing system, and state handling precisely, and defends pattern choices against usability and accessibility constraints.
Feedback and iteration
25%5Cites a design they killed or reworked after evidence, separating personal taste from what testing and analytics actually showed.
Working with the brief
15%5Describes concrete handoff artefacts and pushback moments, converting vague briefs into scoped flows engineers built without repeated rework.
A case study can be built around a design that shipped compromised and moved nothing. A one-way video screen asks what happened after release.
Try it on HirevireScreening FAQ
Process basics
How long should a pre-screening round for a UI/UX designer take?
Fifteen minutes across eight to ten questions, answered async. Enough to establish what shipped and what they owned, hear how they measure design outcomes, and check how they handle stakeholder disagreement.
How should this change the portfolio review?
Run the screen first and let it set the agenda. Once you know which projects shipped and what the candidate personally decided, the review can interrogate those decisions rather than walking through case studies in the order they were prepared.
Evaluating answers
What is the strongest signal when screening a UI/UX designer?
Knowing what happened after release. Designers who stayed with their work can say whether the metric moved, whether support tickets changed, and what they would revise. Portfolios almost always stop at the final mockup.
How do I judge answers about stakeholder disagreement?
Look for both moves in one answer: a time they changed their design after a challenge, and a time they held it with evidence. Designers who always defer produce work with no point of view; those who never do are difficult to ship with.
Go deeper on this role
Sanat has been hiring since 2012 and watching the recruitment industry change up close ever since, and turned that screening process into Hirevire's video screening platform. LinkedIn
