Why pre-screen senior UX designers before the portfolio review
Redesigns that look cleaner and perform worse are common, and they never appear in a portfolio. What distinguishes senior designers is that they measured, found out, and can say so. Add research that shaped a design rather than confirming one, and you have most of the signal. A short screen asks for a design that tested worse, which almost nobody volunteers unprompted.
What actually matters when screening Senior UI/UX Designer candidates
- 01
Portfolio
Ask them to walk through two shipped product flows: onboarding, checkout, or dashboard work. Look for before and after screens, Figma prototypes, and measurable outcomes like task completion or drop-off.
- 02
Craft and rationale
Probe grid systems, type scales, component variants, auto layout, tokens, and WCAG contrast decisions. Ask why they chose a pattern over a modal, drawer, or wizard.
- 03
Feedback and iteration
Test how they handled usability test findings, analytics from Hotjar or Amplitude, and critique from engineers who said a design was not buildable.
- 04
Working with the brief
Check how they turn vague product requests into scoped design work: discovery questions, success metrics agreed with PMs, and handoff specs engineers actually used.
Pre-screening questions to ask Senior 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.
Measured outcomes
3 questions01Can you describe a project where you significantly improved the user experience?
Listen forA measured improvement in task success, conversion or support volume, with the baseline stated.
Improvement described visually, or outcomes claimed with no measurement before and after.
02Can you describe balancing user needs against business goals?
Listen forA real tension resolved with evidence, with what the business gave up or gained stated clearly.
The tension denied, or user needs always described as aligning perfectly with commercial goals.
03Can you describe a difficult design challenge you worked through?
Listen forA genuine constraint such as a legacy system or a complex workflow, with the design response explained.
Challenges described as stakeholder difficulty, with no design problem identified.
Research that informed
3 questions04What is your experience with user research and usability testing?
Listen forResearch they ran themselves, with a case where the findings changed their intended direction.
Research conducted to validate an existing design, or testing outsourced with no involvement.
05What is your experience with controlled testing of design changes?
Listen forTests designed with a primary measure agreed beforehand, and losing variants reported honestly.
Tests stopped early when ahead, or only successful tests ever discussed.
06How do you iterate on a design based on feedback or data?
Listen forIteration driven by observed behaviour, with a version abandoned when the evidence went against it.
Iteration based on opinion, or no design they abandoned after testing.
Accessible by design
3 questions07What is your process for creating a user-centred design?
Listen forThe problem and the users established before any interface work, with assumptions tested early.
Process starting from screens, or user understanding taken from stakeholder descriptions.
08Can you explain your experience with wireframing and prototyping?
Listen forFidelity matched to the question being answered, with prototypes used to test rather than to present.
High-fidelity work produced before the concept is validated, or prototypes used only for sign-off.
09How do you approach accessibility in your design work?
Listen forContrast, focus order and keyboard access designed in, with testing using assistive technology.
Accessibility handled by a later audit, or designs handed over without focus states specified.
Position held
3 questions10How do you handle stakeholder feedback and incorporate it?
Listen forFeedback separated into preference and problem, with the underlying concern addressed rather than the note.
Every stakeholder note implemented, or feedback dismissed as opinion without exploring it.
11How do you handle disagreements about design decisions?
Listen forDisagreements resolved with evidence or a test, with a position held when the evidence supports it.
Disagreements settled by seniority, or the designer always deferring to the loudest voice.
12Do you have experience working in cross-functional teams?
Listen forEngineering constraints treated as inputs, with a design changed because of implementation cost.
Designs handed over as specifications, or engineering concerns treated as a lack of ambition.
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 live shipped screens, explains the problem and constraints behind each, and cites conversion, retention, or support ticket movement.
Craft and rationale
25%5Defends layout, hierarchy, and accessibility choices with specifics on tokens, states, responsive breakpoints, and edge cases like empty and error views.
Feedback and iteration
25%5Describes killing a favoured concept after five user sessions, and reworking specs with engineering rather than defending the original comp.
Working with the brief
15%5Reframes fuzzy briefs into stated user problems, agrees success measures upfront, and delivers handoff files that reduce build-time clarification requests.
Redesigns that look cleaner and convert worse never make it into a portfolio. A one-way video screen asks about one.
Try it on HirevireScreening FAQ
Process basics
How long should a pre-screening round for this role take?
Fifteen minutes across eight to ten questions, answered async, alongside a portfolio. Enough to establish measured outcomes, test their research practice, and check stakeholder handling.
What should I ask for alongside the screen?
Case studies including the outcome, not just the final screens. A portfolio without measured results shows craft; the outcome shows whether the craft solved the problem.
Evaluating answers
What is the strongest signal when screening this role?
A design that tested worse than what it replaced. Designers who measure have one. Anyone whose redesigns all improved things has either not measured or is selecting the wins.
How do I judge their research practice?
Ask about research that changed their direction. Real answers describe abandoning an approach. Anyone whose research always supported the plan was validating rather than investigating.
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
