IT Change Manager interview questions and practice.
Runs the IT change process, assessing and scheduling changes to systems so they go live safely and without surprises.
No card for the taster. Full interviews are paid one at a time. Nothing renews.
Last reviewed
This page is still being written: no authored question bank for this competency family. The role is fully supported in the interview itself; only the published question bank is outstanding.
What interviewers for IT Change Manager actually ask
The question bank for this role is still being written. These are the first three competencies in the model the interview is scored against.
Runs IT services to agreed levels using ITSM practices (incident, problem, change) that are measured and improved, not just documented.
Plans and controls IT spend, negotiates contracts and licences, and manages vendors to deliver value and accountability.
Owns IT risk: security posture, business continuity, data protection (POPIA) and audit findings, and makes risk visible to the business in its terms.
What they are really assessing
Interviewers rarely score whether you seemed nice. They score against a model like this one, usually without telling you it exists. Each competency has a weak, adequate and strong shape, and the difference is almost always the level of specific detail you volunteer without being asked.
Service delivery & operational excellence
Runs IT services to agreed levels using ITSM practices (incident, problem, change) that are measured and improved, not just documented.
- Weak
- Describes ITIL by name but cannot show service metrics, a problem they eliminated, or a change process that reduced incidents; firefighting is normal.
- Adequate
- Has SLAs and metrics and has improved a process, but improvements are anecdotal and problem management is weak.
- Strong
- Gives measured improvements (incident volume, MTTR, change failure rate, satisfaction) from specific changes they led, and a problem-management case that removed a recurring outage.
Budget, procurement & vendor management
Plans and controls IT spend, negotiates contracts and licences, and manages vendors to deliver value and accountability.
- Weak
- Budget is inherited and spent; cannot describe a negotiation, a licence optimisation or a vendor held to account.
- Adequate
- Manages a budget with forecasting and has negotiated a contract renewal, but total cost of ownership and vendor performance are not tracked systematically.
- Strong
- Describes a budget with the trade-offs made, a negotiation with measured savings, a licensing or cloud cost optimisation, and a vendor performance issue managed to resolution or exit.
Risk, security & compliance governance
Owns IT risk: security posture, business continuity, data protection (POPIA) and audit findings, and makes risk visible to the business in its terms.
- Weak
- Security is the security team's problem; cannot describe a risk register, a continuity test or an audit finding they closed.
- Adequate
- Maintains a risk register and has closed audit findings and run a continuity test, but risk is not framed in business terms and findings recur.
- Strong
- Describes presenting a risk to executives in business terms that changed a decision, a continuity exercise with gaps found and fixed, and a security or compliance programme with measured results.
Project & change delivery
Delivers IT projects and business changes (system implementations, migrations) on time and budget with adoption, and handles projects that go wrong.
- Weak
- Projects are late and over budget for reasons outside their control; cannot describe a recovery, a scope decision, or how adoption was measured.
- Adequate
- Has delivered projects using a structured method and handled scope changes, but benefits and adoption were not measured and troubled projects were escalated rather than recovered.
- Strong
- Gives a project with its measured outcome and adoption, a scope or budget decision made with the sponsor, and a troubled project they recovered with the actions taken.
Leading & developing an IT team
Builds and leads a capable team: hiring, development, performance management, on-call fairness and retention in a competitive skills market.
- Weak
- Cannot describe an underperformer handled, a person developed, or a retention problem addressed; team structure is inherited.
- Adequate
- Has managed performance and developed people, but underperformance dragged on and retention of scarce skills is reactive.
- Strong
- Describes an underperformance case with clear expectations and outcome, a person they developed into a senior role, and a retention or on-call change with measured effect.
Business partnership & stakeholder management
Understands the business's goals, translates them into IT priorities, and manages executive expectations including saying no with reasons.
- Weak
- IT is an order-taker; cannot describe pushing back on an executive request or aligning IT work to a business goal.
- Adequate
- Meets regularly with business leaders and prioritises with them, but struggles to decline requests and IT is still seen as a cost centre.
- Strong
- Describes reframing a request into the underlying business need, a prioritisation negotiated with executives with trade-offs explicit, and how they changed the business's perception of IT with evidence.
Technology strategy & modernisation
Sets a realistic technology direction (cloud, legacy retirement, tooling) tied to business needs, and sequences it into achievable steps.
- Weak
- Strategy is a list of vendor products; cannot explain why a modernisation was chosen or a legacy system they retired.
- Adequate
- Has a roadmap tied to business needs and has led a migration, but benefits are unquantified and legacy retirement stalls.
- Strong
- Describes a strategy with business drivers, a modernisation delivered with measured cost or risk reduction, a legacy system retired, and a bet that did not pay off and what changed.
Crisis leadership & communication
Leads through major outages, security incidents and failed changes: calm decision-making, honest communication to executives and users, and follow-through on lessons.
- Weak
- Major incidents are described as chaotic; communication was reactive; cannot name a lesson implemented afterwards.
- Adequate
- Has led major incidents with a process and communicated to executives, but updates were uneven and some follow-up actions were not completed.
- Strong
- Gives a major incident with timeline, the decisions made under uncertainty, the communication cadence to executives and users, and completed follow-up actions with evidence of reduced recurrence.
Reading the questions is the easy half. Try answering three of them out loud, to someone who follows up.
Try 5 minutes freeWhat your 30 minutes covers
The same shape as a real first-round interview, pitched at mid-level IT Change Manager and scored throughout.
Warm-up, then Motivation & fit
Build rapport, settle nerves, and get a short walk-through of your background. Why this role, why this employer, and what you are actually looking for.
Your experience
Two or three real situations from your CV in depth: context, what you did, what happened, what you would change.
Pitched at leadership scope: head of IT or IT director: owns the IT function's strategy, budget, risk, delivery and people.
Role-specific questions
The core competencies and domain knowledge for the role, with follow-ups on anything vague.
Drawn from this role's domain: improving incident, problem and change management with measured results, setting and reporting SLAs that the business actually cares about and building and defending an IT budget with trade-offs, and the rest of the competency model.
Your questions, then Wrap-up
Your questions for the interviewer, and yes, they are assessed. Next steps and a clean finish.
What changes with seniority
The questions barely change between levels. What changes is the answer they will accept.
| Junior | Mid | Senior | |
|---|---|---|---|
| Scope of ownership | Team lead or new manager owning a small team's service delivery (e.g. service desk or a site) while still hands-on. | IT manager owning services, a team of 5-15, a budget line and projects for a site or function. | Senior IT manager or head of a domain (infrastructure, applications, operations) with multiple teams and a significant budget. |
| Tolerance for ambiguity | Works within priorities set by an IT manager; expected to raise capacity and risk issues early. | Translates business needs into IT priorities and handles competing demands without escalating everything. | Shapes strategy with executives, defines team structures and makes trade-offs across teams. |
| People leadership | First direct reports: rostering, one-on-ones, feedback, task allocation. | Full line management: performance, hiring, development, on-call. | Manages team leads and managers; develops leaders; handles complex people situations. |
| Who they deal with | Own team, IT manager, business users. | Business unit managers, vendors, security and infrastructure peers, finance. | Executives, heads of business units, major vendors, auditors and regulators. |
What your report would say
Every competency above scored from your own answers, the sentence that cost you quoted back, and your weakest answers rewritten the way a strong IT Change Manager would have said them.
- Describes presenting a risk to executives in business terms that changed a decision, a continuity exercise with gaps found and fixed, and a security or compliance programme with measured results.
The format, not a result. Scores on your report come from what you actually said.
Is the AI interviewer realistic? See a full sample report