An interview rubric is a shared scorecard. It tells interviewers what to look for and how to record evidence. Set it up before the first interview so each candidate is assessed against the same job requirements.
The example below covers five areas. Adapt them to the role. Use clear examples of what a good answer would show, and keep notes about the answer rather than your overall impression.
Build the scorecard before the interview
- List the tasks the person must be able to do.
- Choose a small set of job-related skills to assess.
- Write the main questions and permitted follow-up prompts.
- Agree what each score means for each skill.
- Have interviewers score answers on their own before discussing them.
The U.S. Office of Personnel Management’s structured interview guidance describes using consistent questions and rating standards. A scorecard supports that process; it does not make every judgment objective.
Use the team gaps before hiring playbook to describe what the current team needs. Then use the teamwork interview playbook to turn those needs into questions and evidence alongside the role’s other requirements.
A sample scoring scale
| Score | What the evidence shows |
|---|---|
| 1 — Below the requirement | The answer shows major gaps in the skill needed for this role. |
| 2 — Partly meets it | The answer shows some relevant skill, with important gaps. |
| 3 — Meets it | The example shows the skill at the level the role requires. |
| 4 — Strong evidence | The example shows sound work in a more demanding situation. |
| 5 — Very strong evidence | The example clearly exceeds the defined requirement for this role. |
| Not assessed | There is not enough evidence to assign a score. Record what is missing. |
These are starting labels. Add role-specific examples before using the scale. “Not assessed” is different from a low score. Do not fill an evidence gap with a guess about personality.
Category 1: Job knowledge and skills
Look for: relevant knowledge, a clear account of the candidate’s own work, and evidence that they can perform the required tasks.
- Describe a project similar to this role. What did you do?
- Which skill mattered most, and how did you use it?
- Tell us about a tool you had to learn. How did you check your work?
Follow up with “What was the result?” or “What would you change?” Separate the candidate’s contribution from the team’s overall result.
Category 2: Communication
Look for: the communication skills the job needs. These may include explaining a task, listening, asking useful questions, or writing clear notes.
- Tell us about a time you explained a complex idea to a new audience.
- Describe a misunderstanding at work. How did you address it?
- How did you check that the other person understood the next step?
Score the evidence against the role’s needs. Avoid treating speaking speed, accent, or personal similarity as a substitute for clear communication.
Your rapid TeamDynamics · two minutes
What makes your team tick?
Start with how your meetings work. Answer 12 quick questions for a first look at how your team communicates, makes decisions, and gets things done.
When we have team meetings…
Question 1 of 12 · Choose an answer to startCategory 3: Problem solving and adaptability
Look for: how the candidate defines a problem, checks facts, compares options, and responds when a plan changes.
- Describe a problem you had to solve with incomplete information.
- Which options did you consider, and why did you choose that one?
- Tell us about a plan that failed. What did you do next?
A polished success story is not the only useful evidence. Ask about trade-offs, mistakes, and what the candidate learned.
Category 4: Collaboration
Look for: job-related teamwork, such as sharing information, handling disagreement, and following through on commitments. Define these behaviors rather than scoring vague “culture fit.”
- Describe a disagreement about a project. What did you do?
- Tell us about a handoff that needed input from another team.
- How did you respond when a colleague needed something you could not provide?
Do not score whether someone’s personality matches the current team. TeamDynamics is for development and discussion, not for screening or ranking applicants.
Category 5: Professional judgment
Look for: how the candidate handles responsibility, sensitive information, and decisions within the role’s scope.
- Describe a time you spotted a risk or error. How did you raise it?
- Tell us about a request you could not safely or properly fulfill.
- When have you asked for guidance instead of making a decision alone?
Ask for examples without requesting confidential details from a previous employer. A candidate can explain their process without naming clients or sharing private records.
Record evidence, then compare
| Area | Score | Evidence from the answer | Follow-up needed |
|---|---|---|---|
| Job skills | 1–5 or not assessed | Task, action, and result | Missing evidence |
| Communication | 1–5 or not assessed | Example tied to the role | Missing evidence |
| Problem solving | 1–5 or not assessed | Options and trade-offs | Missing evidence |
| Collaboration | 1–5 or not assessed | Specific working behavior | Missing evidence |
| Professional judgment | 1–5 or not assessed | Decision and reasoning | Missing evidence |
Compare notes after each interviewer has scored the evidence. Discuss large differences and missing information. Use any weighting agreed before the interviews; do not change it to favor a candidate afterward.
Common mistakes to avoid
- Letting a strong first impression shape every score.
- Asking different core questions without a clear job-related reason.
- Giving a low score when the topic was never assessed.
- Rewarding a rehearsed answer without asking what the person actually did.
- Using personality labels or a vague sense of fit to rank people.
Keep the rubric tied to the job and review it with the people responsible for your hiring process. After someone joins, a separate conversation about team dynamics can help explain working agreements and support their development.
