Understanding the STAR method takes about two minutes. Situation, Task, Action, Result. The problem is that knowing the four letters does almost nothing for you, because the difference between a weak STAR answer and a strong one is not the structure, it is what you put inside it and how you weight the parts.
So this is not another explanation of what STAR stands for. If you want that, the full STAR method guide covers it. This is four complete, worked answers to real competency questions, each annotated so you can see exactly where the answer earns its marks and where a weaker version would have thrown them away.
One principle runs through all four, so watch for it: the Action is the answer. Situation and Task are setup and should be brief. Result is the payoff. But the Action, what you actually did, is where the interviewer is scoring you, and it should be the longest and most detailed part every time. The single most common STAR mistake is a huge Situation and a tiny Action, which is exactly backwards.
Example 1: "Tell me about a time you solved a problem"
(Situation) "In a part-time job at a garden centre, we kept running out of the most popular compost at weekends, which was our busiest time, and losing sales because customers would just leave.
(Task) Nobody had asked me to fix it, but it was my section, so I decided to work out why it kept happening.
(Action) I started actually logging when we sold out, and pretty quickly a pattern showed: the reorder was based on a weekly average, but sales were massively front-loaded to Saturday and Sunday, so we would arrive Monday fully stocked and be empty by Sunday afternoon. So I put together a simple case for my manager: order more, and specifically time the main delivery for Friday rather than Monday. I did not just say 'we need more stock', I brought the sold-out log so it was a fact, not a feeling.
(Result) We stopped running out at weekends, and my manager reckoned we recovered a few hundred pounds of lost weekend sales a month. The bigger thing was he started asking me to keep an eye on the pattern for other lines too."
Where the marks are: The Situation and Task together are three sentences. The Action is the heart of it, and notice it contains a decision (log the data), a diagnosis (front-loaded sales), and a specific, evidenced proposal (order more, deliver Friday, here is the log). A weak version would have said "so I told my manager we needed more stock and we did". The detail is what turns it from a suggestion into a demonstration of problem-solving.
Example 2: "Give an example of when you worked in a team"
(Situation) "For a final-year group project, five of us had to produce a consultancy report for a real client, and we had wildly different standards, two people wanted a quick pass, two wanted a distinction, and it was causing friction.
(Task) I was not the leader, but I could see the standards gap was going to wreck the report if we did not sort it, so I took on getting us aligned.
(Action) Rather than let it turn into an argument about effort, I suggested we spend twenty minutes agreeing what grade we were actually aiming for as a group, up front, before we did any work. It turned out the 'quick pass' pair were not lazy, they were overloaded with other deadlines that week and were being realistic. So we agreed a target we could all genuinely commit to, and I offered to take on a heavier share that week in exchange for them covering more of the final fortnight when my own deadlines eased. I basically turned a values fight into a scheduling problem, which was solvable.
(Result) We delivered a report we were all happy with, hit the grade we had agreed, and the client used two of our recommendations. And nobody fell out, which given where we started was the real win."
Where the marks are: The candidate makes themselves visible without stealing the story, the whole teamwork trap of hiding in "we" is avoided. The Action shows genuine emotional intelligence (reading the "lazy" pair correctly) and a clever reframe (values fight into scheduling problem). The Result includes both the output and the relationship, which is what teamwork questions are really testing.
Example 3: "Describe a time you failed"
(Situation) "I ran the social media for a university society, and I pushed hard to launch a big online campaign for our main event, convinced it would drive attendance.
(Task) I owned it end to end, the content, the schedule, the whole thing.
(Action) I put a lot of effort into making it look polished, and I posted consistently for two weeks. But I made a real mistake: I never actually checked whether our audience was on the platforms I was using. I assumed. I was posting beautifully crafted content mostly into a void, because most of our members were not really on that channel.
(Result) The campaign flopped. Attendance was flat, and honestly slightly down. It was a genuine failure and it was mine. What I did afterwards mattered more though, I actually surveyed our members about where they spent time online, and it turned out the answer was a completely different platform and, weirdly, physical posters in two specific buildings. The next event, I built around that, and attendance was up by about half. The lesson was blunt: I had optimised the execution of an assumption I never tested, and effort spent on an untested assumption is just expensive guessing."
Where the marks are: A real failure, owned without excuses, the honesty is what makes it credible. But the answer's weight is on the recovery and the specific lesson, not the wallowing. The failure question lives or dies on whether you learned something concrete, and "I optimised the execution of an untested assumption" is a genuinely sharp, transferable insight.
Example 4: "Tell me about a time you showed initiative"
(Situation) "In an admin role over a summer, I noticed we were manually re-typing the same customer details into three different systems every time someone signed up, and it was slow and error-prone.
(Task) It was not my job to fix the process, my job was just to do the typing, but it was obviously wasteful.
(Action) On my own time, I mapped exactly what data went where and built a simple spreadsheet template that let you enter the details once and formatted them ready to paste into each system. It was not sophisticated, just a bit of cleverness with formulas, but it cut the entry time for each new customer by more than half and basically eliminated the transcription errors. Then I wrote a one-page guide so the two other people doing the same task could use it too, rather than keeping it to myself.
(Result) It became the standard way the team did onboarding for the rest of the summer, and I gather they were still using it after I left. It saved a genuinely tedious job from eating half of everyone's mornings."
Where the marks are: Initiative means acting on something nobody asked you to. The answer nails this: the candidate explicitly notes it was not their job, which sharpens the initiative rather than weakening it. And the detail of writing a guide so others could use it shows the difference between someone who solves their own problem and someone who improves the team.
The pattern across all four
Look back and you will see the same skeleton every time: a brief Situation, a one-line Task, a rich and specific Action, and a Result that includes a number or a concrete outcome plus, ideally, a transferable lesson. That weighting, thin setup and thick action, is the thing to copy.
Reading annotated examples gets you halfway. The other half is producing your own and hearing whether they land, because the weighting that is obvious on the page collapses the moment you are nervous and start over-explaining the Situation. Build your own four using these as templates, then practise them out loud with feedback until the Action stays the biggest part even under pressure.