How to answer: the STAR method
STAR gives your answer a beginning, middle and end, so you don't ramble or skip the result:
- Situation: the context in one or two sentences. Where you were, what was going on.
- Task: what you were responsible for, or the goal.
- Action: what *you* did, step by step. This should be the longest part.
- Result: what happened, with a number if you can, and what you learned.
Aim for about 90 seconds to two minutes per answer. The most common mistake is spending a minute on the situation and ten seconds on the action. Interviewers are hiring your actions.
Weak
We had a big client complaint once and the team handled it well. Communication is really important, so we talked a lot and it worked out in the end.
Strong
A client threatened to cancel after three late deliveries (situation). As account lead I had a week to keep them (task). I called the client the same day, traced the delays to a handoff between our warehouse and shipping teams, and set up a daily ten-minute check between them, with me reporting progress to the client every Friday (action). The next six deliveries arrived on time, the client renewed for two years, and the daily check is now standard for our largest accounts (result).
Say "I", not "we". Teamwork matters, but the interviewer needs to know what you personally did.
20 common behavioral questions, by the skill they test
| Skill | Questions |
|---|---|
| Teamwork | Tell me about a time you worked with someone difficult. · Describe a time you helped a teammate who was struggling. · Tell me about a successful team project and your part in it. |
| Conflict | Tell me about a disagreement with your manager. · Describe a time you had to deliver bad news. |
| Problem solving | Tell me about a difficult problem you solved. · Describe a time you found a better way to do something. |
| Failure and learning | Tell me about a time you failed. · Describe a mistake you made and how you fixed it. · Tell me about feedback that was hard to hear. |
| Time management | Tell me about a time you had too much to do. · Describe a tight deadline you met. |
| Leadership and initiative | Tell me about a time you led without being in charge. · Describe something you started on your own. |
| Customers | Tell me about an unhappy customer you turned around. · Describe a time you went beyond what was asked for a customer. |
| Adaptability | Tell me about a time things changed suddenly. · Describe learning something new quickly. |
| Communication | Tell me about explaining something complex to a non-expert. · Describe a time you had to persuade someone who disagreed with you. |
Sample answers
In my first year as a marketing coordinator I launched an email campaign without testing the links on mobile. About 40% of our list opened on phones, and the main button didn't work for them. I noticed within an hour when clicks were far below normal, sent a short correction email that afternoon, and recovered most of the clicks by the next day. Since then I use a pre-send checklist that includes testing on two phones, and I shared it with the team; we haven't sent a broken campaign since. What I took from it is that speed only helps if the basics are checked first.
My manager wanted to cut our customer onboarding call from 45 to 20 minutes to save time. I thought new customers would get stuck and file more tickets. Instead of arguing, I asked if we could test it: half of new customers got the short call for a month. The short-call group raised about 30% more support tickets in their first two weeks, so we settled on a 30-minute call plus a checklist email. My manager got most of the time savings, and tickets stayed level. I learned that data turns a disagreement into a shared decision.
During quarter-end close, two colleagues were out sick and I was covering their reconciliations on top of mine, about twice my normal load. I listed every task with its deadline and who depended on it, then went to my manager with the list and proposed delaying two internal reports by three days. She agreed, and I asked a colleague from another team to handle the bank reconciliations, which she'd done before. We closed on time with no errors in the audit sample. Since then I keep that kind of list during every close, so I can see a crunch coming.
At my part-time job at a grocery store, a customer came back angry because the cake she'd ordered for her daughter's birthday had the wrong name on it, and the party was in two hours. I apologized, asked the bakery manager if we could redo the top, and offered her a free tray of cupcakes while she waited. We fixed it in 40 minutes. She came back the next week to thank the team and now orders all her party cakes from us. It taught me that people mostly want to feel someone is taking their problem seriously.
Build a story bank: six stories, most questions covered
Instead of memorizing 50 answers, prepare six strong stories from your own experience. Each one can answer several questions, depending on which part you emphasize.
| Story to prepare | Questions it can answer |
|---|---|
| Your biggest achievement | Proudest accomplishment, problem solving, initiative, going above and beyond |
| A real mistake or failure | Failure, mistake, hard feedback, what you learned |
| A conflict or disagreement | Difficult coworker, disagreeing with a manager, delivering bad news |
| A time you led or influenced | Leadership, initiative, persuading others, teamwork |
| A crunch or tight deadline | Time management, pressure, prioritizing, adaptability |
| A difficult customer or stakeholder | Customer service, communication, staying calm |
Write each story in STAR form with one number in the result. Students and new graduates can draw on class projects, part-time jobs, clubs, sports teams and volunteering; our list of interview questions for freshers has more examples for that stage.
Your resume bullets are a good starting point. A bullet like "Cut month-end close from 9 to 5 days" is the result of a story; the interview is where you tell the rest. The free resume bullet point generator helps you find the numbers.
Mistakes that weaken behavioral answers
- Answering hypothetically. "I would…" instead of "I did…". Behavioral questions want a real example.
- No result. Ending at the action leaves the interviewer guessing whether it worked.
- A failure that isn't one. "I work too hard" isn't a failure story. Pick a real, moderate mistake and show what changed.
- Blaming others in conflict stories. Describe the disagreement fairly and focus on what you did.
- Rambling. Over three minutes, the point gets lost. Practice out loud and time yourself.
Behavioral questions usually come after "tell me about yourself"; see how to answer "Tell me about yourself" for the opener, and questions to ask at the end of an interview for the close. Our resume examples are full of results-first bullets, and each one is the end of a story you could tell in STAR form. And once it's over, a short thank-you email the same day keeps you in mind.