
PM Interview Scorecard: Template and Rating Rubric
Use a product manager interview scorecard with competency anchors, a copyable template, a worked example and a practical hiring debrief process.
A product manager interview scorecard records what a candidate demonstrated against the requirements of a specific role. Use the template below to capture a rating, the evidence behind it and any unanswered question for each competency. Agree the criteria before the first interview and compare completed scorecards in the debrief.
This suggested template uses four rating levels plus Not assessed. Adapt the competency anchors to the role; the scale is not a validated hiring test or a universal pass mark.
Define the role before scoring candidates
Write down the outcomes the PM will own, the decisions they can make and the support available. A first PM working with a founder needs a different assessment from a growth PM joining an established experimentation team. Job title alone does not set the bar.
Separate requirements into three groups:
- Essential on entry: capabilities the person must demonstrate to do this job with the support available.
- Developable: gaps the team can realistically support through onboarding and practice.
- Outside scope: skills that are interesting but unnecessary for this hire.
For example, a growth PM assessment could emphasise metric definitions and experiment decisions. A platform PM assessment could emphasise dependencies, technical trade-offs and internal customer needs. These are suggested starting points; use the actual job brief to choose the criteria.
Use the product manager job description template to clarify responsibilities before building the interview plan.
Choose competencies and define sufficient evidence
Use job-related competencies and common rating standards for candidates applying to the same role. Define what sufficient performance means in observable terms, rather than asking interviewers to score “good product sense” or “culture fit”.
The anchors below are examples to adapt before interviews start. They describe evidence to look for, not an expected script or a requirement to use particular frameworks.
| Competency | Example evidence that meets the role's requirement |
|---|---|
| Problem framing and discovery | Identifies a specific user problem, separates observations from assumptions and explains what further learning could change the decision. |
| Strategy and prioritisation | Connects a choice to the business objective, compares credible alternatives and explains what will be deferred or stopped. |
| Metrics and analytical judgement | Defines the outcome and denominator, checks data limitations and distinguishes an observed change from evidence of its cause. |
| Delivery and ownership | Describes a personally owned decision, dependencies, scope trade-offs and how the team handled rollout or setbacks. |
| Collaboration and influence | Explains another function's concerns, describes their own actions in a disagreement and shows how a decision was reached. |
| Communication | Explains a recommendation and its limitations so the intended audience can understand the decision and ask useful questions. |
Add technical, regulatory or domain criteria only when the role needs them. Avoid rewarding confidence, shared hobbies, employer prestige or familiarity with an interview framework as substitutes for these behaviours. Assess communication against the work required, allowing for agreed adjustments and different communication styles.
Use a shared rating scale
Rate each competency against its agreed anchor. Keep the rating separate from the overall hiring recommendation.
| Rating | Suggested meaning |
|---|---|
| 1 — Below requirement | The observed response shows a material gap against the agreed requirement, after relevant follow-up. Record the gap. |
| 2 — Partly meets | The candidate demonstrates some required behaviours, with a consequential gap or support need. Name it. |
| 3 — Meets | The candidate provides enough relevant evidence to meet the requirement at this role's scope. |
| 4 — Exceeds | The candidate meets the requirement and demonstrates additional relevant depth. State what exceeded the anchor. |
| Not assessed | The interview did not provide enough evidence to judge this competency. Record why and whether follow-up is needed. |
Missing evidence is different from evidence of weak performance. If time ran out before you asked about rollout, mark delivery Not assessed. If the candidate was asked relevant questions but could not explain a rollout decision, document that response and compare it with the anchor. Do not silently turn either situation into a default score.
Avoid a universal rule such as “any 2 is a rejection”. Decide in advance which requirements are essential, what support is available and how unresolved evidence will be handled. A total or average can conceal a gap in an essential competency; it should not replace that review.
Assign interview coverage
Choose common core questions, relevant follow-up prompts and rating definitions before the loop. Structured interviews use predetermined questions and shared scoring standards so candidates are assessed consistently. Follow-up should clarify evidence without giving one candidate the answer or applying a different bar.
A suggested coverage plan is:
- The hiring manager assesses the role's scope and one product decision from the candidate's experience.
- A product or analytical partner assesses problem framing, prioritisation or metrics through a relevant case.
- An engineering or design partner assesses collaboration and delivery through a past example or a bounded discussion.
Combine conversations when a smaller panel can still cover the essential criteria. Every interviewer does not need to rate every competency. Assign an owner to each criterion and identify where a second observation would resolve an important uncertainty; panel size is not a quality guarantee.
For a work sample, specify the task, time budget, permitted tools and assessment criteria in advance. Use a fictional or appropriately shareable problem, and agree any accessibility adjustments. A candidate should be able to describe confidential work at an appropriate level without disclosing protected material.
Use the PM interview question bank to select prompts, then tailor the assessment to the job. For portfolio discussions, the evidence-led portfolio examples help separate an artefact, a person's contribution and an outcome claim.
Copy the scorecard template
Copy this form into your hiring document or applicant tracking system. Complete only the competencies assigned to the conversation; mark other rows Not assessed.
Candidate:
Role and level:
Interview stage:
Interviewer and date:
Role brief / rubric version:
Assigned competencies:
Repeat for each assigned competency:
Competency:
Required behaviour at this role's scope:
Question and follow-up asked:
Observed answer or action:
Candidate's specific contribution:
Outcome described and its limitations:
Rating: 1 / 2 / 3 / 4 / Not assessed
Reason this evidence supports that rating:
Remaining question or support need:
Essential requirements still unresolved:
Development needs and support available:
Overall recommendation: Proceed / Do not proceed / Need evidence
Reason for recommendation:
Targeted follow-up, if needed:
Keep notes factual, job-related and within your organisation's candidate-data access and retention rules. Record a quote accurately or label it as a paraphrase. Avoid speculation about health, family circumstances or other personal matters unrelated to the assessment.
Worked example: scoring a prioritisation answer
Consider this fictional practice response: “We deferred the reporting redesign because customers could not complete account setup. I recommended fixing setup first, compared it with a manual support workaround and agreed the smaller release with engineering. We monitored completed setups and support contacts, but we could not isolate our change from other releases.”
For an example criterion requiring a defensible prioritisation decision, an interviewer could record:
- Observation: The candidate names the customer obstacle, a deferred alternative, their recommendation and the limits of the outcome evidence.
- Rating: 3 — Meets, if those behaviours match the agreed scope for this role.
- Unresolved question: What customer evidence established the setup problem, and how was the cost of delay assessed?
The response alone does not establish a revenue improvement, an independently verified result or readiness to lead a whole product organisation. A 4 would need additional relevant evidence against the pre-agreed higher anchor, rather than a more polished delivery of the same story.
Run the hiring debrief
Have interviewers complete their individual ratings before the group discussion. Then compare the evidence competency by competency, especially where ratings differ.
- Check coverage. Identify unassessed essential requirements before discussing an overall recommendation.
- Compare observations. Ask what each candidate actually said or did, which prompt elicited it and which anchor was applied.
- Resolve differences. Determine whether interviewers saw different evidence, used different standards or inferred more than the response supported.
- Choose the next action. Proceed, decline or collect a specific missing piece of evidence. Keep any follow-up proportionate and consistent with the process used for comparable candidates.
- Record the decision. Name the decision owner, essential requirements met or unmet, accepted development needs and reasons for the outcome.
A useful disagreement is “the answer explained a release plan but not a rollback decision”. “I did not click with them” gives the panel no job-related behaviour to assess. Ask for the observation behind the impression instead of giving it a numerical score.
When a question repeatedly fails to produce useful evidence, revise the question and recalibrate interviewers for future assessments. Record the rubric version and avoid quietly changing the standard halfway through a candidate group.
Use the scorecard with a shortlist
Start with the role brief, then use the scorecard to test submitted experience in conversation. When browsing product builders, use shipped work, scope and availability to identify people to discuss; a profile is not an independent assessment of every claim.
Companies can use the introduction request path to continue that conversation. For candidates preparing their own examples, the separate interview answers and practice scorecard focuses on rehearsal rather than hiring-panel decisions.
Related guides
Get the weekly digest of top product people & jobs
One email a week. No spam.
Ready to get discovered?
Create your profile so companies can request an intro when there is a fit.
Create Your Profile