Why pre-screen human-computer interaction specialists before the portfolio review
A well-run study that changes nothing is the standard failure in this field, and it is invisible in a portfolio. The reasons are usually structural: research arrives after the design is fixed, findings are written for other researchers, or the recommendation ignores what the engineering team can actually build. Specialists who avoid all three get findings implemented. A short screen asks what changed because of their work, and what did not.
What actually matters when screening Human-Computer Interaction Specialist candidates
- 01
Technique and experimental design
Probe how they design studies: within versus between subjects, counterbalancing, sample sizing, and instruments such as SUS, NASA-TLX, think-aloud protocols, eye tracking or Tobii heatmap setups.
- 02
Results that went somewhere
Ask which findings changed a shipped interface: navigation redesigns, error rate drops, task completion or time-on-task gains, WCAG 2.2 fixes that cleared an audit.
- 03
Troubleshooting and reproducibility
Test how they handle noisy or contradictory data: pilot failures, participant dropout, confounded prototypes, disagreement between behavioural logs and self-report scores.
- 04
Documentation and collaboration
Look for study protocols, consent and ethics submissions (IRB or equivalent), tagged qualitative codebooks, and how they hand findings to product managers and front-end engineers.
Pre-screening questions to ask Human-Computer Interaction Specialist 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.
Findings that shipped
4 questions01Can you describe your experience with usability testing and the methods you prefer?
Listen forMethods chosen for the question at hand, with a study whose findings changed something that shipped.
One method used for every question, or studies described with no consequence for the product.
02Describe a time when you used heuristic evaluation during a project.
Listen forEvaluation used to find issues cheaply before testing, with findings prioritised rather than listed exhaustively.
Heuristic evaluation used as a substitute for testing with users, or every violation reported equally.
03Can you share an example of user testing revealing a critical issue with your design?
Listen forA finding that contradicted their own design, with what they changed and how the team reacted to it.
Testing that only confirmed the design, or an issue found and shipped anyway with no attempt to argue.
04What key metrics do you use to evaluate the effectiveness of a user interface?
Listen forTask completion and error rate alongside subjective measures, chosen for what the interface is actually for.
Satisfaction scores used alone, or metrics chosen because they are easy to collect.
Prototypes at right fidelity
3 questions05What tools and software do you commonly use for prototyping and wireframing?
Listen forFidelity matched to the question, with paper or sketches used when that answers it faster.
High-fidelity prototypes built for every question, or tools named with no reasoning about fidelity.
06Tell me about a time when you had to redesign an existing application. What was your process?
Listen forExisting behaviour studied before redesigning, with what they deliberately kept because users relied on it.
Redesign started from a visual refresh, or existing patterns discarded without understanding their use.
07How do you prioritise features during the design process?
Listen forPrioritisation tied to observed user need with something they argued to remove, not just to add.
Priority set by stakeholder seniority, or no feature they have ever recommended cutting.
Built for everyone
2 questions08Can you discuss your experience designing for accessibility and inclusivity?
Listen forAccessibility built into design decisions with testing involving assistive technology, not a review at the end.
Accessibility handled as a compliance check, or no testing beyond an automated tool.
09Can you share experience of designing for international or diverse user groups?
Listen forReal differences accounted for, such as text expansion, reading direction or varying digital familiarity.
Diversity addressed only through translation, or one user model assumed across very different groups.
Engineers who built it
3 questions10How do you collaborate with developers to ensure implementation meets the design?
Listen forEarly involvement with engineering, with specifications detailed enough that edge cases are not invented later.
Designs handed over with no follow-up, or implementations that diverged with nobody noticing.
11Describe an occasion where you had to trade user needs against technical constraints.
Listen forA real constraint accepted with the design adapted, rather than the constraint challenged until someone gave in.
Technical constraints treated as excuses, or every trade-off resolved in the design's favour.
12How do you prioritise user needs when stakeholders give conflicting feedback?
Listen forConflicts resolved with evidence from users, with a case where they told a senior stakeholder the data disagreed.
Conflicts resolved by seniority, or feedback averaged into a design that serves nobody.
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.
Technique and experimental design
35%5Names the study design and rationale, defends sample size and task order, and distinguishes formative usability work from controlled comparative experiments.
Results that went somewhere
25%5Cites specific products and measured deltas, plus the recommendation engineers or designers actually implemented after the study.
Troubleshooting and reproducibility
25%5Describes re-running pilots, triangulating telemetry against interviews, and openly reports where effects did not replicate or were underpowered.
Documentation and collaboration
15%5Keeps traceable protocols and coded transcripts, and turns them into prioritised, developer-legible recommendations rather than a slide deck of quotes.
A well-run study that changes nothing looks identical in a portfolio to one that shipped. A one-way video screen asks what changed and what got ignored.
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, with portfolio links. Enough to establish what their evaluations changed, test their prototyping judgement, and check how they work with engineering.
How does this differ from a UX researcher screen?
Weight evaluation method and implementation more heavily. This role usually sits closer to the interface itself, so ask about heuristic evaluation, prototype fidelity and whether specifications were built as written.
Evaluating answers
What is the strongest signal when screening this role?
A finding the team did not act on and what they did about it. Specialists who get results treat that as a problem to solve. Anyone who describes only findings that were adopted has not worked under real constraints.
How do I judge their prototyping judgement?
Ask when they use paper and when they build something interactive. Sound answers match fidelity to the question being asked. Anyone who always builds high-fidelity prototypes is spending time to answer questions cheaply answerable.
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
