What STAR means
| Part | What to say | Share of your answer |
|---|---|---|
| Situation | The context: where you were and what was going on. | About 10% |
| Task | What you were responsible for, or the goal. | About 10% |
| Action | What you did, step by step, and why. | About 60% |
| Result | What happened, with a number if you can, and what you learned. | About 20% |
The shares matter. Most weak answers spend a long time setting the scene and then run out of steam right when they reach the interesting part. Give enough context for the story to make sense, then move on quickly to what you did.
How to spot a behavioral question
Behavioral questions assume that the way you acted in the past predicts how you will act in the future. You can recognize them from how they begin:
- “Tell me about a time when…”
- “Give me an example of…”
- “Describe a situation where…”
- “What did you do when…?”
- “Have you ever had to…?”
Some questions are worded as hypothetical but work well with a real story. If asked what you would do with an upset client, you can answer and then add, “In fact, something similar happened last year.”
Four worked examples
Situation: At an online furniture store, a business customer’s order for 40 desks arrived damaged a week before their office opened. Task: I handled the account, so it was up to me to fix it and to keep the customer. Action: I called them the same day rather than emailing, and I listened to what the deadline meant for them. Then I found 25 desks in another warehouse, arranged a rush delivery and got the supplier to commit to the rest within five days. I sent them a short update every morning until it was finished. Result: They opened on time. They renewed their contract, and they later referred two other companies to us. I also proposed a damage check before large orders ship, which reduced this kind of claim the following quarter.
Situation: My manager wanted to launch a new pricing page before the holidays. Task: As the analyst on the project, I had to prepare the launch report, and my data suggested that it might cost us sign-ups. Action: I didn’t argue in the meeting. I ran the numbers on our last two pricing tests and brought them to her privately, along with a proposal: test the page on 10% of traffic for two weeks rather than launching it to everyone. Result: She agreed. The test showed a 6% drop in sign-ups, so we changed the page before launch and the final version beat the original by 4%. Since then, we’ve tested every pricing change like this.
Situation: In my first year as a sales representative, I was given a target of 30 new accounts. Task: I had to reach it mainly through cold outreach, which I hadn’t done before. Action: I chased every lead for six months and reached only 12 accounts by mid-year. So I went through my pipeline with a senior colleague, saw I was spending my time on companies that were too small to buy, and focused on a narrower group. I also asked to shadow her calls. Result: I finished the year with 26 accounts, short of the target, but the second half was twice as strong as the first. The next year I reached 110% of target, using the same method.
Situation: Two weeks before a client demo, our only data engineer left the company. Task: I was a backend developer, and I was asked to keep the reporting pipeline running. Action: I asked him for a two-hour handover before he went, then read through the documentation and fixed one small issue each day to learn how it worked. I also listed what we could safely leave out of the demo and agreed this with the product manager. Result: The demo went ahead on schedule, and the client signed. I went on to maintain the pipeline for six months and wrote the documentation that we used when hiring a replacement.
Build a bank of stories
You can’t predict the exact questions, but you can have stories ready that fit almost any of them. Six to eight good stories will cover most interviews.
- Go through your resume and mark your strongest results.
- Read the job posting, and list the skills it asks for most.
- Write down six to eight stories, making sure you have a success, a failure, a conflict, a time you led something and a time you had to learn fast.
- Reduce each to four lines: one each for situation, task, action and result.
- Check which skills each story proves. Most stories can answer several different questions.
- Practice them aloud until you can tell each one in under two minutes.
Common mistakes
Before
We worked hard as a team and we communicated a lot, and in the end it went really well.
After
I rebuilt the handover checklist myself, then trained the three shift leads on it over two weeks. Missed handovers fell from eight a month to one.
- Too much situation. If you’re still explaining the background after 30 seconds, you’ve gone too far.
- “We” all the way through. The interviewer can’t tell what you did.
- No result. Ending on what you did leaves out the part they most want to hear.
- Sounding rehearsed. Remember your key points rather than your exact words.
- Announcing the labels. You don’t need to say “Situation:” aloud. The written labels here are for you.
Your opening answer often leads into these questions, so prepare it as well: here is how to answer “Tell me about yourself”.
