Getting More From Interviews
An interview is your best — and often only — chance to gather decision-grade data about whether a person will make your team stronger. Not "did I enjoy the conversation," not "did they pass a point-in-time skills check" — but will this person raise the bar for years?
What a great interview actually produces
Most interviews underperform not because the interviewer is bad, but because they're optimized for the wrong outcome. A great interview gives you evidence, not impressions — enough that you could walk into a debrief and defend your assessment with specifics.
| Low-value outcome | High-value outcome |
|---|---|
| "They seemed smart and easy to talk to." | "They navigated an ambiguous decision by weighing three options, chose the one with the best risk profile, and quantified the outcome." |
| "Good vibes — I think they'd fit in." | "They demonstrated ownership of a cross-team failure and articulated specific changes they made to how they work." |
| "They knew the tech stack we use." | "They showed judgment on when not to use their favorite tool, and learned a new one in 2 weeks when the situation called for it." |
| "I walked out feeling unsure." | "I walked out with three specific examples and a clear read on how they operate under pressure." |
Point-in-time skills vs. long-term contribution
Here's the shift that changes everything: you're not hiring for what someone can do today. You're hiring for what they'll contribute over the next several years.
| What decays or changes | What compounds over time |
|---|---|
| Specific tech stacks | Judgment under uncertainty |
| Current domain knowledge | Ownership and accountability |
| Framework-specific expertise | How they collaborate and influence |
| "Can they do this exact task" | Learning velocity — how fast they level up |
| Today's tooling | How they handle failure and feedback |
A strong interview process over-indexes on the right column. That's where the long-term value of a hire actually lives — and it's also the column that's hardest to fake in a 45-minute conversation unless you know how to probe for it.
What good interviews have in common
Three non-negotiables:
- Structured. Same questions, same evaluation criteria, every candidate. Structure is what makes signal comparable across candidates and across interviewers.
- Behavioral. Anchor on what the candidate actually did in real situations, not what they would do in hypothetical ones. Past behavior is the best predictor of future behavior — full stop.
- Calibrated. Everyone on the loop knows what "meets the bar" looks like before the interviews start, not after.
Miss any one of these and you're back in vibe territory.
Obstacles that get in the way
Even well-intentioned interviewers fall into predictable traps. Knowing them is the first step to working around them:
| Trap | What happens | Why it costs you |
|---|---|---|
| No structure | Every interviewer asks different questions | No way to compare candidates fairly |
| Confirmation bias | Form an opinion in the first 5 minutes, then hunt for evidence to support it | You stop collecting signal — and miss strong candidates |
| Halo effect | One great answer inflates every subsequent rating | You over-index on a single data point |
| Leading questions | "You're good under pressure, right?" | You get the answer you telegraphed, not the truth |
| Recency bias | The last candidate feels sharper than the first | Unfair calibration across the loop |
| Similarity bias | Favor candidates who remind you of yourself | Homogeneous teams, missed talent |
The goal of this workshop is simple: give you the tools to walk out of every interview with specific, defensible evidence — so your debrief is a conversation about data, not a vote on who seemed nicest.
Exercise: Spot the trap
Read each scenario and identify which trap is in play — and what the interviewer should have done instead.
Scenario 1: An interviewer opens with "I see you went to MIT — I did too!" and spends 10 minutes reminiscing about campus life.
→ Similarity bias. A shared background creates an unearned positive impression before a single question is asked. Better: acknowledge the connection in one sentence and move straight into the structured questions. Treat this candidate the same way you'd treat one with zero overlap.
Scenario 2: A candidate gives a mediocre answer to the first question. The interviewer mentally writes "no hire" and spends the next 45 minutes on easy questions, half-listening.
→ Confirmation bias. The interviewer decided early and stopped collecting signal. Better: treat every question as independent. A rocky start doesn't predict the rest of the interview — candidates often warm up, and you owe them (and your team) a fair read.
Scenario 3: The interviewer asks: "We move really fast here. Can you keep up with a fast-paced environment?"
→ Leading question. The expected answer is baked in. Better: ask for evidence. "Tell me about a time you had to ship something under a tight, externally-imposed deadline. What did you do?" Now you'll learn something real.
Reflect: Think of the last interview you conducted or sat in on. Which of these traps, if you're honest, showed up? What would you do differently next time? (Write it down — you'll come back to it at the end of the workshop.)
What's the most valuable thing a great interview produces?
Why should you weight judgment, ownership, and collaboration over current tech-stack expertise?
An interviewer loves a candidate's answer to question 3 and rates all subsequent answers higher than they deserve. Which trap is this?