Why interviews should be prepared with more context
The interview works better when you arrive with evidence: targeted questions instead of improvising.
You know the scene. The room (or the Meet) open, the resume printed or on screen, and the same old questions: “Tell me about yourself,” “What’s your biggest weakness?”, “Where do you see yourself in five years?”. Thirty minutes later you walk out with a feeling more than a conclusion. You liked them. They speak well. They seem to know their stuff. And that impression, no matter how much experience you have, ends up weighing more than any data.
The problem isn’t the interview. The problem is showing up empty-handed. When you improvise, you end up assessing who communicates best under pressure, not who does the job best. And that’s exactly the opposite of what you need.
The interview isn’t to discover, it’s to confirm
There’s an ingrained idea that the interview is for “getting to know” the person from scratch. You go against the grain if you use it differently: the interview pays off far more when you arrive to confirm or rule out hypotheses you already have on the table.
If before sitting down you already know that someone showed strong signals in problem-solving but weaker ones in working under ambiguity, your conversation changes at the root. You stop asking filler questions and start asking what you actually need to find out.
What you lose when everyone asks the same questions
When each interviewer improvises, three things happen. First, the questions repeat across rounds and the candidate tells the same rehearsed story three times. Second, there are no common criteria: you and your colleague assess different things and then debate opinions, not observations. Third, the decision tilts toward whoever generated the best chemistry, which is rarely the same as who performs best in the role.
The antidote isn’t a rigid script. It’s arriving with evidence beyond the resume that tells you, per candidate, where to look more closely.
Targeted questions instead of generic ones
A generic question sounds like this: “Are you good at teamwork?”. Nobody says no. A targeted question sounds different: “In your assessment, the collaboration signal came out lower than individual execution. Tell me about the last time a project depended on coordinating with someone who didn’t report to you.”
The second question only exists because you arrived with context. You’re not accusing or closing anything: you’re opening the exact point where you have a real doubt. That’s what separates an interview that moves forward from one that just confirms likability. If you want to see how to build that kind of script, look at how to prepare the interview with evidence.
See what a report that tells you where to dig deeper before interviewing looks like.
See sample reportA single set of criteria for the whole panel
When several people interview the same candidate, the risk is that each one brings their own yardstick. Arriving with common criteria —the same combined competencies for the role, the same signals each person will dig into— doesn’t take judgment away from anyone. On the contrary: it turns the decision meeting into a conversation about what each person observed, not about who left the best impression.
That also speeds up the close. Instead of “I liked them,” you have “I probed this role fit signal and this is what they answered.” The team keeps the final decision, but makes it with backing instead of blindly.
Evidence first, intuition later (not the other way around)
Here’s the twist against habit: your intuition isn’t unnecessary, but it works better at the end than at the start. When you arrive with comparable signals across candidates, your experience is applied to data instead of to a first impression from the first two minutes.
Kokoro supports that part: it assesses before you interview, gives you reports to prepare the conversation, and applies integrity controls so the signals are reliable. It doesn’t make the decision for you or replace the panel’s judgment; it gives you something to arrive prepared with. You can see in detail what the product does and how it fits into your process.
In short
The generic interview decides by impression. The prepared interview decides with backing. To switch from one to the other you don’t need more meetings or more rounds, but more context before you sit down:
- Arrive with clear hypotheses per candidate, not filler questions.
- Define which signal you’ll dig into and why, before the conversation.
- Agree on common criteria for the whole panel.
- Let your intuition operate at the close, over evidence, not at the start.
The interview isn’t replaced: it’s respected by giving it the context it deserves.