Interview scorecard template

IT Risk Manager interview scorecard

Evaluate IT Risk Manager candidates across 4 weighted areas: technical depth, real incidents and findings, risk judgement, and getting things fixed. Technical depth leads at 35%, so probe how they quantify technology risk and whether they understand the systems behind the register entries. Use the rubric to compare role-specific evidence consistently.

See AI scoring
security compliancegovernanceit riskrisk managementthird party risk
TL;DR
For technical depth, look for evidence the candidate understands the systems behind each risk and can quantify exposure rather than colouring a heat map. For real incidents and findings, look for evidence the candidate names risks they got closed, and is candid about one that materialised and what the register missed. 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

Technical depth

35% weight

Probe how they quantify technology risk and whether they understand the systems behind the register entries.

Evidence to listen for

  • Command of the specific attack surface, tooling, and controls the role covers
  • Understands how the underlying system works, not just how the tool reports on it
  • Can explain an attack or control chain end to end
  • Distinguishes what they found themselves from what a scanner flagged

Five-point scoring guide

1
Poor

Tool operator only; no understanding of the systems underneath.

2
Needs Improvement

Runs tooling but cannot explain findings or how the attack works.

3
Satisfactory

Solid working knowledge; depth thins outside familiar tooling.

4
Very Good

Strong command of the domain; explains attack and control chains clearly.

5
Excellent

Understands the systems behind each risk and can quantify exposure rather than colouring a heat map.

02
Evaluation factor

Real incidents and findings

30% weight

Look for risks they actually retired, and any that materialised on their watch.

Evidence to listen for

  • Brings specific incidents, findings, or audits they personally worked
  • States their own role rather than the team's
  • Describes what was actually at risk and what changed afterwards
  • Can talk about a finding that turned out to be wrong

Five-point scoring guide

1
Poor

No hands-on work; knowledge is entirely certification or coursework.

2
Needs Improvement

Limited exposure; cannot describe their contribution to an incident.

3
Satisfactory

Real casework with adequate detail; ownership sometimes vague.

4
Very Good

Specific incidents with clear personal scope and what changed after.

5
Excellent

Names risks they got closed, and is candid about one that materialised and what the register missed.

03
Evaluation factor

Risk judgement

20% weight

Test how they judge an accepted risk that the business has been carrying comfortably for three years.

Evidence to listen for

  • Prioritises by actual exploitability and business impact, not raw severity scores
  • Can argue for accepting a risk as well as fixing it
  • Knows the difference between a finding and a problem
  • Does not cry wolf or wave things through

Five-point scoring guide

1
Poor

Treats every finding as critical, or waves real risk through.

2
Needs Improvement

Follows severity scores mechanically; no business context.

3
Satisfactory

Reasonable prioritisation; less confident arguing for risk acceptance.

4
Very Good

Prioritises by exploitability and impact; can justify accepting a risk.

5
Excellent

Re-tests stale accepted risks against current exposure rather than rolling them forward unchallenged.

04
Evaluation factor

Getting things fixed

15% weight

Assess how they get risk owners to act when nothing has gone wrong yet and budgets are committed elsewhere.

Evidence to listen for

  • Writes findings engineers can act on rather than a wall of output
  • Has persuaded a team to fix something they did not want to fix
  • Explains risk to executives in business terms
  • Works with the org rather than policing it

Five-point scoring guide

1
Poor

Adversarial with engineering; findings never get fixed.

2
Needs Improvement

Reports are unactionable; no influence beyond raising tickets.

3
Satisfactory

Adequate reporting; relies on mandate rather than persuasion.

4
Very Good

Actionable findings and a real record of getting fixes shipped.

5
Excellent

Moves risk owners to act pre-incident by framing exposure in business terms, with treatments actually delivered.

Evidence-led prompts

Interview questions for a IT Risk Manager

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

  1. 01

    How do you incorporate quantitative risk analysis into a risk assessment? Walk me through one risk you put a number on.

  2. 02

    Which risk assessment methodology do you actually use, and how do you set inherent versus residual ratings?

  3. 03

    Describe your hands-on experience with cyber security and data protection controls: which ones have you tested yourself?

  4. 04

    How familiar are you with the regulations that drive your risk register, such as GDPR, CCPA, DORA or SOX?

  5. 05

    Tell me about a risk you identified and actually retired. What was the residual rating before and after?

See the complete IT Risk Manager 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