Templates

Interview scorecard for project managers, with anchors for each competency

On this page
  1. Which competencies should a project manager scorecard cover?
  2. What does the scorecard look like?
  3. What do the anchors sound like for each competency?
  4. Which work samples produce the evidence?
  5. What does a filled scorecard look like?
  6. How do you adjust the scorecard by level and project type?
  7. What mistakes are specific to scoring project managers?
  8. Where does the scorecard fit in the hiring process?
  9. Questions people ask

An interview scorecard for project managers should score six things: planning and scoping, risk and dependency management, stakeholder management and escalation, schedule and budget control, status communication, and leading a team that does not report to them. Below is a copy-ready scorecard with example weights, what a 1, a 3 and a 5 look like for each competency, two work samples that produce the evidence, and a filled example. Methodology vocabulary and certificates are not scored: decisions are.

The five levels follow the 1-5 interview rating scale, where 3 is a genuine pass at the level you are hiring and 5 is rare. If you have not settled weights and must-haves yet, the weighted interview scorecard explains how; this page fills the form in for a project manager seat, whether the projects are in IT, operations, marketing or a client-facing agency.

Which competencies should a project manager scorecard cover?

  • Planning and scoping. Turns a goal into milestones, owners and a definition of done, and works back from fixed dates.
  • Risk and dependency management. Sees what can go wrong before it does, keeps a risk and issue log that changes decisions, and tracks what this project needs from others.
  • Stakeholder management and escalation. Handles a sponsor or senior stakeholder who wants something the project cannot give, and escalates with options rather than bad news alone.
  • Schedule and budget control. Knows the baseline, spots variance early, forecasts honestly and recovers a slipping project through explicit trade-offs.
  • Status communication. Writes a status update where the problem and the decision needed come first, and the color matches the facts.
  • Leading without authority. Gets estimates, decisions and work from people who report to someone else, and runs meetings that end in decisions.

What does the scorecard look like?

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

CompetencyExample weight1 looks like3 looks like5 looks like
Planning and scoping20%Describes a plan as a list of tasks with no owners, dates or definition of done.Builds milestones with owners, works back from the fixed date, and names what is out of scope.Found a scope gap no one had noticed (for example in a contract or statement of work) before the plan was agreed.
Risk and dependency management20%Risks are listed once and never revisited; dependencies discovered when they break.Names a risk they saw early, the mitigation and the owner, and tracked external dependencies.Changed the plan because of a risk that had not happened yet, and can show what it saved.
Stakeholder management and escalation20%Agrees to everything a senior person asks, or escalates by forwarding the problem.Says no or "not without a trade-off" with reasons, and escalates with options and a recommendation.Brought two stakeholders with conflicting goals to a decision both kept to, and says how.
Schedule and budget control15%Cannot state the baseline, the variance or who approved changes.Knows the baseline, spotted a slip early, and recovered it through a named trade-off.Forecast a miss weeks ahead from leading signals and gave the sponsor costed options before it happened.
Status communication15%Status is all activity; the problem is buried or missing.Impact, options and the decision needed come first, in a few lines.Reported a project as red when others wanted green, with wording that was accurate and still useful.
Leading without authority10%Relies on the sponsor to make people do things.Gets estimates from the people doing the work and unblocks them, with an example.Got a team they did not manage to change how it worked, and the change outlasted the project.

A copy-ready version for each interviewer:

Candidate: [name]                  Role: [project manager, domain, level]
Interviewer: [name]                Stage: [screen / hiring manager / exercise / stakeholder]
Pass/fail checks: required certification verified [ ]  travel or on-call requirement accepted [ ]

Planning and scoping (20%)                    Score 1-5: [ ]
Evidence: [milestones, owners, fixed dates, out of scope]

Risk and dependency management (20%)          Score 1-5: [ ]
Evidence: [the risk seen early, mitigation, owner]

Stakeholder management and escalation (20%)   Score 1-5: [ ]
Evidence: [the no or trade-off, how the escalation was framed]

Schedule and budget control (15%)             Score 1-5: [ ]
Evidence: [baseline, variance, the trade-off chosen]

Status communication (15%)                    Score 1-5: [ ]
Evidence: [what came first, whether the color matched the facts]

Leading without authority (10%)               Score 1-5: [ ]
Evidence: [who they moved, how, what changed]

Weighted score: [ ]     Recommendation: [Strong yes / Yes / No / Strong no]
Open question for the next interviewer: [ ]

What do the anchors sound like for each competency?

The table gives 1, 3 and 5. These are the questions to ask and the in-between levels that cause most debrief arguments.

Planning and scoping

Ask: "Take your most recent project. What was fixed (date, budget, scope), and how did you build the plan around it?"

A 2: describes the plan they were handed rather than one they built. A 4: describes a dependency that reordered the plan and the buffer they protected.

Risk and dependency management

Ask: "Tell me about a risk you flagged that others thought was unlikely. What did you do about it?"

A 2: kept a log but cannot name a decision it changed. A 4: the mitigation cost something up front and they argued for it successfully.

Stakeholder management and escalation

Ask: "Tell me about a senior stakeholder who wanted something your project could not deliver. What did you say?"

A 2: held the line but damaged the relationship, or escalated without a recommendation. A 4: reframed the request around the stakeholder's real goal and found a smaller version that met it.

Schedule and budget control

Ask: "Tell me about a project that slipped. When did you first see it, and what did you change?"

A 2: recovered the date by working longer hours, with no trade-off discussed. A 4: chose between scope, date and cost explicitly and got the sponsor to own the choice.

Status communication

Ask: "What did your last status report say, and what did the reader do with it?"

A 2: accurate, but the problem appears after the progress. A 4: the reader made a decision from it the same week, and the candidate can say what it was.

Leading without authority

Ask: "Tell me about a team lead who did not report to you and kept missing dates. What did you do?"

A 2: went to the lead's manager first. A 4: found why the dates were missed, fixed the cause with the lead, and only escalated what was left.

Which work samples produce the evidence?

The project manager interview guide already has a plan-building exercise and a sponsor role-play. These two are shorter and test different decisions, so you can use them in a hiring manager round or a second loop. Use the same version for every candidate for the seat.

Change request scenario (15 minutes). "You are two thirds of the way through a project with a fixed launch date. A department head who is not your sponsor asks you to add a feature their team needs. Your lead engineer estimates three weeks of work. You have a small contingency left in the budget. Walk me through what you do this week." (All figures in this scenario are examples.)

What to score: planning and scoping (do they treat it as a change request with an impact assessment rather than a yes or no?), stakeholder management (who decides: the sponsor, not the project manager or the department head), and schedule and budget control (do they lay out options such as later release, swap scope, or move the date, each with its cost?).

Forecast exercise (15 minutes). Hand over a one-page summary: week 10 of a 16-week project, about 70% of the budget spent, half of the deliverables accepted, one vendor invoice not yet received, and the team lead's note that testing "should be fine." (Example figures, invented for the exercise.) Ask: "Is this project on track? What would you tell the sponsor on Friday?"

What to score: schedule and budget control (do they notice spend running ahead of accepted work, and that the pending invoice makes it worse?), risk management (do they question "should be fine"?), and status communication (is the message to the sponsor honest, short and paired with a request?).

What does a filled scorecard look like?

A made-up candidate for a mid-level IT project manager seat, after a hiring manager interview and both exercises:

Planning and scoping: 4. Described working back from a contract end date and finding that the vendor's statement of work left out data migration before the plan was signed off.

Risk and dependency management: 3. Named a dependency on another team's release, tracked it weekly and moved testing earlier when it slipped.

Stakeholder management and escalation: 3. In the change request, routed the decision to the sponsor with two options and recommended a later release for the feature.

Schedule and budget control: 2. In the forecast exercise, called the project "roughly on track" and only noticed spend running ahead of accepted work when prompted.

Status communication: 4. Their sample Friday note opened with the risk to the date and the decision needed, in four sentences.

Leading without authority: 3. Described sitting with a team lead to re-estimate work that kept slipping and agreeing smaller weekly deliverables.

Weighted score (example): 4 x 0.20 + 3 x 0.20 + 3 x 0.20 + 2 x 0.15 + 4 x 0.15 + 3 x 0.10 = 3.2. Recommendation: Yes, with budget forecasting as the area for the next interviewer to probe with a real project of theirs.

How do you adjust the scorecard by level and project type?

SeatAdjustment
Project coordinator or junior PMScore planning and status at full weight on smaller projects; accept evidence from projects they ran for someone else. Lower the weight of stakeholder management.
Senior PM or program managerA 3 on stakeholder management needs competing executives, not one sponsor; add portfolio-level trade-offs across projects to schedule and budget control.
Agile software teamsKeep the anchors; ask how they forecast from the team's delivery history and what they did when the forecast moved.
ConstructionAdd subcontractor coordination and permits to risk and dependencies; use the construction project manager screening questions for the domain checks.
Client-facing agency PMRaise stakeholder management; add a scenario where the client asks for unbilled scope.

What mistakes are specific to scoring project managers?

MistakeWhy it failsFix
Scoring methodology vocabularyFluent use of terms says nothing about what the candidate decided.Ask "what did you decide, and what did it cost?" for every story.
Scoring the certificateA credential is pass or fail; scoring it double-counts it against people who manage well without one.Verify it if required (see below) and leave it off the weighted rows.
Accepting "on time and on budget" at face valueScope cuts and re-baselines hide inside that sentence.Ask for the original baseline and every approved change.
Rewarding confidence in the role-playA candidate who calms the sponsor by agreeing to everything will do the same on the job.Score the accuracy of what they committed to.
Asking about family to judge availabilityQuestions about family plans invite discrimination claims (see illegal interview questions) and do not measure availability.State the travel or on-call requirement and ask every candidate whether they can meet it.

Where does the scorecard fit in the hiring process?

The project manager phone screen confirms project size, budget ownership and certification status before anyone spends an hour on an exercise, and the rows here should match the must-haves in your project manager job description. After the hire, the same six areas become the check-ins in the 30-60-90 day plan for project managers. For more questions per competency, see interview questions for project management skills and interview questions for stakeholder management. If the same team hires product managers, the product manager scorecard shows where the two roles differ.

If the job requires PMP, the check is pass or fail: verify it in PMI's Certification Registry or through the candidate's digital badge, as described in how to verify a PMP certification, and do not score it. Timed exercises should allow for reasonable accommodation, which the ADA regulations define to include changes to the application process (29 CFR 1630.2(o)). Each interviewer submits scores before the debrief and before reading anyone else's.

If you run the interview in Interview Signal (we make it), you can enter these six competencies as the scorecard areas of the role's kit; the app scores each area from 1 to 10 during the call and keeps the candidate's own quotes as evidence, deleting any quote that is not in the transcript word for word.

Questions people ask

What competencies should a project manager interview scorecard include?

Score planning and scoping, risk and dependency management, stakeholder management and escalation, schedule and budget control, status communication, and leading a team that does not report to the project manager. Give each a weight and written anchors for a 1, a 3 and a 5, and score from decisions the candidate describes or makes in a work sample.

Should PMP certification be scored on a project manager scorecard?

No. If the role requires PMP, treat it as a pass or fail check and verify it in PMI's Certification Registry or through the candidate's digital badge. A scorecard row should measure what the person does with a project, which a certificate does not show.

How do you score a project manager who used agile instead of a traditional plan?

Score the decisions, not the vocabulary. A candidate from an agile team should still be able to say how they forecast a delivery date, what they did when the forecast slipped, and how they told the sponsor, and the same anchors apply to those answers.

How can an interviewer tell whether a project really finished on time and on budget?

Ask what the original baseline was, what changed in scope along the way, and who approved each change. A project that finished on the date because half the scope was quietly cut is a different story from one that held scope, and the candidate's answer to those questions belongs in the schedule and budget control score.