Build Fair and Consistent Interview Scorecards

Interview Scorecard Builder helps create structured candidate evaluation forms. It organizes assessment around role-related competencies, behavioral questions, observable indicators, scoring descriptors, evidence notes, and an overall recommendation. Guidance covers using the STAR method to elicit Situation, Task, Action, and Result, with follow-up probes to understand the candidate's contribution.

A scorecard can include technical assessments such as a coding exercise, system design discussion, technical questions, or portfolio review. The guidance recommends asking consistent questions, recording specific examples, scoring after each competency discussion, and calibrating interviewers. It also includes a framework for separating evidence from assessment and tracking how scorecards perform over time.

Use this skill when designing a consistent interview process for a specific role. It can help interview teams define what each competency means, what evidence to collect, and how to distinguish levels of demonstrated behavior.

Do not use generic thresholds, sample weights, or labels as an automatic hiring decision. The role examples and scores are templates, not validated predictors of performance. Do not assess vague "culture fit" or unrelated personal traits; Use job-related criteria and avoiding discriminatory questions. Hiring criteria and record retention rules vary by jurisdiction and organization, so have the process reviewed by qualified HR and legal owners. Scores should support structured discussion rather than replace human review.

Inputs include the job responsibilities, role requirements, competencies to assess, interview stages, question set, evidence standards, scoring method, and decision process. Include a "not assessed" option for competencies that were not tested. Define observable descriptions for each level and allow interviewers to record examples supporting their ratings.

The output is a role-specific scorecard with candidate and interview details, competency definitions, questions and probes, behavioral indicators, evidence notes, and a recommendation section. Technical roles may include assessment methods and criteria. A weighted summary can be used only when its method is agreed and understood. It training interviewers, calibrating ratings, gathering feedback, and reviewing the scorecard as roles evolve.

Guidance covers Markdown scorecards, YAML examples for role competencies, interview panels, reference checks, and hiring workflows. It does not name a required applicant tracking system or assessment platform. Teams may store scorecards with their hiring records under approved access and retention controls.

This skill is for recruiters, hiring managers, and interviewers who need a shared evaluation structure. It helps teams focus on evidence tied to role requirements and apply the same process across candidates. Review criteria with HR, train interviewers, and document decisions consistently.

# Interview Scorecard: [Role Title]

**Candidate:** ________________  **Date:** ________________
**Interviewer:** ________________  **Interview Type:** ________________