IT Change Manager Interview Questions UK: 8 Real Questions and What Interviewers Want

Applying for a IT Change Manager job in the UK? Here is what you are likely to be asked. These questions come from our IT Change Manager question bank of 12 questions, written for UK employers at manager level.

Eight IT Change Manager interview questions, and what the interviewer is thinking

1. How would you structure a Change Advisory Board, and what makes it effective rather than a bottleneck?

Why they ask: CAB design is central to the change manager's role and a frequent interview topic.

2. How do you assess the risk and impact of a proposed change, and what should a good change request contain?

Why they ask: Risk assessment quality determines whether changes cause incidents.

3. What is the difference between standard, normal and emergency changes, and how do you decide which route applies?

Why they ask: They want to see you can apply ITIL change types sensibly.

4. How do you manage change across multiple teams during a large release or migration, including freeze periods and the forward schedule of change?

Why they ask: Coordination across many changes is a core skill of a change manager.

5. Which metrics would you use to manage the change process, and how do you use them to improve it?

Why they ask: They want to see you manage change as a service, with data.

6. A senior director demands that a risky change goes ahead without the normal approvals because of a business deadline. What do you do?

Why they ask: They want to see you hold the line professionally while remaining helpful.

7. Tell me about a time you improved a change management process. What was the result?

Why they ask: They want proof you can deliver measurable process improvement.

8. What does a day in the life of an IT change manager look like, and what qualities does the role need?

Why they ask: They want to check you understand the role's rhythm and demands.

A sample answer to question 1

How would you structure a Change Advisory Board, and what makes it effective rather than a bottleneck?

I would keep the CAB focused on changes that genuinely need a collective decision, which means high-risk or high-impact ones, while routine, well-understood changes follow pre-approved standard change procedures and low-risk ones get peer review or automated approval. Membership should be small and relevant: the change manager chairs, with representatives from service delivery, infrastructure, applications, security, service desk and the business, plus the change owner presenting each item. The agenda is circulated in advance with the change requests, risk assessments, test evidence, rollback plans and communication plans, so the meeting discusses concerns instead of reading documents. I run it to time, with clear outcomes recorded: approve, reject, defer or request more information. For emergencies I would use an emergency CAB with a smaller quorum. I measure effectiveness through change success rate, emergency change volumes and lead time, and review them regularly to streamline the process where evidence shows low risk.

Common mistake to avoid: Sending every change to CAB; Running long meetings with no decisions

Want the rest?

Full model answers, key points and common mistakes for all 12 questions are on the IT Change Manager interview questions page. The first five are free, no sign-up needed.