Project Manager interview questions

PM interviews test whether you control a plan or merely report on one. The strongest answers are specific about dates, dependencies and the moment you knew something was going wrong — and about what you did before escalating rather than after.

12 questions across 4 areas, with what separates a strong answer in each.

Practise these out loud and get your answers graded — calibrated to the actual posting you're applying for.

Planning and estimation

How a schedule gets built and how much you trust it.

  1. How do you build a plan when estimates from the team are unreliable?

    Strong answers cover: Decomposing until estimates stabilise, tracking actuals against estimates over time, and holding buffer at the plan level rather than hidden in every task.

  2. Walk me through how you identify the critical path.

    Strong answers cover: Real dependency mapping rather than a Gantt chart's default, and knowing which dependencies are genuine versus conventional.

  3. A stakeholder asks for a date before scope is defined. What do you say?

    Strong answers cover: Giving a range with named assumptions and a date for when you'll narrow it, rather than either refusing or guessing.

Risk and issues

Whether risk management is a live activity or a document.

  1. Tell me about a risk you saw coming that still hit you.

    Strong answers cover: Why the mitigation didn't work, and honesty about whether you under-communicated the risk beforehand.

  2. How do you decide when to escalate?

    Strong answers cover: A threshold defined in advance, and evidence you escalate early with a proposed option rather than late with a problem.

  3. A key dependency team just slipped by three weeks. What do you do first?

    Strong answers cover: Quantifying the impact on your critical path before reacting, then bringing options — resequence, descope, absorb — rather than only the bad news.

Recovery

Most interviewers have a failing project and want to know if you can save one.

  1. You inherit a project that's 40% over schedule. What are your first two weeks?

    Strong answers cover: Establishing actual status independently of the reported status, then a re-baseline with an explicit conversation about scope, date or resources.

  2. How do you handle a team member who consistently misses commitments?

    Strong answers cover: Finding the cause — capacity, blockers, unclear requirements — before performance-managing, and involving their manager appropriately.

  3. Describe a project you'd call a failure.

    Strong answers cover: A real one, with your own contribution named, and what you'd do differently in specific terms.

Stakeholders and governance

Communication cadence and how bad news travels.

  1. How do you report status to an executive sponsor?

    Strong answers cover: Decisions needed and risks up front, consistent status criteria, and never having a red appear without warning.

  2. Two stakeholders want incompatible things. How do you resolve it?

    Strong answers cover: Surfacing the trade-off to a named decision-maker instead of absorbing the conflict into the plan.

  3. How do you run a change request process without it becoming a bottleneck?

    Strong answers cover: Sizing the process to the change, a clear approval threshold, and always attaching the schedule impact to the request.

Project Manager interview FAQ

Do I need a specific certification?
It helps pass screening for some employers and is rarely decisive in the interview itself. Panels spend their time on how you handled real projects.
Should I mention a methodology by name?
Only alongside what you actually did. Naming a framework without describing the practices behind it is a common way to sound less experienced than you are.

Other roles

Ready to practise for real?

Calibr builds a session from your actual job posting, grades every answer, and tracks the areas you keep losing points on.