Project Manager interview scorecard template
A structured scorecard for interviewing a Project Manager: six weighted competencies, what a 1 and a 5 actually look like, and questions that surface evidence instead of opinions. Print it, or copy it into your ATS.
The Project Manager scorecard
| Competency | Weight | Score 1 — what it looks like | Score 5 — what it looks like |
|---|---|---|---|
| Planning and schedule construction Whether plans are built from estimates and known constraints rather than from a date handed down, and whether the gap between the two can be defended. | 18% | Describes the plan as the date leadership required, with tasks fitted backwards into it; cannot say which estimates came from the people doing the work. | Explains how the estimate was assembled, who supplied each piece, where buffer was placed and why, and what the plan looked like before and after negotiation. |
| Dependency and critical path management Whether the candidate identifies what blocks what across teams and vendors, and acts on the critical path instead of tracking every task with equal attention. | 20% | Reports status by listing every workstream at the same level of detail; when a delivery slipped, the downstream impact was discovered by the team that got blocked. | Names the two or three dependencies that actually controlled the date, how each was tracked, and a case where resequencing work absorbed an external delay. |
| Risk identification and mitigation Whether risks are surfaced early with an owner and a trigger attached, rather than reported as issues once they have already hit the schedule. | 17% | Describes risks generically as resourcing or scope, with no owner and no date; the examples given had already become delays by the time they were raised. | Gives a risk logged before it materialised, the trigger being watched, the mitigation prepared in advance, and what it still cost when the trigger fired. |
| Scope and change control Whether change requests are handled through a visible trade-off rather than absorbed quietly into the same date with the same team. | 15% | Says yes to added scope and describes recovering through overtime or pressure on the team; cannot name a request that was refused or deferred, or by whom. | Describes a mid-project change, the options put to the sponsor with cost and date attached, and the decision recorded before work restarted. |
| Stakeholder communication and escalation Whether bad news reaches sponsors early and in a form they can act on, and whether escalation happens while the schedule can still be recovered. | 15% | Status reports stay green until the deadline is missed; escalation is described as informing leadership after the team had already exhausted its options. | Recounts flagging a slip while there was still room to act, what was asked of the sponsor, and the decision that came back within days. |
| Team coordination and unblocking Whether the candidate removes obstacles for the people delivering the work, instead of only collecting status from them and passing it upward. | 15% | Describes the role as running stand-ups and updating the tracker; asked what they unblocked last quarter, offers meeting logistics rather than a decision or a resource. | Names a blocker they resolved, who they had to go to, how long the team had been stuck, and what changed in the process so it did not recur. |
Weights sum to 100. Agree them before the first interview, not after — adjusting weights once you have scores is how a panel rationalises a favourite.
Questions that surface evidence
Each one asks for something that already happened, in enough detail to verify. Hypotheticals reward rehearsal, not track record.
- Tell me about a project that slipped. When did you first know, who did you tell, and how many weeks of room were left when you raised it?
- Walk me through the last plan you built. Where did the estimates come from, where did you place buffer, and which dependency ended up controlling the date?
- Describe a change request you pushed back on. What did you present to the sponsor, what did they choose, and how was that decision recorded?
- Tell me about a risk you logged that later fired. What trigger were you watching, what mitigation was ready, and what did it still cost the project?
- Pick a blocker your team was stuck on. How long had it been open before you took it, who did you have to go to, and what changed so it did not repeat?
Red flags
- Describes the role entirely as running ceremonies and updating a tracker, with no decision owned.
- Every past project delivered on time; no slip, descope or replan is recalled.
- Attributes delays to other teams without describing what was tried to unblock them.
- Cannot name the dependency or constraint that set the date on a recent project.
How to use this scorecard
- Agree the weights with the panel before anyone interviews, and write them down.
- Every interviewer scores every competency independently, adding a note that quotes what the candidate actually said.
- Compare scores before discussing them. Discussing first anchors the panel on whoever speaks loudest.
Build a custom scorecard → · Boolean string to source a Project Manager →
Frequently asked questions
What is the difference between a project manager and a product manager scorecard?
A project manager scorecard weights planning, dependencies, risk and change control — how the work gets delivered. A product manager scorecard weights problem definition, prioritization and outcome metrics — what gets built and why. Using one rubric for both hides the exact gap you are hiring to fill.
What should you ask a project manager to test real delivery experience?
Ask about a project that slipped and when they first knew. Strong candidates name the day they raised it, who they escalated to, and how much room was left to act. Candidates who describe only on-time deliveries have usually never owned a critical path.
How do you compare two project manager candidates fairly?
Score the same competencies with the same weights for both, and write down the evidence behind each score while the interview is still fresh. Comparing notes taken that way turns the debrief into a review of what each candidate actually did, rather than who interviewed more smoothly.
When the stakes are a real hire, use evidence
These tools are quick heuristics. Verdict reads the CV against your job description and scores six dimensions with verbatim quotes as evidence — a hiring document you can defend.