Project manager interview questions and how to answer them
Questions on the skills open project 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 87 open project 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 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 29 of 87 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.
02 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 22 of 87 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.
03 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 18 of 87 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.
04 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 14 of 87 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.
05 Describe a sprint that went wrong. What did the team learn, and what was your part?
Why this question: Scrum is mentioned in 13 of 87 listings.
What the interviewer is checking. Whether you understand Scrum’s roles and events well enough to use them to recover, and whether you take your share of responsibility.
Answer outline (STAR)
Situation.[The team, the sprint goal and what went wrong, e.g. scope added mid-sprint or a blocked dependency].
Task.[Your role in the team and in the sprint].
Action.[What you did during the sprint and what came out of the retrospective].
Result.[What changed in later sprints]. If there is no number you can support, say what changed as a result or what you learned.
06 Tell me about documentation you wrote in Confluence that other people actually used. How did you keep it current?
Why this question: Confluence is mentioned in 12 of 87 listings.
What the interviewer is checking. Whether you write for a reader, organise information so it can be found, and take ownership of keeping it accurate.
Answer outline (STAR)
Situation.[The topic and the readers, e.g. new joiners, another team or on-call engineers].
Task.[Why the documentation was needed and what was missing before].
Action.[How you structured and wrote it, and the habit or process that kept it up to date].
Result.[How you know it was used, e.g. fewer repeated questions or a smoother handover]. If there is no number you can support, say what changed as a result or what you learned.
07 Walk me through work you did on Azure. How did you handle identity, access and environments?
Why this question: Azure is mentioned in 11 of 87 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.
08 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 8 of 87 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.
Questions about the core work of a project manager
These follow from the work the role title describes, not from a count of listings.
09 Walk me through how you planned a project from the start: scope, schedule, budget and risks.
What the interviewer is checking. Your planning discipline and whether you adapt a method to the project rather than following a template blindly.
Answer outline (STAR)
Situation. Describe the project: [its purpose, size, the team, and the method you used, e.g. waterfall, agile or hybrid].
Task. State what you were responsible for: [e.g. the plan, the budget, delivery to a fixed date].
Action. Explain how you defined scope [e.g. with the sponsor and a work breakdown], built the schedule [estimates and the critical path], set the budget, and recorded risks [your risk log and owners].
Result. Give a result you can support [delivered on time, within budget, or the variance you can explain]. If it did not go to plan, say what the plan helped you control.
10 Tell me about a time the scope of a project kept growing. How did you handle it?
What the interviewer is checking. Whether you can control scope through a clear change process, and how you protect the schedule and budget while keeping the sponsor on side.
Answer outline (STAR)
Situation. Describe the project and where the extra requests came from: [who asked and what they wanted added].
Task. Say what you were accountable for: [e.g. the agreed scope, budget or deadline].
Action. Explain your actions [how you assessed each change for time and cost, the change request or approval route you used, and how you discussed trade-offs with the sponsor].
Result. Share the result you can support [what was added, deferred or refused, and the effect on delivery]. If scope still grew, say what you now agree at the start.
11 Describe a project that was running late. How did you bring it back under control?
What the interviewer is checking. Your ability to diagnose the real cause of a delay, re-plan realistically and communicate honestly to stakeholders.
Answer outline (STAR)
Situation. Describe the project and how far behind it was: [the original date, the size of the slip, and how you noticed].
Task. State what you had to protect: [e.g. a regulatory deadline, a launch, a client commitment].
Action. Explain what you did [how you found the cause, the recovery options you considered such as re-sequencing work or reducing scope, and how you told stakeholders].
Result. Give the result you can support [the revised delivery and how it compared to the new plan]. If it still finished late, say what you learned about early warning signs.
12 How do you handle a team member or supplier who is repeatedly missing their commitments?
What the interviewer is checking. Whether you address performance problems directly and early, find out the cause, and escalate fairly when needed.
Answer outline (STAR)
Situation. Describe the situation: [their role, what they kept missing, and the effect on the project].
Task. Say what you needed to achieve: [e.g. reliable delivery of their part without harming the relationship].
Action. Explain your steps [the conversation you had, what you learned about the cause, the support or changes you agreed, and when you escalated if it continued].
Result. Share the result you can support [whether delivery improved and how you know]. If it did not, say how you protected the project.
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 project 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.