What is the STAR method?

STAR stands for Situation, Task, Action, Result. It's a way to structure your answers to behavioural questions, the ones that start "Tell me about a time when…". Graduate interviews in Australia lean heavily on them.

Interviewers ask these questions because what you've done before is good evidence of what you'll do next. They want a real story from your own experience, not a description of what you'd do in theory.

STAR gives you an order to tell that story in, so you answer the question you were asked and don't wander off.

S
Situation

Set the scene. Give the interviewer enough context to follow the story: where you were and what you were working on. One or two sentences is plenty. The situation is background, so don't let it take over.

T
Task

Say what you were responsible for. This separates your part from what your team or organisation did. The interviewer wants to know what you had to solve or deliver.

A
Action

Walk through what you did, step by step, and be specific. Say "I", not "we". This should be about half of your answer, so don't rush through it to get to the result.

R
Result

Say how it turned out. If you can put a number on it, such as a percentage, a dollar figure or hours saved, do. Then add a line on what you learned or what you'd do differently.

Why STAR works

Without a structure, answers to these questions tend to go one of two ways. Some stay general ("I'm good at working under pressure") and never get to an example. Others ramble through a story and leave the interviewer unsure what the point was.

STAR fixes both. It makes you pick one specific time and say what you did, and it gives your answer a beginning, a middle and an end. That makes it easy to follow, and the interviewer can hear the parts they're listening for.

Use stories you already have

You don't need to invent or memorise answers. STAR is just an order for telling a story you already have, with the right amount of detail in each part.

STAR examples for uni students

The hardest part for most students is believing they have enough experience. You probably do. Group assignments, part-time work, internships, volunteering, sport and student clubs all count.

Here are three worked examples you can use as a model.

Example 1: Teamwork

Question
"Tell me about a time you had to work effectively as part of a team to meet a deadline."
S
Situation
In my second year at uni, my group of four had a marketing case study due in two weeks. Halfway through, one of us had a family emergency and had to step back for a week.
T
Task
I'd ended up as the unofficial project lead, so it was up to me to share out the work and make sure we still submitted on time without wearing out the other two.
A
Action
I called a quick check-in to work out what was left and who had time. I broke the remaining work into daily tasks and gave each person the parts that suited them. I set up a shared checklist in Notion so everyone could see where things were, which cut down the back-and-forth messages a lot. When I noticed one teammate falling behind on their section, I got on a call with them and helped them get unstuck rather than letting it slide.
R
Result
We submitted on time and got a High Distinction, our best group mark that year. Our tutor commented on how clear the analysis was. I learned that regular check-ins helped the group more than everyone just working harder on their own.

Example 2: Problem-solving under pressure

Question
"Describe a situation where you had to deal with a problem you hadn't anticipated."
S
Situation
I was working at a café on a busy Saturday morning when the point-of-sale system crashed in the middle of the rush.
T
Task
I was the most senior person on the floor at the time, so I had to keep the line moving and stop customers walking out while the manager worked on the system.
A
Action
I switched us to writing orders on paper and went down the line apologising and letting people know the wait would be short. I put the orders we'd already started first, worked out prices from memory, and asked customers if they were OK with an approximate price until the system came back. I kept telling people what was going on. They were frustrated at first, but they appreciated knowing.
R
Result
We only lost two customers from the queue, and nobody made a formal complaint. The manager said afterwards it was the calmest she'd seen anyone handle an outage. It taught me that when you stay calm where people can see you, the people around you calm down too.

Example 3: Initiative

Question
"Give me an example of a time you took initiative to improve a process or outcome."
S
Situation
During a six-week internship at a financial services firm, I noticed the team spent several hours each week copying data from spreadsheets into their reporting template by hand.
T
Task
Nobody had asked me to fix it, but it was clearly eating up their time and I thought I could help.
A
Action
I spent a couple of lunch breaks building a simple Excel macro to do the copying. I tested it on the previous two months' data to check it was accurate, then wrote a short how-to so the team could use it without me. I showed it to my supervisor before anyone started using it, rather than changing their process without asking.
R
Result
The macro cut the weekly task from about three hours to under fifteen minutes. My supervisor mentioned it in my end-of-internship review, and the team was still using it after I left. I learned that even in your first weeks somewhere, fixing a small thing that wastes people's time is a good way to be useful.

Common STAR mistakes

People who know the method well still make these mistakes when they're nervous.

Spending too long on the situation It's easy to spend half your answer on background. The interviewer only needs enough to understand the challenge, so keep the situation to about 10–15% of your answer.
Saying "we" instead of "I" in the action The interviewer is assessing you, not your team. "We decided to…" doesn't tell them what you did, so say which parts were yours.
Leaving out the result This happens a lot when people are nervous and run out of steam. The result is how the story ends, so always finish with one, even if you can't measure it ("the client was happy with it", or "the team got on better afterwards").
Choosing a weak example If your best example of handling conflict is a small disagreement with a classmate, the interviewer will notice. Prepare six to eight good stories on different themes, so you have a strong one for most questions.
Not practising out loud Knowing your stories on paper doesn't mean you can tell them smoothly when you're nervous. Say each one out loud a few times before the real interview.

How long should a STAR answer be?

Aim for about 1.5 to 2.5 minutes per answer. Much shorter and you probably haven't given enough detail. Much longer and you're probably spending too long on the situation, or you've lost track of the story.

As a rough guide:

  • Situation: 10–15%, one or two sentences
  • Task: about 10%, what you were responsible for
  • Action: 50–60%, the specific things you did
  • Result: 20–25%, how it turned out and what you learned
Time yourself

Record yourself answering a question and time it. Most people are surprised how long 90 seconds feels, and how much of the situation they can cut without losing anything.

Build a bank of STAR stories

Before you start applying, write down six to ten STAR stories. Between them, they should cover what graduate employers usually ask about:

  • Teamwork
  • Solving a problem under pressure
  • Leading or taking initiative
  • Dealing with conflict or a difficult person
  • A failure, and what you learned from it
  • Juggling competing priorities or deadlines
  • Doing more than you were asked

Most stories can answer more than one question. Your teamwork story might also work for a question about communication or about a deadline, depending on which part you focus on.

Practise your STAR answers out loud tonight

InterviewZap asks you interview questions based on your CV and the job you're applying for. Answer by typing or out loud, and after each answer you'll see what was missing and a stronger way to say it. It's a quick way to find out which of your stories work.

Start Practising Free →

No credit card. Free to start.

How to practise before the interview

Knowing the STAR method and using it well when you're nervous are two different things. Practice is what gets you from one to the other.

  1. Write your stories down first. Before you say anything out loud, write each story as a few bullet points under S, T, A and R. It makes you work out what the story actually is.
  2. Then say them out loud, not in your head. Something that reads well on paper often sounds clunky when you say it, and you only find out by saying it.
  3. Record yourself. A voice memo on your phone is enough. When you play it back, you'll hear what needs fixing: filler words, trailing off at the result, or too long on the situation.
  4. Get feedback on your structure. A friend, a careers adviser or an AI practice tool can tell you whether your action has enough detail in it and whether your result sounds believable.
  5. Practise in conditions like the real thing. Answering at your desk with time to think is very different from answering in a video interview with someone watching. Recreate some of that pressure: camera on, little time to think, and the same formal tone you'd use on the day.
The goal

You want your stories to sound like you're remembering something that happened, rather than reciting it. That comes from saying them out loud enough times.

Quick summary

STAR keeps your answers to behavioural questions focused and specific. Here it is in one paragraph:

STAR in one paragraph

Situation: set the scene briefly. Task: say what you were responsible for. Action: go into detail on what you did, because this is most of the answer. Result: finish with how it turned out, with a number if you have one, and a line on what you learned. Aim for 90 to 150 seconds, say "I" rather than "we", and always end with a result.