By Byte Bright, the team behind Ace That Interview · Last updated October 2026
Behavioural questions are the ones that start with "Tell me about a time when…". They are not a memory test, and they are not looking for a perfect story.
They are checking two things: whether you can think in a structured way, and whether you have really done the work you claim to have done.
Most interviewers are working from a list of things the role requires — problem solving, handling disagreement, working to a deadline, taking initiative. Each behavioural question is mapped to one of those, and they are usually ticking a box as you speak.
This is why a well-told story about a small situation beats a vague claim about a big one. "I led a transformation programme" tells them nothing they can score. "I had four weeks and two people to rebuild a reporting process; here is what I cut and what I kept" gives them something to assess.
Question lists vary by employer, but the underlying capabilities do not. Almost every behavioural interview draws from a shortlist like this one, whatever the wording on the day.
| The question | What it is really testing |
|---|---|
| A time you handled a difficult customer or stakeholder | Composure, and whether you de-escalate or escalate |
| A time you made a mistake, and what you did next | Accountability — do you own it, or explain it away |
| A time you had to meet a tight deadline | Prioritisation, and what you chose to drop |
| A time you disagreed with someone more senior | Judgement and professionalism under pressure |
| A time you had to learn something quickly | How you learn, not how fast you claim to |
| A time you improved a process rather than just running it | Initiative, and whether you notice waste |
| A time you had to deliver bad news | Clarity and honesty when it is uncomfortable |
| A time you worked with someone difficult | Collaboration, and your part in the friction |
Notice that none of these are really about the situation. The interviewer is using the situation to get at a decision. If you describe what happened without describing what you chose, you have answered a different question.
You will see this called STAR: Situation, Task, Action, Result. It works, but people usually get the proportions wrong — they spend 80 per cent of the answer on the situation, then run out of time for the part that matters.
| Part | What it does | Roughly how long |
|---|---|---|
| Situation | One or two sentences of context. Enough to make the rest make sense. | 10% |
| Task | What you specifically had to do. Make clear what was yours. | 10% |
| Action | What you did, in order. This is the part they score. | 60% |
| Result | What happened, and what you would do differently. Ideally with a number. | 20% |
The Action section is where most answers collapse. Say what you decided, not what the team did. If you used a particular method, name it. If you had to choose between two options, say what you chose and why.
Aim for about ninety seconds to two minutes, and treat two minutes as a ceiling rather than a target. That is long enough to include a situation, your decision and a result, and short enough that the interviewer can still remember the beginning when you reach the end. The most common failure is not a short answer but a long one: candidates spend a minute and a half on background, then compress the part being scored into two rushed sentences. If you consistently run over, cut the context first — the interviewer needs roughly one sentence to understand where you were and what was at stake. Everything after that should be you, deciding and doing. If your example genuinely needs more time, say so and offer to summarise first; interviewers usually welcome the structure.
Behavioural questions ask about the past — "tell me about a time when". Situational questions ask about a hypothetical — "what would you do if". They are testing different things, and the mistake is answering one as if it were the other. For a behavioural question, only something that actually happened counts as an answer; describing what you would do is not evidence, however sensible it sounds. For a situational question, the interviewer wants to hear your reasoning applied to their scenario, so reciting an old story answers a question that was not asked. Listen for the tense: "have you done" and "tell me about a time" are past; "would you" and "how would you handle" are hypothetical. When you are unsure which was asked, answer the past first and then add one sentence on how you would approach it next time.
You do not need fifty stories. Six or seven real situations will cover almost every behavioural question you will be asked, if you pick them well.
Write two or three sentences for each, then rehearse saying them out loud. Out loud matters: most people are surprised by how different their answer sounds when spoken, and by how quickly they lose the thread.
Use study, volunteering, family responsibility, sport, part-time or casual work — the setting does not have to be a job, as long as the story is real and you were the one making the decision. A group assignment where you had to chase three people who were not contributing is a genuine example of managing a deadline and a disagreement, and it scores the same as an equivalent story from an office. Retail, hospitality and shift work are particularly strong sources, because they are full of competing priorities and difficult customers. What does not work is inventing a workplace example or stretching a team achievement into a personal one; interviewers probe with follow-up questions, and a story that collapses under a second question is worse than a modest one that holds. Depth beats prestige: one small story told precisely is stronger than a grand one you cannot detail.
Generic behavioural question lists are useful for building your stories, but the questions you will actually be asked are shaped by the advert. If a listing says "work with ambiguous requirements", you can be almost certain you will be asked about a time the requirements were unclear.
That is what Ace That Interview does: it reads a real job advert and produces behavioural and technical questions aimed at that advert, then scores your spoken or typed answers and shows you a stronger version of what you said.
It varies by employer, but most interviews that use them devote somewhere between a third and a half of the time to behavioural questions, and it is common to be asked four to six. The practical implication is that a handful of well-prepared stories covers the whole interview, so preparation effort goes further here than almost anywhere else.
Often yes, if you change what you emphasise. One incident can demonstrate prioritisation and also handling pressure. What does not work is telling the identical story in identical words twice, because the interviewer is listening for a different capability each time and will notice that nothing new was offered.
Pick a more recent one, or one you remember precisely. The interviewer is scoring the specificity of your decision-making, not the size of the situation. A small example you can describe in detail beats an impressive one you can only summarise.
Yes, if you need one, and it costs you nothing. Saying "let me think of the best example" and taking five seconds reads as considered. Starting to speak before you have chosen the story is what produces the rambling answers that score badly.
They are often most of what an entry-level interview consists of, because there is little technical ground to cover. For those roles the evidence comes from study, part-time work, volunteering or sport rather than from a career.