The STAR method: interview answers that survive the follow-up
The STAR method is a simple way to answer "Tell me about a time when..." questions: Situation, Task, Action, Result. The four letters are the easy part. The follow-up questions are not.
One of the stories in my story bank is a client project for a large French industrial group that was slipping: potentially six months late, with a strategic milestone for the company at risk. My role was coordinator and facilitator. I did diplomacy between the stream leads to rebuild trust and collaboration. In the end, the budget overrun was eliminated, the roadmap got ahead of schedule, and the sponsors expect to secure a v1.1. It sounds like a good story. Then ask yourself the three questions below.
This guide is the STAR method as I would use it today, with the part most guides skip: preparing for the follow-up.

What is the STAR method?
The STAR method, also called the STAR format, structures an answer in four parts. It turns a claim ("I'm good with difficult customers") into a short story the interviewer can check.
| Step | What you say | Share of the answer |
|---|---|---|
| Situation | The context in one or two sentences: where, when, what was at stake. | About 20% |
| Task | What was expected of you, personally. | About 10% |
| Action | What you did, step by step, and why. Say "I", not "we". | About 50% |
| Result | What changed because of you, with a number when you have one. | About 20% |
MIT's career office suggests 60% for the action and 10% for the result. I give the result 20%, taken from the action: that is where the follow-up lands. Don't time yourself. Just keep the action the longest part, and give the result real room.
Which behavioral interview questions call for the STAR method?
Behavioral interview questions: the ones that ask for a real example rather than an opinion. An interviewer can't check what you would do. They can check what you did. You can spot these questions by their first words:
- "Tell me about a time when..."
- "Give me an example of..."
- "Describe a situation in which..."
- "How did you handle..."
Some of them sound like yes-or-no questions: "Have you ever managed a difficult stakeholder?" Answering "Yes." is true, and it tells the interviewer nothing. Say yes, then tell the story.
STAR method interview examples: a weak answer, then the same one fixed
The STAR method examples in the guides that rank first on Google come from school or a first job. Here is one with more at stake.
A fictional example, for a Customer Success Manager role.
The question: "Tell me about an unhappy customer you managed to keep."
The weak answer:
"Yes, that happened a lot, it's kind of the core of the job. We had a big customer who wasn't happy with the product, we had several meetings, we worked a lot with the product team, and in the end they stayed. I think it's mostly about listening."
What's wrong: no specific situation, a "we" that hides your role, no concrete action, a vague result, and a general conclusion that proves nothing.
The same answer with STAR:
Situation. "Last year, one of my five largest accounts, a distributor, told us three months before renewal that they wouldn't renew: their teams had almost stopped using the tool."
Task. "I owned the account, and my goal was the renewal."
Action. "First, I pulled usage data by team: two teams out of six had dropped off, because a feature didn't fit the way they worked. I ran a workshop with those two teams and our product team to find a workaround, then set up a call every two weeks with their manager until the renewal date."
Result. "Both teams were back on the tool within a month, and the customer renewed for two years."
Same story, twice as long. Now the interviewer knows what you did, how, and with what effect. It still isn't ready for the follow-up.
Why STAR answers fall apart under follow-up questions
A good interviewer doesn't stop at your story. They dig into the numbers: how big the situation was, how much changed, how much of it was you. That is where a story can fall apart.
The STAR method is there to describe, quantify and justify what you achieved. Describing is the easy part. Quantifying, in broad strokes, is common. Justifying, precisely, is what the interviewer tests.
Before the interview, put each story through the same follow-up test I use in how to prepare for an interview:
- Where does each number come from, and what was it before? Without a "before", your number means nothing.
- What exactly did you do, as opposed to the team?
- What changed because of it, said in one sentence?
If you can't answer one of the three in two sentences, the story isn't ready yet.

Back to the example. "The customer renewed for two years" is a start. This answer survives the test: "Usage in those two teams went from under 10% of seats to over 60% on our usage dashboard, after the workaround I set up with the product team. The account, about 8% of my portfolio, renewed for two years at the same price."
It takes a number. It takes a before. It takes a source. And it takes saying it in two sentences, not ten. Precise and concise.
Link each story to the job, and to the company's values
A STAR story only counts if it proves something the role needs. Put each story next to the job description and write down the requirement it answers. A key requirement with no story next to it? That's the next story to prepare.
Some companies publish their values and ask about them. I once interviewed with one that did, and I was expected to connect my stories to those values, not only to my hard and soft skills. If the company publishes its values, expect a question on each one.
Build your STAR story bank
You don't need one answer per question. Four to six true stories, each told in STAR format, cover most behavioral questions (MIT's career office suggests three to five). One story can answer several questions. Pick them to cover these situations:
| Situation | Example question |
|---|---|
| A success you're proud of | "What are you most proud of?" |
| A failure or a mistake | "Tell me about a failure. What did you learn?" |
| A disagreement | "Tell me about a disagreement with a colleague or a customer." |
| Taking the initiative | "Tell me about a project you started on your own." |
| Pressure or a tight deadline | "How did you handle an impossible deadline?" |
| Influencing without authority | "Tell me about a time you convinced people who didn't report to you." |
Before Raise, I kept mine in a very big spreadsheet. Each consulting project became a STAR story, matched to what the role and the company expected. Write the key points of each step, not full sentences. If you learn the sentences by heart, you will sound like it.
STAR or CAR? When another structure fits better
The CAR method (Context, Action, Result) merges the situation and the task into one part. It gives shorter answers, handy for a first recruiter call or an interview where the questions come quickly. The substance doesn't change: a brief context, a detailed action, a precise result.
Three other structures help, depending on the role. The Minto pyramid starts with your conclusion, then gives the supporting points: useful for a recommendation, in consulting or for a leadership role. SPIN and MEDDIC are sales methods. For a sales role, or presales (the technical side of a sale), tell the story of a deal where you applied them rather than reciting their letters.
Practice with someone who digs into your numbers
On paper, a story can look fine. Out loud, under follow-up questions, it is different. Practice each story out loud, and ask a friend, a mentor or a tool to probe the action and the numbers.
Feeling prepared matters: getting hired is a marathon, and you need that feeling to keep going. But it is not proof. What you need is a sparring partner who asks the follow-up you haven't seen coming.
What Raise does with your STAR answers
I built Raise to be that sparring partner. Here is what its interview prep does with your answers:
- Questions drawn from the job posting: you practice the questions that a job you follow makes likely.
- A written mock interview with feedback on the method: for each answer, which method it follows (STAR, CAR, Minto pyramid, MEDDIC or SPIN), which steps are present or missing, and the words from your answer that cover each one.
- A follow-up question: after an answer, the AI can ask one when it is useful.
- A fictional interviewer: the person asking is an AI character, presented as such.
Frequently asked questions
What is the STAR format in an interview?
The STAR format is the STAR method under another name: an answer in four parts, the Situation, your Task, the Action you took and the Result. It is the expected shape for behavioral interview questions.
How do you answer interview questions in STAR format?
Pick a true story that matches the question. Set the scene in one or two sentences, say what was expected of you, spend the longest part on what you did, and give a precise result real room. Then be ready for "Compared to what?" and "What exactly did you do?".
What are the most common STAR interview questions?
The ones in the story bank table above: a success, a failure, a disagreement, an initiative, a deadline, convincing people who don't report to you. Read the job description too: each key requirement usually turns into a question.
Can I use the same STAR story for different questions?
Yes. A story about keeping a customer can answer a question on conflict, on initiative or on pressure. Change the angle, not the facts.
Does the STAR method work if the result was bad?
Yes. A story with a bad outcome is still a STAR story: say what happened, what you did, and what you changed afterwards. Interviewers ask for failures on purpose.
Can I use the STAR method on a résumé or a cover letter?
Yes, in a shorter form: one action and one result per line. The UK's National Careers Service suggests it for CVs, cover letters and application forms as well as interviews.