People

Structured interviews: how to hire engineers with less bias

How to design a structured interview process for engineering roles: scorecards, consistent questions, independent scoring and debriefs that reduce bias.

· 6 min read

Unstructured interviews — a friendly chat that wanders wherever the conversation goes — feel insightful and predict job performance poorly. Research going back decades finds that structured interviews, where every candidate gets the same questions scored against the same criteria, are among the better predictors available. They are also fairer.

Start with a scorecard

Before posting the role, write down what the person must accomplish in their first year and the four to six competencies that requires: for example system design, code quality, debugging, collaboration and ownership. Define what weak, acceptable and strong look like for each. Every interview stage then tests specific competencies, and no competency is tested by nobody.

Same questions, same rubric

  • Each interviewer owns one or two competencies and asks a prepared question for them.
  • Behavioral questions ask about real past events: “Tell me about a time you found a bug in production that others had missed.”
  • Technical exercises resemble the work: reading and improving code, designing a small system, debugging.
  • Rubrics describe observable evidence for each score, written before the interview.

Score independently, then debrief

Interviewers write their scores and evidence before talking to each other. Otherwise the first or most senior voice in the debrief sets the anchor and everyone else adjusts. In the debrief, discuss evidence against the scorecard rather than impressions, and let the hiring manager decide with the reasons recorded.

Biases to design against

  • Affinity bias: liking people who remind us of ourselves. Rubrics make “I'd get a beer with them” irrelevant.
  • Halo effect: one impressive answer colors everything else. Independent scoring per competency limits it.
  • Confirmation bias: deciding in the first five minutes. Prepared questions keep you gathering evidence.
  • Culture fit as a veto: ask instead what the candidate would add to the team.

Measure the process

Track time to hire, offer acceptance rate and pass rates at each stage, and look for stages where some groups drop out more than others. Revisit questions that do not discriminate between strong and weak candidates. A hiring process is a system; it deserves the same iteration as anything else your team builds.

Quick check

3 questions from the related lessons. Answers are explained, and the ones you get right count towards your progress.

Question 1

Q1.20% of onsite candidates receive an offer and 50% of offers are accepted. How many onsites does one hire take?

Question 2

Q2.How many communication paths are there in a team of eight?

Question 3

Q3.An engineer keeps missing deadlines. It turns out nobody told them which of their four projects mattered most. What is the root cause?

Practice this in a lesson

Each engMBA lesson pairs a short explanation with practice questions that grade themselves. Free, with no signup.

See the full curriculum

Keep reading