About Programme and Project Manager interviews
Interviews for a Programme and Project Manager blend two scrutinies: can you run individual projects to time, cost and quality, and can you orchestrate a portfolio of interdependent projects toward a strategic outcome? Expect a recruiter screen confirming methodology fluency (PRINCE2, MSP, Agile, hybrid), sector context and salary fit. The hiring manager stage — often a Head of PMO, Portfolio Director or sponsoring executive — probes how you handle competing priorities, runaway budgets, slipping dependencies and difficult stakeholders. A case study or scenario loop is common: you might be handed a troubled programme and asked to triage it, or asked to build a governance structure and reporting cadence from scratch. Final stages typically test executive presence and how you escalate, influence and report upward to a programme board. Candidates most often stumble by speaking only in framework jargon without evidence of outcomes, by claiming project manager experience when the role demands genuine programme-level thinking (managing benefits, tranches and inter-project dependencies, not just tasks), and by being vague about commercial control — budgets, business cases and benefits realisation. The strongest candidates move fluidly between the granular (a slipping critical path) and the strategic (why this programme exists and what value it must deliver), and they are honest about programmes that went wrong and what they changed as a result.
Typical stages
- Recruiter screen
- Hiring manager interview
- Case study / scenario loop
- Programme board / executive panel
- Final values & culture conversation
Common formats
- Behavioral STAR
- Scenario triage exercise
- Case study
- Governance / reporting walkthrough
- Stakeholder role-play
What hiring managers screen for
- Genuine programme-level thinking: managing dependencies, tranches and benefits, not just task lists
- Commercial control of business cases, budgets and benefits realisation
- Stakeholder and executive influence, including escalation and difficult conversations
- Pragmatic methodology choice — knowing when to flex PRINCE2, MSP or Agile rather than dogma
- Evidence of recovering troubled programmes and learning from failures
Red flags to avoid
- Describing project admin (Gantt updates, status decks) as if it were programme management
- Hiding behind methodology jargon with no measurable outcomes attached
- No ownership of budget overruns or benefits shortfalls — always someone else's fault
- Inability to articulate how they prioritise across competing projects under constraint
- Avoiding hard stakeholder conflicts or escalation decisions
Primary questions (14)
Behavioural
Tell me about a programme you inherited that was off track. How did you turn it around?
Why this comes up: Recovery of troubled programmes is a core reason this role exists, and hiring managers want proof you can stabilise chaos.
Prep pointers
- Pick a genuine programme (multiple interdependent projects), not a single project.
- STAR Situation: quantify the trouble — schedule slip, budget overrun, stakeholder confidence lost. STAR Task: your specific remit and mandate. STAR Action: how you triaged, re-baselined and re-established governance. STAR Result: measurable recovery and what the board saw.
- Show the diagnostic sequence: what you assessed first and why.
- Common failure: jumping straight to 'I fixed it' without showing how you diagnosed the root causes.
Behavioural
Describe a time you had to deliver bad news to a programme board or executive sponsor.
Why this comes up: Executive escalation and honest upward reporting are critical at programme level, and boards punish managers who hide problems.
Prep pointers
- Choose an example where you escalated proactively, not after a crisis forced it.
- STAR Action should cover how you framed the message: data, options, and a recommendation — not just the problem.
- Emphasise the decision you were seeking from the board, not just the disclosure.
- Avoid making the sponsor look incompetent; show partnership in resolving it.
Behavioural
Give an example of managing conflicting demands across multiple projects competing for the same resources.
Why this comes up: Resource and priority contention across a portfolio is the daily reality of programme management.
Prep pointers
- Demonstrate a prioritisation framework tied to benefits or strategic value, not first-come-first-served.
- STAR Action: how you made the trade-off transparent and who you involved in the decision.
- Show you managed the disappointed stakeholders, not just the winning project.
- Common failure: implying you simply asked for more budget or people rather than making hard choices.
Behavioural
Tell me about a programme where the benefits were not realised as planned.
Why this comes up: Benefits realisation distinguishes programme managers from project managers, and honesty about shortfalls signals maturity.
Prep pointers
- Be candid — a manufactured success story here reads as inexperience.
- STAR Task: clarify who owned benefits and how they were defined and measured.
- STAR Action and Result: what you changed in your approach to benefits tracking afterwards.
- Avoid blaming the business entirely; show your accountability for benefits enablement.
Technical
Walk me through how you would set up governance and reporting for a new £10m, multi-year programme.
Why this comes up: Establishing fit-for-purpose governance from scratch is a foundational programme management competency.
Prep pointers
- Describe the board structure, decision rights, and reporting cadence — not just a tool.
- Explain how you'd define tranches, stage gates and tolerances.
- Cover the RAID and dependency management approach at programme level.
- Tailor governance weight to programme risk — show you avoid bureaucracy for its own sake.
Technical
How do you decide between a waterfall, Agile or hybrid delivery approach for a programme?
Why this comes up: Methodology fluency and the judgement to flex it is screened heavily for hybrid-environment roles.
Prep pointers
- Anchor the decision in requirement stability, risk profile and stakeholder needs — not personal preference.
- Give a concrete example where you blended approaches across constituent projects.
- Address how you reconcile fixed governance gates with Agile delivery cadences.
- Avoid dogma — purely defending one methodology is a red flag.
Technical
How do you manage and track inter-project dependencies across a programme?
Why this comes up: Dependency management is the defining technical discipline that separates programme from project work.
Prep pointers
- Explain how you map dependencies and identify the programme critical path.
- Describe the cadence and forum for surfacing and resolving cross-project dependency risks.
- Cover how you handle a dependency breaking late — escalation and contingency.
- Show tooling is secondary to the discipline and the conversations.
Technical
How do you build and defend a business case, and how do you manage it as costs evolve?
Why this comes up: Commercial control of the business case and budget is non-negotiable at programme level.
Prep pointers
- Cover cost, benefit, options appraisal and the assumptions you'd stress-test.
- Explain how you'd flag the business case becoming invalid and what action follows.
- Discuss earned value or equivalent for tracking cost and schedule performance.
- Be ready to defend a number under challenge — vagueness here undermines credibility.
Situational
A key project within your programme is going to slip by three months and breach a regulatory deadline. What do you do?
Why this comes up: Hiring managers test live decision-making under hard constraints and immovable external deadlines.
Prep pointers
- Show your immediate triage: validate the slip, assess impact across the programme and the regulatory exposure.
- Lay out options with trade-offs (de-scope, re-sequence, add resource) rather than a single answer.
- Be explicit about escalation timing and who needs to know.
- Common failure: reacting emotionally or committing to recover without a credible plan.
Situational
Two senior stakeholders fundamentally disagree on the programme's scope and both outrank you. How do you proceed?
Why this comes up: Programme managers constantly broker conflict between powerful sponsors without formal authority.
Prep pointers
- Show how you'd separate positions from underlying interests and find the data to ground the debate.
- Describe escalating to the right governance forum if you can't reconcile it.
- Emphasise maintaining trust with both parties throughout.
- Avoid implying you'd simply pick a side or wait it out.
Situational
Your programme board wants to cut the budget by 20% mid-flight but keep all the benefits. How do you respond?
Why this comes up: Pushing back on unrealistic executive demands with evidence is a core programme leadership test.
Prep pointers
- Show you'd model the impact rather than refuse or capitulate immediately.
- Present the trade-off between scope, benefits, time and risk explicitly to the board.
- Demonstrate influencing upward with options and a recommendation.
- Avoid both blind acceptance and confrontational refusal.
Competency
How do you manage risk at the programme level versus within individual projects?
Why this comes up: Aggregating and managing risk across a portfolio is a competency that distinguishes the role.
Prep pointers
- Distinguish programme-level risks (strategic, dependency, benefit) from project-level operational risks.
- Explain how risks escalate and de-escalate between the two levels.
- Give a concrete example of a programme risk you actively mitigated.
- Avoid treating risk as a register-filling exercise — show active management.
Competency
How do you lead and motivate project managers who don't report to you directly?
Why this comes up: Programme managers deliver through a team of PMs via matrix authority, making influence without line management essential.
Prep pointers
- Describe how you set direction and standards while respecting their delivery autonomy.
- Cover how you support a struggling PM versus one who is underperforming.
- Show how you create alignment and shared accountability across the team.
- Avoid implying you'd micromanage their individual projects.
Culture fit
What kind of programme environment brings out your best work, and where do you struggle?
Why this comes up: Fit between a manager's operating style and the organisation's maturity and pace strongly predicts success.
Prep pointers
- Be honest about your preferences (structured vs ambiguous, mature vs nascent PMO).
- Tie your answer to what you've learned about this organisation's context.
- Frame a genuine weakness with how you compensate for it.
- Avoid a generic 'I thrive anywhere' answer that signals low self-awareness.
More practice questions (13)
Technical
How do you structure a programme into tranches, and what triggers the transition between them?
Why this comes up: Tranche-based delivery is core MSP-style programme structuring.
Technical
What KPIs and reporting metrics do you put on a programme dashboard for an executive board?
Why this comes up: Concise, decision-focused reporting is expected of senior programme managers.
Technical
How do you apply earned value management, and when is it not worth the overhead?
Why this comes up: Tests depth of cost/schedule control knowledge and pragmatism.
Technical
How do you manage a programme's transition into business-as-usual operations?
Why this comes up: Embedding change and handover is a frequently overlooked programme responsibility.
Situational
A critical supplier underpinning two projects misses a contractual milestone. What's your first move?
Why this comes up: Third-party and commercial dependency management is common in large programmes.
Situational
Your sponsor leaves the organisation mid-programme. How do you protect momentum?
Why this comes up: Sponsor change is a real continuity risk programme managers must navigate.
Behavioural
Tell me about a time you had to stop or cancel a project within a programme.
Why this comes up: Knowing when to kill work is a mark of disciplined portfolio judgement.
Behavioural
Describe a time your reporting or forecast turned out to be wrong. What happened next?
Why this comes up: Tests accountability and how a manager handles forecasting errors.
Competency
How do you manage stakeholder communications across a large, diverse programme audience?
Why this comes up: Stakeholder mapping and tailored communication is a daily programme competency.
Competency
How do you handle scope creep across multiple projects feeding one programme outcome?
Why this comes up: Change control at scale is a recurring challenge for the role.
Competency
How do you balance governance rigour with delivery speed?
Why this comes up: Pragmatic governance is valued over either bureaucracy or chaos.
Culture fit
What does success look like to you twelve months into this programme?
Why this comes up: Reveals whether the candidate thinks in outcomes and benefits, not activity.
Technical
How do you set and use tolerances at programme and project level?
Why this comes up: Tolerance-based management is a PRINCE2/MSP fundamental for delegated control.
Get a prep pack tailored to your experience
describe.me matches these questions against your real work history,
flags your prep priorities, and gives you a STAR scaffold per question.
Start free →