STAR Method Examples: How to Answer Behavioural Interview Questions
What STAR stands for (and why it works)
STAR is a framework recommended by the National Careers Service for structuring answers in interviews, cover letters and application forms. [1] Here is what each letter means:
| Letter | What it covers | Rough word count |
|---|---|---|
| S — Situation | The context: where, when, what was happening | 20–40 words |
| T — Task | Your specific responsibility in that situation | 15–30 words |
| A — Action | What you personally did, step by step | 60–100 words |
| R — Result | What happened, what you learned, what changed | 30–50 words |
The Action section should take up the most space. That is where interviewers learn how you think and work. The Situation is just scene-setting — keep it brief. [1]
You can draw examples from paid work, volunteering, study, sport or community involvement. The source matters less than the quality of the story. [1] For a fuller explanation of the framework itself, see our STAR Method Interview: A Complete Practical Guide.
What good STAR method examples look like
A strong answer does four things well:
- Names a specific event, not a general habit. "I always do X" is not a STAR answer.
- Uses 'I', not 'we'. Interviewers want to know what you did, not what the team did.
- Gives a concrete result — a number, a decision made, a problem resolved, a lesson applied.
- Stays under two minutes when spoken aloud. Aim for 200–300 words on paper.
Interviewers who use behavioural questions are looking for evidence that past behaviour predicts future performance. The clearer your story, the easier it is for them to score you. [4]
STAR method examples: entry-level and graduate roles
Customer service: handling a complaint
- Situation
- I was working a weekend shift at a busy café (this is an illustrative example). A customer became frustrated because their order had been delayed by 20 minutes during a large lunchtime rush.
- Task
- My job was to resolve the complaint quickly, keep the customer calm and make sure they left satisfied — without pulling the manager away from the kitchen.
- Action
- I went over to the customer straight away, apologised without making excuses and explained there had been an unexpected rush. I offered a complimentary drink while they waited and gave them a realistic updated time. I then checked with the kitchen on the order status and relayed that back to the customer personally.
- Result
- The customer thanked me and left a positive comment on the feedback form. The manager later used the approach I took as an example in our next team briefing.
Why it works: the action section shows initiative and communication skills without overstating the stakes. The result is specific and credible. This is the kind of story that answers a classic tell me about a time when interview question about dealing with a difficult customer.
Teamwork: university group project
- Situation
- In my final year, our four-person group had a 3,000-word report due in two weeks (illustrative). Two members had conflicting part-time work schedules and we had not agreed on who was doing what.
- Task
- I took on the role of coordinating the group after it became clear no one else was going to step up.
- Action
- I set up a shared document, broke the report into sections and matched tasks to each person's availability. I scheduled two short check-ins via video call and created a simple tracker so everyone could see progress. When one member fell behind, I redistributed a small section to another volunteer rather than raising it as a conflict.
- Result
- We submitted on time and received a 2:1. The group said the structure I put in place made the process much less stressful than previous projects.
Why it works: this shows leadership without a formal title — a common ask in graduate interviews. The action is detailed and personal, using 'I' throughout even though the context is a team setting.
STAR method examples: mid-level roles
Problem solving: a process that was failing
- Situation
- I was a project coordinator at a logistics company (illustrative). Our weekly reporting process was taking the team six hours to complete manually, and errors were causing delays in client updates.
- Task
- I was asked to find a way to reduce the time spent and improve accuracy, without buying new software.
- Action
- I mapped the existing process end to end, identified three steps that duplicated effort and built a template in Excel that automated the calculations. I ran a short training session with the team and wrote a one-page guide for new starters. I also set up a monthly review to catch any drift back to the old method.
- Result
- The process dropped from six hours to under two. Error rates fell noticeably in the first month and the client team reported fewer queries. My manager presented the change at a department review.
Why it works: the action section shows analytical thinking, communication and follow-through. The result is specific and tied to business impact. Quantifying the time saving — even approximately — makes the story far more memorable than a vague 'things improved'.
Conflict: disagreement with a colleague
- Situation
- I was a marketing executive working on a product launch campaign (illustrative). A colleague and I disagreed on the channel mix — they wanted to focus entirely on paid social, while I felt email nurture was being undervalued.
- Task
- I needed to resolve the disagreement constructively and reach a decision in time for the campaign brief deadline.
- Action
- Rather than escalating, I asked my colleague if we could each put together a short rationale with supporting data. We then presented both views to our line manager together. I made sure to acknowledge the strengths in my colleague's approach before making my case. We agreed on a split budget with a review point at week four.
- Result
- The campaign launched on time. At the four-week review, email had outperformed the initial projection, and the team agreed to increase its share for the next phase. My colleague and I now collaborate on briefs regularly.
Why it works: this answers a common tell me about a time when interview question about conflict without making anyone look bad. It shows maturity and data-led thinking. The result is honest — not a sweeping win, but a measured outcome with a clear follow-on.
STAR method examples: senior and leadership roles
Leadership under pressure
- Situation
- I was head of operations at a mid-sized retailer (illustrative). Three weeks before our busiest trading period, our primary warehouse management system went down following a failed update.
- Task
- I had to keep fulfilment running, communicate with stakeholders and manage a team that was understandably anxious — all while the technical fix was under way.
- Action
- I convened an incident call within the hour, assigned a deputy to liaise with the IT supplier and set up a manual workaround using spreadsheets and a daily stand-up. I sent a brief daily update to the commercial director and the customer service lead so no one was surprised. I also made a point of walking the warehouse floor each morning to keep morale steady.
- Result
- We maintained despatch at close to our normal rate throughout the nine-day outage. The board cited the incident response in my annual review as an example of effective crisis management.
Why it works: senior answers need to show decision-making, communication upwards and downwards, and composure under pressure. This does all three. Notice that the result is honest — it does not claim perfection, which makes it more credible.
Driving change: introducing a new process
- Situation
- I joined a professional services firm as a senior manager (illustrative). The team had no consistent approach to client onboarding — each account manager did it differently, leading to variable client experience and longer ramp-up times.
- Task
- My brief was to design and implement a standardised onboarding process within my first six months.
- Action
- I spent the first four weeks interviewing account managers, clients and the support team to understand what was and was not working. I then drafted a process map, ran two workshops to get buy-in and piloted it with three new clients. I incorporated feedback before rolling it out to the full team, and built a short onboarding guide into the intranet.
- Result
- Average client ramp-up time reduced over the following quarter. Client satisfaction scores for onboarding improved in the next survey cycle. The process has since been adopted by a second regional team.
Why it works: this shows stakeholder management, structured thinking and the ability to deliver change without forcing it. The result is measured and honest — no invented percentages, just clear directional outcomes that any interviewer will find credible.
Common STAR method mistakes to avoid
Even well-prepared candidates make these errors:
- Telling a team story instead of a personal one. Use 'I' throughout the Action section.
- Spending too long on the Situation. If you are still setting the scene after 60 words, cut it back.
- Skipping the Result. 'The project went well' is not a result. What changed? What was measured? What did you learn?
- Choosing an example that makes you look passive. Pick stories where you drove the outcome.
- Memorising a script word for word. Interviewers will ask follow-up questions — you need to know the story, not the lines. [1]
- Picking a negative result and not recovering it. If things went wrong, explain what you learned and what you would do differently.
Practise matters more than most candidates realise. The National Careers Service recommends practising your answers before the interview — ideally with someone who can give honest feedback. [2] Saying your answer aloud is the only way to know if it runs over time.
How to prepare your own STAR method examples
Before any interview, build a bank of six to eight stories that cover the competencies most commonly tested: leadership, teamwork, problem solving, communication, handling pressure, conflict and delivering results. [2]
To build each story, work backwards:
- Read the job description and identify the key competencies.
- Match each competency to a real experience from your work, study or life.
- Draft the four STAR sections in writing first — it forces clarity.
- Read it aloud and time it. Aim for 90 seconds to two minutes.
- Prepare for follow-up questions: 'What would you do differently?' or 'How did your manager react?'
If you want to practise answering tell me about a time when interview questions under realistic conditions, Interview Coach gives you eight role-specific behavioural questions, STAR-structured feedback and a model answer for each. One session is free with no card needed.
Your STAR examples are also useful beyond the interview room. The National Careers Service notes that the method works equally well in cover letters and application form answers. [1] If you are still working on your application, CV Studio can help you tailor your CV to the role before you reach interview stage.
Frequently asked questions
How long should a STAR answer be?
Aim for 200–300 words on paper, or 90 seconds to two minutes when spoken. The Action section should be the longest part. If your Situation alone is taking a minute, cut it back. Interviewers want to hear what you did, not a lengthy backstory.
Can I use the same STAR example for different questions?
Sometimes, yes — a strong story can demonstrate leadership, communication and problem solving at once. But try to have at least six different examples prepared. Reusing the same story for every question makes it look like your experience is narrow, and interviewers often notice.
What if I do not have work experience? Can I still use STAR?
Yes. The National Careers Service explicitly says examples can come from school, volunteering, sport or home life. [1] A university project, a fundraising event or a part-time job all count. Focus on what you personally did and what the outcome was.
What are the most common tell me about a time when interview questions?
The most frequently tested areas cover: a time you dealt with a difficult colleague or customer, a time you worked under pressure, a time you showed leadership, a time you solved a problem, and a time you made a mistake and what you learned. Prepare a story for each before any interview. [4]
How do I give a good result if the project did not go well?
Be honest, then pivot to learning. Explain what happened, what you would do differently and — if possible — what you changed afterwards. Interviewers value self-awareness. A candidate who can reflect on failure clearly is often more impressive than one who only shares successes.
Does STAR work for competency-based application forms as well as interviews?
Yes. The structure works just as well in writing. Keep each written answer to around 200–250 words, use the same four sections and make sure your Result is specific. Many public sector and graduate scheme applications use competency questions that expect a STAR-style response. [1]
Related guides
- STAR Method Interview: A Complete Practical Guide
Master the STAR method interview technique with step-by-step guidance, UK examples, a mistakes table and a preparation checklist you can use today.