I use an interview evaluation form to capture evidence while the conversation is still fresh. The form is not a personality survey and it is not a place to record whether I liked someone. It should help the hiring team answer a narrower question: what did the candidate demonstrate against the requirements of this role?
What a usable form includes
I keep the form in the same order as the interview so the interviewer can complete it without jumping between sections:
- Candidate and role details
- Interviewer name, date, and interview stage
- Competencies or criteria being assessed
- Consistent questions or exercises
- Evidence notes for each criterion
- Anchored rating for each criterion
- Overall recommendation
- Risks, gaps, and follow-up questions
- Confirmation that the form is based on job-related evidence
The form should identify what was assessed in this interview. An interviewer should not be asked to score a competency they were never assigned or given a chance to observe.
Choose job-related criteria
I start with the outcomes of the role, then convert them into observable criteria. For a customer support role, that might be problem diagnosis, written communication, customer judgment, and process ownership. For an engineering role, it might be debugging, system design, collaboration, and delivery judgment.
I avoid criteria such as executive presence, culture fit, polish, or would I enjoy working with this person. Those labels can hide personal preferences. If the team needs clear communication, I name the behavior: explains a complex decision in a way the intended audience can act on.
| Criterion | What I look for | Question or exercise |
|---|---|---|
| Problem solving | Clarifies the problem, compares options, validates the result | Tell me about a difficult problem you diagnosed. |
| Ownership | Describes decisions, actions, and follow-through | Walk me through a deliverable you had to recover. |
| Collaboration | Handles disagreement and keeps work moving | Describe a decision you made with a partner who disagreed. |
| Role-specific skill | Applies the required method to realistic work | Complete a representative work sample or scenario. |
Use an anchored rating scale
I prefer a four-point scale because it prevents the middle rating from becoming an automatic safe choice. The labels matter less than the written anchors. I define them before interviews begin.
| Rating | Meaning | Evidence standard |
|---|---|---|
| 4 | Strong evidence | The example is relevant, specific, and shows the level needed for the role. |
| 3 | Sufficient evidence | The candidate meets the role expectation with a credible example. |
| 2 | Mixed or incomplete evidence | The example is relevant but has a meaningful gap, or the level is unclear. |
| 1 | Insufficient evidence | The candidate did not demonstrate the criterion or gave evidence below the requirement. |
| N/O | Not observed | This interviewer did not assess the criterion. |
I do not turn an N/O into a low score. It means the panel needs another source of evidence. I also require a short explanation for a rating of 1 or 4 so extreme scores are connected to something observable.
Capture evidence, not impressions
During the interview, I write short notes using the candidate's actions, context, and result. A useful note might say, "Explained how they isolated a billing error by reproducing the issue, checking logs, and testing a fix with finance." A weak note says, "Very sharp."
I ask interviewers to separate facts from interpretation:
- Evidence: What did the candidate say, do, or produce?
- Interpretation: What does that evidence suggest about the criterion?
- Open question: What still needs to be tested?
Notes should not include protected personal information, guesses about family or health, comments about accent or appearance, or details unrelated to the job. If a candidate volunteers sensitive information, I leave it out of the evaluation unless a documented process requires otherwise.
Add bias controls to the workflow
The form helps only when the process around it is disciplined. I ask interviewers to submit feedback independently before the panel discussion. I hide earlier ratings where the tool allows it, use the same core questions for comparable candidates, and keep the scorecard visible during the interview.
I also add a reminder at the top: rate the evidence against the criterion, not the candidate against another person. After submissions are complete, the recruiter checks for unexplained score changes, criteria that nobody assessed, and comments that rely on vague fit language. The hiring manager owns the decision, but the recruiter protects the process.
Copyable interview evaluation form
INTERVIEW EVALUATION FORM
Candidate:
Role:
Interview stage:
Interviewer:
Date:
Criterion 1:
Question or exercise:
Evidence observed:
Rating: 1 2 3 4 N/O
What supports this rating?
Criterion 2:
Question or exercise:
Evidence observed:
Rating: 1 2 3 4 N/O
What supports this rating?
Criterion 3:
Question or exercise:
Evidence observed:
Rating: 1 2 3 4 N/O
What supports this rating?
Strongest evidence:
Unresolved concern or gap:
Suggested follow-up question:
Recommendation: Strong advance / Advance / Hold for more evidence / Do not advance
Recommendation rationale:
I based this evaluation on job-related evidence from this interview.
Make the form useful after the interview
I set a submission deadline while the evidence is fresh, then review feedback for completeness before the debrief. A form is working when another interviewer can understand the recommendation without being in the room. If the team cannot tell which requirement was tested or why a rating was chosen, I revise the question, anchor, or field instead of asking interviewers to write longer opinions.