Interview scorecard template

Emerging Technologies Specialist interview scorecard

Pre-screening scorecard for Emerging Technologies Specialist candidates.

See AI scoring
frontier research deep techai adoptioninnovation labproof of concepttechnology scouting
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 depth on the technologies they claim: transformer architectures, edge IoT protocols, zero knowledge proofs, digital twins. Ask where each breaks down and what the current state of the art actually is.

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 mechanisms and known limitations of two or three specific technologies, citing papers, vendor benchmarks, or NIST and standards work.

02
Evaluation factor

From theory to hardware or code

30% weight

Probe pilots they built, not decks they wrote: proof of concept scope, stack used, sandbox or lab setup, and whether anything reached production or was formally killed.

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 shipped pilots with architecture details, cost per inference or device, and a clear record of both graduations and deliberate shutdowns.

03
Evaluation factor

Research judgement

20% weight

Test how they choose bets: technology radar placement, hype cycle scepticism, vendor evaluation criteria, and how they decide a capability is not yet ready for the business.

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

Describes a structured scouting method and a case where they recommended waiting, with the trigger conditions they set for revisiting.

04
Evaluation factor

Explaining it to non-specialists

15% weight

Assess briefings to executives, risk, and legal: business case framing, EU AI Act or data residency implications, and demos given to non-technical sponsors.

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

Translates a technical capability into cost, risk, and timeline language, and cites funding or policy decisions that followed their briefing.

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