An interview scorecard template with rating anchors, evidence notes and a completed example to help interviewers assess candidates consistently.
When two interviewers leave the same candidate conversation with completely different ratings, the issue is rarely candidate performance—it is a lack of evaluative calibration.
Without standardized evaluation criteria, one interviewer’s "3 out of 5" means "meets the bar," while another's means "failed the interview."
An interview scorecard standardizes candidate evaluation by anchoring numerical ratings to observable behaviors and requiring direct, evidence-based notes.
Below is a ready-to-use, copy-pasteable Interview Scorecard Template, followed by behavioral anchor guidelines, evidence documentation rules, and a fully filled-in example for a real-world role.
1. Standardized Interview Scorecard Template
Highlight and copy the template below directly into Google Docs, Microsoft Word, or your Applicant Tracking System (ATS).
Candidate & Interview Information
Candidate Name: [Candidate Full Name]
Target Role: [Job Title]
Interview Stage: [e.g., Technical / Behavioral / System Design]
Interviewer Name: [Interviewer Name]
Date: [MM/DD/YYYY]
Evaluation Rubric
Competency & Weight | Score (1-5) | Behavioral Anchor Summary | Smart Evidence Notes (Quotes, Metrics, Actions) |
Competency 1: [Name] Weight: [e.g., 30%] | [ ] | 1: No clear strategy or evidence. 3: Solid execution, minor gaps. 5: Exceptional, handles edge cases effortlessly. | Must include direct candidate quotes, specific actions, or past metrics. |
Competency 2: [Name] Weight: [e.g., 25%] | [ ] | 1: Fails to demonstrate basic skill. 3: Meets standard expectations. 5: Demonstrates high mastery and foresight. | Must include direct candidate quotes, specific actions, or past metrics. |
Competency 3: [Name] Weight: [e.g., 25%] | [ ] | 1: Reactive, blames external factors. 3: Takes ownership, resolves issue. 5: Proactively prevents future failures. | Must include direct candidate quotes, specific actions, or past metrics. |
Competency 4: [Name] Weight: [e.g., 20%] | [ ] | 1: Poor communication, unorganized. 3: Clear and structured communication. 5: Highly structured, compelling synthesis. | Must include direct candidate quotes, specific actions, or past metrics. |
Scoring Calculation & Recommendation
Hard Requirements Check:
[Pass / Fail] Right to work / Work authorization verified
[Pass / Fail] Core prerequisite requirements met
Overall Hiring Recommendation:
[ ] Strong Hire (4.5 - 5.0)
[ ] Hire (3.5 - 4.4)
[ ] Do Not Hire (2.5 - 3.4)
[ ] Strong Do Not Hire (1.0 - 2.4)
Overall Score Formula:
WeightedScore=(RatingCompetencyWeight)
Summary Justification:
[Provide a 2–3 sentence summary of why this candidate should or should not advance to the next round.]
2. Defining Behavioral Rating Anchors (BARS)
A major flaw in generic scorecards is using vague adjectives like "Poor," "Average," or "Great." Behavioral Anchored Rating Scales (BARS) replace subjective adjectives with observable, objective behaviors.
Anchoring a standard 1 to 5 rating scale requires clear operational definitions:
Score 1 — Strong No (Unacceptable): Gives irrelevant examples, relies on guesswork, or fails to show foundational understanding.
Score 2 — Leaning No (Below Bar): Answers lack depth, misses critical edge cases or trade-offs, and requires heavy prompting.
Score 3 — Meets Bar (Solid): Meets job expectations using structured approaches (e.g., STAR method) with clear personal ownership.
Score 4 — Exceeds Bar (Strong): Proactively explains edge cases, quantifies business impact, and clearly articulates trade-offs.
Score 5 — Exceptional (Expert): Demonstrates deep domain mastery, anticipates macro challenges, and introduces scalable framework solutions.
3. Recording Smart Evidence Notes
A scorecard rating without evidence is an opinion wearing a number. To make feedback actionable, defensible, and usable for team debriefs, interviewers should record Smart Evidence Notes based on observable facts rather than personal impressions.
Subjective Notes vs. Smart Evidence Notes
Evaluation Area | Vague Note (High Bias) | Smart Evidence Note (Audit-Proof) |
System Architecture | "Good understanding of infrastructure." | "Candidate explained splitting a monolithic payments service into microservices. Stated they chose Redis over Memcached specifically for data persistence during node restarts." |
Cross-Functional Leadership | "Seemed like a good culture fit and nice communicator." | "Candidate cited a project where Marketing and Engineering disagreed on scope. They organized a design sprint, prioritized 3 core features using a MoSCoW matrix, and shipped on time." |
Problem Solving Under Pressure | "Struggled under pressure." | "When asked about a failed release, candidate could not state what logs they checked or how they rolled back the deployment. Kept defaulting to 'the team handled it'." |
4. Completed Example: Senior Product Manager Scorecard
Below is an example of a completed scorecard for a Senior Product Manager position.
Interview Summary
Candidate Name: Jordan Lee
Target Role: Senior Product Manager (Growth)
Interview Stage: Product Strategy & Execution Deep Dive
Interviewer Name: Alex Rivera (VP of Product)
Date: 10/14/2026
Evaluation Summary
Competency & Weight | Score | Anchor Level Met | Smart Evidence Notes |
Product Strategy & Vision (Weight: 35%) | 4 | Exceeds Bar | “Used a moat-mapping framework for entering saturated markets. Emphasized retention loops over user acquisition, quoting: 'Acquisition is vanity if Day-30 retention is under 15%.' Quantified past strategy impact: Grew ARR by $1.2M in 8 months.” |
Data-Driven Decision Making (Weight: 25%) | 5 | Exceptional | “Walked through an A/B test failure where conversion dropped 4%. Identified a confounding variable (cohort seasonality) and re-segmented the data to isolate a +12% lift in high-LTV users.” |
Cross-Functional Execution (Weight: 20%) | 3 | Meets Bar | “Gave a standard STAR framework answer regarding engineering misalignment. Set up daily standups and clearer Jira specs. Resolved the conflict effectively, though the approach was standard.” |
User Empathy & Discovery (Weight: 20%) | 3 | Meets Bar | “Conducted 20+ user interviews for their last product rollout using continuous discovery habits. Could have elaborated more on how qualitative feedback directly altered the product roadmap.” |
Final Score Calculation
ProductStrategy:40.35=1.40
DataDecisions:50.25=1.25
Cross-Functional:30.20=0.60
UserEmpathy:30.20=0.60
Total Weighted Score: 3.85 / 5.00
Recommendation: [X] HIRE
Interviewer Summary:
"Jordan excels in data-driven strategy and execution. Strategy and metric skills are well above bar (4.0+). Communication is structured, clean, and backed by hard evidence. Cross-functional execution is standard but solid. Recommend advancing to final leadership round."
Frequently Asked Questions
What makes an interview scorecard legally defensible?
An interview scorecard is legally defensible when it evaluates candidates against job-related criteria, uses standardized behavioral rating anchors, and requires objective evidence (candidate quotes and observable behaviors) rather than subjective impressions.
How many competencies should be included on a scorecard?
A scorecard should evaluate 3 to 6 key competencies per interview stage. Rating fewer than 3 risks missing critical skills, while rating more than 6 causes interviewer fatigue and lowers feedback quality.
Should interviewers see each other's scorecards before the debrief?
No. Interviewers should fill out and submit their scorecards independently before reviewing other panel members' ratings or attending team debrief meetings to prevent confirmation bias and groupthink.