Interview scorecard template

Post-Quantum Cryptography Architect interview scorecard

Pre-screening scorecard for Post-Quantum Cryptography Architect candidates.

See AI scoring
frontier research deep techcrypto agilityfips 203lattice cryptographyml kem
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 lattice and hash-based hardness assumptions: Module-LWE parameter choices in ML-KEM, ML-DSA versus SLH-DSA trade-offs, and why SIKE and Rainbow fell.

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 FIPS 203/204/205 parameter sets and security categories precisely, and cites concrete cryptanalytic results behind algorithm selection.

02
Evaluation factor

From theory to hardware or code

30% weight

Ask what they built: hybrid X25519MLKEM768 key exchange in TLS 1.3, liboqs or BoringSSL integrations, HSM and PKI certificate profiles, constant-time implementations.

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 deployments with measured handshake latency and packet size impact, plus side-channel hardening they verified rather than assumed.

03
Evaluation factor

Research judgement

20% weight

Assess how they sequence a migration: cryptographic inventory and CBOM production, harvest-now-decrypt-later exposure ranking, crypto-agility abstractions, and when to wait for standards rather than deploy.

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

Prioritises long-lived secrets and firmware signing roots with clear reasoning, and states which decisions they deliberately deferred.

04
Evaluation factor

Explaining it to non-specialists

15% weight

Look for evidence they briefed boards, auditors or product teams: quantum risk timelines without hype, CNSA 2.0 mandates, budget and vendor readiness conversations.

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 lattice mathematics into concrete business exposure and dates, and has changed executive or supplier behaviour as a result.

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