How to Hire a Program Manager

Why this role matters

Large changes such as a system migration, a new product line or a reorganisation rarely fail inside a single project. They fail in the gaps: two teams assuming the other owns a dependency, a sponsor changing priorities without anyone resetting plans, or benefits nobody measures after go-live. A good programme manager closes those gaps, raises bad news early and keeps decision-makers honest about trade-offs. A weak one produces status reports that are always green until the deadline passes.

Where to find candidates

• PMI members holding the PgMP (Program Management Professional) or PMP credential, verifiable in PMI's online certification registry
• APM members in the UK, including Chartered Project Professionals
• Practitioners certified in MSP (Managing Successful Programmes), common in UK public sector and large organisations
• SAFe Release Train Engineers and programme leads, for organisations running scaled agile
• Senior project managers and technical programme managers inside your own organisation who have already handled cross-team work
• Consultancies and interim management providers, for programmes with a fixed end date

Skills to look for

Red flags

• Describes the role entirely as producing reports and running meetings
• Every past programme was green right up to the end, with no example of escalating bad news
• Cannot name the benefits a previous programme was meant to deliver or whether they were achieved
• Treats agile and waterfall as tribal positions instead of tools
• Takes credit for delivery but cannot describe a specific dependency they untangled
• Lists certifications but cannot apply the frameworks to a messy real example

The interview process

1. 1

   Screening call

   Confirm the scale and type of programmes they have run, how many project managers reported into them and what governance they set up.

2. 2

   Programme deep dive

   Ask them to walk through one programme end to end: why it existed, how it was structured, what went wrong and what benefits were measured afterwards. Probe the parts they skip.

3. 3

   Cross-project work sample

   Provide three short project plans that share a test environment and a vendor, plus a sponsor email moving a deadline forward. Ask for a dependency map, the top risks and a one-page note to the steering group with options. A job simulation of this kind of programme work is one option for comparing candidates on the same task.

4. 4

   Stakeholder interview

   Have a senior sponsor play a difficult stakeholder who wants scope added without moving the date. Watch how they handle the trade-off.

5. 5

   References

   Speak to a former sponsor and a project manager who worked under them. Ask how early problems surfaced and how decisions were made.

How to evaluate

• Quality of the dependency map and risk list in the work sample
• Clarity and honesty of the steering group note
• Ability to hold a position with a senior stakeholder
• Focus on outcomes and benefits
• Evidence of governance that helped decisions rather than slowing them
• Reference feedback on transparency

Onboarding

• 1Give them the original business case and any benefit targets in week one
• 2Introduce them personally to every sponsor and project manager on the programme
• 3Let them reset the programme baseline after their first month, with a frank view of current status
• 4Agree decision rights clearly: what they can approve and what goes to the steering group
• 5Review their first two steering group packs together before they run solo

Common questions