The STAR method: how to answer behavioural interview questions (6 examples)

The proportions matter more than the labels. Most weak answers spend a minute on the background and ten seconds on what the candidate actually did. Nobody needs to hear the letters out loud; the structure just keeps you on track.

Many employers run structured interviews: every candidate gets the same questions, and each answer is scored against the same criteria, often a competency such as ownership, collaboration or customer focus. The interviewer listens for specific evidence of that behaviour. Vague or hypothetical answers score low, however polished they sound.

Behavioural questions also come with follow-ups: “What exactly was your role?”, “How did you measure that?”, “What would you do differently?” A real story survives that probing. A borrowed or inflated one usually doesn’t, which is why the details of your answer should all be things you can expand on.

1. Pick the story. Recent (ideally the last two or three years), relevant to the job, and one where you personally made a difference.
2. Set the scene in one or two sentences. Only the context the listener needs: your role, the team, the problem.
3. Define your task. What you were responsible for and why it mattered: a deadline, money, customers, safety.
4. Walk through your actions. Three or four concrete steps, using “I”, with the reasoning behind the key decision.
5. Land the result. Numbers if you have them (time, money, quality, customers), otherwise a concrete outcome, plus a sentence on what you learned.
6. Say it out loud and time it. About two minutes is a good target. If it runs long, cut the situation first.

A fill-in template for your notes (don’t memorise it word for word):

Situation: "In [month and year], at [company], [the problem in one sentence]."
Task:      "I was responsible for [goal], and it mattered because [stakes]."
Action:    "First I [step]. Then I [step], because [reason]. Finally I [step]."
Result:    "As a result, [measurable outcome]. Since then, I [what you learned or changed]."

You don’t need a different story for every question. Six to eight good stories, chosen to cover different competencies, will answer most behavioural questions. Go through your CV bullets and pick the ones with the most going on: a problem, a decision, a measurable outcome.

Write each story as four short lines of notes, one per letter, with the numbers you’ll quote. For the questions typically asked in your field, our interview questions by job pages list them with answer outlines, for example for a project manager or a software engineer.

Each of these runs about one and a half to two minutes when spoken. The details are invented; the structure is the part to borrow.

1. “Tell me about a time you made a mistake.” (software engineer)

“Last spring I shipped a change to our checkout service that passed every test but broke payments for customers of one older banking app. It was my change, so fixing it and making sure it couldn’t happen the same way again was my job. I rolled it back within 20 minutes of the first alert and told the support lead what had happened so her team could reply to customers. The next morning I reproduced the bug and found that our test data didn’t include that bank’s response format. I added it, wrote contract tests for our five most common payment providers, and wrote up the incident for the team, including my part in it. We lost about 40 transactions, which support recovered by email. The new tests have since caught two similar problems before release.”

Why it works: it owns the mistake in the first sentence, shows fast action, fixes the cause rather than the symptom, and proves the lesson stuck.

2. “Tell me about a difficult customer.” (customer success manager)

“One of our largest accounts, a logistics company worth about $120,000 a year, told us at a renewal call that they planned to leave because our reporting was too slow. I owned the account and the renewal. Instead of a sales call, I asked for a working session with their operations lead and watched how they used the reports. The real problem was a daily export that took them an hour to clean. I set up a scheduled report that did the cleaning for them, took the issue to our product team together with three other customers who had the same complaint, and checked in every week until the renewal date. They renewed for two years, and the scheduled export became a standard feature the next quarter.”

Why it works: the action is specific and starts with understanding the problem, and the result has both a customer outcome and a wider one.

3. “Tell me about a time you worked to a tight deadline.” (project manager)

“Three weeks before a regulatory deadline, our vendor told us the reporting system migration would be a month late. As project manager, I had to get us compliant on time without the full release. I listed the eight reports the regulator required and found that five could run on the old system with small changes. I agreed with our compliance lead to prioritise the other three, negotiated with the vendor to deliver those first, and moved two analysts onto testing so we didn’t wait for a full test cycle. I sent the steering group a one-page status note twice a week. We filed all eight reports two days early, and the full migration finished five weeks later without further disruption.”

Why it works: the candidate breaks a big problem into a smaller one, and every action has a reason.

4. “Tell me about a conflict with a colleague.” (nurse)

“On a busy surgical ward, a night-shift colleague and I kept clashing over handovers. I felt details were being missed, and she felt I was questioning her judgement. Handover affects patient safety, so I needed to fix the process without damaging the relationship. I asked to talk at the end of a quiet shift, away from the desk. I started with what I valued in her work, then gave one specific example where a missed detail had delayed a patient’s pain relief. We agreed to try a short structured checklist for a month, and I offered to draft it with her rather than for her. Our ward manager later adopted the checklist for the whole ward, and the two of us worked well together from then on.”

Why it works: the colleague isn’t the villain, the candidate takes the first step, and the result helps more than the two people involved.

5. “Give an example of influencing without authority.” (data analyst)

“Our marketing team was planning its budget around a dashboard that counted returning visitors twice. I wasn’t on their team and couldn’t change their plan, but I owned the data, so I needed them to trust a corrected number. Rather than sending a correction by email, I rebuilt the metric next to the old one and walked their lead through three real customer journeys where the double count happened. I suggested running both numbers side by side for a month so they could see the difference themselves. After two weeks they switched to the corrected metric and moved about 15% of their budget from retargeting to new-customer campaigns. They now ask me to review metrics before planning starts.”

Why it works: it shows persuasion through evidence rather than authority, and the result changed a real decision.

6. “Tell me about a time you took the initiative.” (sales development rep)

“When I joined as a sales development rep, new inbound leads waited about two days for a first reply. Nobody owned response time, but I thought it was costing us meetings. I pulled three months of data from our CRM and showed that leads contacted within an hour booked meetings at roughly three times the rate of those contacted after a day. I proposed a rota where one rep covered new leads each morning, tested it myself for two weeks, and presented the results at our team meeting. Average first response fell to under an hour, and our team’s booked meetings rose by about a quarter that quarter. The rota is still running.”

Why it works: the candidate spots a problem nobody owned, tests the fix before asking others to change, and quantifies the outcome.

• CAR (Challenge, Action, Result) and PAR (Problem, Action, Result) merge the situation and task into one opening line. They suit phone screens, short answers and written application questions.
• STARL (STAR plus Learning) adds what you took from the experience. It’s the natural shape for questions about failure, feedback or mistakes.

The labels matter less than the principle behind all of them: brief context, detailed actions, a clear result. Use whichever version keeps your answer focused.

• Too much situation. A minute of background before you mention what you did. Cut it to two sentences.
• “We” instead of “I”. The interviewer can’t score your team. Say what you did, and give others credit briefly.
• No result, or a vague one. “It went well” isn’t a result. Give a number, a decision that was made or a concrete change.
• Hypothetical answers. “I would…” in reply to “Tell me about a time…” scores poorly. If you have no work example, use the closest real one from study, volunteering or a side project.
• A villain. In conflict stories, describe the other person fairly. How you talk about colleagues is part of what’s being assessed.
• A recited script. Memorise the points and the numbers, not the sentences, or you’ll sound like you’re reading.

For each story, prepare one extra layer of detail: the exact numbers, who else was involved, and one thing you’d do differently. If an interviewer asks for a detail you don’t remember, say so. A guess that falls apart under the next question costs more than an honest “I don’t remember the exact figure, but it was roughly…”.

Practise out loud, not in your head. Record yourself on your phone, check the timing, and listen for how often you say “we”. Pair STAR stories with a clear answer to the opening question too: our guide to “tell me about yourself” covers that, and our guide to “what is your greatest weakness?” shows how to handle the question that most often needs a STAR-style example. Have a few questions to ask at the end ready as well.

Your stories should match your CV, because interviewers often pick bullets from it to ask about. The free CV score checker shows how your CV reads against a specific job ad, and after the interview, the thank-you email generator helps you send a short note that mentions one detail from the conversation.