The STAR Method: How to Answer Behavioural Interview Questions

A behavioural interview question asks you to prove a skill with a story. "Tell me about a time you disagreed with a teammate." "Describe a time you missed a deadline." The interviewer is not asking what you would do. They are asking what you did, because what you did last time is the best evidence they have of what you will do next time.

The STAR method is the standard way to tell that story so it lands. This guide covers what each part is for, three worked examples with a weak and a strong version side by side, the mistakes that come up again and again, and a routine for practising until it is automatic.

What STAR stands for

• Situation: the context. Where you were, when, and who was involved. One or two sentences.
• Task: what needed doing and why it mattered. The goal or the problem that was yours to deal with.
• Action: what you personally did. This is the part the interviewer is grading, so it should be the longest.
• Result: what happened because of it, ideally something concrete, and what you learned.

A useful rule of thumb: spend about a quarter of your answer on the Situation and Task together, about half on the Action, and the rest on the Result. A strong spoken answer usually runs somewhere between one and two minutes. Under a minute tends to be thin; well past two minutes, the interviewer starts waiting for you to get to the point.

Three worked examples

The answers below are examples we wrote to show the shape. The details are invented. Read the weak version first and try to name what is missing before you read the notes.

Example 1: "Tell me about a time you missed a deadline."

Weak answer:

"Yeah, so this happens to everyone, right? At my last job we had a lot going on and there was a report that was due on Friday and it was just really busy. We ended up being a few days late. But I think it was fine in the end and I learned to manage my time better."

What is wrong with it: the Situation is vague ("a lot going on"), there is no Task, the Action is missing entirely, and the Result ("it was fine") is not an outcome. "I learned to manage my time better" is the line every interviewer has heard a hundred times. It also opens by minimising the failure, which reads as defensive.

Strong answer:

"In my first year as an analyst, I owned the monthly sales report for our regional managers, due on the first working day of the month. In March, two of our data feeds broke in the same week, and by Wednesday I knew I would not have clean numbers by Friday. My job was to get the managers something they could trust, not something on time and wrong. So I told my manager on Wednesday, not Friday, and proposed a plan: I would send the figures that were already verified on Friday with the two affected regions clearly marked as pending, and the complete report by Tuesday. I then rebuilt the two feeds by hand from the source exports. The full report went out on Tuesday, and none of the managers had acted on bad numbers. Since then I check the feeds on the Monday of report week, so I find problems with four days to spare instead of two."

Why it works: it admits the miss plainly, the Action is specific and in the first person ("I told", "I proposed", "I rebuilt"), and the Result has a concrete outcome plus a habit that changed. The lesson is something the interviewer can picture, not a slogan.

Example 2: "Tell me about a time you persuaded someone to change their mind."

Weak answer:

"In my internship, the team wanted to use a new tool, but my supervisor wasn't sure about it. So we put together a presentation and showed him all the benefits, and we were able to convince him. He agreed and we started using it, and it made things a lot more efficient."

What is wrong with it: everything is "we". The interviewer cannot tell whether you built the presentation or sat in the room while someone else did. "A lot more efficient" is not measured, and there is no sense of why the supervisor objected, which is the interesting part of any persuasion story.

Strong answer:

"During my internship at a small events company, the team was tracking every booking in a shared spreadsheet, and double bookings were happening about once a month. I thought a simple booking tool would fix it, but my supervisor had tried one before and his team had stopped using it within weeks. So the task was really to answer his objection, not to sell him features. I asked him what had gone wrong last time, and it was the setup: nobody had time to move the old bookings across. I offered to do the migration myself over two evenings and to run both systems side by side for a month, so nothing was at risk. He agreed to the trial. In that month we had no double bookings, and he moved the whole team over at the end of it. What I took from it is that people usually object to the cost of a change, not the change itself."

Why it works: the Task names the real obstacle (his bad experience), the Action shows the speaker listening first and then removing the risk, and the Result is countable. It also ends on a lesson that shows judgement.

Example 3: "Tell me about a time you made a process work better."

Weak answer:

"So at my part-time job at a cafe, I noticed that things were kind of disorganised, especially at closing. The closing process took really long and everyone hated it. I came up with a checklist and I talked to my manager about it and we started using it. I'm really passionate about efficiency and I always look for ways to improve things."

What is wrong with it: this one has all four parts in name, but each is thin. "Really long" has no number, the Action is one sentence, and the answer ends on a claim about personality instead of a result. Interviewers discount self-description; they believe evidence.

Strong answer:

"At my part-time cafe job, closing took two people about an hour and a quarter, and the morning shift kept finding things missed, like the milk fridge not restocked. I was usually on the closing shift, so I wanted to get us out earlier without making mornings worse. For a week I timed each closing job on my phone and noticed that we both did the same jobs in a different order every night, and some got done twice. I wrote a checklist split into two columns, one per person, ordered so nobody waited for the other, and I asked my manager if we could trial it for two weeks. By the end of the trial, closing was taking about fifty minutes and the morning shift had stopped reporting missed jobs. My manager made it the standard checklist for every closing shift."

Why it works: numbers at the start and the end make the improvement visible, the Action shows a method (timing the jobs first), and the Result includes what other people did because of it. Notice that it never says "I'm passionate about efficiency". The story makes the point.

The common mistakes

1. Too much setup

The most common failure is spending half the answer on background. The interviewer needs enough context to follow the story and no more. If you are still describing the team structure after 30 seconds, cut.

2. "We" instead of "I"

Teamwork is good. But the interviewer is hiring you, not your old team. Say what the team did in one sentence, then say what you did. If you genuinely did very little, pick a different story.

3. Stopping before the result

Many answers end on the action ("...so I set up the meeting, and yeah."). The result is the proof. If you do not know the exact outcome, say what you do know: what happened next, what changed, what someone said about it.

4. A result with nothing in it

"It went well" and "everyone was happy" are not results. A number, a before and after, or a named consequence ("the client renewed", "my manager rolled it out to the other branch") is.

5. Inventing details

Under pressure, it is tempting to round a story up. Do not. A good interviewer will ask follow-up questions ("What did your manager say?", "How did you measure that?"), and an invented detail falls apart on the second question. Use a real story and find the real numbers before the interview.

6. Answering a different question

If they ask about a time you failed, a story about a success with a small hiccup does not count. Answer the question that was asked, early, so the interviewer knows you heard it.

A practice routine that works

STAR is easy to understand and hard to do on the spot. Reading about it will not make it automatic. Saying it out loud will. Here is a routine for the two weeks before an interview.

1. Build a story bank. Write down six to eight real stories from work, study, volunteering or part-time jobs: a conflict, a failure, a time you led, a time under pressure, a time you persuaded someone, an achievement. For each, note the result, with a number if there is one. Most behavioural questions can be answered with one of these stories.
2. Map stories to questions. Take a list of common behavioural questions and decide which story you would use for each. One story often covers three or four questions.
3. Answer out loud, once a day. Pick a question you have not practised, give yourself a few seconds to think, and answer it out loud with a timer running. Do not write the answer out first: in the real interview you will not have a script.
4. Listen back and check the four parts. Record yourself and play it back. Ask: where did the Situation end? Did I say "I" in the Action? Did I actually say the Result? How long did the setup take?
5. Say it again with one fix. Change one thing and record it again straight away. One fix per take is far easier than trying to correct everything at once.
6. Practise the follow-ups. For each story, think of the two questions an interviewer would most likely ask next, and answer those out loud too.
7. Do one mock with a person. A friend, a family member or a career adviser. A real listener adds the pressure that recording alone does not.

Practising with an app

Steps 3 to 5 are where most people stop, because checking your own recording against STAR is tedious and it is hard to be honest about your own answer. That is the part we built into RankedSpeak, our iPhone app. Its interview prep section has 48 behavioural questions. You answer out loud, and the report splits your answer into Situation, Task, Action and Result, shows how much of the answer each part took, and grades each part. If you told the action as "we", it says so. Pro adds the coaching: how an interviewer would hear the answer, the follow-up questions to expect, and your answer rebuilt with any missing facts left as blanks in brackets for you to fill in, so it never makes up a result for you.

An app is not a replacement for a mock interview with a real person, and it cannot tell you what a particular company is looking for. What it does well is the repetitions: one question, one answer, one fix, every day, until a clear STAR answer is what comes out when you are nervous.