HHireCream

HireCream / Guides

Interview answers

The STAR method for interviews, with answers you can adapt

Situation, Task, Action, Result: keep the first two short, spend most of your time on what you did, and end with something that changed. Below are worked answers for three kinds of candidate, a story bank and a prep sheet.

By The HireCream teamUpdated November 7, 202610 min read
See who is hiring nowShort quiz, about 2 minutes
Two blank white cards side by side on an amber wooden desk seen from above, with a laptop corner and a mug at the edges

The STAR method (in the UK it is usually called the STAR interview technique) is how you answer questions that start with “Tell me about a time when...”. You tell one real story in four parts: the Situation, your Task in it, the Action you took and the Result. Keep the first two short, spend most of your time on what you personally did, and finish with something that changed, ideally with a number attached. We aim for about two minutes spoken.

Below: how the time should split, what the interviewer is writing down, worked answers for a fresher, a career changer and a manager, and a prep sheet for your own stories.

How a two-minute STAR answer splitsSSituation15 secOne or two sentencesTTask10 secYour part, not the team'sAActionwhere the scoring happens70 secThree or four steps, each starts with IRResult25 secWhat changed, with a numberIf the situation runs longer than the action,cut the situation.
The seconds are our suggestion for a two-minute answer, not a rule from any employer.

What is the STAR method in an interview?

Behavioural questions ask what you did, not what you would do. “Tell me about a time you disagreed with your manager.” “Describe a deadline you nearly missed.” In the UK they are usually called competency-based questions, and in Indian campus placements they tend to come up in the HR round after the technical ones. The format is the same everywhere: the interviewer wants one real story, told so they can see your decisions.

STAR gives that story a spine. Situation and Task set it up. Action is the part being judged. Result shows it worked, or what you learned when it did not. The reason employers like these questions is old and simple, and the US government's own hiring guidance states it plainly:

Past behavior is the best predictor of future behavior.

Where you will meet STAR questions, and what they are scored against
EmployerWhat they score againstWhat they say about STAR
UK Civil ServiceSuccess Profiles: nine behaviours, such as Making effective decisions. Each role tests a selection.GOV.UK suggests the STAR method for your behaviour examples
Amazon16 Leadership Principles, such as Customer Obsession and OwnershipAmazon's UK recruiters call STAR “a structured way to respond to behavioural-based interview questions”
US federal agenciesJob competencies, scored against written benchmarks, often by a panelOPM describes behavioural questions as asking you “to describe a past behavior”
Most other employersThe skills and duties listed in the job adRarely stated: prepare a story for each main requirement in the ad

Source: GOV.UK Success Profiles, Amazon Leadership Principles, About Amazon UK, OPM.gov; checked November 7, 2026

Amazon says it uses its Leadership Principles to evaluate candidates but does not expect you to memorise them all. Pick the five or six closest to the role and have a story for each. Our Amazon careers page lists its current remote openings. For the Civil Service, GOV.UK says to read the job description for the behaviours required, so build your stories around exactly those.

How long should each part of a STAR answer take?

We split a two-minute answer roughly like the diagram above: about 15 seconds of situation, 10 of task, a minute and a bit of action, the rest on the result. Nobody times you to the second. But if your situation runs longer than your action, the interviewer has heard a lot about the company and very little about you.

A quick test: record your answer on your phone and note the second where you first say “I did”. In a first draft it usually comes far too late.

A STAR answer before and after

The question: “Tell me about a time you dealt with a difficult customer.” Here is the kind of first draft most of us give before we have practised.

The same story in STAR order
Situation: Last December I was the most senior person on a Saturday shift at a phone repair shop. A customer came in upset because her repair had been promised for Friday and the part hadn't arrived.

Task: My job was to calm things down without promising anything the shop couldn't deliver.

Action: I took her to the side counter so she wasn't arguing in front of the queue. I let her finish before I said anything, then repeated back the two things she needed: a working phone for the weekend and a firm date. I checked our stock, found a loan handset and set it up for her while she waited. Then I rang the supplier, got a Tuesday delivery confirmed, and wrote that date on her receipt with my name next to it.

Result: She left with a working phone and collected her repair on Tuesday. She later posted a review that mentioned me by name, and my manager made the loan-phone step our standard for repair delays.

The labels are only for practice. When you say it out loud, drop the words Situation, Task and so on and use plain links like “so I...” and “in the end...”.

STAR method examples for freshers, career changers and managers

The three answers below are invented to show the shape. Yours need real facts and real numbers, because the first follow-up (“what did your manager say?”) is where an invented story comes apart.

Fresher or graduate: a teamwork question

Fresher: “Tell me about a time you worked in a team”
In my final year of B.Tech, four of us were building an attendance app for our college as our major project. Six weeks before the review, one teammate left for an internship in Pune, and his part, the backend, was only half done.

I was responsible for the Android front end, but the demo would fail without a working backend, so I took on getting us back on track.

I listed every unfinished task in a shared sheet with a rough estimate. I took the login and database work myself because I had built something similar in my internship, and asked the other two to split testing and the report. I set up a 15-minute call every evening so problems came up the same day. When we disagreed about cutting the reports screen, I suggested we build it last and drop it if time ran out.

We demoed on time with everything except the reports screen, and the panel's main question was about the database design, which I could answer in detail. Since then I write tasks down on day one of every group project.

Career changer: an unhappy stakeholder

Teacher moving into customer success: “Describe a time you handled an unhappy stakeholder”
As a Year 9 maths teacher, I had a parent email the head teacher saying her son was being set up to fail after he moved down a set.

The head asked me to handle it. I needed to keep the parent on side and keep the decision, because it was based on three terms of test results.

I rang her that afternoon rather than replying by email, because tone gets lost in writing. I asked what she had noticed at home before explaining anything. Then I went through his last three test scores and offered a plan: a short progress note every fortnight and a review at half term, with a clear score that would move him back up.

She agreed, he moved back up after the review, and she wrote to the head to thank the department. That call is close to what a customer success manager does with an account that wants to cancel: listen first, show the data, agree a next step with a date.

End by naming the link to the new job in one sentence. Do not leave the interviewer to do the translation.

Manager or senior: a decision with missing information

Senior: “Tell me about a difficult decision you made without all the facts”
Last year I led a team of eight moving a software company's billing to a new system. Three weeks before go-live, testing showed that roughly one invoice in fifty was rounding tax differently from the old system, and we didn't know why.

The call was mine: launch on the date sales had promised customers, or delay.

I gave two engineers 48 hours to find the cause while the rest carried on. I met the head of sales and the finance controller together, so both heard the same numbers, and set out two options with the cost of each. With no answer after two days, I launched for new customers only and kept existing accounts on the old system for one more billing cycle.

New customers moved over on schedule. We found the bug a week later, and existing accounts moved the next month without a single corrected invoice. What I would change: set a decide-by date at the start of testing, not in the middle of a problem.

Senior answers are judged on trade-offs and on who you brought with you. Say what you gave up, not only what you gained.

Build a STAR story bank before the interview

You don't need 30 stories. Six or seven good ones, each able to answer two or three questions, cover most of a competency interview. Write them, then check the job ad for any requirement that has no story yet.

One story, several questions
Story to prepareQuestions it can answerWhat it shows
A deadline you rescuedWorked under pressure; juggled competing prioritiesDelivering at pace, prioritising
A disagreement you sorted outDisagreed with a colleague; persuaded someoneInfluencing, communication
A mistake you ownedFailed; received tough feedbackSelf-awareness, learning
Something you improved unaskedTook initiative; changed a processOwnership, changing and improving
A time you led without the titleLed a team; motivated othersLeadership
A difficult customer or stakeholderHandled a complaint; managed expectationsCustomer focus
A call made with missing factsMade a hard decision; took a riskJudgement, making decisions

Use a different story for each question in the same interview. Panels compare notes afterwards.

STAR prep sheet (fill one in per story)
Story name:
Questions it answers:

Situation (one sentence, with when and where):
Task (your part, starting with “My job was” or “I had to”):

Action (three or four steps, each starting with “I”):
1. I
2. I
3. I
Why I chose that:

Result (a number, a date, or what changed):
What I would do differently:

Spoken length: ___ seconds (aim for about two minutes)

When the STAR method is the wrong shape

STAR fits questions about the past. Plenty of interview questions are not.

  • “What would you do if...” questions. OPM calls these situational: there is no past story to tell. Answer in steps, then add “I did something similar when...” if you have a real example.
  • Strengths-based questions such as “When are you at your best?”, which some UK graduate recruiters use. Answer conversationally; a rigid four-part story sounds rehearsed.
  • Tell me about yourself, why this company, salary: no story needed.
  • Technical and case questions: think out loud instead.

You will also see CAR (Context, Action, Result) and SOAR (Situation, Obstacle, Action, Result). They are the same idea with fewer or renamed parts. Pick one and stop worrying about the acronym.

Some questions sit in between: what is your greatest weakness isn't a STAR question, but it goes better with a short story inside it.

Common STAR mistakes that cost people the answer

  • Saying “we” all the way through. “We” is fine in the situation. In the action, every sentence should start with “I”.
  • Stopping at the action. Without a result the story just ends, and the interviewer has to ask “and then?”
  • A result that was luck. If the client was always going to sign, your actions did not cause it.
  • Blaming a colleague. Even when it is true, the story makes you sound like the hard part to work with.
  • Reciting a memorised script. Lose your place and you freeze. Remember four points, not 300 words.
  • Old stories for senior roles. With ten years of work behind you, a university example makes people wonder what happened since.

When the interview is done, a short thank-you email is a good place to add the one story you forgot to tell. And save a few minutes at the end for your own questions to ask the interviewer.

Questions people ask

How long should a STAR answer be?

About two minutes spoken is a good target, with most of it on the action. If an answer runs past three minutes, cut the situation first. The interviewer can always ask for more detail, and in a structured interview they often will.

Can I use the STAR method with no work experience?

Yes. College projects, internships, part-time jobs, volunteering, sport and fest committees all count. The story has to be real and the actions have to be yours, which matters more than how big the setting was.

What if the result of my story was bad?

Use it for questions about failure or mistakes, and make the result what you changed afterwards. “I sent a report with the wrong filter, corrected it within the hour, and added a check that has caught two errors since” is a good failure story. For other questions, pick a story where your actions worked.

Is a competency-based interview the same as a STAR interview?

Competency-based interview is the name for the interview style, used mostly in the UK; in the US it is usually called a behavioural interview. STAR is the way you answer it. The questions are the same kind: tell me about a time when.

Which questions should I answer with STAR?

Anything that starts with “Tell me about a time”, “Describe a situation” or “Give me an example of”. If the question asks what you would do in the future, answer the approach first and add a past example only if you have one.

Keep reading