"Tell me about a time when..." is where many prepared candidates go blank. The question is not a trick. The interviewer wants one real event, told clearly enough to judge what you did. STAR is a simple way to tell it.
Why interviewers ask for stories#
Behavioral questions rest on a simple premise. As the US Office of Personnel Management puts it, the best predictor of future behavior on the job is past behavior under similar circumstances.
Research supports the wider format, with limits. A major review in the Journal of Applied Psychology ranked structured interviews first among the hiring methods it examined for predicting job performance. Their average correlation with job performance was .42, where 1.0 would be perfect. That is lower than older estimates but still top of that list. In a structured interview, questions are planned and answers are scored against a standard.
You will meet STAR in many places. The consulting firm DDI says it introduced the format in 1974. OPM teaches it for writing interview questions, the UK Civil Service suggests it to candidates, NHS England publishes a guide to it, and Amazon lists it in its interview preparation.
How STAR works#
| Part | What to cover | Rough share of your answer |
|---|---|---|
| Situation | The context, in a sentence or two | 20% |
| Task | What you were responsible for | 10% |
| Action | What you personally did, in order | 60% |
| Result | What changed, and what you learned | 10% |
The percentages come from MIT's career office, which treats them as approximate. The useful part is the 60%. Most weak answers spend their time on background and rush past the actions. The National Careers Service includes what you learned in the Result, and it advises keeping examples short and conversational. As a rule of thumb, aim for one to two minutes, then let the interviewer ask for more.
What weak and strong answers look like#
Here is a weak answer to "Tell me about a time you handled a difficult customer":
I always stay calm with difficult customers. At my last job we had a lot of complaints, so we would listen and try to solve them. Customers were usually happy in the end.
It sounds fine and proves nothing. It describes a habit instead of an event, hides behind "we," and ends with no result. The retail example further down answers the same question properly. These are the patterns to watch for:
| Weak pattern | Sounds like | Fix |
|---|---|---|
| Habit, not event | "I always make sure to..." | Name one day and one problem |
| Hiding in "we" | "We fixed the schedule" | "My part was rebuilding the weekend shifts" |
| All setup | Ninety seconds of company background | One or two sentences of context |
| Hypothetical | "I would speak to them" | "I spoke to them that afternoon" |
| No result | "It went well" | A number, a decision, or what changed afterward |
| Lone hero | "Nobody else could handle it" | Credit others, then name your own actions |
Expect follow-ups. OPM's training lists probes such as "What was your role?", "What was the outcome?" and "Is there anything you would have done differently?" So pick stories you can discuss for five more minutes. Never invent one, because a made-up story is hard to defend under a second follow-up.
Not every question wants STAR. "What would you do if a client missed a payment?" is what OPM calls a situational question. Answer the hypothetical directly, then add a real example if you have one.
14 common behavioral questions#
These questions often open with "tell me about a time when," "give me an example of" or "describe a situation when."
| Question | What it tests |
|---|---|
| Tell me about a time you handled a difficult customer, client or patient. | Patience, problem solving |
| Describe a conflict with a coworker and how you handled it. | Maturity, directness |
| Tell me about a teammate who was not doing their share. | Fairness, courage |
| Tell me about a mistake you made. | Honesty, ownership |
| Describe a time you missed a target or failed. | Resilience, learning |
| Describe a time you had too much to do and had to prioritize. | Judgment under pressure |
| Tell me about a tight deadline you had to meet. | Planning |
| Give an example of a time you showed initiative. | Ownership without being asked |
| Describe a problem you did not anticipate. | Adaptability |
| Tell me about a time you persuaded someone who disagreed. | Influence |
| Tell me about critical feedback you received. | Coachability |
| Describe a time you led people without formal authority. | Leadership |
| Tell me about something you had to learn quickly. | Learning speed |
| Give an example of a process you improved. | Practical improvement |
Six worked example answers#
All six are fictional examples written for this guide. The people, workplaces and numbers are invented, so borrow the shape and use your own facts.
Retail: "Tell me about a time you handled a difficult customer."#
Situation: I was a shift lead at a home appliance store. A customer came back furious because her new washing machine had arrived dented, and the delivery crew had told her the store would not replace it.
Task: She wanted a refund on the spot. Refunds that size needed the manager, who was off that day, so I had to calm things down and offer something I could actually approve.
Action: I moved us away from the queue and found the delivery note, which recorded the damage. I told her plainly what I could do: a replacement within 48 hours, or a refund the manager could authorize next morning. She chose the replacement. I booked it and phoned her the next day to confirm the slot.
Result: She kept the purchase and later left a good review. I also asked the delivery crew to call the store whenever they noted damage, and my manager made that the rule.
Nursing: "Describe a time you had too much to do and had to prioritize."#
Situation: We were one nurse short on a night shift on a medical ward. Around 2 a.m., one of my patients became confused and his oxygen level was falling. Two others were due time-critical medicines, and a relative wanted an update.
Task: I was responsible for six patients and had to decide who needed me first.
Action: I assessed the deteriorating patient first, calculated his early warning score and escalated to the on-call doctor. I asked the healthcare assistant to stay with him and repeat observations every 15 minutes. I asked the nurse in charge to give one medicine and gave the other once the doctor arrived. I told the relative honestly that I would return in 20 minutes, and I did.
Result: He was treated for a chest infection and stayed on the ward, and both medicines were given on time. I flagged the staffing gap at handover. I also learned to ask for help earlier, before I am stretched.
Warehouse: "Give an example of a process you improved."#
Situation: I supervised 12 pickers at a distribution warehouse. Returns for wrong items had been rising for three months.
Task: My manager asked me to find out why and bring errors down without adding staff.
Action: I sorted a month of returns by product and found that over half came from two aisles where look-alike items sat side by side. I spent two shifts picking with the team to see it firsthand. Then I moved those items apart, added larger labels and made a scanner check compulsory on those aisles. I briefed each shift myself, starting with nights, where errors were highest.
Result: Wrong-item returns fell by about 40% over two months. Picking slowed slightly for a week and then recovered, and the other shifts adopted the layout.
Accounts: "Tell me about a mistake you made."#
Situation: I was an accounts executive at a distributor. At month-end I paid a supplier twice, about 2.4 lakh rupees, because I was working from two versions of a payment list.
Task: I spotted it the next morning. I had to tell my manager and recover the money.
Action: I told her within the hour, before trying anything else, with the amount, the cause and a plan. I called the supplier's accounts team, and they agreed to adjust it against the next invoice. I got that in writing and corrected the ledger. Then I set up one shared payment sheet with a locked "paid" column and asked for a second check on large batches.
Result: The money was recovered within ten days at no cost. We had no duplicate payments in the 14 months before I left. I learned to report problems early, while the fix is still cheap.
Fresher: "Tell me about a teammate who was not doing their share."#
Situation: In my final year, four of us built a market survey for a local food business, worth 30% of our course mark. Two weeks before the deadline, one teammate had not sent his 50 interviews.
Task: I was coordinating the group, so I had to get the data in without starting a fight.
Action: I met him alone instead of raising it in the group chat and asked what was going on. He had taken evening shifts and was embarrassed to be behind. I suggested a swap: he would clean the data, which he could do late at night, while another teammate and I split the remaining interviews. I told our tutor so the contribution record stayed accurate.
Result: We submitted on time and earned one of the top grades in the class. He also found errors in my own entries. Now I ask before I assume someone is not trying.
Software: "Describe a conflict with a coworker."#
Situation: I was a backend developer on a billing product. A product manager wanted a new invoice feature live by Friday for a customer demo, and I believed that meant skipping tests on tax rounding.
Task: I needed to raise the risk without blocking the demo or turning it into a fight between teams.
Action: I asked for 15 minutes and showed her two past invoices where rounding had gone wrong. We worked out what the demo truly needed. I proposed releasing the feature only to the demo customer, then finishing the tests before general release the next Tuesday.
Result: The demo went ahead. On Tuesday the tests caught one rounding error, which we fixed before any other customer saw it. She now brings me in earlier on billing work.
Building your own answers#
Start with the job description, since it lists the skills the employer wants. MIT suggests preparing three to five stories, since one can often be adapted to several questions. Draw a grid with your stories across the top and the 14 questions down the side, then tick where each story fits. Any empty row shows where you may need another.
Short on work history? The UK Civil Service says examples can come from work, volunteering or a hobby. Coursework, a family business or caring for a relative can count too, if you can say what you did and what came of it.
Say "I" without feeling boastful. MIT's advice is to use "I" statements even in team stories. If you were raised to say "we," try this: "My team of five had the target. My part was the supplier side."
For failure questions, pick something real that you have since fixed, and avoid anything central to the job you want. Spend most of your time on what you changed afterward.
Write bullets, not scripts, then practice aloud twice. The interview preparation guide covers the rest of the groundwork, from employer research to the questions you should ask.
To rehearse with questions closer to your target role, make a set with the interview questions generator and answer two of them aloud using the stories you chose.
