
Before: decide what you are measuring
Pick three to five competencies for the role, such as problem solving, communication, ownership and the specific technical area. For each one, write what a strong answer looks like. If you cannot, you will end up scoring whether you liked the person.
Ask the same core questions
Different questions for different candidates measure the questions, not the candidates. Keep a fixed core and let the follow-ups differ. The follow-ups are where you learn the most anyway.
Ask for evidence
- "Tell me about a time you did this" tells you more than "How would you do this?".
- When an answer says we, ask what the candidate did personally.
- When an answer stays general, ask for the specific case.
Follow-ups that work
- What made that hard?
- What did you consider and decide against?
- How did you know it worked?
- What would you do differently now?
Write down what was said
Note the candidate's words, not your conclusion. "Good communicator" cannot be checked later. "Explained the cache trade-off without being asked" can. Notes like that also protect the candidate from your mood on the day.
Score right away, one part at a time
- Score each competency separately, with the evidence next to it.
- Do it before the debrief, so the first loud opinion does not rewrite yours.
- If you have no evidence for a competency, write that down. It is not a low score.
Respect the candidate's time
Start on time, say how the hour is split, and leave five minutes for their questions. Candidates talk to each other about how they were treated.