STAR Method: How to Answer Behavioral Interview Questions

"Tell me about a time you disagreed with your manager." Most candidates hear a question like this and start talking before they know where the answer ends. Two minutes later they are still describing the project, the interviewer has written nothing down, and the actual decision they made took one sentence near the end.

Behavioral questions ask for a past event because past behavior is the evidence the interviewer is allowed to score. Many employers train interviewers to look for three things in each answer: what the situation was, what you personally did, and what came of it. If one of the three is missing, the answer gets a low mark, however good the story was. STAR is a way to make sure all three are there.

What STAR stands for

• Situation: where and when, in one or two sentences. Enough context for the rest to make sense, nothing more.
• Task: what you were responsible for, or what had to be achieved. This is the part that separates your role from the team's.
• Action: what you did, step by step. This is the longest part of the answer and the one the interviewer scores most closely.
• Result: what changed because of it. A number if there is one, an outcome if there is not, and what you would keep or change.

A useful split is roughly 15% situation and task together, 60% action, 25% result. Most weak answers invert it: a long setup, a short action, and a result that is either missing or vague.

One answer, before and after

The question: "Tell me about a time you had to deliver under a tight deadline."

Before:

We had a big migration project last year and the deadline got moved up by a month because of a contract renewal. It was a stressful period and the whole team worked really hard. We had to cut some scope but in the end we managed to go live on time, and the client was happy.

Nothing in this answer is false, and nothing in it can be scored. "The whole team worked hard" says nothing about the candidate. "We managed" hides who decided what. "The client was happy" is a feeling, not a result.

After:

Last year I was leading the database side of a data-centre migration. Three months in, the go-live moved forward by four weeks because the old hosting contract couldn't be renewed. My job was to get 40 databases moved without extending the downtime window we had agreed with the business. I split them by risk: 28 low-traffic ones I moved with the existing scripted process over two weekends, and I spent my own time on the 12 that had replication or custom jobs. For those I ran a rehearsal on a copy first, which found two jobs that broke on the new version, and we fixed them before the real cut-over. We went live on the new date with 3 hours of downtime against the 4 we had agreed. The thing I would do again is the rehearsal; without it those two failures would have happened on the night.

The second version takes about 90 seconds to say. It uses "I" for the decisions that were the candidate's, gives the interviewer two numbers to write down, and ends with a reflection that shows judgement.

STARR: adding the second R

Some interviewers, and many public-sector and graduate schemes, expect a fifth part: Reflection. What did you learn, and what would you do differently? The last sentence of the answer above is a reflection.

Add it when the question invites it ("what did you learn", "looking back") or when the result was mixed. A reflection on a failure is often the strongest part of the answer, because it shows you can assess your own work without being asked twice.

CAR: the short version

CAR stands for Context, Action, Result. It is STAR with situation and task folded into one sentence. Use it when:

• the interviewer asks for several short examples in a row;
• you are in a screening call and the recruiter has ten questions to get through;
• you are writing an example into an application form with a word limit.

CAR is also the right shape for CV bullets. "Moved 40 databases to a new data centre four weeks early, with 3 hours of downtime against a 4-hour window" is context, action and result in one line. If you have written your CV this way, preparing for behavioral questions is mostly a matter of expanding the bullets you already have. Our guide to tailoring your CV to a job description covers how to choose which ones lead.

PREP: for opinion questions

Not every question asks for a past event. "Why do you want to work here?", "What makes a good team lead?" and "Should we rewrite this system or keep patching it?" ask for a view. STAR doesn't fit them, and forcing a story into the answer sounds evasive.

PREP stands for Point, Reason, Example, Point:

• Point: your answer, in one sentence, first.
• Reason: why you think so.
• Example: one concrete case that supports it, which can be a short STAR story.
• Point: the answer again, in one sentence, so the interviewer knows you have finished.

Starting with the answer is the part people find hardest. Most of us build up to a conclusion. Interviewers listening to many candidates in a day remember the first sentence far better than the last.

Mistakes that make a true story sound weak

Saying "we" for everything. Teamwork is fine, but if every verb is "we", the interviewer cannot tell what you did. Use "we" for the team's goal and "I" for your decisions.

Choosing the biggest project instead of the clearest example. A small problem where your role was obvious scores better than a large programme where you were one of thirty people.

Stopping at the action. Candidates often finish with "and that's what I did". Say what happened next, even if the honest answer is "it worked partly, and here is why".

Inventing numbers. If you don't know the exact figure, say "roughly" or describe the outcome in words. Interviewers ask follow-up questions, and a number you cannot explain does more damage than no number at all.

Preparing one story per question. You will not guess the exact questions. Prepare six to eight stories that each show several things (a deadline, a disagreement, a mistake, a decision with incomplete information) and practise adapting them.

How to prepare your stories

1. Read the job posting and list the four or five skills it mentions more than once.
2. For each skill, find a moment from the last three to five years where you used it and the outcome was clear.
3. Write each story in STAR form in under 150 words. Then say it out loud and time it. Aim for 60 to 120 seconds.
4. Check the action section for "we", and rewrite the parts that were yours with "I".
5. Check the result for a number or a concrete outcome. If neither exists, choose a different story.

Then test the stories against your CV. An interviewer usually has your CV in front of them and will ask about what is on it. If your best story is not on the CV, consider adding it; if a bullet on the CV has no story behind it, expect to be asked about it anyway.

FAQ

How long should a STAR answer be?

Between one and two minutes when spoken, which is about 150 to 250 words. Under a minute usually means the action is missing detail. Over two minutes, the interviewer has often stopped taking notes and is waiting for you to finish.

Can I use the same story for more than one question?

Yes, as long as you tell it from a different angle each time. A project that went wrong can answer a question about failure, about conflict and about working under pressure, with a different action and result in focus. Avoid repeating the same story within one interview unless you say so openly.

What if I don't have a good example?

Use an example from study, volunteering or a side project, and say where it comes from. Interviewers score the behavior, not the setting. If you have no example at all for a skill, say so and describe how you would approach it: an honest gap scores better than an invented story.

Is STAR only for behavioral interviews?

It is designed for questions about past behavior. Opinion questions work better with PREP, and technical problems with talking through your reasoning step by step, which we cover in our guide to thinking aloud in technical interviews.

Do interviewers know candidates use STAR?

Yes, and many of them were trained with the same structure. That is the point: you are giving the information in the order they are writing it down. What they do not reward is a recited script, so learn the stories, not the sentences.