Project manager interview questions
The short answer
A project manager interview checks whether the results on your resume hold up when someone asks how they happened. Expect questions about a project you brought back on track, a scope change you handled, a risk you acted on and a stakeholder you moved. In each answer the hiring manager listens for the plan you were measured against, the part you did yourself, and where the result was recorded.
Practice these questions in Claude with Interview Coach, free
How to use these questions
Each question below comes with what a hiring manager usually listens for. Prepare one real story per question from your own record: the plan, the status reports, the change log, the sign-off email. A story answer works best in four parts: the situation in two or three sentences, what you did yourself, what changed, and how you know. Spoken, that is about one to two minutes. If you have not done what a question asks, say so plainly and give the closest example.
Behavioral questions
Tell me about a project that was off track when you took it over. How did you bring it back?
In the Interview Coach question bank
Listen for: the state you found, stated from the plan of record (schedule, budget or scope), the first actions you took yourself, and the state at close against the re-approved plan. A re-baseline you name openly reads better than a recovery that sounds effortless.
Tell me about a project or a decision that did not go to plan. What was your part in it?
In the Interview Coach question bank
Listen for: your own part in what went wrong, without blaming the vendor or the sponsor, what you did once you saw it, and one habit you changed since. Pick a real miss, not a strength in disguise.
Tell me about the hardest deadline you have worked to. What did you cut, and who agreed?
In the Interview Coach question bank
Listen for: why the date could not move, the trade-off you proposed, who approved it, and what was left for a later release. The interviewer wants to hear a cut that someone signed off, not overtime.
Tell me about a time you had to give a sponsor bad news about your project.
Listen for: how early you raised it, what you brought with the news (options, impact on date and cost, a recommendation) and what the sponsor decided. Waiting for certainty before telling anyone is the answer they hope not to hear.
Situational questions
Your status report says green, but two workstream leads tell you privately they will miss the next milestone. What do you do this week?
Listen for: that you check the plan and the work, not the report; that you talk to the leads and reforecast; and that you change the status and raise it with options before the milestone, not after it.
A sponsor asks for one more feature two weeks before go-live. Walk me through your response.
Listen for: an impact check on time, cost and risk before any yes or no, the change control route, who decides, and how the decision is recorded. A good answer protects the go-live without refusing the sponsor outright.
You inherit a project with no baseline and an unhappy client. What do you do first?
Listen for: listening before planning, an agreed baseline as an early goal, a clear view of who decides what, and one early result the client can see. Promising to fix everything at once is a warning sign.
A vendor misses a delivery that sits on the critical path. What happens next?
Listen for: what the contract allows, a re-sequenced plan, the conversation with the vendor's own manager, and who you inform and when. The interviewer is checking that you manage the vendor and not only report on it.
Project delivery questions
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 and who raised it, how you assessed the impact on time, cost and risk, the decision, the approver and where it was recorded. A change you turned down, with the reason, is a strong example.
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 early signal, what you proposed and to whom, and what the action avoided or cost. A risk that only sat in the RAID log is a duty, not a story.
Which method did you use on your last project, and what did you change about it for that team?
Listen for: a method inside the work, why it fit that team and that client, and one thing you adapted. A list of methods with no effect on how the work ran tells the interviewer little.
How did you build the schedule on your last project, and who signed it off?
Listen for: where the estimates came from, the dependencies and the critical path, the contingency you held, and who approved the baseline. "We used the template" is not an answer.
Stakeholder questions
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: what each side wanted, what you did yourself to move it, and how it ended, including any part that did not go your way.
Tell me about two stakeholders who wanted opposite things on one project. How was it settled?
Listen for: the decision you helped reach, who made it, and what happened next. "I managed stakeholders" with no decision in it is the weak version.
Who had to say yes for your last project to go ahead, and how did you get that yes?
Listen for: the approvers by role, what each needed to see, and the document or forum where the yes was given.
Tell me about a time you had to get people to act when they did not report to you.
In the Interview Coach question bank
Listen for: who had to act and why they had no reason to, the steps you took (data, a trade, an escalation) and what they did in the end.
Metrics and evidence questions
Your resume says the project finished on time and on budget. Against which baseline, and how many changes were approved along the way?
Listen for: the approved date and budget, the number of re-baselines, and who approved each one. "On time against the re-approved plan, after one approved change" is a better answer than an unconditional claim.
How did you report status, and how did you know the status was true?
Listen for: the sources behind the colours (plan, burn, defect counts, acceptance), and one time you changed a status because the work said something the report did not.
What was different when you left that project, compared with when you arrived?
Listen for: one specific change and the record that shows it, then which part of it was yours and which part belonged to others.
How many people were on your team, and who reported to you directly?
Listen for: a clear split between direct reports and people you led without authority. "A team of 25" is read as 25 direct reports unless you say otherwise.
Practice these with Interview Coach in Claude
Interview Coach has a project manager track. The questions marked above as in its bank come from it, and it adds questions that quote your own resume lines and the requirements of the posting.
- 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.
Resources
Your answers start from your resume. The resume guide for this role shows how to write each line so you can back it up.
- Resume guide: Project manager resume guide
- Related resume guide: IT project manager resume guide
- Related resume guide: PMP on a resume
Questions
What do hiring managers listen for in project manager interview answers?
They listen for the plan you were measured against, the part you did yourself and the record behind the result. Most follow-up questions test one of those three. An answer that names the baseline, uses "I" for your own actions and points to a report or a sign-off holds up.
How do I answer a question about a project that was late?
Say it was late, by how much against which plan, and why. Then say what you did once you saw it and what you do differently since. Interviewers expect late projects. They listen for whether you saw it early and told the right people.
Should I mention my PMP in the interview?
If you hold it, it is already on your resume. In the interview, show the practice instead: how you handled scope, risk and change on a real project. Mention the credential only when it answers the question. Your PMP status needs to match what the issuer's record shows.
Keep going
- Role hub: Project manager resume and career help
- Guide: 10-question resume self-check
- Related: Program manager interview questions
- Related: Delivery manager interview questions
- Related: Scrum master interview questions
- Guide: AI resume review: what Reed checks
Last updated: October 13, 2026