Guide

The STAR method for behavioural interview questions

"Tell me about a time when..." questions are easier with a shape to follow. STAR gives you one: Situation, Task, Action, Result. Here's how to use it without sounding robotic.

What behavioural questions are testing

Behavioural questions ask about something you've actually done: "Tell me about a time you disagreed with a colleague", "Describe a deadline you nearly missed", "Give an example of when you took the lead". The idea is that how you handled a real situation says more than how you think you'd handle an imaginary one.

The trouble is that real stories are messy. Without a structure, answers wander, skip the important part, or end without saying what happened. STAR fixes that.

The four parts

• Situation. Set the scene in one or two sentences. Where were you, and what was going on? Only include what the listener needs to follow the story.
• Task. What were you responsible for, or what problem needed solving? This makes your role clear.
• Action. What did you do, step by step? This is the heart of the answer and should take the most time. Say "I", not only "we".
• Result. What happened in the end? Give a concrete outcome if you can, and what you learnt or would do differently.

A rough balance: Situation and Task together take about a fifth of the answer, Action takes more than half, and Result takes the rest. The whole thing usually runs from one and a half to two and a half minutes.

A full STAR example

Question: "Tell me about a time you had to deal with a difficult problem under time pressure."

Situation. In my final-year project, our team of four was building a booking system for the college sports facilities. Two weeks before the demo, the person handling the database left the project because of a health issue.

Task. I'd been working on the front end, but I was the only other person who had used the database before, so I took over that part as well. We needed working bookings, cancellations and a simple admin view by the demo date.

Action. First I spent an evening reading through what had been built and listing what was finished, half-finished and missing. I shared that list with the team and suggested we drop the reporting feature we'd planned, since it wasn't essential for the demo. Our guide agreed. Then I split my days: mornings on the database, afternoons pairing with a teammate who took over some of my front-end work, so I could explain decisions as we went. I also set up a short check-in at the end of each day so problems surfaced early instead of the night before.

Result. We demoed bookings, cancellations and the admin view on time, and the project got one of the higher grades in our batch. The thing I took away was how much a clear list of what's done and what isn't helps a team under pressure. I've used that habit in every project since.

Notice that the Action section is the longest, it's full of specific steps, and it's clear what the speaker did personally.

Common mistakes

• A long Situation. If you're still explaining the background after thirty seconds, you've lost time you needed for the Action.
• "We" all the way through. Team work is fine, but the interviewer is hiring you. Make your own part clear.
• No Result. Some answers stop at the action. Always say how it ended, even if the result was mixed.
• Only perfect stories. A story where things went partly wrong, and you explain what you learnt, is often more convincing than a flawless one.
• Reading out the labels. Don't say "The situation was... the task was...". Use the structure in your head and let the story flow.
• Using the same story for everything. Prepare five or six different stories so you're not stretching one example to fit every question.

Building your story bank

Before an interview, write down five or six situations from study, work, volunteering or a team activity. Good ones to cover:

• a time you solved a hard problem
• a disagreement or conflict you handled
• a mistake you made and fixed
• a time you led something, formally or not
• a time you worked under pressure or to a tight deadline
• something you learnt quickly

Note the Situation, Task, Action and Result for each in a few bullet points, not full sentences. Most behavioural questions can be answered with one of these, adjusted for the angle of the question.

Saying it out loud

STAR answers look fine on paper and then come out long and tangled when spoken. The only fix is to say them out loud, time them, and listen back. Watch for the Action section shrinking when you're nervous; that's the part people rush. If "Tell me about yourself" is giving you trouble too, see how to answer it.

Practise it in Kayavak

Choose Interview mode and the Behavioural (STAR) question set. Try a Mock interview: the interviewer asks the questions aloud, and with a local AI model installed it can ask a follow-up when your answer needs one, which is a good test of whether your Result really landed. Check answer length in the report, then Retake your weakest answer and compare the two side by side. The interview practice page explains what each part of the report shows.