Project manager situational interview questions
The short answer
Situational questions for a project manager start with "what would you do if" and put pressure on the baseline: a sponsor adds a feature after it is approved, a vendor misses a milestone and promises to catch up, a key person resigns two months before delivery, a status report would turn red for the first time. Interviewers listen for whether you go back to the plan before you act, size the change, and hand the scope, date or cost decision to the sponsor in writing. Strong answers often end with a short example from a project you ran.
Practice these questions in Claude with Interview Coach, free
How a project manager's situational answer is judged
For a project manager the scene is usually a change to the plan, so hiring managers often listen for the baseline: what was agreed, what the change does to scope, date and cost, and who has the authority to accept it. An answer that absorbs the change quietly to keep the sponsor happy, or moves the date without asking, tends to land worse than one that sizes the change first and puts the options in front of the person who owns the decision.
The second thing heard is how you deliver a bad number. Many situational questions are really about a status that will disappoint someone. Say when you would tell the sponsor, what the report would say and which plan goes with it, then close with a project where you did that, and the change request or the steering minutes that record it.
- Go back to the baseline. What was approved, by whom and when. A change only has a size against the plan it changes.
- Size it before you answer. Days, cost and the features it pushes out. A sized change turns a demand into a choice.
- Hand the choice to the sponsor. You give the options; the sponsor picks scope, date or cost, in writing.
- Finish with your own project. One or two sentences, with the change request or the status report that shows what happened.
How to use these questions
Under each question is what a hiring manager usually listens for. A project story is only as good as the plan it is measured against, so for each one find the record first: the baseline, the risk log entry with its date, the change request with its signature. Then say what you saw, what you did and when, whom you told, and where the result shows.
Scope and plan scenes
Walk me through a scope change request you handled. How did you decide, and who approved it?
In the Interview Coach question bank
Listen for: the request, the options you gave, who approved the change and what it cost, and that the change request and the decision are on record.
The sponsor adds a feature after the baseline is approved and says the date cannot move. What do you do?
Listen for: that you size the feature, show the choices of date, cost or scope, and ask the sponsor to choose, in writing.
Two teams give you different dates for the same milestone. What do you do?
Listen for: that you find the assumptions behind each date, test them with the team leads, and give the sponsor one date with a range.
Risk and vendor scenes
Tell me about a risk you saw early. What did you do before it became an issue?
In the Interview Coach question bank
Listen for: the risk, how early you saw it, what you did before it became an issue, and what did not happen as a result.
A vendor misses a milestone and says it will catch up. What do you do?
Listen for: that you ask for the evidence of catching up, escalate on both sides if there is none, and prepare the sponsor's options.
A key team member resigns two months before delivery. What do you do?
Listen for: that you look at what only that person knows, plan the handover first, and tell the sponsor the effect on the date the same week.
Communication scenes
Your status report would be red for the first time. The sponsor prefers amber. What do you do?
Listen for: that the report says red with the reason and the plan, and that you brief the sponsor before it lands.
Tell me about a time you disagreed with a senior stakeholder. What did you do, and how did it end?
In the Interview Coach question bank
Listen for: the disagreement stated fairly, what you did to move it, and how it ended.
A stakeholder who does not report to you keeps missing reviews. What do you do?
Listen for: that you ask what is in the way, make the cost of the delay visible, and go to their manager only after you have told them.
Closing
Tell me about the last time you were wrong about a date. What did you change?
Listen for: the date you gave, the gap, how you told the sponsor, and the change in method since.
Answers as written, and what the check says
Illustrative, not a real client. Each answer below replies to the question Interview Coach asks as "Walk me through a scope change request you handled. How did you decide, and who approved it?" and was sent on its own through the answer check. All four are also marked short for a spoken answer, because each is one or two sentences; the table shows the other finding, word for word, and one way to fix it.
| Answer as written | What the check says | What to change |
|---|---|---|
| When the sponsor asked for a new report in the portal after the plan was set, the report was sized with the lead developer and three options were put on one page for the sponsor, and the sponsor agreed to release two and the first release shipped on its date, per the change request. | No sentence says what you did yourself, with I. | Say which of these steps were yours, with I. |
| When the sponsor asked for a report after baseline, we sized it, we re-planned, we updated the backlog, we retested and we briefed the users. I sized it with the developer and I put three options on a page, and the sponsor agreed to release two, per the change request. | Mostly we and the team. The interviewer cannot tell which part was yours. | Give the team's work one sentence, then say which calls were yours. |
| I sized the report with the lead developer in two days and I put three options on one page for the sponsor, and the sponsor agreed to release two and the first release shipped on its date, per the change request. | No context is set before the action. Add what was at stake. | Open with what was at stake before you acted. |
| When the sponsor asked for a new report in the portal after the plan was set, I sized the report with the lead developer in two days and I put three options on one page for the sponsor, per the change request. | No result is named. Say what changed. | Say what changed in the end, and where it shows. |
The check never adds a figure or an approver for you. If the sponsor chose to move the date, say so, and say what the record shows about why.
An illustrative answer
Illustrative, not a real client. Every figure is invented. This answer to the same question gets all nine marks of the decision check: length, situation, own action, team versus me, result, evidence, and no vague words, filler or hedges.
When I ran a customer portal project for a utilities company, the sponsor asked for a new usage report after the baseline was approved, and said the launch date could not move. The options were the report in the first release with two features dropped, the report in a second release six weeks later, or the report in the first release with a later date. I sized the report with the lead developer within two days, and I put the three options on one page with the cost and the risk of each. I took the page to the sponsor myself and I asked for a choice in writing, because the date and the scope could not both stay. The sponsor chose the second release, and the first release launched on its date, per the change request and the steering minutes. The report shipped in the second release, and support calls about usage went from sixty a month to twenty, per the support dashboard.
Why it works. The request and the sponsor's constraint are stated. The options are named with their cost. The actions are the speaker's own and the choice sits with the sponsor, on record. The result is tied to named records and a before and after pair.
Choosing your stories
- Keep a change request story ready. Scope, vendor and staffing scenes all lead back to one. Prepare it, then use it to close your answer.
- Pick cases where you stayed in role. You sized it, put the options in front of the sponsor and asked for a choice. The sponsor chose.
- Pick one date you got wrong. Interviewers often ask what you would do differently. A forecast that missed, and what you changed in your estimates, says more than a hypothetical regret.
Your resume is where an interviewer picks these stories from, and a line such as "managed projects on time and on budget" invites the hardest version of these questions. Get a free AI review of your resume and see which lines Reed flags first.
Practice these with Interview Coach in Claude
Interview Coach asks the project manager track of its question bank. A situational answer lands best when it closes with a project where you sized a change for the sponsor; write that story the way you would say it and ask for a check.
- Paste your resume and the job posting. Interview Coach returns the lines a hiring manager is likely to ask about, each as a question that quotes your own line, with the points a strong answer covers.
- It matches the requirements of the posting to your resume and turns the gaps into questions to prepare.
- Write one answer at a time and ask for a check. It looks for a situation, your own action, a result and a before and after figure or a named record. It does not judge whether the story is true.
Your answers start from your resume. The free review quotes your own lines and flags the 5 to fix first, so you know which lines an interviewer may question.
Free in Claude, no account. We do not store the text you send through it.
Questions
Should I answer a situational question with a story from my past?
Yes, once you have said what you would check in the plan and who owns the decision. For a project manager the best closing story has a record behind it, a change request, a revised baseline or a status report, so the interviewer hears the judgment and then sees the evidence.
What if I have never faced the situation described?
Say so, then reason from the plan: what the baseline says, what the change would cost, who signs it off. A project manager who walks the plan out loud shows the habit the question is testing, and saying plainly that you have not faced it is a fair way to begin.
Does Interview Coach know whether my story is true?
No. Interview Coach runs in Claude and checks the structure of an answer by fixed rules: a situation, your own action, a result, a figure or a record. It does not judge whether the story is true or good, and it never adds a figure you did not give. You decide what to say.
Keep going
- Role hub: Project manager resume and career help
- All questions: Project manager interview questions
- Same role: Project manager interview questions in healthcare
- Same role: Project manager interview questions in fintech and banking
- Same role: Project manager behavioral interview questions
- Resume guide: Project manager resume guide
- Guide: AI resume review: what Reed checks
Last updated: October 15, 2026