Answering well

STAR method examples: six worked answers for graduates

Six complete STAR answers from different parts of a graduate’s life, how long to spend on each part, and what to do when the interviewer digs into your story.

By the Deeplink Interview teamLast reviewed 10 minute read

At a glance

Written for
Students, graduates and career changers facing competency questions
Reading time
10 minutes
Questions to practise
16 in our practice bank

The short answer

The STAR method answers “Tell me about a time…” questions in four parts: the situation, your task, the actions you took and the result. Spend about 20 seconds on the situation and task, a minute or more on your own actions, and finish with a result you can measure and what you learned. Most graduates lose marks by saying “we” instead of “I” and by stopping before the result.

What is the STAR method?

STAR is a way of telling a short story about something you’ve done, so the interviewer can hear the evidence they’re listening for. It stands for situation, task, action and result. It’s used for competency questions, which usually start “Tell me about a time…”, “Give an example of…” or “Describe a situation where…”.

Interviewers use these questions because what you did before is some of the best evidence of how you’ll work. Many graduate interviews are built on a short list of competencies, such as teamwork, problem solving, resilience, communication and leadership, with one question on each. The interviewer usually has a score sheet for each competency, and STAR makes it easy for them to find what they need to score.

PartWhat it answersTime in a two-minute answer
SituationWhere, when, who, and why it matteredAbout 10 to 15 seconds
TaskWhat needed to happen, and what your part wasAbout 10 seconds
ActionWhat you did, step by step, and whyAbout 60 to 70 seconds
ResultWhat changed, ideally with a number, and what you learnedAbout 20 to 30 seconds

The action is the answer. Situation and task are only there so the actions make sense.

How long should a STAR answer be?

Aim for 90 seconds to 2 minutes when you’re speaking, which is roughly 250 to 300 words. In a one-way video interview the clock decides for you, and answers are often capped at 2 or 3 minutes. In a live interview you can go a little longer if the interviewer is engaged, but they’ll ask follow-up questions about anything they want more of, so it’s better to finish cleanly and let them.

If you’re writing a STAR answer for an application form instead, the word limit sets the length. The Civil Service, for example, often asks for behaviour examples of about 250 words at entry grades. The shape is the same.

Six worked STAR answers

These are outlines, not scripts. Each one comes from a different part of life, to show that you don’t need a graduate job to have strong examples. Read them for the shape, then build yours from your own experience.

Teamwork, from a group project

Worked example“Tell me about a time you worked in a team to reach a difficult goal.”A geography graduate, from a final-year group project
Situation
Final-year group project, four of us, a 6,000-word flood risk report for a real parish council, due in eight weeks.
Task
Halfway through, two members had done almost nothing and the council wanted a draft in ten days. I was responsible for the mapping section, but the whole mark was shared.
Action
I didn’t complain to the tutor first. I asked the group for 30 minutes and put the remaining work on one page, split into 12 pieces with a name and a date on each. I asked the two quieter members which pieces suited them, and one admitted she hadn’t understood the software, so I spent an hour showing her. I set up a 15-minute check-in every Monday and Thursday and kept a shared tracker.
Result
The draft went to the council two days early, and they used two of our maps in a funding bid. We got a 68. I learned that people who go quiet are often stuck, not lazy, and that asking them directly works better than working round them.

Why it works: the problem is real, the candidate’s own part is clear (“I asked”, “I spent an hour”), and the result has a date, a mark and an outside effect.

Resilience, from a part-time job

Worked example“Tell me about a time something went wrong. How did you respond?”An economics graduate, from a weekend job in a phone shop
Situation
Weekend sales job in a phone shop. I missed my monthly target by a long way for two months running, and my manager put me on a support plan.
Task
Get back to target within six weeks, while still in my final year.
Action
I asked to shadow the top seller for two Saturdays and wrote down what she did differently. She asked customers what they used their phone for before showing anything. I copied that, kept a tally of every customer I spoke to and what they bought, and noticed I was losing people when I talked about contracts too early. I moved contract talk to the end.
Result
I hit target in week five and stayed above it for the rest of the year. The tally showed about one in six of my customers bought something before, and one in four after. It taught me to treat a bad result as data, not a verdict.

Why it works: the setback is honest and personal, and the recovery comes from specific actions the candidate chose, with a before and after figure.

Initiative, from volunteering

Worked example“Give an example of when you spotted something that could be done better and acted on it.”A history graduate, from volunteering at a food bank
Situation
Saturday volunteer at a town food bank. Donations were logged on paper, and every month a volunteer spent a whole day counting stock.
Task
Nobody asked me to fix it, but the monthly count kept delaying orders to the wholesaler.
Action
I asked the coordinator if I could try a simple spreadsheet for one month alongside the paper. I built a sheet with one tab per shelf, trained three other Saturday volunteers in ten minutes each, and kept the paper log running so nothing was lost if it failed. At the end of the month I compared the two counts with the coordinator.
Result
The counts matched within 2%, and the monthly stock take went from a day to about an hour. The food bank now uses the sheet at both its sites. The lesson: run a new idea next to the old way first, so people can trust it.

Leadership, from a society

Worked example“Tell me about a time you led other people. How did you get the best from them?”A biology student, as social secretary of a hiking society
Situation
Social secretary of a 120-member hiking society. Our spring trip had sold only 14 of 40 places, three weeks before the deposit was due.
Task
Fill the trip or cancel it and lose a £400 deposit, with a committee of five who were all busy with exams.
Action
I gave each committee member one small job that matched what they liked: our designer made new posters, our first-years posted in their halls’ group chats, and I rang the coach company to ask for a later deposit date, which they agreed. I sent a two-line update every Friday so nobody had to chase.
Result
We sold 38 places and kept the deposit. Two of the first-years who helped stood for committee the next year. I learned that small, specific jobs get done; vague ones don’t.

Problem solving, from a data task

Worked example“Describe a problem you solved where the answer wasn’t obvious.”A maths graduate applying for a data analyst role, from a summer internship
Situation
Summer internship at a regional bus company. A weekly report showed passenger numbers on one route falling 20% in a month.
Task
My manager asked me to find out why before a meeting with the council on Friday.
Action
I checked the data before the story. The fall started the same week the ticket machines were updated, so I compared the old and new machine logs and found the new ones weren’t recording concessionary passes. I confirmed it with the depot, counted the missing passes from a sample of paper tallies, and wrote a half-page note with the corrected figure and how confident I was.
Result
The corrected figure showed a 3% fall, not 20%. The council meeting went ahead with the right number, and the machine supplier fixed the setting. I now look for a change in how data is collected before I look for a change in what it measures.

Communication, from a customer role

Worked example“Describe a time you explained something complicated to someone without your background.”A physics graduate, from a part-time job at a tech repair desk
Situation
Part-time job at a university IT help desk. A lecturer kept losing work because she saved files to a synced folder that was full.
Task
Explain why it happened, without making her feel stupid, and stop it happening again.
Action
I skipped the technical terms and used her own filing cabinet as the example: the synced folder was a drawer that looked open but had stopped accepting paper. I showed her the one icon that meant it was full, cleared space with her rather than for her, and wrote three steps on a sticky note.
Result
She didn’t call again about it, and she sent two colleagues to the desk with the same problem. I learned to explain using the other person’s world, not mine.

What makes a STAR answer strong?

  • You can see the person. Every action is something the candidate did, chose or said. “We decided” hides you; “I suggested, and the group agreed” shows you.
  • There are reasons. Strong answers say why each action was taken. That’s what separates judgement from luck, and it’s what interviewers probe.
  • The result is specific. A number, a date, a mark, a before and after, or something someone else did because of you. If you have no number, say what changed.
  • There’s a lesson. One sentence on what you learned or would do differently shows you reflect, which many score sheets reward.
  • It fits the competency. A teamwork question wants how you worked with people, not how clever your solution was.

Common mistakes with the STAR method

  • Too much situation. Spending 45 seconds on background leaves too little for actions. Two sentences is enough.
  • “We” all the way through. The interviewer can’t score what they can’t attribute. Say “I” for your part, and be honest about others’.
  • Stopping at the action. Ending with “and so we did the presentation” leaves the interviewer to guess. Always land the result.
  • A hypothetical answer. “I would…” answers a different question. Competency questions want something that happened.
  • The same story every time. One brilliant example used for teamwork, leadership and resilience starts to sound thin. Have six to eight.
  • Memorised word for word. Scripts sound recited and fall apart when the interviewer asks a follow-up. Learn the outline, not the sentences.

How do interviewers test a STAR answer?

In a live interview, your first answer is often only the start. Interviewers ask follow-up questions to check the story is yours and to fill gaps on their score sheet: “What exactly did you say to her?”, “Why that order?”, “What would you do differently?”, “How did you know it had worked?”. Prepare for these by knowing the reasons behind each action and one thing you’d change. Our guide to follow-up questions covers them in detail.

In a one-way video interview there are no follow-ups, so the first answer has to be complete: every part of STAR, with the result and the lesson, inside the time.

How to build your own story bank

  1. List your raw material. Your degree (projects, dissertation, labs), jobs (including shop, bar and care work), volunteering, societies, sport, caring responsibilities and anything you’ve taught yourself.
  2. Pick six to eight moments where something was hard, went wrong, needed changing or involved other people.
  3. Write one line for each part of STAR, including the number or change in the result.
  4. Tag each story with the competencies it shows. A good story usually covers two or three.
  5. Check the spread. You want at least one example each for teamwork, problem solving, resilience, initiative, communication and leadership, and a mix of settings.

Signed-in members can keep their examples on the STAR examples page and see which competencies they cover. Then practise them against real questions: the list below has every question in our competency set, and the guide to competency questions has more on each part of STAR.

Practice checklist

Work through these before the real interview. Each one is something you can do, not just read about.

  • Write a story bank of six to eight real examples, one line each, and tag each with the two or three competencies it shows best.
  • For each story, write the result as a number or a concrete change, plus one sentence on what you’d do differently.
  • Say three of your stories out loud with a two-minute timer. Note where you ran out of time: it’s usually before the result.
  • Record one answer and count how often you say “we”. Change each one that hides your own part to “I”.
  • Ask a friend to ask “why did you do that?” after each action. If you can’t answer, add the reason to your outline.
  • Practise one story for two different competencies, so you can reuse it without it sounding recycled.

Questions to practise

These include every question in our “Competency questions” practice set. Each has its own page with what it’s really asking and an example outline. Then practise it out loud, with thinking time and a timed answer.

Go further

Written by the Deeplink Interview team and last reviewed 29 September 2026. The examples are invented to show the shape of a good answer: yours should come from your own experience, in your own words. This is general practice advice, not linked to any employer, and not a prediction of any hiring decision. How we write these guides.

Keep reading

All interview guides

Now say it out loud

Reading helps, but answers improve when you say them. Practise on camera with thinking time and a timed answer, or talk it through with an AI interviewer that asks follow-up questions, then read written feedback on each answer. Free to start, with no card needed.

Start practising freeBrowse interview questions