Why pre-screen quantum cryptography researchers before the panel
Security proofs in this field hold under assumptions that hardware does not meet. Detectors can be blinded, sources emit extra photons, and side channels leak through timing. The important skill is stating exactly what a proof assumes and where a device breaks it. Researchers worth hiring do that unprompted. A short screen asks what a real system does not guarantee.
What actually matters when screening Quantum Cryptography Researcher candidates
- 01
Theoretical command
Probe depth in QKD security proofs, entropy accumulation, device-independent protocols, and lattice or isogeny based post-quantum schemes; ask which assumptions their proofs actually rest on.
- 02
From theory to hardware or code
Ask what they built: BB84 or CV-QKD testbeds, single photon detectors, FPGA sifting and error correction stacks, or liboqs and Kyber reference implementations.
- 03
Research judgement
Test how they chose problems: abandoned attack lines, side channel discoveries in detectors, responses to NIST standardisation shifts, and how they judged a result worth publishing.
- 04
Explaining it to non-specialists
Judge how they explain quantum advantage and harvest-now-decrypt-later risk to CISOs, procurement teams, or funders without equations, including migration timelines they have recommended.
Pre-screening questions to ask Quantum Cryptography 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.
Research they produced
3 questions01Can you discuss a project where you implemented quantum cryptographic techniques?
Listen forA specific piece of work with their contribution stated, and the result including negative findings.
Projects described at group level, or work with no output that can be examined.
02Can you explain research publications you have authored in this field?
Listen forPublications they can explain in depth, with their specific contribution to each one clear.
Author lists cited without being able to explain the method or the contribution.
03Can you describe a challenging aspect of your research and how you handled it?
Listen forA real difficulty in proof or experiment, with the approach that eventually resolved it.
Difficulty described as funding or access, or no research problem they had to work through.
Protocols precise
3 questions04Can you explain your experience with key distribution protocols?
Listen forProtocol families distinguished precisely, with the security assumptions of each stated correctly.
Protocols described generically, or the assumptions behind their security proofs not known.
05What experience do you have with entanglement and its role in cryptography?
Listen forThe role in device-independent approaches understood, with the practical difficulty acknowledged honestly throughout.
Entanglement invoked loosely, or device-independent protocols described as practical today.
06Can you explain the importance of randomness and how it is generated?
Listen forRandomness treated as a security-critical component, with generation and testing both addressed.
Randomness assumed available, or generator quality never considered as an attack surface.
Knows the gap
3 questions07Have you worked with quantum computing or communication platforms?
Listen forHands-on use with the practical limits of current systems described from experience.
Platform experience claimed without results, or capability described from documentation.
08What tools do you use for simulating and analysing these protocols?
Listen forSimulation run with realistic device parameters rather than ideal assumptions applied throughout.
Simulations run with perfect devices, or results presented without noise modelling.
09Can you describe troubleshooting a complex issue in one of these systems?
Listen forMethodical isolation between theory, implementation and hardware causes, with data behind it.
Problems attributed to hardware without investigation, or troubleshooting handled entirely by others.
Claims with assumptions
3 questions10What do you see as the current limitations of quantum cryptography?
Listen forDistance, rate, cost and implementation attacks all named, with an honest view of practical use.
Limitations described as engineering details, or deployment presented as imminent everywhere.
11How would you approach securing classical data against future quantum attacks?
Listen forStandardised post-quantum algorithms recommended for most cases, with the migration sequencing discussed properly.
Key distribution hardware proposed as the general answer, or migration planning not considered.
12How do you validate the security of a quantum cryptographic system?
Listen forAssumptions checked against the actual devices, with implementation attacks tested rather than assumed absent.
Security inherited from a proof, or the physical implementation never tested adversarially.
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%5Derives finite-key bounds and composable security arguments unprompted, and states precisely where each assumption on the adversary or device breaks.
From theory to hardware or code
30%5Names measured artefacts: secret key rates over fibre distance, QBER figures, detector dead time fixes, or merged code in a PQC library.
Research judgement
20%5Describes killing a promising direction on evidence, cites specific referee critiques absorbed, and explains why one threat model mattered more than another.
Explaining it to non-specialists
15%5Translates security parameters into concrete business risk and dates, holds up under sceptical questioning, and avoids overselling quantum threat hype.
Proofs assume ideal devices and hardware is not ideal. A one-way video screen asks what is not guaranteed.
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 research they produced, test their protocol depth, and hear how they handle implementation security.
Should I expect experimental or theoretical candidates?
Both exist and they answer very differently. Decide which your group needs, because a theorist and an experimentalist will each struggle with the other's questions.
Evaluating answers
What is the strongest signal when screening this role?
What a real system does not guarantee. Researchers with judgement name implementation attacks and assumption violations. Anyone describing unconditional security is quoting a proof, not a device.
How do I judge their broader usefulness?
Ask how they would protect classical data against future quantum attack. Sound answers point to standardised post-quantum algorithms rather than key distribution hardware for most cases.
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
