# Situation, Task, Action, Result — Behavioural Interview Prep

Source: https://www.skillbyai.com/en/behavioural-interviews/s-star

> Four parts, uneven time.

## The structure and its proportions

**STAR** is a widely used way to structure a behavioural answer. **Situation**: brief context (team, product, constraint). **Task**: what you were responsible for or what needed to happen. **Action**: the specific steps **you** took and why, including options you weighed. **Result**: the outcome, ideally measurable, and its effect on users, the team or the business. Keep Situation and Task short, around a sentence or two each; spend most of your time on Action, then finish with a clear Result. Use 'I' for your own actions and 'we' only when describing shared work, so the interviewer can tell what you contributed.

## Structure that keeps you focused

STAR gives answers a beginning, a middle and an end, with most of the time spent on what you did.

![Three ideas: the four parts, variants such as STAR-L and CAR, and common mistakes.](assets/figures/behavioural-interviews/section-2-map.svg) — Figure 2.1 — Situation, Task, Action, Result; variants; and the mistakes that weaken answers.

## A STAR answer template

Fill this in for each story.

```text
Question: ____________________________________________

S  Situation (1-2 sentences)
   Where, when, which team or product, what was at stake?

T  Task (1 sentence)
   What was my responsibility or the goal?

A  Action (most of the answer)
   1. First thing I did and why
   2. Options I considered / trade-off I made
   3. Who I worked with and how I communicated

R  Result (1-3 sentences)
   What changed? Numbers I can honestly stand behind.
   What happened to users / team / business?
```

## A worked STAR answer

A fictional example, to show the shape.

```text
Q: Tell me about a time you improved something without being asked.

S  On a team of five maintaining an internal billing service, our
   nightly test suite took about 90 minutes and often timed out.
T  I wanted feedback before the morning stand-up so failures were
   not discovered mid-day.
A  I profiled the suite and found that a handful of integration
   tests rebuilt the database for every case. I proposed sharing one
   fixture per test file, wrote a short design note, paired with the
   test owner to migrate the slowest files first, and added a CI
   check that flagged new tests creating their own database.
R  The suite dropped to roughly 30 minutes and timeouts stopped.
   Two other teams copied the fixture pattern.

(Fictional example; use your own real experience.)
```

## Signpost the structure lightly

Phrases like 'The situation was...', 'What I did was...', 'As a result...' help listeners follow you without sounding robotic.

**Quiz:** Which STAR part should usually take the most time?

- [ ] Situation
- [x] Action
- [ ] Task
- [ ] The introduction of your team members

*Answer:* Action. Your actions are the evidence.