A candidate answers every technical question. Their experience matches the role, the case study is strong and the panel likes them. Three months later, the team discovers a problem the interview never explored: the person avoids difficult feedback, waits too long to raise risk and becomes defensive when priorities change.
The interview tested whether the candidate could do the work. It did not test how they were likely to approach the work with other people.
That is the purpose of a behaviour round. It should not be an informal conversation about "culture fit" or a search for someone the panel would enjoy having lunch with. A useful behaviour round examines specific actions that matter in the role and scores every candidate against the same evidence.
Define behaviour before writing questions
Words such as ownership, collaboration and resilience sound sensible but mean different things to different interviewers. Translate each one into observable behaviour.
For a project manager, ownership might mean raising a dependency early, presenting options and following a decision through to closure. For a sales leader, it might include challenging an unrealistic forecast and helping a team learn from a lost deal. The same label can require different evidence.
Choose four or five behaviours that are necessary for the role. Avoid building a list of every quality an ideal employee could possess. For each behaviour, write:
- what good evidence would look like
- what weak or incomplete evidence would look like
- a question that asks for a real example
- one or two follow-up prompts
- a simple scoring guide
This preparation matters more than finding a clever interview question.
Five areas worth testing in many roles
Ownership
Ask: "Tell me about a problem you noticed before anyone asked you to solve it. What did you do, and where did you need help?"
Listen for the candidate's own actions, how they defined the problem and whether they involved the right people. Ownership is not the same as working alone.
Feedback
Ask: "Describe feedback you initially disagreed with. How did you respond, and what happened after that conversation?"
Strong evidence can include asking for an example, testing a change or explaining a disagreement respectfully. A polished claim that the candidate "loves feedback" tells you very little.
Ambiguity and judgement
Ask: "Tell me about a decision you had to make with incomplete information. What did you know, what was missing and why did you act when you did?"
Look for reasoning, awareness of risk and an ability to distinguish reversible choices from decisions that require more care.
Collaboration and conflict
Ask: "Give me an example of a disagreement that changed how the work was done. What was your position, and how did you handle the relationship?"
Do not score the absence of conflict as a strength. It may mean the candidate has worked in an unusually aligned team, or that they avoid disagreement.
Reliability under pressure
Ask: "Describe a period when several commitments competed for your attention. How did you decide what would move, and what did you communicate?"
Listen for prioritisation and early communication, not a heroic story about working every night.
Use a structured scorecard
Give interviewers a four-point scale with behavioural anchors. A score of one might mean the answer remains general or the candidate cannot separate their actions from the team's. A score of two may show a relevant example with limited reflection. A three can show clear action, reasoning and learning. A four should require strong evidence in a complex situation, not simply a confident delivery.
Ask each interviewer to record evidence before the group debrief. When the panel discusses first and scores later, the most senior or persuasive voice can shape everyone else's memory.
The scorecard should not make the decision automatically. It makes the reasoning visible. If interviewers disagree, they can compare evidence rather than impressions.
Do not turn behaviour into culture fit
"Culture fit" often rewards familiarity. A candidate may feel comfortable because they share the panel's background, humour or communication style. Another may appear reserved because the interview format is unfamiliar, not because they lack collaboration.
Keep the assessment tied to work. Ask the same core questions in the same order. Allow reasonable adjustments. Tell candidates what competencies the round will explore so that the process does not reward surprise performance.
Avoid questions that invite disclosure about health, family, religion or other personal matters unrelated to the role. Store notes carefully and follow the organisation's hiring and privacy requirements.
Where handwriting analysis may fit
Some organisations use handwriting analysis to add behavioural context before an interview or development conversation. If it is used, candidates should understand the purpose, the data being collected and how the result will affect the process.
The report should generate prompts, not a hidden pass-or-fail score. A theme around decision pace, response to pressure or communication might lead to a follow-up question. The candidate's answer and work evidence should carry the decision.
For example, an interviewer might ask: "Tell me about a time when waiting for more information improved a decision, and another when waiting created a problem. How did you judge the difference?"
Do not use graphology as the sole basis for hiring or rejection. Combine any assessment with structured interviews, relevant work samples, reference checks where appropriate and clearly defined role criteria.
A simple 60-minute behaviour round
Use the first five minutes to explain the structure and help the candidate settle. Spend about forty minutes on four role behaviours, leaving time for follow-up questions. Reserve ten minutes for the candidate's questions and five minutes to explain next steps.
One interviewer should lead each competency while another takes notes. More interviewers do not necessarily produce better evidence. A large panel can make the conversation harder without improving the decision.
After the interview, each person should submit their score and evidence independently. During the debrief, discuss major differences and identify any gap that requires another source of evidence. Do not add a new criterion because one candidate triggered a personal preference.
Review whether the round is working
After hiring, compare the interview evidence with the behaviours observed during onboarding. The goal is not to prove the interview was right. It is to improve the questions and scoring.
If a behaviour repeatedly surprises managers, the interview may be asking the wrong question or accepting rehearsed answers. If one group of candidates consistently scores lower, review whether the wording, examples or panel behaviour create an unnecessary barrier.
A good behaviour round becomes better through this feedback. It should remain a structured source of evidence, not a ritual added to the final stage.
Conclusion
Skipping the behaviour round leaves a predictable gap. Technical skill shows whether a candidate can perform the task; behavioural evidence helps you understand how they approach responsibility, feedback, uncertainty and other people. Define the behaviour, ask for real examples and score the evidence consistently. That makes the interview fairer and the hiring decision easier to explain.