Project manager interview questions test whether you can run the three things every project is judged on, scope, schedule and budget, and the fourth thing that decides most outcomes, people. Interviewers want stories with numbers: the size of the budget, the length of the slip, the number of stakeholders, and what you did when the plan broke. Below are 40 project manager interview questions grouped by area (methodology, planning, risk, stakeholders, failure, tools), sample answers for the twelve most common, what changes for Agile and PMP-style interviews, and the questions to ask about the projects you would inherit.
The 12 most common project manager interview questions, with sample answers
Project manager interview questions and answers
One project, in order: goal and scope, budget and timeline, team size, the two biggest problems, the outcome with numbers. "A 12-country SAP rollout, 9M dollar budget, 20-person team, 18 months. The two problems were a vendor that missed its integration date and a scope request from finance in month nine. We delivered in 19 months at 5% under budget." Ninety seconds; they will ask about the problems.
"By making it visible and priced. Every request goes through a change log with impact on schedule, budget and risk; the sponsor decides with those numbers in front of them. On the SAP rollout, finance's month-nine request added three weeks and 140K dollars; the sponsor approved it, and it went into the baseline rather than being absorbed quietly."
Diagnose, re-plan, communicate. "Six weeks in, the vendor's integration was four weeks late. I re-sequenced testing to start on the modules we had, brought two contractors onto data migration, negotiated a partial delivery with the vendor, and told the steering committee the new date with the plan behind it. We recovered three of the four weeks."
"I ask the sponsor to rank, with the trade-offs made explicit: if A and B both ship on the date, quality or cost gives. If they will not rank, I rank by business value and risk, write it down, and ask them to correct it. A priority list that exists only in people's heads is how projects slip."
STAR, with the stakeholder's reason understood. "The head of operations blocked go-live because his team had not been trained. He was right. I moved training forward two weeks, gave his team a say in the cutover date, and he became the project's loudest supporter."
"A risk register that is actually used: identified at kickoff and every two weeks, each with a probability, an impact, an owner and a trigger. The top five are on the steering-committee slide every time. On my last project the register flagged the vendor's capacity three months before it became an issue, which is why we had contractors lined up."
"The one the work needs. Software and product work with uncertain requirements: Scrum or Kanban, two-week sprints, a backlog the product owner controls. Infrastructure, construction or regulated work with fixed scope: a waterfall plan with stage gates. Most of my projects have been hybrid: an agile delivery team inside a fixed-date programme, with a milestone plan for the sponsor."
"Short, regular, and the same format every time: a one-page status with RAG, the top three risks, decisions needed, and the date. Bad news goes early and in person, with a plan. The steering committee should never learn something from the status report that I did not tell them the week before."
An honest one. "A CRM implementation was cancelled at month eight because adoption in the field was 20%. I had treated it as a technology project; it was a change project. What I do differently now is start with the people who will use it, measure adoption from the pilot, and make a change manager part of the core team."
"Bottom-up from the work breakdown, checked against a top-down analogy with a similar past project, with a contingency that reflects the uncertainty rather than a flat 10%. I give ranges early and narrow them; a single number in week one is a guess presented as a commitment."
"Visible progress and protection. Milestones close enough that the team sees something finish every few weeks, credit given publicly and specifically, problems taken off the team's plate before they become the team's problem. And no surprise scope: the team hears about changes from me first."
Name what you actually used and for what: Jira or Azure DevOps for delivery, MS Project or Smartsheet for the milestone plan, Confluence for decisions, Excel for the budget, Power BI for the dashboard. Then one line on the principle: the tool matters less than whether the plan is updated weekly.
28 more project manager interview questions by area
Planning and execution
- How do you build a project plan from a one-page brief?
- How do you decide what to do when a sponsor gives you a date before you have a scope?
- Describe how you run a kickoff.
- How do you track progress, and how often?
- What is your approach to resource conflicts between projects?
- How do you close a project?
Budget and cost
- Tell me about a project where you managed a budget. How large, and what was the variance?
- How do you handle a project that is going to overrun its budget?
- How do you present cost trade-offs to a sponsor?
- What is earned value, and have you used it?
Agile and product-adjacent
- What is the difference between a project manager and a scrum master?
- How do you handle a product owner who keeps changing the sprint?
- How do you report progress on an agile project to a waterfall steering committee?
- How do you measure velocity, and what do you do with it?
- Describe a retrospective that changed how the team worked.
People and leadership
- How do you manage a team member who is underperforming?
- Tell me about a conflict on your team and how you resolved it.
- How do you onboard a new team member mid-project?
- How do you manage a distributed or offshore team?
- Describe a time you had to deliver bad news to your team.
Quality, risk and governance
- How do you ensure quality without slowing delivery?
- Describe a risk that materialised. What happened?
- How do you handle a vendor that is not delivering?
- What governance do you put around a project, and what do you leave out?
- How do you manage dependencies on other teams?
- What would you do if you discovered a compliance problem late in a project?
- How do you decide when to escalate?
- What do you do in the first 30 days on a project you inherit?
What changes for PMP-style and Agile interviews
| Interview style | What they probe | Prepare |
|---|---|---|
| PMP / PRINCE2 / programme | Process: integration, scope, schedule, cost, risk, procurement; governance; earned value | Two projects with full numbers; a risk register story; a change-control story; know your methodology's vocabulary |
| Agile / product | Servant leadership, backlog and stakeholder management, metrics (velocity, cycle time), continuous improvement | A sprint-gone-wrong story; a retrospective that changed something; how you report to non-agile stakeholders |
| Technical PM (IT, engineering) | Domain depth, dependency management, vendor and integration work, cutover | An integration or migration story; how you plan a cutover; how you talk to engineers |
Questions to ask about the projects you would inherit
- Which projects would I take over, and what state are they in?
- What is the sponsor's view of the last project this team delivered?
- How are priorities set between projects, and by whom?
- What does the PMO or governance look like in practice?
- What went wrong on the last project that slipped, and what changed as a result?
- How much authority does the PM have over budget and resourcing here?
Practise PM questions with follow-ups
The AI interview tool asks project management questions for your level, probes the numbers, and scores your answers on structure and specificity.
Start a mock PM interviewProject manager interviews: practical questions
Prepare two projects with full numbers (budget, timeline, team size, variance, outcome) and eight STAR stories: scope creep, a slip, a difficult stakeholder, a risk that materialised, a failure, a budget problem, an underperformer, a vendor issue. Revisit the posting for its methodology and tools, and prepare questions about the projects you would inherit.
Tell me about a project you managed; how do you handle scope creep; describe a project behind schedule; how do you prioritise; tell me about a difficult stakeholder; how do you manage risk; which methodology and why; tell me about a failure; how do you estimate; what tools do you use.
Use projects you coordinated rather than owned: a university capstone, an event, a work project where you ran the plan. Keep the numbers real and small; interviewers hiring junior PMs and coordinators want to see planning, communication and honesty, not a 9M dollar budget.
Yes, briefly, and only as evidence of vocabulary, not competence. Interviewers care far more about the slipped project you recovered than about the exam you passed.
"What went wrong on the last project that slipped here, and what changed as a result?" It tells you how the organisation treats failure and whether lessons get applied, which predicts your life as a PM there.
Share article