Behavioural Interview Questions and How to Answer

Behavioural questions are the "Tell me about a time you…" family — and they make up a large share of most interviews because they work. The logic is simple: the best predictor of how you'll behave in a job is how you've behaved before. Hypothetical answers are easy to fake; real stories are much harder to invent on the spot.

That's also why they make people nervous. But behavioural questions are some of the most coachable in the whole interview, because they reward preparation more than quick thinking.

What they're really testing

Behind almost every behavioural question is a specific trait the interviewer wants evidence of: how you handle pressure, conflict, failure, leadership, ambiguity, or working with others. They're not looking for a perfect hero story — they're looking for self-awareness, judgement, and the ability to reflect. A messy situation you handled thoughtfully often lands better than a flawless one you narrate without insight.

The most common ones

You can prepare for the vast majority by having stories ready for these themes:

• Conflict: "Tell me about a time you disagreed with a colleague."
• Failure / mistakes: "Tell me about a time something went wrong" or "a time you failed."
• Leadership / initiative: "Tell me about a time you led something" or "took the lead without being asked."
• Pressure / deadlines: "Tell me about a time you worked under pressure."
• Problem-solving: "Tell me about a difficult problem you solved."
• Teamwork: "Tell me about a time you worked with a difficult person."
• Adaptability: "Tell me about a time priorities changed suddenly."

Notice these aren't really seven different questions — they're seven doors into your handful of real experiences.

The framework: STAR

Structure every behavioural answer with STAR so it stays specific and doesn't ramble:

1. Situation — one sentence of context.
2. Task — one sentence on what you needed to do.
3. Action — the bulk of the answer: what you specifically did. Use "I", not just "we".
4. Result — what happened, ideally measurable, plus what you took from it.

Keep the setup short and spend your time on the Action. End on a result and, where it fits, a brief lesson — that reflection is often what the interviewer is really listening for.

Build a story bank, not scripts

The efficient way to prepare isn't to write an answer for each of the seven questions above — it's to prepare six to eight real stories from your past and shape each with STAR. Choose varied ones: a success, a failure, a conflict, something you led, a tight deadline. Because most behavioural questions overlap, a strong bank of eight flexible stories can answer almost anything you're asked — you just pick the closest one.

Have a story ready for…	A real example from your past
A conflict you handled
A failure or mistake you owned
Something you led or initiated
Working under real pressure
A hard problem you solved
Working with a difficult person

Fill that table in with your own situations and you've done most of the work.

A worked behavioural answer

Here's one theme — handling pressure — turned into a full STAR answer, so you can see the shape end to end:

Question: "Tell me about a time you worked under significant pressure." Situation: "A week before a major client deadline, a colleague on the project went off sick, and their part wasn't finished." Task: "I had to get both their work and mine over the line without dropping the quality the client expected." Action: "I listed everything outstanding and split it into must-have and can-follow-later. I flagged the situation to my manager early with a realistic plan rather than waiting, picked up the critical half of my colleague's work myself, and moved two non-urgent tasks of my own to the following week so I wasn't spread too thin." Result: "We delivered the must-haves on time and the client never knew there'd been a wobble. What stuck with me was how much calmer it felt to triage and communicate early than to quietly try to do everything."

Notice the Action carries the answer and the Result ends on a brief, honest reflection. Two common mistakes to avoid: saying "we" so much that the interviewer can't tell what you did, and telling a story with no result — always land the plane on an outcome, even a modest one.

The step people skip

Even a well-built story bank can fall apart in the moment, because speaking a story is different from writing one. Under a little pressure, sentences wander and the "Result" gets lost. The only fix is to rehearse out loud — ideally with someone asking the questions cold, out of order, so you're recalling rather than reading.

If you want to practise that way without borrowing a friend every evening, Ofarwise is a Windows app that builds prep from your CV and the job description, then runs realistic mock interviews so you can drill your behavioural answers out loud and tighten them before the day. It's a free 14-day trial, then a one-time £49.99 pass for three months — one payment rather than another subscription. However you do it, the order is the same: build the stories, then say them aloud until they're smooth.