Interview guide for project managers: a full loop with a plan, a status report and a sponsor role-play

Project managers are hired to make a plan, keep it honest and tell people early when it will not hold. The interview loop should test those three things with the candidate doing them, because most project managers can describe a successful project fluently and many resumes credit them with outcomes the whole team produced. This guide gives hiring managers a full loop for a mid-level project manager delivering cross-functional business or technology projects: five stages, who owns which competency, core questions with what to listen for, a planning and status exercise, a sponsor role-play, example weights and the debrief decision rule.

The first call is covered in project manager phone screen questions, which checks budget and scope ownership, methodology and certifications. If the role decides what to build rather than how to deliver it, you want the interview guide for product managers instead.

The loop at a glance

The exercise and the role-play are linked: the status report the candidate writes in stage 3 is what the sponsor reacts to in stage 4. The coverage logic is in the interview process template.

Stage 1: the screen (30 minutes)

• "Tell me about your current or most recent project: budget, team size, duration, and what you personally controlled." Listen for: numbers, and the difference between tracking a budget and approving spend against it.
• "How is work planned and tracked on your projects: phases, sprints, or a mix?" Listen for: a method they can describe in practice, and comfort with the one your teams use.

Stage 2: hiring manager interview (45 minutes)

1. "Tell me about a project that was going to miss its date. When did you know, and what did you do in the following week?" Listen for: early signals they watched, options they put to the sponsor (cut scope, add people, move the date), and the decision that was made. A strong answer includes the moment they wished they had raised it sooner.
2. "Tell me about a time the budget was at risk." Listen for: how they tracked spend against progress, not only spend against the budget, and what they changed.
3. "Tell me about a scope change you accepted and one you pushed back on." Listen for: a change process that weighed impact on time and cost, and a sponsor decision rather than a project manager absorbing work silently.
4. "Which project are you least proud of, and why?" Listen for: their own part in it and a practice they changed afterward.

Stage 3: the planning and status exercise (60 minutes, plus 20 minutes of discussion)

The candidate works alone with a written brief and their usual tools, then discusses the result with a senior project manager. The brief is invented.

Part 1: the plan (35 minutes)

"We are moving 120 staff in two offices to a new scheduling system before the old contract ends in five months. The vendor configures the system; our IT team handles single sign-on and data migration; HR runs training. The vendor's statement of work does not mention data migration." Ask for a milestone plan with owners, the main dependencies, the top five risks and one question for the sponsor before the plan is agreed.

Part 2: the status update (15 minutes)

At minute 35, hand over a new fact: "It is week nine. The vendor has told you configuration will be three weeks late because of a staffing change." Ask for the status update to the sponsor, in no more than 200 words.

What to listen for in the discussion

• Planning: realistic milestones that work back from the contract end, with buffer, and owners who are teams or people rather than "TBD".
• Risk: spotting the data migration gap in the statement of work, and the contract end date as a hard constraint.
• Dependencies: single sign-on and migration needed before training can be realistic.
• The status update: the impact on the end date first, the options with their costs, a recommendation, and what the candidate needs from the sponsor. Status that hides the problem below three paragraphs of progress scores low.

Priority judgment shows up here too; interview questions for prioritization pairs well if you want a behavioral check.

Stage 4: sponsor role-play (30 minutes)

A business leader plays the sponsor, having read the candidate's status update. The script: the sponsor is unhappy, asks "Can't you just make the vendor catch up?", suggests skipping the training pilot, and finally asks the candidate to tell the board the project is on track until there is more certainty.

Listen for: calm restatement of the facts; options with honest consequences (skipping the pilot moves risk to go-live rather than removing it); a clear refusal to report the project as on track, with an alternative wording that is accurate; and an agreed next step and date. A candidate who agrees to everything to end the conversation will do the same on the job.

Stage 5: team member interview (30 minutes)

• "How do you get estimates from the people doing the work, and what do you do when they seem too high?" Listen for: asking for the reasoning, splitting the work, and challenging assumptions rather than the person. Cutting an estimate because the date is fixed is a warning sign.
• "Tell me about a meeting you run every week. What happens in it, and what did you stop doing?" Listen for: a purpose, an agenda tied to decisions and risks, and a willingness to cancel meetings that do not earn their time.

Scorecard competencies and weights

Example weights for a mid-level project manager. Set yours at intake and lock them before the first candidate.

The scorecard builder checks the weights add up to 100. How a gate differs from a weight is in weighted interview scorecard.

The debrief decision rule

1. Scorecards first, with the plan and status update attached, before anyone reads anyone else's.
2. Gate: honest reporting. A candidate who agreed in the role-play to report a late project as on track does not proceed.
3. Floor: planning and risk at 3 or above. These are the core of the job and show up in every project from week one.
4. Weighted total: in this example, 2.8 or higher on the 1–4 scale goes to references.
5. References: at least one sponsor or senior stakeholder from a past project. Ask what they heard from the candidate when things went badly.

The debrief record and speaking order are in the interview debrief template.

Adjusting by project type and level

Common mistakes in project manager loops

• Methodology debates. Arguing agile versus waterfall tells you little. Watch them plan the kind of work you do.
• Only success stories. Every project manager has a project that slipped. Ask about it directly.
• No sponsor in the loop. The hardest part of the role is the conversation with the person paying for the project.
• Crediting the team's outcome to the candidate. Ask what they did in a specific week, not what the project achieved.

After the hire, use the 30-60-90 day plan for project managers to set expectations for the first three months.