Why pre-screen BCI user experience researchers before the panel
This field breaks the usual usability playbook. Sessions are long, calibration drifts, signals are noisy, and a study with six participants is normal rather than a failure of recruitment. On top of that, participants often have a personal stake in the technology working, which shapes what they report. Researchers who handle all of this design differently and are careful about what they claim. A short screen surfaces whether someone has actually done it.
What actually matters when screening Brain-Computer Interface UX Researcher candidates
- 01
Theoretical command
Check command of EEG/ECoG signal basics, ITR and bits-per-minute metrics, P300 and SSVEP paradigms, plus NASA-TLX, SUS and workload instruments used in neuroergonomics studies.
- 02
From theory to hardware or code
Probe hands-on work with actual headsets or implant studies: OpenBCI, g.tec, Neurable, LSL streaming, Psychopy or Unity task builds, and IRB-approved protocols they wrote.
- 03
Research judgement
Assess how they choose between within-subject crossover designs and longitudinal single-case work when N is five, and how they handle participants with ALS or tetraplegia.
- 04
Explaining it to non-specialists
Test how they brief hardware engineers and clinicians: journey maps, calibration-burden findings, and translating a drop in classifier confidence into a design change.
Pre-screening questions to ask Brain-Computer Interface UX Researcher 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.
Studies they ran
3 questions01Can you provide examples of past projects related to neurological or cognitive devices?
Listen forStudies run with real hardware and participants, with their own role and what the findings changed in the device.
Experience limited to conventional software usability, or projects where findings changed nothing.
02What experience do you have with human-computer interaction research?
Listen forResearch they designed and ran themselves, with the questions each study was meant to answer.
Involvement limited to note-taking or recruiting, or research described with no research question.
03Can you detail your experience with usability testing in the context of these interfaces?
Listen forSession design that accounts for calibration time, fatigue and signal drift, with realistic session lengths.
Standard usability protocols applied unchanged, or no allowance for setup and calibration time.
Methods for small samples
4 questions04How familiar are you with quantitative and qualitative research methods?
Listen forBoth used with a reason for each, and awareness of what small samples support and what they do not.
Statistical tests applied to samples too small to support them, or qualitative work treated as preliminary only.
05How do you approach designing experiments to test these user interfaces?
Listen forWithin-subject designs and counterbalancing used deliberately, with learning effects and drift accounted for.
Between-subject designs proposed with six participants, or order effects never considered.
06How do you handle complex datasets and statistical analysis for user research?
Listen forAnalysis matched to the data with uncertainty reported, and a result they declined to claim as significant.
Significance found by testing many comparisons, or effect sizes never reported alongside tests.
07What metrics do you consider when evaluating the effectiveness of one of these interfaces?
Listen forMeasures beyond accuracy, including time to calibrate, workload and how usable it feels after an hour.
Effectiveness reduced to classification accuracy, or no measure of effort or fatigue.
Clinical participants
3 questions08Have you worked with participants from clinical populations?
Listen forPractical accommodations described, including session length, breaks and how they check consent is still willing.
Clinical participants treated as any other sample, or no adjustment for fatigue or communication needs.
09How do you ensure ethical standards and compliance in your research?
Listen forEthics approval as routine, with consent treated as ongoing and a case where they stopped a session.
Ethics described as a form completed once, or no situation where they have halted a study.
10How do you prioritise user needs in the development lifecycle of these systems?
Listen forResearch placed early enough to change the design, with a specific requirement that changed because of a participant.
Research run only to validate a built system, or findings that arrived after decisions were fixed.
Reporting honestly
2 questions11What strategies do you use to communicate research findings to a non-technical audience?
Listen forFindings reported with their confidence and sample limits intact, framed around the decision being made.
Findings simplified into confident claims, or sample size omitted when presenting results.
12How would you integrate insights from engineering, design and psychology into your research?
Listen forReal collaboration with signal processing and hardware colleagues, including a finding an engineer disputed.
Works within research only, or engineering constraints treated as obstacles to good design.
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.
Theoretical command
35%5Explains signal artefacts, calibration drift and decoder retraining alongside validated workload scales, without conflating usability metrics with decoding accuracy.
From theory to hardware or code
30%5Names specific devices and study builds they ran, including participant counts, session length and how findings changed the decoder or interface.
Research judgement
20%5Justifies small-N designs, defines stopping criteria, and treats non-transfer between able-bodied pilots and clinical users as a real risk.
Explaining it to non-specialists
15%5Turns neural and behavioural data into a concrete design recommendation clinicians and firmware engineers both act on, with caveats stated plainly.
Long sessions, drifting calibration and six participants is a normal study, not a recruitment failure. A one-way video screen asks what their sample could not show.
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. Enough to establish what studies they ran with real devices, test their method choices for small samples, and check their ethics practice.
Does general UX research experience transfer here?
Partly. Interviewing and observation transfer; the statistics and session design often do not. Ask specifically about small-sample work and long sessions rather than assuming a strong usability background carries over.
Evaluating answers
What is the strongest signal when screening this role?
What their sample could not support. Researchers with real experience volunteer the limits of a six-participant study. Anyone reporting confident conclusions from small samples will produce findings the team cannot rely on.
How do I judge their work with clinical participants?
Ask about consent and fatigue. Sound answers cover ongoing consent, session length limits and what they do when a participant tires. Anyone treating them as ordinary study participants has not run these sessions.
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
