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

Most IT Project Manager interviews in the UK follow a pattern, and knowing it beats guessing. Below are eight questions from our bank of 25, each with a note on what the interviewer is really after.

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

1. How do you decide whether an IT project should use Agile, Waterfall or a hybrid approach?

Why they ask: They want to see that you choose a delivery method on the merits of the project rather than by habit.

2. How do you build a realistic project plan and schedule for a software or infrastructure project?

Why they ask: They want to know you can estimate, sequence and baseline work so that dates are credible.

3. How do you manage scope creep on an IT project?

Why they ask: Scope creep is one of the most common causes of overruns, so they want to see practical control.

4. Your project is three weeks behind schedule and over budget, and the sponsor does not yet know. What do you do?

Why they ask: They are testing honesty, early escalation and your ability to bring options rather than just problems.

5. How do you manage risks and issues on a project, and what goes into your RAID log?

Why they ask: They want to see a disciplined, proactive approach rather than firefighting.

6. How would you plan and run a go-live for a major system release or cutover?

Why they ask: They want to see that you can control a high-risk event with rehearsal, rollback and clear communication.

7. Tell me about an IT project you delivered that achieved clear business benefits.

Why they ask: They want evidence of delivery and impact, not just activity.

8. What does a typical week as an IT project manager involve?

Why they ask: They want to check you understand the practical reality of the role.

A sample answer to question 1

How do you decide whether an IT project should use Agile, Waterfall or a hybrid approach?

The deciding factor is how well the requirements are understood and how much change I expect. If the scope is fixed and regulated, such as a data centre migration or a network refresh with hard dependencies, a predictive approach with PRINCE2 stage gates gives the control the board wants. If the users can't define the end product up front, as with a new customer portal, I'd use Scrum or Kanban so we learn through short feedback cycles. Often the honest answer is hybrid: a governance wrapper with business case, stage boundaries and risk reporting, and Agile delivery inside the stages. I also weigh team experience, supplier contracts, because fixed-price deals fight against Agile, and the organisation's appetite for change. I'd always agree the approach with the sponsor early and write it down in the project initiation document, so nobody is surprised when the plan looks different from what they expected.

Common mistake to avoid: Claiming one method always wins; Ignoring contract and team constraints

Want the rest?

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