Interview preparation guide

How to Answer Behavioural Interview Questions

Behavioural interview questions ask you to describe what you actually did in a past situation. Employers use them because past behaviour gives evidence of how you may act in a similar future role. The interviewer is not only listening for a good story. They are testing judgement, ownership, communication, problem solving, teamwork, leadership, resilience, and self awareness.

These questions often begin with phrases such as: Tell me about a time when, give me an example of, describe a situation where, or how did you handle. A strong answer gives a specific example, explains your role, describes your actions, and shows the result.

Core idea: A strong behavioural interview answer is specific, relevant, recent, and structured. Use the STAR method to explain the Situation, Task, Action, and Result, but make sure most of the answer focuses on what you personally did.

1. Understand what behavioural questions are testing

A behavioural question is not asking whether you believe you are a good communicator, leader, or problem solver. It asks for evidence. The interviewer wants to see how you behaved when there was pressure, ambiguity, conflict, responsibility, or a measurable outcome.

For example, if the question is about teamwork, the interviewer is not looking for the sentence I work well in teams. They want to know what the team was trying to achieve, what problem appeared, what role you took, how you acted, and what changed because of your action.

Weak answer: I am a strong team player and I always communicate well with colleagues.

Stronger answer: In my final year project, our team was falling behind because the testing work was not clearly assigned. I proposed a shared task board, split test cases by component, and set up two short check ins each week. As a result, we completed the test plan before the deadline and reduced duplicate work.

2. Use the STAR method

The STAR method gives your answer a clear structure. Situation explains the context. Task explains your responsibility or goal. Action explains what you personally did. Result explains the outcome and what you learned.

The most common mistake is spending too long on the Situation and Task. MIT Career Advising suggests that a strong behavioural answer should place most emphasis on Action. That is because the interviewer is mainly assessing your behaviour, not the background story.

STAR structure:

  • Situation: What was the context?
  • Task: What responsibility or goal did you have?
  • Action: What did you personally do?
  • Result: What happened, what changed, and what did you learn?

3. Choose one specific story

Behavioural answers fail when they become too general. Do not answer with what you usually do. Answer with one situation. A specific story gives the interviewer evidence and makes your answer easier to believe.

For instance, instead of saying that you often manage deadlines well, describe one project where the deadline was at risk. Explain the competing tasks, how you prioritised, what trade off you made, and what the final result was.

Question: Tell me about a time you had to manage competing priorities.

Weak answer: I usually make a list, prioritise the most important tasks, and communicate with people.

Stronger answer: During my internship, I had to prepare a client report while also fixing a data issue in the dashboard. I spoke with my manager to confirm which output had the nearest business impact, blocked two hours for the dashboard fix, and then reused the cleaned data for the report. Both tasks were delivered on time, and the team avoided presenting inaccurate numbers.

4. Build a story bank before the interview

You do not need a new story for every possible question. A small set of strong stories can be adapted to many questions. Prepare six to eight examples across the main competency areas.

For example, one project story may answer questions about teamwork, leadership, conflict, communication, and problem solving. The key is to frame the same story differently depending on what the interviewer asks.

Useful story bank categories:

  • Teamwork and collaboration.
  • Leadership and initiative.
  • Conflict or disagreement.
  • Problem solving under pressure.
  • Failure, mistake, or setback.
  • Adaptability and learning.
  • Communication with a difficult audience.
  • Time management and prioritisation.

5. Match the story to the competency

Before answering, identify the competency behind the question. A question about conflict is not only asking whether you resolved disagreement. It may be testing emotional control, communication, negotiation, accountability, and respect for others.

For example, a question about failure should not become an excuse. It should show self awareness, responsibility, learning, and changed behaviour.

Question: Tell me about a time you made a mistake.

Strong answer direction: Choose a real but recoverable mistake. Explain the context briefly, take responsibility, describe the corrective action, show the result, and end with the system you now use to avoid the same mistake.

6. Focus on your personal action

Interviewers need to know what you did, not only what the team did. Use I for your own actions and we only when describing shared context. This is especially important in group projects, internships, research projects, and committee work.

For example, instead of saying we solved the problem, explain whether you diagnosed the issue, wrote the analysis, coordinated the team, spoke with the client, redesigned the process, or checked the final result.

Weak answer: We worked together and completed the project successfully.

Stronger answer: I noticed that our requirements were unclear, so I drafted a one page summary of the assumptions, asked the client to confirm the priorities, and then updated the task list for the team. That reduced rework and helped us deliver the prototype on schedule.

7. Quantify the result when possible

A result is stronger when it is observable. This can be a number, deadline, quality improvement, customer response, grade, efficiency gain, reduced error rate, stakeholder decision, or lesson learned.

Not every result needs a large metric. If you cannot quantify the result, explain the practical effect. For example, the team adopted your process, the client approved the report, the defect was resolved, or the group avoided a delay.

Weak result: The project went well and everyone was happy.

Stronger result: We submitted the report two days before the deadline, reduced the number of unresolved issues from twelve to three, and the manager used our analysis in the client presentation.

8. Answer difficult behavioural questions honestly

Some behavioural questions ask about failure, conflict, criticism, or difficult people. Do not choose a fake weakness or blame others. The safest answer shows responsibility, proportionate judgement, and changed behaviour.

For instance, when discussing conflict, avoid attacking the other person. Explain the disagreement, your communication approach, the compromise or decision, and what the outcome was.

Question: Tell me about a time you had a conflict with a teammate.

Strong answer: In a group project, one teammate wanted to add more features while I was concerned that the core functions were not stable. I suggested that we list the must have requirements and compare them with the time remaining. We agreed to freeze new features for one week and fix the core issues first. The final prototype was less ambitious, but it was reliable enough for the demonstration.

9. Keep the answer concise

A behavioural answer should be detailed but not rambling. A practical target is one to two minutes. If the interviewer wants more detail, they will ask a follow up question.

You can control length by keeping the background short and giving more space to Action and Result. The answer should not become a full project history.

Simple timing guide:

  • Situation: twenty seconds.
  • Task: ten to fifteen seconds.
  • Action: forty to sixty seconds.
  • Result: twenty seconds.

10. Adapt answers to the role

The same story should be framed differently for different roles. Read the job description before the interview and identify the behaviours the employer is likely to test. These may include customer focus, ownership, analysis, leadership, inclusion, stakeholder management, resilience, or attention to detail.

For example, if the role requires client communication, emphasise how you clarified expectations and communicated progress. If the role requires technical problem solving, emphasise diagnosis, evidence, trade offs, and validation.

Same story, different focus:

  • For teamwork: emphasise coordination and shared delivery.
  • For leadership: emphasise initiative and decision making.
  • For problem solving: emphasise diagnosis, options, and result.
  • For communication: emphasise audience, message, and feedback.

11. Prepare for follow up questions

Interviewers often probe the story after your first answer. They may ask what you would do differently, what you learned, how others reacted, why you chose that action, or how you measured success.

This is why you should use real stories. If the story is invented or exaggerated, follow up questions become difficult to answer consistently.

Possible follow ups:

  • What was your exact role?
  • Why did you choose that approach?
  • What was the hardest part?
  • What feedback did you receive?
  • What would you do differently now?

12. Avoid common mistakes

The first mistake is giving an opinion instead of an example. The second mistake is using a story where your role is unclear. The third mistake is spending too long on background. The fourth mistake is ending without a result. The fifth mistake is using the same story too many times without adapting it to the question.

For example, if the interviewer asks about leadership, do not only say that the group succeeded. Explain what leadership action you took, why it mattered, and what changed.

Bad answer pattern: I am good at X. In one project, we had a problem. It was difficult. We worked hard. It ended well.

Better answer pattern: The problem was X. My responsibility was Y. I took actions A, B, and C. The result was Z. I learned or changed my approach in this way.

13. Prepare common behavioural interview questions

Practise the questions below aloud. For each question, select one story, write a short STAR outline, and practise the answer without memorising a script.

14. Final preparation checklist

Before the interview, check whether you can clearly answer these points:

Practise behavioural interview questions with MockBase

Reading examples is useful, but behavioural interviews test whether you can tell clear, specific stories under pressure. Use the Behavioural Interview Practice App to practise STAR answers, build a story bank, and prepare for follow up questions.

Open Behavioural Interview Practice App View more MockBase guides

Related guides

How to answer behavioural interview questions How to answer academic job interview questions How to prepare for a faculty interview How to prepare for a grant interview Common PhD viva questions and how to answer them

Preparation sources

This guide was informed by career guidance on behavioural interviews, competency based interviews, and the STAR method from MIT Career Advising and Professional Development, the UK National Careers Service, Imperial College London Careers Service, Dartmouth Guarini School of Graduate and Advanced Studies, and Harvard Extension School Career Services.