The STAR Method: How to Answer Behavioral Interview Questions (With Examples)

Behavioral interview questions ask about something you've done: "Tell me about a time you disagreed with your manager." "Describe a project that went wrong." They are popular with interviewers because what someone did before is a better guide to what they'll do next than what they say they would do.

They are hard to answer well on the spot. People either ramble through the background or give a tidy summary with nothing in it. The STAR method fixes both problems by giving every answer the same shape.

What STAR stands for

• Situation. Where you were and what was going on.
• Task. What you were responsible for, or what needed to happen.
• Action. What you did, step by step, and why.
• Result. What happened because of what you did, and what you learned.

What each part needs

Situation (one or two sentences). Give the interviewer just enough to follow: the company or team, the timing, and what made it difficult. "Last spring, two weeks before our biggest client's renewal, their main contact told us they were reviewing other vendors."

Task (one sentence). Your responsibility in that moment, not the team's. "As account lead, I had to find out why and keep the renewal."

Action (most of your answer). This is what the interviewer is scoring. Say what you did in the order you did it, with the reasoning: who you spoke to, what you found, what you decided and what you chose not to do. Use "I". If others helped, say what they did and what your part was.

Result (two or three sentences). What changed. Use numbers if you have them ("renewed for two years at the same price"), but a clear outcome without numbers is fine. Then add one sentence of reflection: what you learned, or what you'd do differently. That sentence often separates a good answer from a great one.

How interviewers score a STAR answer

Most structured interviews score answers against a short rubric. Whatever the exact wording, interviewers tend to look for the same things:

• Specific. One real occasion, not "I usually…". General answers score low because they can't be checked.
• Yours. Clear ownership of the actions. "We decided" hides what you did.
• Reasoned. Why you chose that action over the alternatives. Judgement is often what's really being tested.
• Proportionate. Most time on the action, little on the background.
• Evidenced. A result someone could verify, even approximately.
• Reflective. What you learned, especially when things didn't go well.

If you know the role's key skills, the job description is usually a good guide to which of these a question is probing.

A worked example

This example is invented, to show the shape.

Question: "Tell me about a time you had to deliver bad news to a customer."

Situation: "At my last job I ran support for our payroll software. In March, a bug in an update caused about forty customers' payslips to show the wrong tax code. The payments themselves were right, but the payslips weren't."

Task: "I was the support lead, so I owned telling customers and handling what came back."

Action: "First I confirmed with engineering exactly what was wrong and what wasn't, because the worst thing would have been to frighten people about their pay when it was correct. Then I wrote one plain email: what happened, that payments were unaffected, when corrected payslips would arrive, and who to call. I called our five largest customers myself before the email went out, so they heard it from a person. And I set up a short script for my team so every caller got the same answer."

Result: "Corrected payslips went out in two days. We had fewer than ten calls, no cancellations, and two of the customers I'd called thanked us for the warning. Afterwards I pushed for a release check on payslip output, which engineering added. Looking back, I'd involve engineering in the customer email earlier; I lost half a day waiting for a technical review."

Notice where the words go: two sentences of context, most of the answer on actions and the reasons for them, a concrete result, and an honest reflection.

Mistakes that cost marks

• Too much Situation. If you're a minute in and still setting the scene, the interviewer has stopped listening.
• "We" all the way through. Interviewers can't hire your team.
• A hypothetical. "I would…" answers a different question. If you have no example, say so and give the closest one you have.
• No result. Stories that stop at the action leave the interviewer wondering whether it worked.
• A perfect hero story. For questions about failure or conflict, an answer where everything went right sounds rehearsed. Real examples have trade-offs.
• The same story for every question. Reuse is fine, but four answers about one project suggest you've only done one thing.

How to prepare

Build a story bank. Write down six to eight real situations from your work, studies or volunteering: a success, a failure, a conflict, a time you led, a time you changed your mind, a time you worked under pressure, a time you dealt with a difficult person. For each, note the STAR points in a few bullet words, not a script.

Map stories to likely questions. Most stories answer several questions. A project that slipped can be about failure, about pressure or about communication, depending on what you emphasise.

Read the job description. If it stresses stakeholder management, expect questions about influence and disagreement. Choose the stories that show what the role needs.

Practise out loud and time it. Two minutes is about right. Recording yourself is uncomfortable and very effective: you'll hear the long set-up and the missing result immediately.

Prepare for follow-ups. Good interviewers will ask "What would you do differently?" or "What did your manager think?" Know your story well enough to go one level deeper.

A STAR answer template

Use this to prepare each story in your bank:

• Question it answers:
• Situation (one sentence):
• Task (one sentence, your responsibility):
• Action (three or four steps, each with the reason):
• Result (what changed; a number if you have one):
• What I learned or would do differently:

Beyond STAR

Some interviews now ask you to do a piece of the work rather than describe it: reply to a customer, analyse a spreadsheet, or talk a client through a problem. STAR still helps there, because the habits are the same: understand the situation, be clear about what you're responsible for, explain your reasoning and finish with a result.

Cohesyve, which publishes this guide, runs practice job simulations that combine both: written and spoken questions, some about how you'd handle a situation and some that ask you to handle it, with a scored report on where you lost marks.