Interview scorecard template

Brain-Computer Interface Developer interview scorecard

Pre-screening scorecard for Brain-Computer Interface Developer candidates.

See AI scoring
frontier research deep techbci decodingeeg ecogneural signal processingneuroprosthetics
Complete evaluation framework

What to assess and how to score it

Review the evidence signals before interviewing. Then use the anchored descriptions—not instinct alone—to choose the score that best matches each answer.

01
Evaluation factor

Theoretical command

35% weight

Check command of neural signal foundations: sensorimotor rhythm and P300 paradigms, spectral feature extraction, CSP, artifact rejection for EMG and ocular noise, and non-stationarity across sessions.

Evidence to listen for

  • Explains the underlying theory at the level the role demands, and can go a layer deeper when pushed
  • Knows which results are established and which are contested
  • Distinguishes their own contribution from the field's
  • Comfortable saying where the theory runs out

Five-point scoring guide

1
Poor

Recites terminology without understanding; cannot go one layer deeper.

2
Needs Improvement

Surface familiarity; conflates established results with speculation.

3
Satisfactory

Solid grasp of the core theory; thin at the frontier.

4
Very Good

Strong command; separates settled results from open questions.

5
Excellent

Explains decoder choices from neurophysiology, not just accuracy tables; discusses session drift, referencing schemes and sampling trade-offs precisely.

02
Evaluation factor

From theory to hardware or code

30% weight

Probe what they built end to end: OpenBCI or g.tec rigs, LSL or BCI2000 pipelines, Blackrock or Utah array data, closed-loop latency budgets, cursor or speller demos.

Evidence to listen for

  • Has built, simulated, or run something real, not only published about it
  • Knows the gap between the idealised model and the actual apparatus or system
  • Names the practical constraint that dominates in real conditions
  • Can describe a result that did not match prediction

Five-point scoring guide

1
Poor

Purely theoretical; no contact with implementation.

2
Needs Improvement

Some exposure but unaware of practical constraints.

3
Satisfactory

Has implemented work; understands the main real-world limits.

4
Very Good

Strong practical record; articulate about theory-versus-reality gaps.

5
Excellent

Names working systems with measured bit rate, latency in milliseconds, and hours of human or primate recording behind them.

03
Evaluation factor

Research judgement

20% weight

Assess how they chose problems and killed dead ends: invasive versus non-invasive framing, calibration burden, subject counts, and when a decoder gain was noise.

Evidence to listen for

  • Chooses problems by tractability and value, not novelty alone
  • Knows when to abandon a line of work
  • Reads and evaluates others' results critically
  • Can say what would falsify their own approach

Five-point scoring guide

1
Poor

Chases novelty; no sense of tractability or when to stop.

2
Needs Improvement

Weak problem selection; persists past the point of value.

3
Satisfactory

Reasonable judgement within a defined programme.

4
Very Good

Selects problems well and knows when to abandon a line.

5
Excellent

Abandoned promising approaches on evidence, cites cross-subject validation and honest failure cases rather than best-run results.

04
Evaluation factor

Explaining it to non-specialists

15% weight

Look for how they brief clinicians, IRB reviewers, and participants: consent language, realistic capability claims, and translating decoder output into patient-relevant function.

Evidence to listen for

  • Explains the work to an engineer, an executive, or a funder without either mystifying or dumbing it down
  • Writes clearly
  • Collaborates across disciplines
  • Makes the case for resources in terms the audience cares about

Five-point scoring guide

1
Poor

Cannot communicate outside their specialism.

2
Needs Improvement

Explanation is either impenetrable or hollow.

3
Satisfactory

Adequate with technical peers; less effective with lay audiences.

4
Very Good

Explains clearly to specialists and non-specialists alike.

5
Excellent

Explains signal quality and risk plainly to surgeons or ethics boards without overselling restored function or hiding calibration limits.

Put this rubric to work

Score every candidate against the same standard

Add these weighted factors to Hirevire and let AI evaluate recorded answers against your rubric.

Explore AI Scorecards