Most interviewers were never actually taught how to interview. They sat in a few themselves, absorbed a handful of habits — good and bad — and now run their own conversations on instinct. That's how you end up with three interviewers on the same panel asking three unrelated sets of questions, then arguing in the debrief because they weren't even evaluating the same thing.
This is a practical walkthrough for the interviewer's side of the table: what to do before the candidate arrives, how to structure the conversation, which questions actually predict performance, and how to score without letting gut feel quietly override the evidence.
Preparing Before the Candidate Arrives
Interview preparation means translating the job's real requirements into three to five specific competencies, writing one or two questions per competency in advance, and reading the candidate's background closely enough to ask informed follow-ups. Walking in with the CV open for the first time is the single most common way interviews go sideways.
Build a shared scorecard before the loop starts, not after. If two interviewers are covering different competencies, agree on the split explicitly — otherwise you'll get three people asking about teamwork and nobody probing the one technical gap that actually matters for the role.
Structuring the Interview Itself
A well-structured interview follows a clear arc: a short warm-up to settle nerves, core competency questions in a consistent order, room for the candidate's own questions, and a clear close on next steps. That shape takes the guesswork out of pacing and ensures you actually get through everything you planned to cover.
Aim for roughly 5 minutes of warm-up, 30-35 minutes of structured questioning, and 10 minutes reserved for the candidate to ask you things — their questions are themselves a signal worth scoring, not just a courtesy at the end.
An unstructured interview is a conversation. A structured interview is a measurement. Only one of those scales across a hiring panel.
The Four Question Types Worth Using
Behavioural, situational, technical, and motivational questions each test something different, and a balanced interview draws from all four rather than defaulting to one comfortable style. Relying only on hypothetical "what would you do" questions, for instance, rewards articulate improvisers over people with proven track records.
Behavioural questions
"Tell me about a time you had to..." questions rely on the idea that past behaviour predicts future behaviour better than a hypothetical answer. Push past the rehearsed opening line — ask what specifically the candidate did, not what the team did, and what the actual outcome was.
Situational questions
These present a realistic scenario the candidate hasn't lived through yet and ask how they'd approach it. They're useful for junior candidates without much track record, or for testing judgement on situations specific to your company that a candidate couldn't have prior experience with.
Technical questions
Direct skill checks — a system design walkthrough, a case study, a language test. These should map tightly to the actual work, and where possible be paired with a work-sample exercise rather than a purely verbal explanation of how the candidate would do the task.
Motivational questions
Why this role, why now, why this company — these surface retention risk more than they surface skill. A candidate who can't articulate why they want this specific job is a flight risk within the first year, regardless of how strong their technical answers were.
Taking Notes Without Losing the Conversation
Effective interview note-taking captures specific quotes and concrete examples in real time, while judgement and scoring happen only after the interview ends. Mixing the two — scoring an answer in your head mid-sentence — is exactly how first impressions quietly override everything that comes after them.
Write down what the candidate actually said, not your interpretation of it. "Led a team of six through a system migration" is a note; "seems like a strong leader" is a premature conclusion dressed up as one.
Scoring Candidates Consistently
Consistent scoring means rating each competency independently against the scorecard immediately after the interview, before comparing notes with other panelists or reading anyone else's scores. Discussing impressions before individual scoring locks in groupthink and erases the value of having multiple interviewers in the first place.
A semi-structured interview format gives you room to follow up on interesting answers while keeping the core scorecard identical across candidates — the format most hiring teams land on once they've tried both fully scripted and fully freeform approaches and found the middle ground works best.
| Interview style | Consistency across candidates | Best for |
|---|---|---|
| Unstructured | Low | Informal culture chats — not final hiring decisions |
| Semi-structured | Medium-high | Most hiring panels; scorecard core plus natural follow-up |
| Fully structured | Highest | High-volume roles, legal-sensitive hiring, large panels |
Common Mistakes That Undo Good Preparation
The most damaging interview mistakes are deciding in the first five minutes, letting one interviewer's strong opinion anchor the whole panel's debrief, and asking questions that test likeability rather than job-relevant competency. Any one of these can undo an otherwise well-prepared interview process.
Gallup's workplace research has repeatedly linked structured, competency-based interviewing to better quality-of-hire outcomes than intuition-led panels — the gap isn't about interviewer talent, it's about process discipline.
Running Panel Interviews Without Losing Structure
Panel interviews work best when each interviewer owns a distinct competency, agrees their questions in advance, and scores independently before any group discussion begins. Without that division of labour, panels tend to duplicate the same easy questions while nobody probes the harder, more diagnostic ones.
Assign a lead interviewer to manage pacing and introduce the candidate, but give every panelist real ownership of their section rather than a passive observer role. After the interview, collect written scores from each panelist before the group debrief starts — the moment someone speaks first and confidently, the rest of the panel tends to anchor toward that opinion whether or not it's the most accurate one.
Interviewing Over Video Without Losing Signal
Remote interviews require the same structure as in-person ones, plus a few adjustments — confirm the tech works before the call, watch for connectivity issues that unfairly penalise otherwise strong answers, and resist reading less engagement into a flat camera presence than you would a flat in-person one. Video changes delivery, not competence.
Send the candidate a clear agenda beforehand so they know what to expect and aren't wasting the first five minutes figuring out the format. And be honest with yourself about video fatigue on your own side — a fourth back-to-back video interview in one afternoon is not the moment to trust your gut on a close call; that's exactly when a scorecard earns its keep.
Where the Interview Fits in the Bigger Picture
The interview is only as good as the pipeline feeding it — a great structured process wastes its value if the candidates reaching it were poorly matched to the role in the first place. Sourcing quality and interview quality are two halves of the same hiring outcome, not separate problems.
This is where Yena fits upstream of the interview room: our Sourcer builds a shortlist explaining why each candidate matches the brief before a single interview slot is booked, so panels spend their structured process on genuinely relevant candidates rather than screening out mismatches that never should have reached the interview stage. Once a candidate clears the interview loop, keeping scorecards and notes inside a proper applicant tracking system — rather than scattered spreadsheets — is what makes the next hiring round faster than the last one.
If your ATS itself is the bottleneck, our best ATS for recruiters comparison is a reasonable next stop.
Handling the Candidate's Questions Properly
The candidate's questions at the end of an interview are a genuine evaluation opportunity, not a formality to rush through — thoughtful questions about the team, the mandate, or how success is measured signal real engagement with the role. Treat that segment with the same attention you gave your own prepared questions.
A candidate who asks nothing at all, or only asks about salary and holiday policy before anything about the actual work, is worth noting — not automatically disqualifying, but worth weighing against everything else you observed. Conversely, a candidate who asks sharp questions about how the team handles a specific kind of problem is often showing you exactly the kind of judgement you're trying to assess elsewhere in the interview.
Debriefing the Panel Without Groupthink
A well-run debrief has every interviewer submit independent scores before the group discussion opens, then works through disagreements point by point rather than settling on a vague overall impression. Skipping straight to "so, what did everyone think?" is how one confident voice quietly becomes the whole panel's verdict.
Where scores diverge sharply between panelists, that's valuable information, not noise to average away — dig into why one interviewer scored a competency high while another scored it low, since the disagreement often traces back to different definitions of what "strong" looks like for that competency, which is worth resolving for the next round of interviews too.
Bringing It Together
Conducting a strong interview comes down to three disciplines: prepare a scorecard before the conversation starts, ask a balanced mix of question types in a consistent order, and score independently before comparing notes with other interviewers. None of this requires charisma — it requires structure, and structure is trainable.