The STAR method for interview answers, with examples
The STAR interview method turns “Tell me about a time…” into a short, true story: the Situation, your Task, the Action you took and the Result. Here’s how much to say in each part, eight STAR method examples, and a free checker for your own answer.
Updated September 2026. Sources are listed at the end.
What is the STAR method?
Behavioural interview questions ask what you did, on the idea that how you handled a real situation says more than how you say you would. They start with “Tell me about a time…”, “Give an example of…” or “Describe a situation where…”. The STAR technique is the shape of a good answer. MIT’s careers office suggests a rough balance for each part:
- SSituation Where you were and what was going on. Just enough context for the rest to make sense: one or two sentences.
- TTask What you were responsible for, or the goal. This is what makes the action yours.
- AAction What you did, step by step, in the first person. The interviewer is scoring this part most.
- RResult What changed because of what you did, with a number where you have one, and what you learned.
Spoken, a common guide is one and a half to two minutes. The action is where you show the skill the question is about, so it gets most of the time. The result closes the story; the UK’s National Careers Service suggests including what you learned.
A STAR answer, before and after
“Tell me about a time you improved a process.”
In my last job the invoice process was really slow, so we looked at it and made some changes to how things worked. It took a while, but in the end it was a lot better and everyone was happier. I’m always looking for ways to make things more efficient.
SAt my last job, a building supplies company, suppliers were paid late about one month in three because invoices sat in email inboxes waiting for approval.
TMy manager asked me to find out why payments were late and fix it before our end-of-year audit.
AI tracked 200 invoices from arrival to payment in a spreadsheet and found that 70% of the delay was waiting for a manager to approve by email. I proposed a shared approvals inbox with a two-day rule, wrote a one-page guide for the 12 managers who approve invoices, and set up a Friday report listing anything older than five days. When two managers kept missing the deadline, I met them to find out why and moved their approvals to their team leaders.
RWithin three months, the average time to pay fell from 38 days to 19, and we paid on time every month that year. I learned to measure a problem before proposing a fix: the data made the case for me.
- The situation takes one sentence, and the task makes clear it was this person’s job.
- The action is specific: 200 invoices tracked, a two-day rule, a one-page guide, a weekly report.
- The result has a before and after (38 days to 19) and a lesson.
STAR method examples
Made-up people and numbers, to show the shape of a strong answer. Yours should use your own experience.
- Tell me about a time you solved a difficult problem.
- Describe a time you had to deal with a difficult customer.
- Give an example of a time you worked under a tight deadline.
- Tell me about a time you disagreed with a colleague.
- Tell me about a time you made a mistake.
- Tell me about a time you led a team.
- Describe a time you had to learn something new quickly.
“Tell me about a time you solved a difficult problem.”
SAt the accounting firm where I work, staff in one office kept losing their connection to our client system several times a day, and two other support people had already closed the ticket as “network issues”.
TI picked up the ticket when the office manager escalated it, with a client deadline two weeks away.
AI asked the 15 affected staff to log the exact time of every drop for three days and matched the times against our network logs. The drops lined up with the building’s backup running every two hours, which was saturating the office’s older internet link. I rescheduled the backup to 11 pm with the building manager, asked our provider to confirm the link speed, and wrote up the cause in our knowledge base so the next person wouldn’t start from scratch.
RThe drops stopped the same day, and the office hit its client deadline. Since then I always ask for the times of a fault before I look for the cause.
“Describe a time you had to deal with a difficult customer.”
SOn a fully booked Saturday night, a guest arrived to find the room type he’d booked wasn’t available because of a burst pipe, and he was angry at the desk in front of a queue of other guests.
TAs the supervisor on shift, it was my job to calm the situation and find him somewhere to sleep that night.
AI asked a colleague to take the queue and moved the conversation to a quiet corner of the lobby. I let him explain everything without interrupting, apologised for what had happened rather than defending it, and told him exactly what I could do: an upgraded room at our sister hotel ten minutes away, a paid taxi there and back, and breakfast included. I rang ahead to make sure the room was ready before he left, and emailed him a written summary so he didn’t have to take my word for it.
RHe accepted, and the next week he left a review naming me for how the problem was handled. Our manager now uses the same steps for any overbooking.
“Give an example of a time you worked under a tight deadline.”
STwo weeks before a trade show, the printer we’d booked for our stand graphics went out of business, and our design files were in a format other printers couldn’t use.
TI was responsible for the stand, so I had to get new graphics made and delivered in nine working days.
AI called five printers that afternoon and found two that could meet the date if they had print-ready files within three days. I asked our designer to prioritise the two main panels over the smaller signs, agreed with my manager which smaller items we could drop, and booked the printer that offered delivery straight to the venue. I checked the proofs the same evening each time so no day was lost waiting for approval.
RThe stand was up the day before the show, and we collected 240 leads, our best result at that show. I now keep print-ready backups of every file.
“Tell me about a time you disagreed with a colleague.”
SOn a surgical ward, a senior colleague and I disagreed about whether a patient recovering from surgery was ready to be moved to a general ward overnight.
TI was the nurse caring for the patient that shift, so it was my job to raise my concern clearly and safely.
AI asked my colleague for five minutes away from the patient and explained what I’d seen: the patient’s breathing rate had risen twice in four hours, which wasn’t yet at the escalation level but was trending the wrong way. I suggested we check again in an hour and ask the doctor on call rather than argue about it. I documented both readings and my concern in the notes before we spoke to the doctor.
RThe doctor kept the patient on our ward overnight, and a chest infection was picked up early the next morning. My colleague and I agreed to use the same “check, then escalate together” approach when we disagree.
“Tell me about a time you made a mistake.”
SIn my first year as an assistant accountant, I sent a client’s quarterly tax figures to our manager with one expense account counted twice.
TI found the error myself two days later while preparing the next client’s return, before anything had been lodged.
AI told my manager straight away, showed her where the double count came from and gave her the corrected figures the same morning. Then I looked at why it had happened: I’d copied the expense list from a spreadsheet that already included one account. I added a check to my own routine, comparing each total against the general ledger before sending anything, and suggested the team add the same line to our review checklist.
RThe client’s return was lodged correctly and on time, and the checklist change was adopted by the whole team. I learned that owning a mistake early makes it small.
“Tell me about a time you led a team.”
SAt university I volunteered with a student group that ran a free tax help service for other students, and in my final year our coordinator left a month before tax season.
TI agreed to step in and lead the 14 volunteers through the six-week season.
AI split the volunteers into three shifts, each with one experienced person, so no new volunteer worked alone. I ran a two-hour training session using real (anonymised) questions from the year before, set up a shared booking sheet so students could choose a time rather than queue, and held a ten-minute check-in at the end of each week to fix what wasn’t working. When one shift kept running late, I moved a volunteer from our quietest shift to help.
RWe helped 310 students, up from 220 the year before, and 11 of the 14 volunteers came back the next year. It taught me that a clear structure lets people do their best work.
“Describe a time you had to learn something new quickly.”
SAs a high school maths teacher, I was asked to take over the school’s student results reporting when the staff member who ran it went on leave, a week before reports were due to 900 families.
TI had to learn the reporting system and get the reports out on time without errors.
AI spent the first evening working through the system’s training guide and wrote down every step I didn’t understand. The next morning I booked 30 minutes with the vendor’s support line and worked through my list. I ran the reports first for one class of 28 students and checked every figure by hand against the markbook before running the rest, and I asked a colleague to spot-check ten reports at random.
RAll 900 reports went out on the due date with no corrections needed. It’s also what got me interested in data: I’ve since completed a certificate in data analytics.
Check your STAR answer
Paste an answer below. The checker shows which parts of STAR it has, whether the result has a number, and the questions that would fill any gaps. It never invents details for you. Free, no account needed.
Common STAR mistakes
- “We” all the way through. The interviewer can’t tell what you did. Say “I” for your part.
- A long situation. Half the answer on background leaves no time for the action. Keep it to a sentence or two.
- No result. “It went well” isn’t a result. Say what changed, with a number if you have one.
- Too general. “I always communicate clearly” isn’t an example. Pick one specific time.
- The wrong skill. A great story that doesn’t show what the question (or the job ad) asks for still misses.
- Stretching the truth. Interviewers ask follow-up questions. Only tell stories you can talk about in detail.
How to prepare STAR stories
- 1Read the job adList the skills it asks for: teamwork, problem-solving, customer service, leadership.
- 2Find 6 to 8 storiesFrom work, study, volunteering or home. One story can cover more than one skill.
- 3Write each in STARShort notes, not a script, so you sound natural rather than rehearsed.
- 4Say them out loudAnswers that read well often run long when spoken. Time yourself.
Questions
What is the STAR method?
A way to structure answers to behavioural interview questions (“Tell me about a time…”) as a short, true story: the Situation, your Task, the Action you took and the Result. It keeps answers specific and shows the interviewer what you did, not what you would do.
How long should a STAR answer be?
A common guide is one and a half to two minutes spoken, roughly 200 to 300 words. MIT suggests spending about 20% on the situation, 10% on the task, 60% on your actions and 10% on the result.
Is the STAR technique the same as the STAR approach?
Yes. STAR method, STAR technique, STAR approach and STAR format all mean the same structure. Variants add a letter: STARL (or STAR+L) ends with what you learned, and CAR or PAR (Challenge or Problem, Action, Result) fold the situation and task together.
Can I use examples from outside work?
Yes. The UK’s National Careers Service suggests examples from work, home or volunteering, and study or part-time jobs work too. Choose the example that best shows the skill the question asks about.
Should I say “I” or “we”?
Say “I” for what you did. Mention the team for context, but the interviewer needs to know your part: an answer that says “we” all the way through gives them nothing to score.
Can I use STAR in written applications?
Yes. It works for cover letters, application forms and selection criteria. The Victorian and NSW governments both recommend it for job applications. See our selection criteria examples.