A rating can be settled in the first few minutes of an interview, by a warm opening or a company on the resume the interviewer respects, and then the rest of the hour goes on collecting reasons for it. The scorecard from that hour reads like evidence and holds a first impression with quotes attached.
Most interview best practices cover what to do in the room, from preparing the questions to following up on the answers. I agree with them, and I think they skip the place where good interviewers pull away from the rest, which is what they do at the moments their instinct speaks up.
My position is that a gut read is a question to test, and a good interviewer spends the rest of the interview testing it. Below are the moments, from the resume read to the scorecard, where instinct is most likely to mislead, and the habit I’d put in place of each one.
Why a structured interview still lets instinct in.
A first impression can turn into a score without anyone deciding that it should, and a structured interview still leaves it room.
Instinct forms from cues that say little about the job. A warm opening or an employer you rate on the resume can start a verdict forming before the first question that tests anything.
Once it forms, the rest of the interview tends to get read through it. A vague answer from a candidate you like sounds modest, and the same answer from one you don’t sounds evasive. Follow-ups get gentler for the first and sharper for the second, and the scorecard records the difference as though the candidate produced it.
The cost lands in the debrief. A hiring manager reading that scorecard sees a rating and a few quotes, with nothing to show whether the answers earned the rating or the first five minutes did.
The usual answer is a structured interview, where every candidate hears one set of questions in one order. I’d keep the structure, and I don’t think it’s enough on its own, because instinct works inside the structure. An interviewer can ask the approved question word for word and still accept a thin answer from the candidate they warmed to. The craft sits in a handful of moments when instinct pulls hardest, and they’re predictable enough to plan for.
Before the call, decide what would change your mind.
Two decisions you make before the candidate joins leave a first impression less room to work: how you read the resume, and what you’ll accept as a strong answer.
Read the resume for questions.
Instinct usually starts with the resume, often the day before the interview. A famous employer or a fast promotion reads as proof, a gap or an unfamiliar company reads as a warning, and both are guesses about a person you haven’t spoken to.
Read it with a pen. For each thing that impresses or worries you, write a question for it: what the candidate owned at the employer you respect, what they did in the year that looks empty. The impression then has a job in the interview, and the candidate’s answer replaces it.
Set the bar for each question before you meet the candidate.
Decide what a strong answer to each of your questions would have to contain while the candidate is still a resume. Once you’ve met them, a bar written afterward has a way of landing wherever they did.
Your team’s rubric should supply most of that bar. A separate guide covers writing rubric levels from real candidate answers.
Keep interview best practices when instinct pulls the other way.
Four moments turn up in most interviews, and each has a habit that keeps the interview gathering evidence while your instinct makes its case.
When the first few minutes go well.
A warm, articulate start is the strongest pull an interviewer feels, and it tends to soften everything after it. The same goes for a candidate who reminds you of yourself, or of a great hire you once made. Write the impression down as one line in the margin, marked as a guess (“confident, already likes the team”), so it sits on the page where you can check it later instead of in your head, where it colors the next answer.
Then ask the first evidence question exactly as you would of anyone, and give it the same depth of follow-up. The candidate you like is the one most likely to get an easy interview, and an easy interview gives the debrief nothing to rely on. For teams with many interviewers, there’s a guide to calibrating a whole bench on one recorded interview.
If the story sounds right, ask whose story it is.
A fluent story about a project that went well feels like evidence, because it has a problem and a happy ending, and often most of it is about what the team did. Listen for “we,” then ask which decision was theirs and what they argued for that the team didn’t want. A candidate who owned the work answers quickly and in detail, and one who watched it happen tends to drift back to the team’s result.
Wait out the pause after a hard question.
Notice which candidates you feel like rescuing when they fall silent, because the help usually goes to the one your gut has already picked. Wait the same length of time for everyone, and if you rephrase the question, rephrase it the same way for anyone who stalls on it.
Save the pitch for the end.
Liking a candidate pulls an interviewer into selling the role and the team, sometimes in the middle of an answer. Every minute of pitch is a minute of evidence you won’t get back, and the candidate learns which answers you were hoping for.
Keep the pitch for the last few minutes, after the questions you came to ask, and keep the closing time equal for every candidate. Selling the job is part of interviewing, and at the end of the call it can no longer shape the answers.
After the call, test the gut call against your notes.
The impression you parked in the margin gets its hearing once the call ends, while the conversation is still fresh and before anyone else’s view reaches you.
Write the gut call down, then argue with it.
Straight after the call, before you look at your notes, write one line: the rating you’d give if you had to decide now, and why. Then set it aside. Work through your notes competency by competency and mark the candidate’s words that bear on each one, before you choose any rating.
Now compare the two. Where the notes support the gut call, you’ve spent five minutes confirming it. Where they don’t, the rating follows the notes, and the gut call becomes a question for the next interviewer instead of a score. A competency the hour never reached goes to the next interviewer the same way, unrated.
Where Metaview fits in interviewer craft.
The test after the call is only as good as the notes it runs against. Notes typed during an interview carry the gut read too, and an instinct checked only against the interviewer’s memory of the call is being checked by the one witness it has already persuaded.
For a team that records its interviews, the Metaview Notetaker gives that test a better witness than memory. On a recorded call it is one of the visible participants, and it leaves a transcript and structured notes behind. Metaview captures every spoken word, so your gut line meets the candidate’s own answer instead of your recollection of it. Which interviews are recorded at all is settled between your team and each candidate.
Metaview also drafts a scorecard from the interview. Write your gut line before you open that draft, then edit it and set every rating yourself. The hiring recommendation is always the interviewer’s to complete.
The Metaview Assistant helps with the story that sounded right. Ask it about the candidate’s own part in the project, and it recalls the details they gave. For their exact words, open the transcript.
Siadhal Magos treats interviewing as a skill in its own right:
Interviews are vital when building an exceptional team, and being an effective interviewer is a highly-valued skill. But there is so little data available to leaders about these crucial moments.”
He was writing about leaders, and the same gap faces each interviewer. A skill improves with feedback, and an interviewer rarely learns which of their ratings a first impression wrote.
Read back your gut lines before the next interview.
The gut lines you write after each call tell you more as a set than one at a time, because a set shows which cues fool you.
Before your next interview, read the last month of them beside the ratings you submitted. Where a gut line and a rating parted, look at what the gut line was reacting to. If one cue keeps fooling you, such as a warm start or a familiar employer, that’s the moment to slow down next time: write the impression down, then give that candidate your hardest follow-up first.
A talent acquisition lead can take the same habit into the debrief by asking each interviewer to bring their gut line along with their submitted rating, so the room hears where first impressions and evidence parted before it argues about the candidate.
Instinct will keep speaking up, and it’s often right about the next question to ask. At the score, craft replaces it.
Settle a hunch about a candidate with the interview record.
See how the Metaview Assistant answers a question about a captured interview with the specific details a candidate gave.
Frequently asked.
Should you ever trust your gut in an interview?
Trust it to notice things, and turn what it notices into your next question. A sense that something is off often comes from a real cue, such as an answer that skipped the part you asked about. Ask about that part directly, and rate the answer you get.
What if a nervous candidate makes a bad first impression?
Handle it the way you would a good one: write it down as a guess and ask your evidence questions at full depth. Nervous candidates often settle after a question or two, and an interviewer who has already decided stops asking for the detail that would have shown it.
Is it fair to mark down a candidate who says “we” instead of “I”?
Mark nothing down for the word itself. Plenty of people say “we” out of habit or modesty, and some company cultures expect it. Treat it as the cue to ask which decisions were theirs, and rate what they tell you.
How can a new interviewer practice these habits?
Shadow an experienced interviewer and write your own gut line and ratings without seeing theirs, then compare after the call, including where each of you changed your mind. Then run interviews with them shadowing you. While you shadow, a list of the habits that separate good and bad interviewers gives you more to watch for than instinct alone. Turning habits like these into a program for the whole team is the work of an interviewer training process.
