What does a program manager do?
A program manager runs a group of related projects toward one shared goal and stays responsible for the benefits after those projects finish. Neither BLS nor O*NET has a separate profile for the title. The nearest is project management specialists, and a US federal memo spells out how a program differs from a project.
The Bureau of Labor Statistics page on project management specialists, last modified August 27, 2026, says they "coordinate the budget, schedule, staffing, and other details of a project." Its duties include to "monitor project milestones and deliverables" and to "propose, review, and approve modifications to project plans." It gives a median annual wage of $102,320 in May 2025 and projects employment to grow 7 percent from 2025 to 2035.
O*NET OnLine's profile for Project Management Specialists (13-1082.00) lists tasks such as "communicate with key stakeholders to determine project requirements and objectives" and "negotiate with project stakeholders or suppliers to obtain resources or materials." Its top transferable skills are judgment and decision making, coordination, time management, complex problem solving and management of personnel resources. Its sample job titles do not include program manager.
The clearest public split between the two jobs comes from the US Office of Management and Budget. Its memo M-18-19, dated June 25, 2018, defines a project as "a temporary endeavor to create a unique product or service with a start date, a completion date, and a defined scope." It describes program management as work that aims "to achieve benefits and advance outcomes." The memo was written for federal agencies, though the same split is a useful frame for any program manager answer.
How were these program manager questions chosen?
They come from the duties in the BLS and O*NET profiles and the OMB definitions, matched to the question each duty tends to produce. They are drawn from the job's published duties, not from a survey of real interviews. Nothing here claims to be the most asked, or to match what any named company asks.
| Duty (BLS, O*NET and OMB) | Question it tends to produce | What the interviewer is checking |
|---|---|---|
| Develop plans with objectives, funding, schedules and staff | "How would you plan a program with five teams and one launch date?" | Dependencies, milestones and a named owner for each piece |
| Communicate with stakeholders to set requirements | "Tell me about stakeholders who wanted different things." | How you found the shared goal and settled the conflict |
| Monitor milestones and deliverables | "How do you know a program is off track before it's late?" | Early warning signs, beyond a status colour |
| Propose, review and approve changes to plans | "Walk me through a scope change you handled." | A clear change process and a written record of the decision |
| Monitor costs to stay within budget | "Your program is 15 percent over budget. What do you do?" | Facts first, then options, then who decides |
| Report status to managers | "How do you report status to executives?" | Short, honest updates with risks and clear asks |
| Achieve benefits and advance outcomes | "How would you know this program worked a year later?" | Outcomes measured after delivery, beyond shipping on time |
Which behavioral questions should you expect?
Behavioral questions ask for real stories from past programs, told in STAR order: situation, task, action, result. Interviewers listen for how you got teams that don't report to you to move together, how you spotted trouble early, and what happened to the goal. A story that only lists meetings and status reports tends to score low.
The STAR method guide covers the structure. The page on influence without authority fits here too, because most program managers lead people they don't manage.
1. Tell me about a program you led across several teams.
What they listen for: the shared goal, how you mapped who depended on whom, and one decision that kept the program on course. Name your own part clearly, separate from what each team did.
Made-up example answer. Situation: our company was moving customer billing from an old system to a new one, and four teams each owned a piece. Task: I was the program manager, and none of the four leads reported to me. Action: in the first two weeks I mapped every handoff between the teams on one page and agreed a single cutover date with all four leads. I set a weekly 30-minute review that covered only the risks and the next two milestones. When the data team found that old invoices needed cleaning first, I moved that work earlier and pushed a lower-priority report to after launch. Result: we cut over on the agreed date with no billing outage, and the delayed report shipped three weeks later.
2. Tell me about a program that slipped.
What they listen for: when you first saw the warning signs, who you told and how fast, and what you changed in your planning afterwards. The page on what to say about a missed deadline has a structure for this.
3. Describe a conflict between two teams over people or budget.
What they listen for: how you put both sides' facts on the table, tied the choice back to the program goal, and took it to the right person when you couldn't settle it yourself.
4. Tell me about a time you gave an executive bad news.
What they listen for: speed, a clear statement of the problem, options with their costs, and a recommendation. Waiting for a fix before telling anyone is the answer that hurts most.
What role-specific program manager questions come up?
Role-specific questions test how you would run a program: setting it up, managing dependencies and risk, handling change and measuring benefits. Interviewers check that you start with the goal, name owners and dates, and say how you would know things are going wrong. Listing tools without saying how you use them rarely helps.
5. You inherit a new program on Monday. What do you do in the first 30 days?
What they listen for: learning the goal and the sponsor's view of success, meeting each team lead, building a map of dependencies and risks, and agreeing how decisions and changes will be made.
Made-up example of thinking out loud: "In week one I'd meet the sponsor to agree what success looks like, in a number if possible, and ask what worries them most. Then I'd meet each project lead and ask for their plan, their biggest risk and what they need from other teams. By the end of week two I'd have one page showing every dependency and its owner. By day 30 I'd want an agreed milestone plan, a risk list with owners, and a simple rule for who approves changes."
6. How do you manage dependencies between projects?
What they listen for: a visible list of who needs what from whom and by when, a named owner on both sides of each handoff, and a habit of checking the riskiest ones every week.
7. How do you run risk management on a program?
What they listen for: a list of risks with an owner, how likely and how harmful each one is, what would trigger action, and what the action would be. Interviewers often ask for an example of a risk you closed before it happened.
8. When would you recommend stopping a project inside your program?
What they listen for: a link back to the goal. If a project no longer helps the program reach its benefits, or costs more than it returns, say so with numbers and let the sponsor decide.
9. How do you measure whether a program delivered its benefits?
What they listen for: measures agreed at the start, a baseline, a check after launch, and someone who owns the result once the program closes. The OMB memo ties program management to benefits and outcomes, so delivery alone is half an answer.
Which situational questions test judgment?
Situational questions describe a problem you have not faced yet and ask what you would do first. Interviewers look for an order of steps: get the facts, judge the effect on the goal, tell the people who need to know, then decide or escalate. Asking one or two clear questions before you answer often scores better than a fast plan.
The guide to situational interview questions explains the format.
10. A team your launch depends on announces a two-month delay.
What they listen for: confirming the facts and the cause, measuring the effect on the launch, finding options, and bringing a recommendation to the sponsor quickly.
Made-up example answer: "First I'd meet that team's lead to understand why, and whether any part of their work could arrive on time. Then I'd check which other projects depend on it and what the delay does to our launch date. I'd look for options, such as launching without that piece, adding people, or moving the date. Within a day or two I'd bring the sponsor those options with their costs and my recommendation, and update everyone affected once we decided."
11. The executive sponsor changes the program's goal halfway through.
What they listen for: understanding why, showing what the change does to scope, cost and dates, and getting the new goal agreed and written down before teams change direction.
12. Every project reports green, yet you suspect the program is in trouble.
What they listen for: checking evidence beyond the status report, such as milestones actually met and open risks. Then talking to the leads directly and raising the concern early. The guide to competing priorities helps when the trouble is too much work for too few people.
What follow-up questions tend to come next?
Follow-ups test whether your answer survives a change. Expect the interviewer to remove your best option, cut your budget, or ask how you would explain the choice to an executive in two minutes. Prepare by asking yourself what you would do if your first plan were blocked, and keep a second option ready.
- "What would you do if the sponsor refused to move the date?"
- "Which of those risks actually happened, and what did it cost?"
- "How did you get the team leads to agree?"
- "What did you decide yourself, and what did you escalate?"
How should you prepare for a program manager interview?
Write four or five STAR stories about real programs or large projects, including one that slipped. For each, note the goal, the teams involved, one hard decision and the result. Read the posting again and mark which duties it stresses, such as budget, vendors or executive reporting, then match a story to each one.
The free interview question generator lets you paste the job and pick the round, and it returns likely questions, why they come up, and what the interviewer listens for. Program managers often compete with or work beside related roles, so the pages for project manager, technical program manager and operations manager interviews are worth a read.
Prept's Mock room lets you practise these answers out loud on a clock, scores each answer out of 10 and checks it against your resume. It is included in the free plan.