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

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

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

1. How is running an IT programme different from managing a single project, and what do you think makes a great IT Programme Manager?

Why they ask: They want to hear a clear understanding of programme leadership at director level.

2. How do you apply Managing Successful Programmes, or a similar method, to define and track benefits realisation?

Why they ask: Benefits are why programmes exist, so they want to see rigour beyond delivery of outputs.

3. What governance structure would you put in place for a large, multi-million-pound technology programme?

Why they ask: Governance is how a programme remains controlled and accountable, and directors design it.

4. Your programme has been reporting amber for months, and you now realise it will miss its date by three months. What do you do?

Why they ask: They want to see transparency, analysis and options under senior pressure.

5. How do you manage dependencies and build an integrated plan across several projects, suppliers and business teams?

Why they ask: Cross-project dependencies are the usual source of programme delay.

6. The business sponsor wants to go live on the planned date, but testing shows unresolved severity-two defects and the cutover rehearsal overran. What do you do?

Why they ask: This tests judgement, risk framing and your readiness to challenge a sponsor.

7. Tell me about a time you delivered a large, complex technology programme, and what your personal contribution was.

Why they ask: They want to establish scale, leadership impact and real accountability.

8. How do you manage the financial side of a programme, including the business case, budget control and change requests?

Why they ask: Directors are accountable for money and need to demonstrate financial discipline.

A sample answer to question 1

How is running an IT programme different from managing a single project, and what do you think makes a great IT Programme Manager?

A project delivers a defined output within agreed scope, time and cost. A programme coordinates a group of related projects and business change to deliver outcomes and benefits that none could achieve alone, such as replacing a core platform across the organisation. So my focus moves from tasks to benefits, interdependencies, stakeholders, funding and risk across the whole portfolio of work. I believe a great programme manager has several traits. They keep the vision and business case in view when the detail gets noisy. They build credibility with senior sponsors and with the engineers doing the work, and they are honest about bad news early. They are comfortable with ambiguity, and make decisions with incomplete information. They also develop their project managers and create a culture where problems are raised, not hidden. Finally, they care that the change sticks after go-live, rather than stopping at delivery.

Common mistake to avoid: Describing it as a bigger project; Ignoring business change

Want the rest?

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