STAR Method for Behavioural Interviews: Examples That Work

Behavioural questions start with "Tell me about a time when…". Interviewers ask them because past behaviour is a good predictor of future behaviour. A vague answer ("I'm good at handling conflict") tells them nothing. A specific story does.

The STAR method gives every story the same clear shape.

What STAR stands for

• Situation: the context, in one or two sentences. Where were you, what was going on?
• Task: your responsibility or the goal. What did you need to achieve?
• Action: what you did, step by step. This is the most important part; spend about half your answer here.
• Result: what happened, ideally with a number, and what you learnt.

Aim for one and a half to two minutes per answer.

Example 1: conflict with a colleague

Question: "Tell me about a time you disagreed with a teammate."

Situation: "On my last team, a senior engineer and I disagreed about how to handle failed payment retries. He wanted to retry immediately in the request; I thought that would overload the payment provider during outages."

Task: "I was responsible for the retry logic, so I needed us to agree on a design before the release two weeks later."

Action: "Instead of arguing in the code review, I asked for 30 minutes together. I pulled our logs from the last provider outage and showed that immediate retries had tripled traffic at the worst moment. I proposed a queue with exponential backoff and asked him to poke holes in it. He suggested a cap on total retries, which made the design better, and we wrote it up together."

Result: "We shipped on time, and during the next provider outage our retry traffic stayed flat and we recovered every payment within 20 minutes. We still use that design document as a template."

Example 2: a failure

Question: "Tell me about a time you failed."

Situation: "In my first year as an analyst, I sent a weekly sales report to leadership with a wrong currency conversion."

Task: "I owned the report, so I had to fix it and make sure it couldn't happen again."

Action: "As soon as I spotted it, I told my manager, sent a corrected version within an hour with a short note explaining what changed, and then added automated checks that compare each week's totals to the previous four weeks and flag big jumps."

Result: "The checks have caught two data problems since, before the report went out. I learnt to own mistakes quickly and to build checks rather than rely on being careful."

Pick a real failure with a real lesson, not a disguised strength.

Example 3: leadership without authority

Question: "Describe a time you led a project."

Situation: "Our onboarding drop-off was 40%, and no single team owned the problem."

Task: "I wasn't a manager, but I volunteered to coordinate a fix across product, design and engineering."

Action: "I set up a weekly 30-minute sync, mapped the funnel with our analyst to find the biggest drop (the KYC step), ran five user interviews, and proposed three small changes we could test in two sprints."

Result: "Drop-off at the KYC step fell from 40% to 26%, and the weekly sync became the onboarding team's regular meeting."

Common behavioural questions to prepare

1. Tell me about a time you disagreed with your manager
2. Describe a project that didn't go to plan
3. Tell me about a time you had to learn something quickly
4. Give an example of going beyond your role
5. Describe a time you handled a difficult customer or stakeholder
6. Tell me about a decision you made with incomplete information
7. Describe a time you received critical feedback
8. Tell me about your proudest achievement

Build a story bank

You don't need a new story for every question. Prepare six to eight strong stories covering conflict, failure, leadership, learning, a customer and a big win. Most questions can be answered with one of them, adjusted for the angle.

Write each story in STAR bullets, practise saying it aloud, and keep the numbers handy.

Mistakes to avoid

• Saying "we" throughout. Interviewers want to know what you did.
• Spending too long on the situation
• No result, or a result with no number or lesson
• Blaming others in conflict stories
• Made-up stories. Follow-up questions find out quickly.

Start your interview with a strong summary of yourself: see how to answer "Tell me about yourself". For engineering roles, also read the system design interview guide.