20 questions
Scoring rubric 1–5

Project Manager Interview Questions

Ask project managers about the projects that went wrong. Anyone can narrate a delivery that went to plan. What separates a strong PM is how they detected slippage early, what they cut, and how they told a stakeholder bad news.

Try Voicit free Book a demo

4.8 out of 5 350+ reviewsUpdated: August 2026

Chosen by over 1,000 companies to document their interviews

Project management interviews often turn into a tour of methodologies. Whether someone prefers Scrum or Kanban tells you very little.

What predicts performance is how they behave when the plan meets reality: scope creep, a missing dependency, an unhappy sponsor.

20interview questions

4question sets by competency

1–5scoring rubric for every answer

Delivery under pressure

Tell me about a project that slipped. When did you know, and what did you do?

What a strong answer shows: Early detection with a concrete signal, plus a decision: cut scope, add time, or add people knowingly.
Red flag: Found out when the deadline passed.

Describe a project you had to cut scope on. What went and why?

What a strong answer shows: A clear prioritisation criterion and a conversation with the sponsor about the trade-off.
Red flag: Cut quality or testing silently to protect the date.

What’s the worst estimate you’ve given? What did you learn?

What a strong answer shows: Owns it and changed how they estimate: buffers, breakdown, historical data.
Red flag: Estimates were always fine; delivery teams were the problem.

Tell me about a project you’d run differently today.

What a strong answer shows: Specific, structural change rather than «I’d communicate more».
Red flag: Nothing to change.

Tell me about a project you delivered late. What was the first sign?

What a strong answer shows: They can name the early signal and say how long they sat on it before raising it.
Red flag: The first sign was the deadline itself.

How do you estimate when nobody can give you a number?

What a strong answer shows: A method — ranges, comparable past work, breaking it down — plus how they communicate the uncertainty.
Red flag: Takes the engineer’s number and adds a fudge factor with no reasoning.

Stakeholders and communication

How did you tell a sponsor the project wouldn’t hit the date?

What a strong answer shows: Told them early, with options attached, not just a problem.
Red flag: Waited, hoping to recover, until it was undeniable.

Describe a stakeholder who kept changing requirements.

What a strong answer shows: Made the cost of change visible instead of absorbing it silently.
Red flag: Either said yes to everything or refused everything by process.

How do you keep people informed without drowning them in updates?

What a strong answer shows: A rhythm and format matched to the audience: exec summary vs delivery detail.
Red flag: A weekly report nobody reads is their only mechanism.

Describe a time you had to tell a stakeholder something they did not want to hear.

What a strong answer shows: The framing they used and what they proposed alongside the bad news.
Red flag: Softened it until the message did not land, or let someone else deliver it.

How do you keep a sponsor engaged without wasting their time?

What a strong answer shows: A deliberate cadence and a clear view of which decisions actually need the sponsor.
Red flag: Either invisible or constantly escalating.

Risk and dependencies

Tell me about a dependency that nearly derailed a project.

What a strong answer shows: Identified it early, tracked it, had a fallback.
Red flag: Dependencies appear in their stories only as surprises.

What risk did you flag that nobody wanted to hear about?

What a strong answer shows: Raised it anyway, documented it, and kept working the problem.
Red flag: Only mentions risks that materialised, in hindsight.

How do you decide what goes on a risk register versus what you just handle?

What a strong answer shows: Judgement based on impact and reversibility, not on ceremony.
Red flag: Everything or nothing goes on the register.

Tell me about a dependency that slipped and took you with it.

What a strong answer shows: They had visibility into it beforehand and had a contingency, even a weak one.
Red flag: Found out when it was already late, and blames the other team entirely.

Working with the team

How do you get commitment from people who don’t report to you?

What a strong answer shows: Built credibility by removing obstacles for them, not by chasing status.
Red flag: Authority-by-Gantt-chart.

Tell me about a conflict between two teams on your project.

What a strong answer shows: Surfaced it, mediated on the substance, and got a decision made.
Red flag: Escalated immediately, or let it fester to keep the peace.

What does your status meeting actually look like?

What a strong answer shows: Focused on blockers and decisions, with the rest handled asynchronously.
Red flag: A round-robin where everyone reads their update aloud.

How do you run a project where you have responsibility but no authority?

What a strong answer shows: Concrete influence mechanics: making progress visible, making commitments public, using the sponsor sparingly.
Red flag: Relies on escalation as the only lever.

What does your project status report look like, and who actually reads it?

What a strong answer shows: They have adapted the format to the reader, and know when it is being ignored.
Red flag: One template sent to everyone, with no idea whether it is read.

How to score the answers

1
Methodology only
Talks about frameworks, not about projects
2
Happy path
Only projects that went to plan
3
Solid
A real problem, their decision, the outcome
4
Strong
Above, plus early detection and an explicit trade-off
5
Exceptional
Above, plus a change to how the organisation delivers projects

FAQ

Frequently asked questions

What should I ask a project manager in an interview?

Ask about projects that went wrong: when they knew about slippage, what scope they cut, how they told the sponsor. Methodology preferences are far less predictive than behaviour when the plan breaks.

Should I ask about Agile, Scrum or Waterfall?

Briefly, and only to check they can adapt. A PM who can only work one way is a risk. Better to ask how they chose an approach for a specific project and what they’d do differently in a different context.

How do I interview a PM for a technical team if I’m not technical?

Focus on the parts you can evaluate: dependency management, stakeholder communication, risk handling, trade-off decisions. Have an engineer assess technical depth in a separate session with the same competencies.

What are the most important skills to look for in a project manager?

Realistic estimation, early escalation, stakeholder communication and the ability to make progress visible. Methodology knowledge matters far less than most job descriptions suggest — a PM who raises risks three weeks early is worth more than one who can name every Scrum ceremony.