Interview scorecard template

IT Change Manager interview scorecard

Evaluate IT Change Manager candidates across 4 weighted areas: execution and reliability, improving the process, judgement and autonomy, and communication. Execution and reliability leads at 35%, so check volume and cadence of changes they governed: weekly CAB chairing, emergency change approvals, freeze window enforcement, and tooling like ServiceNow, Jira Service Management. Use the rubric to compare role-specific evidence consistently.

See AI scoring
operations administrationchange advisory boarditilrelease managementservicenow
TL;DR
For execution and reliability, look for evidence the candidate names weekly change volumes, chaired CAB personally, and cites change failure rate or unauthorised change counts they tracked. For improving the process, look for evidence the candidate describes a specific policy or workflow change with before and after figures for lead time, backout rates or failed changes. 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

Execution and reliability

35% weight

Check volume and cadence of changes they governed: weekly CAB chairing, emergency change approvals, freeze window enforcement, and tooling like ServiceNow, Jira Service Management or BMC Remedy.

Evidence to listen for

  • Describes a workload they owned and how they kept it from slipping
  • Names the tools and systems they ran day to day
  • Can talk about volume: tickets, inboxes, orders, uptime
  • Nothing quietly falls through when they are busy

Five-point scoring guide

1
Poor

Cannot describe their own workload; things slip without them noticing.

2
Needs Improvement

Handles routine volume; drops work under pressure.

3
Satisfactory

Reliable on steady-state work; struggles when volume spikes.

4
Very Good

Consistently reliable at real volume with a system for staying on top.

5
Excellent

Names weekly change volumes, chaired CAB personally, and cites change failure rate or unauthorised change counts they tracked.

02
Evaluation factor

Improving the process

25% weight

Probe redesigns they drove: standard change catalogues, pre-approved templates, automated CI-linked risk scoring, or shrinking lead time for low-risk changes without raising incident rates.

Evidence to listen for

  • Has changed a process rather than only following one
  • Can name what was slow or error-prone and what they did about it
  • Documents so the improvement survives them
  • Knows when a process is worth automating and when it is not

Five-point scoring guide

1
Poor

Follows instructions only; no sense that process can change.

2
Needs Improvement

Notices problems but escalates rather than solving.

3
Satisfactory

Makes small improvements; impact is local and undocumented.

4
Very Good

Has redesigned a real process with measurable effect.

5
Excellent

Describes a specific policy or workflow change with before and after figures for lead time, backout rates or failed changes.

03
Evaluation factor

Judgement and autonomy

25% weight

Test how they handle a poorly documented change request landing hours before a peak trading freeze, plus their line between emergency change and full CAB review.

Evidence to listen for

  • Knows what to decide alone and what to escalate
  • Handles an exception without freezing or improvising recklessly
  • Protects confidentiality and access appropriately
  • Asks a clarifying question rather than guessing on something costly

Five-point scoring guide

1
Poor

Either escalates everything or acts recklessly on their own.

2
Needs Improvement

Needs frequent direction; uneasy with exceptions.

3
Satisfactory

Sound judgement on familiar decisions.

4
Very Good

Clear sense of their own authority; handles exceptions well.

5
Excellent

Rejects or conditionally approves with clear reasoning: test evidence, backout plan, blast radius, and named accountable owner.

04
Evaluation factor

Communication

15% weight

Assess how they push back on release engineers and application owners, communicate blackout calendars, and brief senior stakeholders after a change-induced P1 outage.

Evidence to listen for

  • Writes clearly enough that people act without a follow-up
  • Manages expectations before a deadline slips, not after
  • Handles a frustrated colleague or customer calmly
  • Works across time zones or async where the role needs it

Five-point scoring guide

1
Poor

Unclear written communication; goes quiet when things slip.

2
Needs Improvement

Communication needs chasing; raises problems late.

3
Satisfactory

Clear enough day to day; proactive updates are inconsistent.

4
Very Good

Clear, proactive, and calm under pressure.

5
Excellent

Holds firm on evidence requirements while staying constructive; writes plain post-implementation reviews that assign actions, not blame.

Evidence-led prompts

Interview questions for a IT Change Manager

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

  1. 01

    What experience do you have with IT change management?

  2. 02

    How do you track and measure the success or failure of a change?

  3. 03

    How do you assess the potential impact of a proposed change?

  4. 04

    Can you explain your process for implementing change within an organisation?

  5. 05

    Which tools and software have you used for change management?

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