In this article
- Start here: the learning path
- What is the difference between a project manager and a program manager?
- How are project, program and technical program roles asked about?
- Scrum master interview questions: what to know
- Agile questions: what do the principles say?
- Stakeholder and leadership communication questions
- Technical program manager interview questions
- Prioritisation frameworks: how do you choose between projects?
- Program manager scenario questions
- Questions interviewers ask on project and program management
- What does the job market look like for project management?
- All 8 guides in Program, project and agile
- Follow-up questions
- Sources
Start here: the learning path
- Project
- A project is a temporary piece of work with a defined goal, a schedule and a budget, which ends when its goal is delivered or abandoned.
- Program
- A program is a group of related projects managed together so the combined result is greater than managing each one alone; definitions vary by organisation, and this guide uses this common one.
- Technical program manager
- A technical program manager (TPM) is a program manager for engineering work who understands the systems involved well enough to find technical dependencies and risks, and who coordinates teams without owning the design.
- Scrum
- Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions, as the Scrum Guide defines it, built around fixed-length Sprints.
- Sprint
- A Sprint is a fixed-length Scrum event of one month or less in which a team turns selected work into a usable increment.
Follow this order. Each step adds one theme that interviewers probe.
- Read this page for the role, the vocabulary and the shape of the questions.
- Practise short answers on scope, schedule, risk and people, the entry-level themes in interview questions for a project manager.
- Learn Scrum and agile roles in the Scrum Master section below.
- Practise stakeholder and leadership communication.
- Learn the technical program manager scope.
- Practise prioritisation frameworks, then program manager scenario questions.
Text description of the diagram
- Program manager interviews probe six areas: project delivery, Scrum and agile, stakeholders, technical programs, prioritisation and scenarios.
- A program manager is accountable for the outcome of several related projects.
- Interview questions for Scrum masters on events, artifacts and team situations
- How do you answer prioritisation framework questions as a TPM?
- How do you answer program manager scenario questions?
- How do you answer stakeholder and leadership communication questions?
- Technical program manager interview questions and answers
What is the difference between a project manager and a program manager?
A project manager is accountable for delivering one project to its goal, schedule and budget, while a program manager is accountable for the outcome of several related projects. The U.S. Bureau of Labor Statistics describes project management specialists as people who "coordinate the budget, schedule, staffing, and other details of a project" (Bureau of Labor Statistics, last modified August 2026). The U.K. government's delivery standard treats portfolios, programmes and projects as three related levels of management in one standard (U.K. Government, updated September 2025). Boundaries differ by company, so in an interview ask which level the role owns and say which you have done.
Knowing it is half the job. Saying it is the other half.
Interview Clozo is an AI interview copilot for real interview rounds: it hears the question and puts a strong answer on your screen, and you say it in your own words. See the features or how it works.
Start Free Trial →How are project, program and technical program roles asked about?
In a structured interview, interviewers use the same two question types for all three roles. The U.S. Office of Personnel Management describes a structured interview as one that probes past behavior, likely behavior in hypothetical scenarios, or both, with every candidate asked the same questions and scored on the same rating scale (Office of Personnel Management). In practice, a project manager is asked about a project they delivered. A program manager is asked how you would sequence dependent projects, and a technical program manager is also asked to reason about a system. Learn the method in how to answer interview questions and the situation, task, action, result structure in behavioral interviews.
Scrum master interview questions: what to know
A Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide, and the guide calls Scrum Masters "true leaders who serve the Scrum Team and the larger organization" (2020 Scrum Guide). Know the three accountabilities: the Product Owner maximises the value of the product, the Developers create a usable increment each Sprint, and the Scrum Master establishes the framework. Know the events and their limits: a Sprint of one month or less, a Daily Scrum of 15 minutes, and Sprint Planning, Review and Retrospective capped at eight, four and three hours for a one-month Sprint.
| Event | Maximum for a one-month Sprint |
|---|---|
| Sprint Planning | 8 hours |
| Sprint Review | 4 hours |
| Sprint Retrospective | 3 hours |
| Daily Scrum | 15 minutes, each working day |
Agile questions: what do the principles say?
The Agile Manifesto's principles are the usual source of "what does agile mean" questions. They ask for working software delivered frequently, "from a couple of weeks to a couple of months, with a preference to the shorter timescale". They also say that "working software is the primary measure of progress" and that "at regular intervals, the team reflects on how to become more effective" (Agile Manifesto principles). A good interview answer names a principle and then a practice that carries it out: short iterations, a demo of working output and a regular retrospective. Mention what you changed after a retrospective, because the question is usually a test of follow-through, not recall.
Stakeholder and leadership communication questions
Stakeholder questions ask how you keep people informed, aligned and honest about bad news. A stakeholder is anyone who is affected by the work or can affect it, and a program has many of them across teams. A strong answer names the audience, the message and the rhythm: what each group needs to decide, how often they hear from you, and how you escalate a risk before it becomes a date change. Use one real example, lead with the conclusion and end on what changed. Typical questions, with what each tests:
- "How do you report that a project is off track to an executive?" Tests whether you give the facts, cause and a recovery option early.
- "Tell me about a time you disagreed with a senior stakeholder." Tests influence without authority.
- "How do you keep ten teams aligned on one outcome?" Tests rhythm and clear ownership. A short tell me about yourself answer sets the tone for these.
Technical program manager interview questions
A technical program manager is asked everything a program manager is asked plus technical reasoning, so the extra preparation is systems vocabulary. Scope varies a great deal between employers, and some job descriptions stress engineering depth while others stress planning and reporting, so read the posting before choosing what to rehearse. Be ready to explain a system you coordinated work on, how you found a dependency between two teams, and how you would plan a migration or a launch with a hard date. You are not expected to design the system, but you are expected to ask the questions that surface its risks. Typical questions:
- "How do you find a dependency across teams?" Tests whether you map work, not just ask for updates.
- "Walk me through planning a migration with a hard date." Tests sequencing and a plan for undoing the change if it fails.
- "Explain a system you coordinated to a non-engineer." Tests plain language. System design practice helps with the vocabulary.
Prioritisation frameworks: how do you choose between projects?
Prioritisation questions ask how you decide what to do first when everything is urgent. The answer is a method, not a framework name: state the goal, score each option on impact and effort or on the cost of delaying it, and say who has the final decision.
Frameworks such as weighted scoring (adding up scores against agreed criteria) and impact-versus-effort grids (plotting each option by value and cost) make the trade-off visible to others; none of them replaces agreeing the criteria with stakeholders first. Say what you would do when two items score the same, and what you would do when a senior person overrides the order. Give a number where you can, such as how long an item delays a launch. Typical questions:
- "Decide what to cut when three projects need the same team." Tests criteria and trade-offs.
- "How do you measure program success?" Tests outcomes over activity.
- "A senior person overrides your order. What now?" Tests escalation and whether you can carry out a decision you argued against.
Program manager scenario questions
Scenario questions are hypothetical: a dependency slips, two teams disagree, a launch date is fixed and scope grows. The Office of Personnel Management notes that structured interviews score hypothetical answers on the same scale as behavioral ones, so structure matters (Office of Personnel Management). A workable shape is: clarify the facts, state the decision you would make and why, name the risk that remains, and say who you would tell. Ask one clarifying question before answering, as you would in a real situation. Typical questions:
- "A dependency slips and the launch date is fixed. What do you do?" Tests the clarify-decide-inform shape.
- "Two teams disagree on scope. How do you resolve it?" Tests facilitation and decision rights. Practise answering out loud.
Questions interviewers ask on project and program management
What do you do when a project falls behind schedule?
Find the cause first, then offer options: cut scope, add time or move resources, with the cost of each. Tell the sponsor early with a recommendation, not only the problem, and say how you will know the recovery is working.
How do you handle scope creep?
Compare each request with the agreed goal, state what it would cost in time and money, and let the person who owns the priorities decide what to trade. Record the decision so the change is visible to everyone.
How do you manage risk across a program?
Keep one shared list of risks across all projects, with an owner and a next step for each. Look first for risks that touch more than one team, because those are the ones a single project manager cannot see.
How do you handle a dependency on another team?
Name the dependency, agree a date and an owner with the other team, and check in before the date, not after. If it slips, say which downstream work moves and who must hear about it.
How do you measure program success?
Measure the outcome the program was created for, such as revenue, adoption or cost saved, and not only on-time delivery of its projects. Agree the measure with the sponsor at the start.
For a round-by-round view, interview loops explains how these questions are spread across interviews, and questions to ask the interviewer covers the other side of the table.
What does the job market look like for project management?
The Bureau of Labor Statistics projects employment of project management specialists to grow 7% from 2025 to 2035, much faster than the average for all occupations, and lists a bachelor's degree as the typical entry-level education (Bureau of Labor Statistics, last modified August 2026). That figure covers the specialist occupation as the agency defines it, not every program or technical program role, so treat it as context and not as a forecast for your target job.
Follow-up questions
Who owns what in project and program work?
A project manager delivers one project to its goal, schedule and budget; a program manager owns the combined outcome of related projects.
What does a technical program manager do?
A technical program manager coordinates engineering work across teams and is expected to reason about the systems involved; scope differs by employer, so read the posting.
What does a Scrum Master do?
A Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide and serves the team and the wider organisation (2020 Scrum Guide).
How do you prioritise competing projects?
State the goal, score options on impact and effort or cost of delay, agree the criteria with stakeholders and say who decides, as the prioritisation section describes.
How should I answer a program manager scenario question?
Clarify the facts, state the decision and its reason, name the remaining risk and say who you would tell; practise it aloud using how to answer interview questions.
- A program manager owns the combined outcome of related projects.
- Structured interviews ask about past behavior and hypothetical scenarios, scored on the same scale.
- Scrum caps its events: 15 minutes daily and hours per Sprint event.
- A prioritisation answer is a method with stated criteria and a named decider.
- Read the posting to learn what the technical program manager role covers at that employer.
Sources
- The 2020 Scrum Guide — Ken Schwaber and Jeff Sutherland (ScrumGuides.org), 1 Nov 2020
- Principles behind the Agile Manifesto (undated page, read 2026-10-24) — agilemanifesto.org, 24 Oct 2026
- Project Management Specialists, Occupational Outlook Handbook — U.S. Bureau of Labor Statistics, 27 Aug 2026
- Government Functional Standard GovS 002: Project delivery — U.K. Government, 17 Sep 2025
- Structured Interviews (undated page, read 2026-10-24) — U.S. Office of Personnel Management, 24 Oct 2026
