Question 1

Tell me about a project whose schedule was slipping. When did you know, and what did you do?

Accepted Answer

Name the early signal (earned value trending down, a critical-path task overrunning, a vendor going quiet), how many weeks before the deadline you called it, the recovery options you costed (crashing, fast-tracking, descoping, re-baselining), what you recommended, and what the sponsor decided. Include the conversation where you delivered the bad news. Common mistake: A story where the slip was discovered near the end and heroically recovered with overtime. The panel hears "no early warning system."

Question 2

How do you handle a scope change request mid-project?

Accepted Answer

A defined change-control path: capture the request in writing, assess impact on time, cost, quality and risk, price it, and take it to the change board or sponsor for a yes/no — never absorb it silently. Give an example of a change you pushed back on and one you accepted, and what each did to the baseline. Common mistake: Saying you "try to accommodate the client." Uncontrolled scope is the number-one cause of project failure and the panel knows it.

Question 3

Walk me through how you build and use a risk register.

Accepted Answer

Identify risks in a workshop with the team, not alone; score by probability and impact; assign an owner and a specific response (avoid, mitigate, transfer, accept); review it in every weekly meeting, not just at kickoff. Give one risk that actually materialised and how the pre-planned response saved time. Common mistake: Describing a register that was filled in at the start and never opened again — which is what most panels have seen in practice.

Question 4

Describe a time a key stakeholder stopped responding to you.

Accepted Answer

Who they were and what you needed (a sign-off, a decision, access), the escalation ladder you climbed — a direct call, a face-to-face visit, their manager, your sponsor — and how you protected the schedule while waiting, such as documenting the dependency and its cost per day. Show persistence without burning the relationship. Common mistake: Sending five emails and then blaming the stakeholder in the status report. The panel wants to hear what you did beyond email.

Question 5

Tell me about a project that went over budget.

Accepted Answer

The size of the overrun, when you caught it (variance analysis, cost-to-complete forecasting), the causes, what you did — descoped, renegotiated with vendors, requested contingency with justification — and what you changed in your cost tracking afterwards. Honesty about your own part in it scores well. Common mistake: Claiming you have never been over budget. Either you have run very few projects or you are not tracking cost.

Question 6

How do you manage a vendor or subcontractor who is underperforming?

Accepted Answer

Start with the contract: what were the deliverables and the acceptance criteria. Then the conversation — specific misses, in writing, with a recovery plan and a date. Then the levers: withholding payment milestones, liquidated damages, replacing them, and the point at which you escalate to procurement or legal. Give a real example with the outcome. Common mistake: Going straight to penalties. Panels want to see that you tried to fix performance before you punished it.

Question 7

How do you report status to executives who have five minutes?

Accepted Answer

One page or one slide: RAG status with the reason for any amber or red, the top three risks, the decisions you need from them by when, and the milestone dates that changed. Give an example of a status report that got a decision made, and mention that you never let a project go from green to red without an amber in between. Common mistake: Reporting everything green until it cannot be. Executives on the panel have been burned by exactly that.

Question 8

Tell me about a project that failed. What was your role in the failure?

Accepted Answer

A real failure — cancelled, delivered late and unused, or over budget by half — with the honest root cause, the specific thing you would have done differently as PM (raised a risk earlier, refused a scope creep, insisted on a decision), and one habit you kept from it. Blameless language about the team. Common mistake: A failure that was entirely someone else's fault. The question asks about your role; answer it.

Question 9

How do you choose between an agile and a waterfall approach for a project?

Accepted Answer

Base it on the uncertainty in requirements and the cost of change: fixed-scope, regulated, physical work (construction, fit-out, hardware) leans to stage-gated planning; software and services with evolving requirements suit iterations. Give an example where you blended them — an agile delivery inside a contractual milestone structure — and how you handled the reporting. Common mistake: Advocating one methodology as always better. The panel wants judgment fitted to the project, not a preference.

Question 10

Describe a time you had to get work done through people who did not report to you.

Accepted Answer

The people and what you needed from them, how you understood their priorities, what you offered in return (visibility, cover with their manager, clearing a blocker), how you made the ask specific, and what happened. This is a test of influence without authority, which is most of the job. Common mistake: Describing escalation as the first step. Show that you tried to win them before you went to their boss.

Question 11

How do you run a project kickoff?

Accepted Answer

Objectives and success criteria agreed in writing, roles and decision rights (a RACI), the communication plan, the top risks identified with the team present, and the first three milestones. Give an example of a kickoff that surfaced a problem early — a stakeholder missing, an assumption nobody shared — and what it saved. Common mistake: Treating kickoff as a presentation of the plan. It is where you find out what the plan got wrong.

Question 12

Tell me about a delay caused by an approval, permit or dependency outside your control.

Accepted Answer

What the dependency was (municipality approval, a third-party integration, a client decision), how you had planned for it (lead times in the schedule, a named owner, early submission), what you did when it slipped anyway — re-sequencing work, an extension-of-time notice with evidence, parallel activities — and how you kept the client informed. Common mistake: Presenting an external delay as simply not your problem. The panel wants to see that you managed around it.

Question 13

How do you keep a team motivated on a long project that is going badly?

Accepted Answer

Be honest with the team about the state of things, break the remaining work into short visible wins, protect them from blame flowing down from above, remove the blockers that are frustrating them most, and make sure the sponsor sees their effort. Give one specific example of something you did that changed the mood. Common mistake: Pretending to the team that everything is fine. They already know it is not, and they lose trust in you.

Question 14

Why this role, and what kind of projects do you want to be running in three years?

Accepted Answer

Two specific reasons this organisation fits — its sector, the size of its programmes, a project you know it delivered — and a direction that is realistic for them to offer (programme management, a sector specialism, larger contract values). Then what you bring on day one. Common mistake: A generic answer about leadership and growth. Say what projects, what size, what sector.

Project Manager interview questions — and what a strong answer includes

Tell me about a project whose schedule was slipping. When did you know, and what did you do?

How do you handle a scope change request mid-project?

Walk me through how you build and use a risk register.

Describe a time a key stakeholder stopped responding to you.

Tell me about a project that went over budget.

How do you manage a vendor or subcontractor who is underperforming?

How do you report status to executives who have five minutes?

Tell me about a project that failed. What was your role in the failure?

How do you choose between an agile and a waterfall approach for a project?

Describe a time you had to get work done through people who did not report to you.

How do you run a project kickoff?

Tell me about a delay caused by an approval, permit or dependency outside your control.

How do you keep a team motivated on a long project that is going badly?

Why this role, and what kind of projects do you want to be running in three years?

Answer these out loud, get coached

More operations roles

Before the interview

Get new project manager questions by email

Project Manager interview questions — and what a strong answer includes

Tell me about a project whose schedule was slipping. When did you know, and what did you do?

How do you handle a scope change request mid-project?

Walk me through how you build and use a risk register.

Describe a time a key stakeholder stopped responding to you.

Tell me about a project that went over budget.

How do you manage a vendor or subcontractor who is underperforming?

How do you report status to executives who have five minutes?

Tell me about a project that failed. What was your role in the failure?

How do you choose between an agile and a waterfall approach for a project?

Describe a time you had to get work done through people who did not report to you.

How do you run a project kickoff?

Tell me about a delay caused by an approval, permit or dependency outside your control.

How do you keep a team motivated on a long project that is going badly?

Why this role, and what kind of projects do you want to be running in three years?

Answer these out loud, get coached

More operations roles

Before the interview

Get new project manager questions by email