Project managers are hired for judgment under pressure: scoping honestly, spotting risk early, and telling stakeholders the truth at the right altitude. Certifications say little about any of that. The questions below pull for real projects, real slips, and real recoveries. Pick 10-12 for a round at {{Company name}}, ask every candidate the same set, and score with the guidance notes.

Planning and scoping

• Walk me through how you turned a vague executive ask into a scoped, estimated plan.
• How do you build an estimate you can defend when you have never done this type of project before?
• Tell me about a time you pushed back on scope at kickoff. What happened?
• How do you decide what is genuinely out of scope, and where do you write it down?
• What does your work breakdown look like for a 3-month, multi-team project?
• How much buffer do you plan for, and how do you defend it when someone wants to cut it?

What good looks like: strong candidates describe decomposing work with the people who will do it, estimating in ranges, and writing scope exclusions down where stakeholders sign off. They treat the plan as a living forecast, not a contract carved in stone — and they can tell you exactly where their last plan was wrong and how fast they caught it.

Risk and dependency management

• Tell me about a risk you flagged early that others dismissed — and what happened.
• How do you track dependencies on teams that do not report to you?
• What is on your risk register right now, in your current or last project?
• Describe a project where a single vendor or hire was the critical path. How did you de-risk it?
• When a dependency slips two weeks, what are your first three moves?

Stakeholder communication

• How do you deliver a status report that an executive actually reads?
• Tell me about telling a sponsor the project would be late. Walk me through the conversation.
• How do you handle a stakeholder who keeps adding requirements in the hallway?
• Two senior stakeholders want contradictory outcomes from the same project. What do you do?
• How do you keep a distributed team and stakeholders across {{Time zones}} on the same page without meeting overload?

What good looks like: the best candidates share bad news early, in person, with options attached — never burying a slip in slide twelve. Listen for a communication system: a cadence, a single source of truth, and status that leads with what changed and what is needed, tailored to the audience reading it.

Execution and delivery

• Tell me about a project you rescued. What was broken and what did you change first?
• How do you know a project is slipping before the dates say so?
• Describe your approach when quality, scope, and deadline cannot all survive.
• What do you do in the first week of taking over someone else's project?
• How do you close a project — what happens between done and actually finished?

Methods and tooling

• Which methodologies have you run — agile, waterfall, hybrid — and how do you choose per project?
• What project tools have you used, and what do you actually track in them versus in your head?
• How do you run a retrospective that produces changes instead of complaints?
• What is one process artifact you refuse to skip, and one you happily drop?

Leading without authority

• How do you get work prioritized by a team whose manager has other plans?
• Tell me about a team member who was missing deadlines. What did you actually say to them?
• How do you build credibility fast with a technical team when you are not the expert?
• Describe a conflict inside the project team you resolved without escalating.