Interview scorecard template

IT Compliance Manager interview scorecard

Evaluate IT Compliance Manager candidates across 4 weighted areas: technical depth, real incidents and findings, risk judgement, and getting things fixed. Technical depth leads at 35%, so check command of control frameworks they name: SOC 2 Trust Services Criteria, ISO 27001 Annex A, NIST CSF, SOX ITGCs, plus how they test access. Use the rubric to compare role-specific evidence consistently.

See AI scoring
security complianceaudit evidenceit compliancesoc 2sox itgc
TL;DR
For technical depth, look for evidence the candidate maps specific controls to framework clauses, describes testing procedures and sampling, and distinguishes design effectiveness from operating effectiveness. For real incidents and findings, look for evidence the candidate recounts named audits with cycle dates, exception counts, root causes, and the remediation evidence that closed each finding. 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

Check command of control frameworks they name: SOC 2 Trust Services Criteria, ISO 27001 Annex A, NIST CSF, SOX ITGCs, plus how they test access provisioning and change management evidence.

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

Maps specific controls to framework clauses, describes testing procedures and sampling, and distinguishes design effectiveness from operating effectiveness.

02
Evaluation factor

Real incidents and findings

30% weight

Probe actual audits they carried: external auditor fieldwork, PCI DSS assessments, findings and management responses they wrote, and any qualified opinions or exceptions they had to remediate.

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

Recounts named audits with cycle dates, exception counts, root causes, and the remediation evidence that closed each finding.

03
Evaluation factor

Risk judgement

20% weight

Assess how they rank risk: control gap severity, compensating controls, residual risk acceptance, vendor risk tiering, and when they escalated to legal or the audit committee.

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

Separates genuine control failures from documentation gaps, and justifies risk acceptance with business impact rather than blanket policy citation.

04
Evaluation factor

Getting things fixed

15% weight

Look for evidence they moved engineering teams: Jira remediation tickets, control owner sign-offs, automated evidence collection in tools like Vanta or Drata, and audit readiness timelines.

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

Names owners, deadlines and tooling used to close gaps, and shows repeat findings dropping across successive audit cycles.

Evidence-led prompts

Interview questions for a IT Compliance Manager

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

  1. 01

    Can you provide an example of when you developed or improved a compliance programme?

  2. 02

    Have you developed compliance strategies within an organisation, and what was the outcome?

  3. 03

    Can you describe a time when you used technology to improve compliance?

  4. 04

    Can you explain your experience with audits and reporting?

  5. 05

    What is your experience dealing with regulators or industry bodies?

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