Why pre-screen HCI specialists before the research interview
HCI candidates often come from academic backgrounds where the standard of evidence is high and the timescale is long. That rigour is exactly what a product team lacks and frequently cannot absorb, because a study that takes eight weeks arrives after the decision. The specialists worth hiring have learned to size a method to the decision in front of them without abandoning what makes the finding trustworthy. A short screen establishes whether a candidate has made that adjustment.
What actually matters when screening Human-Computer Interaction (HCI) 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 (HCI) 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.
Method fits the question
3 questions01How do you approach usability testing?
Listen forA protocol sized to the decision, with participant numbers justified and an explicit statement of what that sample can support.
One standard protocol regardless of question, or percentages reported from a handful of participants.
02Which methods do you use for gathering user feedback?
Listen forA range with a basis for choosing between them, and awareness that what people say and what they do routinely differ.
Relies on surveys asking people what they want, or a single method applied to every question.
03What role does user research play in your design process?
Listen forResearch used to shape a question early rather than to validate a decision already made, with an example of each.
Research run after the design is finished, or findings only ever confirming what the team already believed.
Work that reached product
3 questions04Can you give an example of a project where you improved the user experience?
Listen forWork that shipped with the measured effect stated, and their own contribution separated from the design and engineering teams.
Academic or speculative projects only, or an improvement claimed with no measurement after release.
05Can you give an example of solving a challenging interaction design problem?
Listen forA specific interaction difficulty with the alternatives they tested, and why the chosen approach won on evidence rather than preference.
The problem described as visual, or a solution chosen because it matched a familiar pattern.
06Have you worked with accessibility in mind? How?
Listen forTesting with assistive technology and disabled participants, with a specific design change that followed rather than a standard cited.
Accessibility described as a compliance checklist, or no testing with anyone using assistive technology.
Observed against concluded
3 questions07How do you measure the success of your designs?
Listen forMeasures agreed before the work with the result known afterwards, including a change that did not move what it was meant to.
Success measured by launch or stakeholder approval, with no measurement after release.
08Can you discuss your experience with data visualisation and reporting findings?
Listen forFindings presented with uncertainty visible, and observation separated clearly from the inference drawn on top of it.
Visualisations that hide sample size or uncertainty, or conclusions presented as if directly observed.
09Describe your experience with information architecture.
Listen forStructure validated with users through card sorting or tree testing rather than derived from the organisation's own mental model.
Architecture that mirrors internal team structure, or structure decided with no user validation.
Findings that landed
3 questions10How do you handle design critiques and feedback?
Listen forBoth moves in one answer: a finding revised after a fair challenge, and one held with the evidence set out plainly.
Repeats the finding more firmly, or abandons a conclusion as soon as a senior person disagrees.
11How do you prioritise features and improvements based on user findings?
Listen forSeverity and frequency weighed together, with a problem they deprioritised despite it being real because the cost outweighed it.
Every finding treated as equally urgent, or prioritisation handed entirely to product with no input.
12Describe your experience working in a multidisciplinary team.
Listen forEngineers and designers brought into sessions as observers, with findings delivered early rather than as a report at the end.
Works in isolation and delivers a report, or no experience of a developer watching a session.
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.
Academic rigour is what product teams lack and frequently cannot absorb at their pace. A one-way video screen asks whether a candidate has made that adjustment.
Try it on HirevireScreening FAQ
Process basics
How long should a pre-screening round for an HCI specialist take?
Fifteen minutes across eight to ten questions, answered async. Enough to hear how they choose methods, whether their work has shipped, and how they handled a delivery team that would not act on a finding.
How does this differ from screening a UX researcher?
The overlap is large. HCI screening leans harder on method rigour, accessibility and interaction-level problems; UX research screening leans harder on stakeholder work and pace. Decide which emphasis your team needs before weighting the questions.
Evaluating answers
What is the strongest signal when screening an HCI specialist?
A study sized to the decision. Specialists who have worked in product describe cutting a method down to fit a two-week window while being explicit about what that cost in confidence. Academic answers describe the study they would have preferred to run.
How much should accessibility count?
Heavily, because it is the clearest test of whether someone designs for real users rather than assumed ones. Ask what they changed after testing with assistive technology. Anyone treating accessibility as a compliance checklist has not done it.
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
