# Interview Scorecard

> Design structured interview scorecards with competency-based questions and calibrated rating scales

- Skill: `uitbreidenos/interview-scorecard-2` (Agent Skill)
- Install (CLI): `npx skillmds@latest add uitbreidenos/interview-scorecard-2`
- Raw SKILL.md: https://api.skillmd.com/api/skills/uitbreidenos/interview-scorecard-2/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: UitbreidenOS (https://skillmd.com/u/uitbreidenos)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/uitbreidenos/interview-scorecard-2

---


## When to activate

- Creating interview scorecards for new roles
- Standardizing evaluation criteria across interviewers
- Building behavioral and situational question banks
- Calibrating interviewer ratings for consistency
- Reducing bias in interview assessments

## When NOT to use

- For technical coding assessments (use role-specific tools)
- For take-home assignment design
- For salary negotiation guidance

## Instructions

1. **Define competencies.** Extract 4-6 key competencies from the job description (e.g., system design, communication, leadership).
2. **Weight competencies.** Assign relative importance (1-3x) based on role level and team needs.
3. **Write behavioral questions.** 2 questions per competency using STAR format (Situation, Task, Action, Result).
4. **Create rating anchors.** 1-5 scale with clear behavioral descriptions: 1=no evidence, 3=meets expectations, 5=exceptional.
5. **Add probing follow-ups.** 2-3 follow-up prompts per question to dig deeper if initial answer is thin.
6. **Build calibration guide.** Example responses at each rating level so interviewers align on scoring.
7. **Generate scorecard template.** Formatted for print/digital with competency, question, rating, and notes columns.

## Example

```
Competency: System Design (Weight: 3x)
Q1: "Tell me about a system you designed that had to scale to 1M+ users."
  1: Cannot describe a system they've built
  3: Describes components, acknowledges tradeoffs
  5: Details architecture, load balancing, caching, failure modes, and measured outcomes

Follow-ups:
- "What would you change if you built it again?"
- "How did you handle data consistency?"
```