Behavioural Interview Questions: The Complete STAR Method Guide 2026

Behavioural interview questions ask you to describe a specific situation from your past experience as evidence of how you would behave in the future. The underlying logic — called the behavioural prediction hypothesis — is that past behaviour is the best predictor of future behaviour in similar circumstances.

They almost always begin with one of these phrases:

• "Tell me about a time when you…"
• "Give me an example of a situation where you…"
• "Describe a time you had to…"
• "Can you walk me through a situation where…"

What makes them different from situational questions ("What would you do if…?") is that behavioural questions demand a real, specific story — not a hypothetical. Interviewers are trained to probe any answer that sounds general or theoretical until they get a concrete example. If you try to answer with "I would normally…" or "In general, I…" rather than a specific incident, a good interviewer will interrupt and redirect you to a real story.

Where behavioural questions appear in the process

Understanding when you will face behavioural questions helps you prepare efficiently. The typical graduate recruitment timeline looks like this:

At most Big Four and investment banking firms, the assessment centre interview is the stage where behavioural questions are most heavily used. You should expect 6–10 behavioural questions in a 45-minute structured interview — leaving roughly 4–5 minutes per answer.

The STAR method is the most widely taught framework for structuring behavioural interview answers. It stands for Situation, Task, Action, Result — four components that together produce a complete, credible, well-evidenced story.

Time allocation within a STAR answer

A well-structured STAR answer for a 4-minute slot runs roughly: 30 seconds on Situation, 30 seconds on Task, 2.5 minutes on Action, 30 seconds on Result and reflection. Practice this until the pacing feels natural — it is a skill that improves dramatically with repetition.

Every major employer has a published or implied list of competencies — the skills and behaviours they use as interview criteria. Tailoring your stories to explicitly address these competencies is what separates a good answer from a great one. Below are the core competency frameworks used by the most competitive graduate employers.

Universal competencies tested across all employers

Despite different branding, almost every graduate employer assesses eight core competency areas. Your story bank should include at least one strong example for each:

• Leadership — Taking initiative, influencing others, making decisions under uncertainty
• Teamwork & collaboration — Contributing to group success, managing conflict, supporting others
• Problem-solving & analytical thinking — Breaking down complexity, using data, creative solutions
• Communication — Adapting your message, presenting, influencing without authority
• Resilience & handling pressure — Performing under stress, bouncing back from failure, managing competing priorities
• Commercial awareness — Understanding business context, client/customer focus, strategic thinking
• Integrity & ethics — Doing the right thing, speaking up, maintaining standards under pressure
• Learning agility — Taking feedback, adapting quickly, seeking continuous improvement

The questions below appear consistently across Goldman Sachs, PwC, Deloitte, KPMG, EY, HSBC, JP Morgan, Amazon, Microsoft, and Barclays. For each question, the competency it tests is noted, along with a skeleton example answer structured in STAR format. Use these as a template — the specific details must come from your own experience.

Leadership & Initiative

Teamwork & Collaboration

Problem-Solving & Analytical Thinking

Resilience & Handling Pressure

Communication & Stakeholder Management

Commercial Awareness & Client Focus

Integrity & Values

Learning & Development

A story bank is a structured set of 8–12 detailed personal examples you prepare before your interview season, each of which can be adapted to answer multiple different competency questions. Without a story bank, you will find yourself improvising under pressure — which produces unfocused, poorly evidenced answers that interviewers score poorly.

How to build your story bank

Start by auditing your experiences across the following categories:

The story bank matrix

Once you have identified 8–12 experiences, map each one to the competencies it demonstrates. The goal is coverage: you want at least one strong story for each of the eight core competencies listed in Section 3, and ideally two stories for the most commonly tested ones (leadership, problem-solving, resilience).

How to make your stories stand out

The difference between a forgettable and a memorable STAR answer usually comes down to three things:

• Specificity over generality: "I managed a team of four engineers over six weeks" is always more credible than "I managed a team." Numbers, names, timelines, and concrete details signal that the story is real.
• Personal agency: The interviewer wants to understand what you did, not what happened to you or what the team decided. Use active verbs: "I identified", "I proposed", "I challenged", "I built", "I decided".
• Authentic difficulty: Interviewers are not impressed by stories where everything went smoothly. The best stories include a genuine obstacle, setback, or moment of uncertainty — and show how you navigated it. If your situation sounds easy, the competency being tested has not really been demonstrated.

Some behavioural questions are deliberately designed to be uncomfortable. Understanding why they are asked — and how to handle them — is what separates well-prepared candidates from those who stumble.

"Tell me about a time you failed"

This is the question most candidates handle worst. The two most common mistakes are: (a) choosing a failure that is not really a failure ("I worked too hard"), or (b) choosing a catastrophic failure and focusing on how bad it was rather than what you learned. The ideal answer picks a genuine failure — one where you made a real mistake with real consequences — and focuses 70% of the answer on what you did to address it and what you learned. Interviewers are not judging the failure; they are judging your relationship with failure.

"Describe a time you disagreed with your manager or a decision"

This question tests whether you have the courage to challenge upwards while maintaining a professional relationship. The answer must include: (a) how you raised the disagreement constructively, (b) evidence that you listened to their reasoning, and (c) how you either aligned or professionally escalated. Answers that suggest you simply deferred without expressing your view score poorly. Answers that suggest you went over your manager's head without first discussing it directly also score poorly.

"Give me an example of when you had a negative impact on a team or project"

A variation on the failure question that some interviewers use to probe self-awareness. Choose a real example where your action or inaction did cause a problem. Frame your answer around what you recognised, what you did to repair it, and what you changed in your behaviour as a result. Candidates who claim they have never had a negative impact — or pick a trivially minor example — signal low self-awareness, which is a red flag for senior interviewers.

When you have limited work experience

Graduate recruiters know most applicants have limited professional experience. Behavioural interview questions can be answered using examples from university, clubs, societies, volunteering, sports teams, and even part-time retail or hospitality work. What matters is the quality of reflection and the clarity of your personal contribution — not the prestige of the setting. A compelling story about resolving a conflict in a student society is more impressive than a vague story from a prestigious internship that does not clearly describe your individual role.

These mistakes appear repeatedly in candidate feedback from assessment centres at Big Four, investment banks, and large corporate graduate programmes. Avoiding them is as important as preparing good content.