STAR Method Explained: 20 Real Interview Answer Examples

Before: build, match and time your STAR answers

Three weeks out — build the story bank

1. Book two 45-minute sessions in your calendar, on separate days. One session produces a thin bank; sleeping on it surfaces the stories you forgot.
2. Open your last two years of work: calendar, emails, handover notes, shift rotas, appraisal forms. Pull out anything with a date and an outcome attached.
3. Write one line per story, not a script. Each line needs four things: who you were, where, how big it was, and how it ended.
4. Aim for twenty prompts covering the competencies below. Most interviews draw from this set regardless of sector.

• A complaint you fixed — tests service recovery. A café supervisor who refunded a spoiled catering order and kept the account.
• A deadline at risk — tests planning under pressure. A junior analyst who moved a month-end report from five days to three.
• A disagreement with a colleague — tests conflict resolution. Two shift leads arguing over who covered the bank holiday rota.
• A mistake you made — tests accountability. A dispensing near-miss caught at the final check.
• A change imposed on you — tests adaptability. A new rostering system introduced across four sites in one month.
• Persuading someone senior — tests influencing without authority. Convincing a store manager to move deliveries to mornings.
• Training someone — tests coaching. Bringing a new care assistant up to independent shifts in six weeks.
• Improving a process — tests continuous improvement. Rewriting a returns checklist used by nine staff.
• Competing priorities — tests prioritisation. Three clients wanting the same Friday slot.
• A difficult customer, patient or client — tests emotional regulation. A distressed relative at a reception desk.
• Working with incomplete information — tests judgement under ambiguity. Quoting a job with half the survey missing.
• Spotting a risk — tests safety and compliance awareness. A blocked fire exit noticed on a night shift.
• Leading without the title — tests initiative. Running a handover when the supervisor called in sick.
• Detail and accuracy work — tests precision. Reconciling a stock count across two warehouses.
• Delivering bad news — tests difficult conversations. Telling a customer their order would miss a wedding date.
• Working across departments — tests collaboration. Getting finance and operations to agree one invoice format.
• Learning something fast — tests learning agility. Picking up a new booking system over one weekend.
• Pushing back on scope — tests boundary setting. Declining an extra task that would have breached a deadline.
• A technical or system failure — tests troubleshooting. A till network outage during a Saturday trade.
• The result you are proudest of — tests ownership and impact. Anything with a number and your name on it.

Two weeks out — match stories to this job

1. Print the job advert. Highlight every phrase that describes behaviour rather than qualifications — 'works to tight deadlines', 'handles escalations', 'supports new starters'.
2. Write the highlighted phrase in one column and the number of the matching story beside it. If a phrase has no story, that is your gap; go and find one before you rehearse anything else.
3. Cap it at eight core stories for a one-hour interview. Any story can answer three or four different questions if you change which part you emphasise.

One week out — write the long version, then cut it

1. Write two or three of your strongest stories out in full, then cut them to 150 words. Anything over 180 words spoken aloud runs past two minutes.
2. Split your time roughly 15 seconds Situation and Task, 45 seconds Action, 20 seconds Result.
3. Check every sentence in the Action section starts with 'I' rather than 'we'. Panels cannot score a 'we'.

Near-miss in a community pharmacy — accountability

I was the dispensing technician on a Saturday shift covering around 300 items with one pharmacist. I picked a 10mg pack instead of 100mg for a repeat patient and the pharmacist caught it at the final check. My task was to make sure it never reached a patient and never happened again on my bench. I logged it as a near-miss the same hour rather than at the end of the day, told the pharmacist exactly what I had done, and asked to be part of the review. I found I was picking two prescriptions at once when the queue built up. I changed to one basket at a time and suggested we mark the three highest-risk strengths with coloured tags. In the following three months my bench recorded no further picking errors, and the tags stayed in place after I left.

Rota conflict on a distribution site — conflict resolution

As shift supervisor on a night pick-and-pack operation with eighteen staff, I clashed with the day supervisor over who released agency workers at the end of peak. He was sending them home before our volume landed, which left me two people short twice in one week. My task was to fix the handover without escalating it to the site manager. I asked him for fifteen minutes before shift rather than arguing on the floor, and I brought the scan data for both weeks so we were looking at the same numbers. He had been given a labour-hours target I did not know about. We agreed he would hold four agency staff back on any night the inbound trailer was late, and I would text him the trailer status by six. We ran the remaining five weeks of peak without a shortfall, and kept the arrangement afterwards.

48 hours out — rehearse out loud, on a clock

1. Say each answer aloud, standing, with a timer visible. Silent rehearsal hides the rambling.
2. Record two answers on your phone and listen back once. You are listening for one thing only: how long it takes you to reach the word 'I'.
3. Write your twenty story titles — three or four words each — on one index card. Titles only. A card with sentences on it will pull your eyes down during the interview.

Morning of — set the room

1. For a video interview, sit down 10 minutes early, test audio, and put the index card just under the camera so glancing at it reads as eye contact.
2. For an in-person interview, keep the card in a folder you can open on the table. Ask 'do you mind if I keep a few notes in front of me?' as you sit down.
3. Have one glass of water within reach. A two-second sip is a legitimate way to buy thinking time.

During: what to actually do in the room

• Pause for two or three seconds before you start. Silence reads as considered; filling it with 'so, um, I suppose' reads as unprepared.
• Name the story first in one clause: 'This is from my time as a night shift supervisor during peak.' The interviewer now knows where to file everything that follows.
• Keep Situation to two sentences. Name the place, your role, and the scale — number of staff, size of the caseload, value of the order.
• Say the Task as an explicit sentence beginning 'My job was to…'. Most weak answers skip this entirely and the panel cannot tell what you were accountable for.
• Use 'I' for every action you personally took, and use 'we' only where you are genuinely crediting a team. If you catch yourself three 'we's in a row, stop and restate: 'My part in that was…'.
• Signpost the ending out loud: 'The result was…'. It tells the panel to start writing, and it stops you drifting into a second story.
• Finish the Result with something countable or something observable — a time saved, a complaint closed, a person who passed probation, a policy that is still in use.
• Watch the note-taking. If the interviewer's pen stops, you have moved past what they are scoring. Land the result and stop.
• Offer the off-ramp when you are unsure how much detail they want: 'I can go into how I built the checklist, or move on — which is more useful?'
• When they probe with 'what would you do differently?', answer it properly with one specific change. Saying 'nothing, it went well' is scored as a lack of reflection.
• If you blank, say so and redirect: 'Can I come back to that one? I have a closer example from the rota problem I mentioned.' A short repair beats ninety seconds of invented detail.
• Glance at your index card between questions, not during answers.

Month-end under pressure — planning and prioritisation

I was the junior analyst on a three-person finance team producing the month-end pack for a business with four regional depots. In my second month, the depot files arrived two days late and the pack was due to the board on the Thursday. My task was to deliver a usable pack on time without guessing at numbers. I called each depot manager that morning rather than emailing, and got verbal confirmation of the two figures that drove ninety per cent of the variance. I built those in first, flagged the outstanding lines in amber, and sent the pack on the Wednesday evening with a note listing exactly what was provisional. The board got its numbers on time and nothing had to be restated. After that I set a standing reminder to the depots five working days out, and the files arrived on time for the rest of the year.

After: what to send, and when

• Within two hours — write it down for yourself. List every question you were asked, in order, and mark the two answers that went badly. This is the single most useful thing you will do, whether or not you get this job.
• Within 24 hours — send one short thank-you email to whoever arranged the interview, asking them to pass it on to the panel if you do not have their addresses. Keep it to four or five sentences.
• Use that email to repair one answer, not three. Two sentences: 'You asked about a time I handled a system failure and I gave you the till outage. The stronger example is the stock system migration I led over one weekend — happy to talk it through if useful.'
• Reference one specific thing from the conversation — a project they mentioned, a change to the team, a shift pattern. It proves you were listening and separates your message from the templates.
• Send anything they requested the same working day — references, a portfolio, right-to-work documents, a task or presentation. Delay here is scored even when nobody says so.
• If they gave a decision date, wait until two working days after it before chasing. Then send one message asking whether there is an update and confirming you are still interested.
• If you are rejected, reply once, within a week, thanking them and asking for one line of feedback on your examples specifically. Asking about your answers rather than 'why didn't I get it' gets a reply more often.
• Update your story bank the same week. Add any question you had no story for, and rewrite the two answers you marked as weak. The next interview is a month away at most.
• Do not send a second thank-you, a connection request with a pitch attached, or a message to someone on the panel you did not speak to.

What to avoid in STAR answers

Here is the same story told badly and then properly. The weak version: 'We had a lot of escalations coming in and we worked really hard as a team and eventually we got on top of them.' No role, no scale, no action, no result.

Escalation backlog in a contact centre — ownership

I was a team leader in a twelve-seat contact centre and we had around ninety escalated complaints sitting past their ten-day response target. My task was to clear the backlog inside a month without pulling the whole team off live calls. I sorted the queue by age and by the reason for escalation, and found that just over half were billing queries with the same root cause. I wrote a single response template for that group, checked it with the billing lead, and handled those cases myself across four afternoons. I gave the remaining complex cases to two advisors with protected time of two hours a day. We cleared the backlog in three weeks, and the template was adopted by the other two teams on the floor. Nothing went past target again while I was in the role.

STAR method checklist

Three weeks out

• Two 45-minute sessions booked on separate days
• Twenty story prompts written, one line each
• Every prompt has a role, a setting, a scale and an outcome

Two weeks out

• Job advert printed and behaviour phrases highlighted
• Each phrase matched to a story number
• Gaps identified and filled with a real example
• Eight core stories selected

One week out

• Three strongest answers written out and cut to 150 words
• Timing split checked: 15 seconds Situation and Task, 45 Action, 20 Result
• Every Action sentence starts with 'I'
• A 'what would you do differently' line ready for each story

48 hours out

• Each answer said aloud against a visible timer
• Two answers recorded and listened back once
• Index card written with story titles only, three or four words each

On the day

• Seated and tested 10 minutes early, or card in an openable folder
• Water within reach
• Permission asked to keep notes on the table

In the room

• Two-second pause before each answer
• Story named in the opening clause
• 'My job was to…' said explicitly
• 'The result was…' signposted before you stop
• Off-ramp offered when detail is uncertain
• Blanks repaired out loud rather than filled with invention

Afterwards

• Questions written down within two hours, weak answers marked
• Thank-you email sent within 24 hours, repairing one answer
• Requested documents or tasks sent the same working day
• Chase sent two working days after any stated decision date
• Story bank updated the same week

Frequently asked questions