# Common behavioural interview questions and how to answer

By RoundAlpha team · Published 2026-09-11 · https://www.roundalpha.com/blog/common-behavioural-interview-questions

Behavioural interview questions ask for a real example from your past, because how you handled a situation before is the best guide to how you'll handle it again. Prepare six to eight true stories — a conflict, a failure, a deadline, a disagreement, an achievement, a weakness — and learn what each question is really testing, so you can pick the right story and tell it briefly.

## Key takeaways

- Every behavioural question tests one specific trait; name it before you pick a story.
- Six to eight well-prepared stories can cover almost every question you'll get.
- Keep the setup short and spend most of your answer on what you did.
- End with a result and what you learned, even when the story is about a failure.
- Use true, specific examples; vague or invented ones fall apart under follow-up questions.

## What is a behavioural interview question, and how do you answer one?

A behavioural interview question asks you to describe something you actually did in the past — usually starting “tell me about a time when…” — and the best answer is a short, true story: a little context, what you did, and the result.

The idea behind these questions is simple: the way you handled a real situation is a better guide to how you'll act in the job than any promise about what you would do. So the interviewer isn't looking for a perfect answer. They're looking for evidence, and a good interviewer will test it by asking what happened next, what you said, and what you'd do differently.

That's why the [STAR method](https://www.roundalpha.com/blog/the-star-method-that-actually-lands) — situation, task, action, result — is worth using: it stops you rambling. Our post on the STAR method covers how to keep it from sounding rehearsed. The part most people get wrong is the balance. The setup should take seconds, not a minute. The actions you took are the main event, and the result is what makes the story land.

Aim for about two minutes per answer. If the interviewer wants more, they'll ask — and a short, complete answer invites better [follow-up questions](https://www.roundalpha.com/blog/handle-interview-follow-up-questions) than a long, wandering one.

## What are the most common behavioural questions, and what do they test?

Most behavioural questions are variations on a small set of themes, and each theme is testing one thing. Before you answer any of them, ask yourself what the question is really testing: it's the quickest way to pick the right story and to know which part of it to spend your time on.

- “Tell me about a conflict with a colleague.” Tests whether you can disagree without damaging the working relationship.
- “Tell me about a time you failed.” Tests honesty, ownership, and whether you learn from mistakes.
- “Describe a time you worked to a tight deadline.” Tests how you prioritise when time runs short.
- “Tell me about a time you disagreed with your manager.” Tests whether you can push back respectfully and still commit to the final decision.
- “What achievement are you most proud of?” Tests what you value, and the size of the problems you've owned.
- “What is your biggest weakness?” Tests self-awareness, and whether you're actively working on it.
- “Tell me about a time you had to learn something quickly.” Tests how you approach the unfamiliar.
- “Describe a time you led without being in charge.” Tests influence and initiative.

## How do you answer “tell me about a conflict with a colleague”?

Pick a real disagreement about the work, not about personalities, and show how you understood the other side, found common ground, and kept the relationship intact.

A good outline: you and a colleague disagreed on how to approach a piece of work; you asked to talk it through and listened to their reasons first; you found what you both cared about, such as shipping on time without skipping testing; you agreed a plan together; the work shipped, and you still worked well together afterwards.

Avoid stories where the other person is simply wrong and you win. Interviewers are listening for whether you'd be easy to work with when you disagree, not whether you were right.

## How do you answer “tell me about a time you failed”?

Choose a real failure that mattered, own your part of it without blaming anyone else, and spend the second half of your answer on what you changed afterwards.

An outline that works: you missed something that had a real cost — an estimate that slipped, a bug you shipped, a stakeholder you didn't keep informed. You say plainly what your mistake was. You describe how you fixed the immediate problem. Then you explain the habit you changed so it didn't happen again, and, if you can, a later moment where that change paid off.

Don't pick a disguised strength, such as “I just cared too much”. It sounds evasive, and the interviewer will usually ask for a real failure anyway.

## How do you answer questions about deadlines or disagreeing with a manager?

For a deadline, show how you decided what mattered most; for a disagreement with a manager, show that you raised your concern with reasons and then committed to the decision.

Deadline outline: the time available suddenly shrank; you listed what had to be done and what could wait; you told the people affected early; you delayed the lower-priority work instead of cutting corners everywhere; you delivered what mattered on time.

Manager disagreement outline: you thought a decision was risky; you raised it privately, with evidence rather than opinion; you listened to their reasoning; then either they changed course, or you committed fully to their plan and kept an eye on the risk you'd flagged. Both endings are fine, as long as you don't describe going around your manager.

## How do you answer “what is your biggest weakness”?

Name a real weakness that isn't central to the role, and describe the specific steps you're taking to improve it.

For example: you used to take on too much yourself instead of asking for help early, which caused a late scramble on one project. Now you break work down at the start and raise risks at your first check-in. That answer is honest, shows self-awareness, and ends with action.

Keep it short. The weakness question is a check on honesty and self-awareness, not an invitation to list your flaws.

## How do you prepare enough stories without memorising scripts?

Write down six to eight true stories from your work, studies or projects, note which themes each one covers, and practice telling them out loud rather than memorising them word for word.

Scripts break the moment a question is phrased differently, while stories you know well bend to fit whatever you're asked. Work through these steps for each one:

1. List the situations you remember best: projects, problems, disagreements, mistakes and wins.
2. For each one, note the context in a line, what you did in three or four points, and the result.
3. Tag each story with the themes it could answer. One good story often covers conflict, deadlines and leadership.
4. Say each story out loud, timed, until it fits in about two minutes.
5. Ask someone to push you with “why?” and “what would you do differently?” after each one.

## Where can you practice behavioural questions out loud?

Practice with anyone who will listen and push back with follow-up questions — a friend, a colleague, a mentor or a practice interviewer — because answering out loud is a different skill from rehearsing in your head.

RoundAlpha's interviews include behavioural questions alongside questions about your CV, and the AI interviewer follows up when an answer is thin, so it's one way to find out which of your stories hold up before the real interview. The report gives a verdict on each question and one thing to change before your next attempt.

## Frequently asked questions

### How many stories should I prepare for a behavioural interview?

Six to eight true, well-understood stories are usually enough. A good story can answer several questions — a single project might show conflict, deadline pressure and leadership — so you don't need a separate story for every possible question.

### How long should a behavioural interview answer be?

About two minutes is a good target. Spend a sentence or two on the context, most of the time on what you did, and finish with the result. If the interviewer wants more detail, they will ask a follow-up question.

### Can I use examples from university or personal projects in a behavioural interview?

Yes. Early in your career, examples from coursework, internships, part-time jobs, clubs or personal projects are fine. What matters is that the example is real and shows the trait the question is testing.

### What if I don't have an example for a behavioural question?

Say so briefly, then offer the closest real example you do have and explain why it's relevant. Don't invent a story: invented answers tend to fall apart when the interviewer asks follow-up questions about the details.

### Should I say “I” or “we” in behavioural answers?

Say “I” when describing your own actions. Mention the team for context, but the interviewer is assessing what you personally did, so make your part clear.