How to build interview questions from the evaluation

To build your questions, sort each signal from the report into two groups: confirm and explore. Where the candidate shows a solid signal, prepare a question that asks for a real example. Where the signal is weak or ambiguous, prepare an open-ended question to explore live. With that, you leave each report with three or four written questions specific to that person, instead of the same generic questionnaire as always.

Most interviews are prepared poorly for a simple reason: they’re prepared without information. With nothing to look at beforehand, you end up asking everyone the same three textbook questions (“what’s your greatest weakness?”) and leaving the room with the same feeling as always — that of not being sure of anything. Evaluating before interviewing changes that starting point: you arrive at the conversation knowing what to confirm and what’s left to resolve.

The report is raw material, not a verdict

Before turning the report into questions, it helps to be clear about what it is. An evaluation report gathers comparable signals about how the candidate reasons and solves problems, plus integrity controls that provide context. It’s evidence beyond the résumé. It’s not a sentence that decides for you: the team keeps the final decision, and the interview is still where it’s closed.

If you want the detail on how to interpret each block, we break it down in how to read an evaluation report. Here we take the next step: going from reading it to writing questions.

Confirm vs. explore: the method

Take each relevant signal from the report and ask yourself just one thing: do I take this as a given, or do I verify it?

• Confirm. Where the signal is strong, don’t assume it: ask for it in their own voice. “The report suggests you organize work well under pressure — tell me about the last time you had three deliverables on the same day.” If the evidence has real backing in their experience, you’ll notice it in the example.
• Explore. Where the signal is weaker or ambiguous, don’t discard: explore. “Tell me about a situation where you had to coordinate people who didn’t report to you.” A weak competency may be a lack of exposure, not a ceiling.

From signal to question: examples

It works better with concrete cases. Some patterns you can reuse:

1. Strong signal in a critical competency. Ask for a behavioral example: “Tell me about a real situation where…”. You’re looking for past behavior, not opinion.
2. Low signal in an important competency. Open the door without judging: “How have you handled it when…?”. You’re looking for context before concluding.
3. Interesting contrast. Strong in one thing, weak in a related one. Ask about the tension: “When you had to be both fast and thorough, what did you prioritize?”.

For questions focused on specific competencies, we have a dedicated guide in what to ask in a competency-based interview.

Keep a common core so you can compare

Here’s the balance that matters: if every interview is completely different, you can’t compare candidates with sound criteria. The solution is mixed. Define a core of questions that are the same for everyone, anchored in the role’s critical competencies, and let each person’s report give you the follow-up questions.

That way you get the best of both worlds: comparability across candidates and depth where each one requires it. It’s the same logic of evaluating everyone against the same yardstick, brought into the conversation.

Mistakes when building the questions

• Not writing anything down. If the questions stay in your head, you improvise. Leave each report with three or four written down.
• Turning a low signal into a rejection. It’s a question, not a conclusion.
• Asking opinion questions. “Do you consider yourself organized?” doesn’t help. “Tell me about…” does.
• Personalizing everything and leaving nothing comparable. Without a common core, you lose the basis for deciding.

In short

Read the report, sort each signal into confirm or explore, and write three or four questions per candidate: ask for the strong ones with a real example, explore the weak ones with an open-ended question. Keep a common core for everyone and personalize only the follow-up. That way the evaluation doesn’t replace the interview: it makes it more focused. If you want to see the full flow, check out how to prepare the interview with evidence or the detail of the product.