Why pre-screen key distribution network managers before the panel
Running one of these networks is an operations job. Fibre loss sets the ceiling, detectors drift, polarisation wanders overnight, and the key rate that matters is the one sustained over weeks rather than the one measured on a good afternoon. Managers worth hiring quote that number. A short screen asks what rate they sustained and what limited it.
What actually matters when screening Quantum Key Distribution Network Manager candidates
- 01
Theoretical command
Probe command of BB84, decoy-state and MDI protocols, finite-key security proofs, QBER budgets, and where trusted-node assumptions break under photon-number-splitting or detector blinding attacks.
- 02
From theory to hardware or code
Ask what they physically built or ran: ID Quantique or Toshiba links, SNSPD or InGaAs detectors, dark fibre or DWDM coexistence, ETSI QKD 014 key delivery into HSMs.
- 03
Research judgement
Test how they choose between trusted-node relays, MDI-QKD, and PQC hybrids given budget, distance and threat model, and when they judged a quantum link not worth deploying.
- 04
Explaining it to non-specialists
Judge how they brief telecom operators, regulators or CISOs on quantum-safe roadmaps without hand-waving; look for BSI, NSA or ETSI guidance cited honestly, including QKD's limitations.
Pre-screening questions to ask Quantum Key Distribution Network Manager 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.
Links they operated
3 questions01Can you discuss real deployments of key distribution you have worked on?
Listen forNamed links with distance, sustained key rate and their operational responsibility described.
Deployments described from publications, or no system they operated day to day.
02Describe your experience with key distribution protocols.
Listen forProtocol variants used in practice, with the reason for choosing one for a deployment.
Protocols described only in theory, or the practical differences between them unclear.
03Describe your experience integrating this technology with existing communication systems.
Listen forKey delivery into conventional encryptors handled, with the interfaces and their limits understood.
Integration assumed straightforward, or the classical infrastructure treated as somebody else's.
Protocols precise
3 questions04How familiar are you with the main key distribution protocol families?
Listen forPrepare-and-measure and entanglement-based approaches clearly distinguished, with the assumptions behind each stated.
Protocol families confused, or the security assumptions behind each not understood.
05Can you explain the role of entanglement in this technology?
Listen forThe role explained accurately, with the practical difficulty of entanglement-based systems acknowledged.
Entanglement invoked loosely, or entanglement-based deployment described as routine today.
06Explain the role of repeaters in extending distance.
Listen forHonest assessment that true repeaters remain experimental, with trusted nodes described accurately.
Repeaters described as available, or trusted node security implications not acknowledged.
Diagnoses instability
3 questions07How do you mitigate loss and error rates in a link?
Listen forError sources separated between fibre, detectors and alignment, with each addressed on evidence.
Errors attributed to the channel generally, or detector noise never characterised.
08How do you handle synchronisation problems in these systems?
Listen forTiming and drift managed actively, with recovery from loss of synchronisation designed in.
Synchronisation assumed stable, or drift over temperature not encountered in practice.
09How do you evaluate the performance of a deployed network?
Listen forKey rate and error rate tracked continuously, with availability measured over months not days.
Performance quoted from commissioning, or availability never measured over a long period.
Claims match hardware
3 questions10How do you ensure the security of the keys these systems generate?
Listen forKey handling after generation addressed, with storage and classical authentication both secured.
Security assumed from the physics, or key handling after generation not considered.
11What are the main challenges in deploying one of these networks?
Listen forDistance, cost, dedicated fibre and trusted nodes named as the practical obstacles from experience.
Challenges described as awareness or cost alone, or physical constraints not mentioned.
12What experience do you have with post-quantum cryptographic algorithms?
Listen forStandardised algorithms understood, with an honest view of where each approach actually fits.
Post-quantum dismissed in favour of hardware, or standardisation status unfamiliar.
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 secret key rate scaling with loss, cites finite-key bounds, and names concrete side channels their protocol choice does not cover.
From theory to hardware or code
30%5Describes commissioned links with span loss, key rates in kbps, uptime figures, and the integration path into existing KMS or IPsec tunnels.
Research judgement
20%5Weighs cost per key bit against realistic adversaries, argues for hybrid PQC where QKD adds little, and states assumptions plainly.
Explaining it to non-specialists
15%5Gives non-specialists a clear picture of what QKD does and does not guarantee, correcting hype rather than selling it.
Loss sets the ceiling and detectors drift overnight. A one-way video screen asks what rate they sustained.
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 links they operated, test their protocol knowledge, and check how they diagnose instability.
Should I also look for post-quantum knowledge?
Yes. Most organisations protect data with standardised post-quantum algorithms rather than key distribution hardware, and a manager who cannot discuss both will misadvise on scope.
Evaluating answers
What is the strongest signal when screening this role?
A sustained key rate over distance, with the limiting factor named. Managers who operated a link know both. Anyone answering only in protocol terms has studied rather than run one.
How do I judge their security claims?
Ask what the deployed system does not protect against. Sound answers cover implementation attacks and the need for authenticated classical channels. Unconditional security describes the proof, not the hardware.
























