Interviews

Behavioural Interviews: What They Test and How to Prepare

Behavioural interviews ask what you actually did in real situations, on the reasoning that past behaviour is better evidence than a description of yourself. Preparing for one means working out which qualities will be tested and collecting true stories that show them, including the uncomfortable ones.

Key points

  • Read the advert and any person specification for the qualities the employer names, because the questions are usually built from them.
  • Collect six to eight true stories, and note which qualities each one can show.
  • For a question about failure, choose a real mistake of your own and finish with what you changed afterwards.
  • For a question about conflict, describe the other person's position fairly and say how the disagreement ended.
  • If you have no example, say so and offer the nearest real one; do not invent a story.

A behavioural interview is built from questions about things you have done: "Tell me about a time when...", "Describe a situation where...", "Give me an example of...". Each question targets a quality the employer wants, such as teamwork or handling pressure, and your answer is the evidence.

You may also see it called a competency-based interview. Whatever the name, the preparation is the same: find out which qualities are being tested, and arrive with true stories that show them.

Why employers ask about past behaviour

A question like "How would you deal with an angry customer?" can be answered well by someone who has never met one. "Tell me about the last time you dealt with an angry customer" is harder to answer without having done it, and the interviewer can dig into the details.

Many employers also use these questions for consistency. In a structured interview, every candidate is asked the same questions and the answers are scored against written criteria, which is intended to make the comparison fairer. That has a practical consequence: the interviewer may take notes throughout, keep closely to a list and give little reaction. It is the format, not a judgement on you.

Not every question will be about the past. "What would you do if..." questions, often called situational, test your approach. Answer them directly and, where you can, add a real example that shows you have done something similar.

Work out which qualities will be tested

The questions usually come from the advert. Look in the requirements and any person specification for phrases about how the work is done, not only what is done: "works well under pressure", "builds relationships with suppliers", "takes ownership". The guide on how to read a job description shows how to pull these out.

Some employers, particularly large organisations and public bodies, publish a list of values or competencies and say that candidates are assessed against it. If you have been sent one, treat it as the syllabus.

Build a bank of stories

Six to eight stories are enough for most interviews, because one story can show several qualities. List yours in a table and note what each could be used for. This list belongs to Mateus Oliveira, a fictional customer support specialist.

StoryQualities it can show
Rewrote the refund help article after a spike in ticketsInitiative, customer focus, written communication
Disagreed with the team lead about a change to the weekend rotaHandling conflict, influencing without authority
Missed a promised call-back to a business customerOwning a mistake, learning, repairing a relationship
Trained three new starters during a product launch weekCoaching, prioritising under pressure
Organised the volunteer rota for a local food bankPlanning, reliability outside paid work

Include at least one story where something went wrong and one that involves a disagreement. If you are early in your career, stories from study, volunteering and part-time work count; the guide to finding your first job has more on drawing evidence from them.

Give each story a clear order using the STAR method: situation, task, action, result. Then keep the pairing loose. In the interview you choose the story that fits the question asked, which may not be the one you planned.

Questions about failure and mistakes

"Tell me about a mistake you made" tests whether you can be honest about an error and whether you learn from one. The choice of story matters most. Pick a mistake that was really yours, that had a real but limited cost, and that led you to change something.

Avoid the two extremes: a disguised success ("I took on too much because I care about quality") and an error serious enough to raise doubts about your judgement or honesty. Then tell it plainly: what happened, your part in it, how you put it right, what you do now.

Model answer on a mistake: Mateus Oliveira, customer support specialist

Last spring I promised a business customer a call-back by the end of the day about a billing error. Then I got pulled into a queue backlog and forgot. She rang the next morning, understandably annoyed, and my team lead took the call. That was my mistake: the promise was in my head and nowhere else. I phoned her back myself within the hour, apologised without excuses, and stayed on the line until the credit was applied. Since then, every promise I make goes into the ticket as a timed reminder before I end the call, and I tell the customer the time I've set. I haven't missed one since, and she asked for me by name when she upgraded her plan.

He names the mistake as his own in one sentence, spends more time on the repair than on the excuse, and ends with a habit that anyone could check.

Questions about conflict

Questions about disagreement test whether you can differ with someone and keep working with them. Choose a disagreement about the work, such as priorities, methods or deadlines, and not a clash of personalities. Describe the other person's view as they would recognise it.

Weaker

My team lead kept changing the rota without asking anyone, which was really unfair. In the end I went to her manager and it got sorted out.

Stronger

My team lead moved the weekend rota to a four-week pattern at short notice. I asked her for ten minutes and learned she was covering a gap left by two leavers. I suggested a swap board so that people could trade shifts, and offered to run it. She kept the new pattern, the swaps took most of the heat out of it, and I still run the board.

Why: The strong answer shows the candidate finding out the reason behind the decision, offering something practical and accepting an outcome that was not exactly what he wanted. The weak answer blames the team lead and ends with going over her head.

The outcome does not have to go your way. "We did it her way, and I was wrong about the risk" is a perfectly good ending if it is true.

Follow-up questions and missing examples

Expect probing: "What exactly did you say?", "What was your role, as opposed to the team's?", "What happened afterwards?". These follow-ups check the detail of the story and give you a chance to add what you left out. Answer with specifics, and if you cannot remember a detail, say so.

If you have never been in the situation described, do not invent one. Say that you have not, offer the closest real example and explain how it relates. "I have not managed anyone formally, but I trained three new starters last year" is an answer the interviewer can use.

Practise telling the stories

Tell each story aloud until it runs to about two minutes without notes. Ask a friend to choose questions at random, so that you practise matching a story to a question on the spot. The list in common interview questions is a good source.

After each real interview, add the questions you were asked to your notes. Over a job search the bank grows, and the same stories get easier to tell.

Common mistakes

  • Answering "Tell me about a time" with a general statement about how you usually behave, when the question asks for one specific occasion.
  • Preparing only success stories, then having nothing ready when asked about a failure or a disagreement.
  • Choosing a fake failure that is really a boast, which avoids the question and wastes the chance to show that you learn.
  • Blaming a colleague or manager in a conflict story, when describing their position fairly would have shown the quality being tested.
  • Inventing an example to fill a gap, which rarely survives the follow-up questions; offer the nearest true one.

Questions and answers

What is the difference between behavioural and situational questions?

Behavioural questions ask what you did in a real situation in the past. Situational questions describe a hypothetical and ask what you would do. Many interviews mix the two, and a real example strengthens an answer to either.

How many stories do I need to prepare?

Six to eight cover most interviews, provided they are varied: some about working with others, some about solving problems, at least one failure and one disagreement. Each should be usable for more than one question.

Can I use the same story twice in one interview?

Try not to, since a second story gives the interviewer more evidence. If the same event really is your best example for two questions, say so and focus on a different part of it the second time.

How far back can my examples go?

Recent examples are generally more convincing, so prefer the last two or three years where you can. An older story is fine if it is clearly your best evidence for a quality, especially after a career break or a change of field.

Why does the interviewer keep writing and not react to my answers?

In structured interviews, interviewers often record answers so that candidates can be scored against the same criteria afterwards. Some are also asked to stay neutral. It is usually part of the method and says nothing about how you are doing.