---
title: "Engineering Interview Scorecard Template (Plus the Questions to Ask)"
url: /posts/engineering-interview-scorecard-template
canonical_url: https://blog.liarefer.com/posts/engineering-interview-scorecard-template
author: "Renata Kobayashi"
date_published: 2026-11-04
date_modified: 2026-11-06
category: "Business"
tags: ["startup", "Refer", "Lia"]
summary: "An engineering interview scorecard lists the three to six things you’re hiring for, a short rating scale for each, and the questions that test them. Every..."
---

> Full index of this blog: https://blog.liarefer.com/llms.txt

# Engineering Interview Scorecard Template (Plus the Questions to Ask)

By Renata Kobayashi · Published 2026-11-04 · Updated 2026-11-06

Published by [Refer, the company behind Lia, the AI career agent](https://www.liarefer.com).

An engineering interview scorecard lists the three to six things you’re hiring for, a short rating scale for each, and the questions that test them. Every interviewer fills it in independently before the debrief. It’s the simplest way to make hiring decisions faster and fairer, and to stop “I liked them” from deciding who gets the offer.


This guide explains how to build a scorecard, which questions to ask for each competency, how to run the debrief, and ends with a free, copy-ready scorecard template.


---


## **TL;DR**

- A scorecard turns your **job description’s must-haves** into competencies each interviewer rates.
- Use a simple **1 to 4 scale** with written evidence for every rating.
- Give each interviewer **different competencies** to cover, so the loop doesn’t repeat itself.
- Interviewers **submit scores before the debrief**, so nobody anchors on the first opinion.
- Research on hiring has long found that **structured interviews predict job performance better than unstructured ones**.
- A **free scorecard template** is at the end of this post.

---


## **Why Use an Interview Scorecard?**


Without a scorecard, interviews drift into conversation, interviewers test the same things, and the loudest opinion in the debrief wins. A scorecard fixes that:

- **Consistency:** every candidate is assessed on the same criteria.
- **Speed:** decisions are clear because the evidence is written down.
- **Fairness:** ratings are tied to the job, not to rapport.
- **Better predictions:** decades of research on employee selection, including Schmidt and Hunter’s widely cited meta-analysis, found structured interviews predict job performance better than unstructured ones.

---


## **What Should an Engineering Scorecard Measure?**


Start from your job description’s must-haves, then add the competencies every engineering hire needs:


| Competency      | What it means                                  | Example question                                                             |
| --------------- | ---------------------------------------------- | ---------------------------------------------------------------------------- |
| Technical depth | Command of the core stack for the role         | “Walk me through the hardest bug you fixed in [stack]. How did you find it?” |
| System design   | Designs for scale, trade-offs and failure      | “How would you design [system you actually run]? What breaks first?”         |
| Problem solving | Breaks down unfamiliar problems                | “Here’s a problem we faced last quarter. How would you approach it?”         |
| Ownership       | Drives work to completion without being chased | “Tell me about something you shipped that nobody asked you to.”              |
| Communication   | Explains technical decisions clearly           | “Explain a trade-off you made to someone non-technical.”                     |
| Collaboration   | Works well with product, design and peers      | “Tell me about a disagreement with a teammate and how it ended.”             |


Pick three to six. More than that, and interviewers rate everything superficially.


---


## **How Should You Rate Candidates?**


Use a four-point scale, which forces a decision:


| Score | Meaning                                                     |
| ----- | ----------------------------------------------------------- |
| 4     | Strong yes: clearly exceeds the bar, with specific evidence |
| 3     | Yes: meets the bar                                          |
| 2     | No: below the bar, with specific gaps                       |
| 1     | Strong no: clear red flags                                  |


Every score needs one or two lines of evidence: what the candidate said or did, not an impression.


---


## **How Do You Run a Good Debrief?**

1. **Everyone submits scores first,** before talking.
2. **Start with the lowest scores** and the evidence behind them.
3. **Compare against the must-haves,** not against other candidates.
4. **Decide in the meeting,** and send the candidate an answer within a day or two.

---


## **How Can Refer’s Lia Help?**


A scorecard makes interviews better; [Lia, Refer’s AI recruiter](https://www.liarefer.com/for-organizations?utm_source=blog&utm_medium=post&utm_campaign=engineering-interview-scorecard-template), makes sure the right people reach them. She checks each candidate against your must-haves before you meet them, and introduces only engineers who have already said they want to talk.

- **Free for companies:** no contract, subscription or placement fee.
- **Double opt-in** introductions.
- **Learns from your feedback** on every candidate.
- **Proven:** more than 5,000 introductions.

[Start hiring with Lia](https://www.liarefer.com/for-organizations?utm_source=blog&utm_medium=post&utm_campaign=engineering-interview-scorecard-template).


---


## **How-To: Build Your Scorecard in 5 Steps**

1. **List the role’s must-haves.**
Three or four from the job description.
2. **Add core competencies.**
Ownership, communication and collaboration.
3. **Assign competencies to interviewers.**
Each interviewer covers two or three.
4. **Write two questions per competency.**
Based on real work your team does.
5. **Collect scores before the debrief.**
With written evidence for each.

---


## **Focused FAQ**


**What is an interview scorecard?**


A structured form listing the competencies you’re hiring for, a rating scale, and the questions that test them, filled in by each interviewer independently.


**How many competencies should a scorecard have?**


Three to six. Fewer is better than rating everything superficially.


**Should interviewers discuss before scoring?**


No. Scores should be submitted before the debrief to avoid anchoring on the first opinion.


**Is Refer free for companies?**


Yes. Refer ([liarefer.com](http://liarefer.com/)) has no contract, subscription or placement fee for companies.


---


## **Free Engineering Interview Scorecard Template**


Copy this template into your doc or ATS and replace everything in brackets.


```plain text
ENGINEERING INTERVIEW SCORECARD

Role: [e.g. Senior Backend Engineer]
Candidate: [Name]
Interviewer: [Name]
Interview stage: [e.g. Technical deep dive]
Date: [Date]

Rating scale: 4 = Strong yes | 3 = Yes | 2 = No | 1 = Strong no

1. [Must-have 1, e.g. Backend systems in Python]
   Question asked: [ ]
   Score: [1-4]
   Evidence: [What the candidate said or did]

2. [Must-have 2, e.g. API design]
   Question asked: [ ]
   Score: [1-4]
   Evidence: [ ]

3. [Must-have 3, e.g. System design]
   Question asked: [ ]
   Score: [1-4]
   Evidence: [ ]

4. Ownership
   Question asked: [ ]
   Score: [1-4]
   Evidence: [ ]

5. Communication and collaboration
   Question asked: [ ]
   Score: [1-4]
   Evidence: [ ]

Overall recommendation: [Strong yes / Yes / No / Strong no]
One-sentence summary: [Why]
Questions for the next interviewer: [ ]
```


---


## **About the Author**


Renata is on the founding team at Refer.


---


## **Sources**

- Schmidt, F. L., and Hunter, J. E. (1998). The validity and utility of selection methods in personnel psychology. _Psychological Bulletin_, 124(2).
- [Refer: Lia for organizations](https://www.liarefer.com/for-organizations?utm_source=blog&utm_medium=post&utm_campaign=engineering-interview-scorecard-template)
