Questions to Ask a Program Manager
Interview questions for a program manager candidate, focused on the scope they have actually run, how they handled slippage and cross-team dependencies, and when they escalate rather than absorb a problem.
The questions
Open any question for the note
Walk me through the largest program you have run: how many teams, what budget, over how long?
Why ask it
Three numbers early sets the scale of everything that follows. Candidates often describe programs they coordinated a part of, so ask specifically what they owned and who else was doing the same job alongside them.
What did your weekly status update look like, and who actually read it?
Why ask it
Ask them to describe the format. People who name the fields, and who admit that only two of eleven recipients read it, have thought about reporting as a tool rather than a ritual.
How did you find out when something was going wrong?
Why ask it
Good answers describe a route that does not depend on people volunteering bad news: a metric, a standing one-to-one, sitting in on a team's own review. Answers that rest on "my leads tell me" mean they hear about problems when they are already late.
Tell me about a problem you learned about too late. What made it invisible?
Why ask it
Everyone has one. The useful part is whether they can name the structural cause, a team that reported up a different chain, a metric nobody owned, rather than blaming a specific individual.
When two teams disagreed about sequencing, how did it get settled?
Why ask it
Listen for whether they resolved it themselves, brokered a decision between the leads, or escalated. All three are legitimate; a candidate who always chose the same one is a poor fit for a program with strong technical leads.
How do you keep a dependency honest when the other team does not report to you?
Why ask it
This is the core of the job. Strong answers involve making the commitment visible to someone the other team cares about, plus an early test that the dependency is real. Weak answers are about relationship-building alone.
What was the gap between your original plan and what actually shipped, and what caused most of it?
Why ask it
A candidate who quotes a real number, even a bad one, has run a program to the end and looked back at it. Vagueness here usually means they left before the reckoning or never compared the two.
What did you cut when the date could not move?
Why ask it
The specifics reveal how well they understood the work. Cutting testing and documentation is the reflex answer; cutting a named feature after a conversation with the person who wanted it is the practiced one.
Describe a time you told a senior stakeholder something they did not want to hear.
Why ask it
Ask what words they used and what happened next. Candidates who cannot recall an instance either work somewhere with no bad news or have been managing upward by omission.
Tell me about a risk you flagged that nobody acted on.
Why ask it
You find out how they escalate when the first attempt fails, and whether they kept a record. Also watch whether the story ends in vindication and nothing else, which suggests they treat being right as the deliverable.
How do you decide what not to escalate?
Why ask it
This separates program managers from message relays. Look for a threshold they can articulate: cost, reversibility, whether the owning team already has it in hand. Escalating everything burns credibility as fast as escalating nothing.
You inherit a program already in trouble. What do you do in the first month?
Why ask it
Strong answers start by finding out what is actually true, talking to people doing the work, checking the plan against reality, before changing process. A candidate who opens with new rituals will spend the month producing paperwork.
How do you handle a team lead who agrees in the meeting and then does nothing?
Why ask it
The realistic answer involves finding out why, since it is usually a competing priority from their own manager rather than obstruction. Answers about accountability and follow-up alone suggest they have never diagnosed the cause.
What changed in how you worked between a program of five people and one of fifty?
Why ask it
Anyone who has crossed that line can describe it: they stopped attending everything, started managing through leads, gave up on knowing all the detail. Candidates who say nothing changed have probably not run the larger one.
How did you know the program was finished?
Why ask it
Programs end messily, and a candidate who describes a closing criterion agreed in advance is unusual. Others describe attrition of attention, which is honest and tells you they have seen how it really goes.
What tools did you use, and what did you stop using?
Why ask it
The abandoned tool is the interesting half. It shows they noticed overhead that produced nothing, and it usually comes with a story about what the team was doing to satisfy the tool rather than the work.
Which part of this work do you find tedious?
Why ask it
Everybody has one, and the honest answer tells you what will quietly go undone. Someone who claims to enjoy all of it is either inexperienced or performing.
How do you work with an engineering or product lead who thinks the role is overhead?
Why ask it
It is a common view and worth hearing them handle it without defensiveness. The best answers involve making themselves useful on something concrete first, rather than arguing for the discipline in the abstract.
What would your last three team leads say is frustrating about working with you?
Why ask it
Naming three people forces specificity, and the answer is checkable in references. A candidate who offers a real irritation, too many check-ins, slow to let a decision go, is likely to have asked them at some point.
What do you want to know about this program before you decide whether to take it on?
Why ask it
Experienced candidates ask about the sponsor, whether the date is fixed, and who has tried this before. Someone with no questions is treating it as a job rather than a program, which is how programs stall.
Interviewing for program management
Practical guidance for the conversation itself
Running the conversation
Ask for one program in depth, not five in summary
Take a single program and stay in it for twenty minutes: the plan, the slip, the cuts, the ending. Breadth is easy to narrate from a resume. Depth is not.
Make them use numbers
Teams, headcount, budget, original date, actual date. Candidates who talk in scale and outcomes without figures are often describing programs they were adjacent to.
Separate what they did from what the team did
Follow every "we" with "what was your part of that?" This is the most reliable way to size a program manager's real contribution.
Give them a live problem
Describe an actual dependency or staffing conflict from your own program and ask what they would do first. It shows whether they gather facts before installing process.
What to listen for
- They can state a slippage figure and its main cause without prompting.
- They describe influencing teams that did not report to them, by making commitments visible rather than by force of personality.
- They have a threshold for escalation and can say what falls below it.
- They talk about the people doing the work, not only the leads and the sponsor.
- They have abandoned a process or a tool, and can say why.
- They ask you about the sponsor and whether the date is genuinely fixed.
Common interviewing mistakes
Accepting methodology as an answer
A fluent account of a framework tells you what they have read. Ask what they did the week the plan stopped being true.
Testing tool knowledge instead of judgment
Any competent candidate learns your tracker in a fortnight. What they cannot learn quickly is when to escalate and what to cut.
Skipping references from peers
Managers report on visibility, peers report on whether the program manager made their work easier or added meetings. Ask two team leads who worked alongside them.
Hiring for a program you have not defined
If you cannot say who the sponsor is, what is fixed, and what success looks like, no candidate will be able to either. Settle that before the interviews.