Interview scorecard template

Quantum Communications Engineer interview scorecard

Evaluate Quantum Communications Engineer candidates across 4 weighted areas: theoretical command, from theory to hardware or code, research judgement, and explaining it to non-specialists. Theoretical command leads at 35%, so probe command of QKD protocols: BB84 with decoy states, MDI or twin-field variants, finite-key security proofs, and how channel loss in dB. Use the rubric to compare role-specific evidence consistently.

See AI scoring
frontier research deep techentanglement distributionphotonicsqkdsnspd
TL;DR
For theoretical command, look for evidence the candidate derives secret key bounds from measured loss and QBER, and names the security assumptions each protocol family actually relies on. For from theory to hardware or code, look for evidence the candidate describes a link they brought up end to end, quoting fibre length, detector efficiency, QBER, and sustained key rate over days. Apply the written 1–5 anchors to every answer, record the evidence behind each rating, and use the factor weights to reach a consistent overall assessment.
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

Probe command of QKD protocols: BB84 with decoy states, MDI or twin-field variants, finite-key security proofs, and how channel loss in dB sets achievable secret key rate.

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

Derives secret key bounds from measured loss and QBER, and names the security assumptions each protocol family actually relies on.

02
Evaluation factor

From theory to hardware or code

30% weight

Ask what they built and ran: time-bin or polarisation encoders, SNSPD or InGaAs detector setups, FPGA time-tagging, key distillation software, dark fibre or free-space link commissioning.

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

Describes a link they brought up end to end, quoting fibre length, detector efficiency, QBER, and sustained key rate over days.

03
Evaluation factor

Research judgement

20% weight

Test how they choose between approaches: trusted-node relays versus quantum repeaters, WDM coexistence with classical traffic, and which experiments they abandoned and why.

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

Explains a decision to drop or pivot an approach using data on Raman noise, drift, or cost rather than novelty.

04
Evaluation factor

Explaining it to non-specialists

15% weight

Look for how they brief telecom operators, ETSI or ITU standards groups, and security auditors who want certification evidence, not photon statistics.

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 key rate and eavesdropper bounds into operational risk language, and has presented to network engineers or standards bodies.

Evidence-led prompts

Interview questions for a Quantum Communications Engineer

Use these prompts to surface evidence for the weighted factors above and compare candidates against the same role-specific criteria.

  1. 01

    Can you describe projects you have worked on involving quantum communications?

  2. 02

    Do you have experience with quantum key distribution systems?

  3. 03

    Do you have experience designing and implementing quantum communication systems?

  4. 04

    Can you explain what qubits are and how they are used in communications?

  5. 05

    Are you able to develop and analyse quantum communication protocols?

See the complete Quantum Communications Engineer question set
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