Program manager interview questions and how to answer them
Questions on the skills open program manager listings mention and on the core work of the role. For each: what the interviewer is checking, and a STAR answer outline with placeholders for your own example.
Based on 233 open program manager listings on ROLIVA as of . Each question below is about a term from ROLIVA’s skills vocabulary that appears in at least two of these listings, most-mentioned first.
01 How have you used Jira to keep a piece of work visible and on track? Tell me about a time the board did not match reality.
Why this question: Jira is mentioned in 42 of 233 listings.
What the interviewer is checking. Whether you use the tool to support delivery rather than for its own sake, and whether you notice and fix it when tickets drift from the real state of the work.
Answer outline (STAR)
Situation.[The team, the work and how it was tracked in Jira].
Task.[What went wrong or what you were responsible for, e.g. a board everyone had stopped trusting].
Action.[What you changed, e.g. clearer ticket definitions, a workflow fix or a regular review, and how you got the team to adopt it].
Result.[Whether status became reliable and what decisions it supported]. If there is no number you can support, say what changed as a result or what you learned.
02 Describe something you built or ran on AWS. Which services did you choose, and what went wrong at some point?
Why this question: AWS is mentioned in 39 of 233 listings.
What the interviewer is checking. Whether you understand the trade-offs behind the services you used, including security, cost and failure modes, rather than just naming them.
Answer outline (STAR)
Situation.[The system and what it did, e.g. an API, a data pipeline or a batch job].
Task.[Your part in building or operating it].
Action.[The services you used and why, how you handled permissions and cost, and how you dealt with the failure].
Result.[How the system ran afterwards and what you changed to prevent a repeat]. If there is no number you can support, say what changed as a result or what you learned.
03 Tell me about a time an Agile way of working was not helping your team. What did you change?
Why this question: Agile is mentioned in 36 of 233 listings.
What the interviewer is checking. Whether you understand the purpose behind Agile practices and adapt them to the team, rather than following ceremonies for their own sake.
Answer outline (STAR)
Situation.[The team and the practice that was not working, e.g. planning that never matched delivery].
Task.[What you were responsible for or chose to take on].
Action.[What you noticed, what you proposed, and how the team agreed to try it].
Result.[What changed in delivery or in how the team worked]. If there is no number you can support, say what changed as a result or what you learned.
04 Tell me about a stakeholder who disagreed with you or your team. How did you handle it?
Why this question: Stakeholder management is mentioned in 34 of 233 listings.
What the interviewer is checking. Whether you can understand another person’s interests, disagree constructively, and reach a decision without damaging the relationship.
Answer outline (STAR)
Situation.[The stakeholder’s role, what they wanted and why it conflicted with the plan].
Task.[What you were responsible for deciding or delivering].
Action.[How you understood their concern, the options you put forward, and how the decision was made].
Result.[The outcome and the state of the relationship afterwards]. If there is no number you can support, say what changed as a result or what you learned.
05 Tell me about a go-to-market launch you were part of. How did you decide on the audience and the message, and how did you judge whether it worked?
Why this question: Go-to-market is mentioned in 32 of 233 listings.
What the interviewer is checking. Whether you connect positioning, audience, channels and sales readiness into one plan, and measure the launch against goals set in advance.
Answer outline (STAR)
Situation.[The product or feature, the target audience and the goal of the launch].
Task.[Your part, e.g. positioning, sales enablement, channels or pricing input].
Action.[How you chose the audience and message, who you worked with, and what you measured].
Result.[What the launch achieved against its goals, and what you would change]. If there is no number you can support, say what changed as a result or what you learned.
06 Walk me through work you did on Azure. How did you handle identity, access and environments?
Why this question: Azure is mentioned in 28 of 233 listings.
What the interviewer is checking. Whether you can work safely in a cloud platform: least-privilege access, separate environments, and repeatable deployment instead of manual changes.
Answer outline (STAR)
Situation.[The system or migration and the Azure services involved].
Task.[What you were responsible for and the constraint, e.g. a compliance requirement].
Action.[How you set up access, environments and deployment, and any problem you solved along the way].
Result.[The result, e.g. a successful migration or fewer manual changes]. If there is no number you can support, say what changed as a result or what you learned.
07 Describe a spreadsheet you built that people used to make a decision. How did you stop it from giving a wrong answer?
Why this question: Excel is mentioned in 22 of 233 listings.
What the interviewer is checking. Whether you can build a model or analysis others can follow, and whether you control errors: clear inputs, consistent formulas and checks against known figures.
Answer outline (STAR)
Situation.[The decision, the people making it and the data the spreadsheet held].
Task.[What the spreadsheet had to calculate or show, and how often it would be updated].
Action.[How you structured it, e.g. separate input and calculation sheets, lookups or pivot tables, and the checks you added].
Result.[The decision it informed and any error you caught before it mattered]. If there is no number you can support, say what changed as a result or what you learned.
08 Tell me about a system you built or operated on Google Cloud. How did you decide between the managed services available?
Why this question: GCP is mentioned in 19 of 233 listings.
What the interviewer is checking. Whether you choose services for a reason (operational effort, cost, scale, team skills) and understand what you gave up.
Answer outline (STAR)
Situation.[The workload and its requirements, e.g. traffic, data volume or latency].
Task.[The decision you had to make or the part you owned].
Action.[The options you compared, the one you chose, and how you set up access, monitoring and cost controls].
Result.[How it performed in use and anything you would choose differently]. If there is no number you can support, say what changed as a result or what you learned.
Questions about the core work of a program manager
These follow from the work the role title describes, not from a count of listings.
09 Tell me about a programme with many dependent teams. How did you keep the dependencies visible and managed?
What the interviewer is checking. Your ability to coordinate across teams you do not manage, find critical dependencies early and create a plan that teams actually use.
Answer outline (STAR)
Situation. Describe the programme: [its goal, the number of teams or workstreams, and the timeline].
Task. State your responsibility: [e.g. the integrated plan, dependency tracking, cross-team reporting].
Action. Explain how you mapped dependencies [the method or artefact you used], how you kept owners accountable [your regular check-ins or reviews], and how you raised risks [who you escalated to and when].
Result. Give a result you can support [e.g. milestones met, a dependency risk caught early]. If something still slipped, say what the visibility allowed you to do about it.
10 Describe a time a critical milestone was going to slip. What did you do?
What the interviewer is checking. Whether you spot slippage early, present options rather than just bad news, and communicate honestly to leadership.
Answer outline (STAR)
Situation. Describe the milestone and what was putting it at risk: [the cause, e.g. a vendor delay or a team capacity gap].
Task. Say what you had to do: [e.g. protect the launch date or reset expectations with leadership].
Action. Explain your actions [how you assessed the impact, the options you laid out such as scope changes, extra resources or a new date, and how you communicated the decision].
Result. Share the result you can support [what was delivered and when]. If the date moved, say how stakeholders responded and what you changed in planning.
11 How do you report programme status to senior leaders so that they can make decisions?
What the interviewer is checking. Whether your reporting is honest and decision-focused rather than a list of activity, and whether you can say "red" when it is red.
Answer outline (STAR)
Situation. Describe the audience and the programme: [who you reported to and what they needed to decide].
Task. State what the reporting had to achieve: [e.g. early warning of risks, approval of trade-offs].
Action. Explain the format and rhythm you used [e.g. a one-page weekly status with risks and decisions needed], and give one example where you escalated a problem [what you raised and what you asked for].
Result. Give a result you can support [e.g. a decision leadership made in time because of your report]. If your reporting changed after feedback, say how.
12 Tell me about a conflict between two teams over priorities or resources on your programme.
What the interviewer is checking. Influence without authority, fairness, and knowing when to resolve something yourself and when to escalate.
Answer outline (STAR)
Situation. Describe the two teams and what they disagreed about: [the resource or priority, and each team’s reason].
Task. Say what was at stake for the programme: [the milestone or outcome affected].
Action. Explain what you did [how you brought the facts together, the meeting or decision process you ran, and whether and how you escalated].
Result. Share the result you can support [the decision and its effect on delivery]. If it was not fully resolved, say what you would do earlier next time.
Using the outlines
One real example per answer. Replace every [bracketed] part with something you did and can talk about in detail.
Keep the situation short. Spend most of the answer on what you did and why.
Say “I” for your part. Name the team’s work as the team’s, and your own decisions as yours.
Results you can support. If there is no number, say what changed or what you learned. Never estimate a figure you cannot back up.
How these questions are chosen
Each open program manager listing’s description and stated skills are checked, on whole words, against the fixed skills vocabulary ROLIVA uses on its job pages, resume examples and monthly skills reports. A listing counts once per term. A mention is not a requirement, and the counts change as employers open and close roles. The questions and outlines are preparation prompts written for this role. They are not a record of what any employer has asked, and no employer’s process is described here.
Interview Studio prepares questions and STAR outlines for a real job from its description and the experience you have confirmed. No generative AI: when a detail is missing, it asks you instead of inventing one.