In short
The STAR method is a way to answer behavioural questions ("Tell me about a time you...") in four parts: the Situation (brief context), the Task (what you were responsible for), the Action (the specific steps you took, the longest part), and the Result (what happened, with a number if possible, and what you learned). Prepare 6 to 8 real stories in advance, covering teamwork, conflict, failure, leadership, deadlines and problem-solving, and you can answer most behavioural questions in 60 to 120 seconds.
On this page
What the STAR method is
Behavioural interview questions ask about what you have done, on the idea that past behaviour is the best guide to future behaviour. They usually start with "Tell me about a time...", "Give me an example of..." or "Describe a situation where...". Campus interviews, graduate schemes and most large companies use them, and many interviewers score your answers against a checklist.
STAR keeps your answer structured so the interviewer can find what they are scoring:
- S, Situation: where and when, in one or two sentences.
- T, Task: your responsibility or the goal.
- A, Action: what you did, step by step.
- R, Result: the outcome, measured if possible, plus what you learned.
MIT's career office makes the same point most interviewers do: spend the bulk of the answer on the actions you personally took (MIT CAPD guide to the STAR method).
How much time to spend on each part
| Part | Share of the answer | Typical length |
|---|---|---|
| Situation | About 15% | 1 to 2 sentences |
| Task | About 10% | 1 sentence |
| Action | About 55% | 3 to 5 sentences |
| Result | About 20% | 1 to 2 sentences |
The full answer should take 60 to 120 seconds. The most common mistake is the reverse ratio: a long story about the situation and a vague "so we fixed it" at the end. Interviewers cannot score context; they score actions and results.
Use "I", not "we", for the action. Teamwork stories are fine, but the interviewer is hiring you, so say what your part was.
Try it on your profile
The free LinkedIn Experience Description Generator applies this in a minute.
6 STAR answer examples
1. Teamwork (fresher)
Question: "Tell me about a time you worked in a team that was struggling."
S: "In my final-year project, our team of four was three weeks from the deadline with the app's backend only half built." T: "I was responsible for the database and the API." A: "I listed every remaining task on a shared board and estimated each one. Two teammates were stuck on the same login bug, so I suggested one move to the front end while I paired with the other on the bug for an afternoon. I set a 15-minute check-in every evening on video." R: "We submitted two days early and got an A. I learned that a visible task list fixes a lot of team friction on its own."
2. Deadline pressure (internship)
Question: "Describe a time you had to meet a tight deadline."
S: "During my marketing internship, a client moved a product launch forward by a week." T: "I had to deliver 10 social posts and a landing page draft in four days instead of eleven." A: "I agreed with my manager which three posts mattered most and did those first. I reused the brand's existing templates instead of designing new ones, and I sent drafts in two batches so feedback came while I kept working." R: "Everything went out on time and the launch post had the highest engagement of the quarter. Since then I always ask what the must-haves are before I start."
3. Conflict with a colleague (early career)
Question: "Tell me about a disagreement with a colleague."
S: "A designer and I disagreed about a checkout change: she wanted a full redesign, I wanted a smaller test." T: "As the analyst, I had to recommend what to ship that quarter." A: "I asked her to walk me through the user research behind her design, which I hadn't seen. Then I proposed testing her two strongest changes first, with a clear success metric we agreed on together." R: "The test lifted completed checkouts by 6%, and the full redesign was scheduled with data behind it. We've worked together on three projects since."
4. Failure
Question: "Tell me about a time you failed."
S: "In my first year as a sales executive, I lost a renewal worth about 8% of my annual target." T: "The account was mine to manage." A: "Looking back, I'd only spoken to the buyer, not the people using our product. After we lost it, I called two of the users to understand why, and I built a simple check-in plan for my other accounts: a call with an actual user every quarter." R: "The next year I renewed every account I managed. The lesson was to know the people who use the product, not just the person who signs."
5. Leadership without a title
Question: "Give an example of when you took the lead."
S: "Our support team kept answering the same refund question in different ways." T: "Nobody owned the help articles, so I offered to." A: "I pulled the 20 most common questions from a month of tickets, wrote clear answers, got them approved by the operations lead, and ran a 20-minute session to walk the team through them." R: "Repeat contacts on refunds dropped by about a third in the next month, and I was asked to own the knowledge base permanently."
6. Problem-solving (senior)
Question: "Tell me about a complex problem you solved."
S: "Our month-end close took ten working days and the board wanted results sooner." T: "As finance controller, I had to cut it to six without adding headcount." A: "I mapped every close task and its dependencies, found that most delays came from waiting on intercompany confirmations, moved those to a weekly cycle, and automated three reconciliations in our ERP. I reviewed progress with the team after each close." R: "We reached six days within three months and have held it for a year."
These are illustrations; build yours from real events.
Build a story bank of 6 to 8 stories
You cannot predict every question, but you can prepare stories that adapt. Build a bank of 6 to 8:
- List your raw material: jobs, internships, projects, college roles, volunteering, freelance work.
- For each, note moments when something went wrong, you changed something, you disagreed, you led, you learned fast, or you delivered under pressure.
- Write each as four bullet points (S, T, A, R), not a script. Bullets keep you sounding natural.
- Add a number to every result where possible: time saved, percentage improved, people affected, money.
- Tag each story with the themes it can answer, using the table below.
- Practise out loud, aiming for 90 seconds each.
Your resume and LinkedIn bullets are a good source of stories, and the reverse works too: a strong STAR result often makes a better bullet. The free experience description generator turns rough notes about a role into results-focused bullets you can reuse in both places.
Common behavioural questions and which story to use
| Theme | Typical question |
|---|---|
| Teamwork | "Tell me about a successful team project." |
| Conflict | "Describe a disagreement with a colleague or manager." |
| Failure | "Tell me about a time you failed or made a mistake." |
| Leadership | "Give an example of when you took the lead." |
| Pressure | "Describe a time you had several deadlines at once." |
| Problem-solving | "Tell me about a difficult problem you solved." |
| Initiative | "Tell me about something you improved without being asked." |
| Adaptability | "Describe a time plans changed suddenly." |
| Customer focus | "Tell me about a difficult customer or stakeholder." |
| Learning | "Tell me about a time you had to learn something quickly." |
One good story often covers two or three themes. The failure story can also answer the weakness question; see how to answer "What is your greatest weakness?", and the proof in your stories is what powers your answer to "Why should we hire you?".
Mistakes that weaken STAR answers
- Too much situation. If the context takes more than 20 seconds, cut it.
- "We" all the way through. The interviewer cannot tell what you did.
- No result. Even a partial or negative result is fine; say what happened and what you learned.
- Hypothetical answers. "I would..." is not a STAR answer. They asked what you did.
- Reciting a memorised script. Know the bullet points, not the sentences.
- Picking a trivial story. Choose stories with real stakes: a deadline, a customer, money, a grade.
- Making it up. Follow-up questions ("What did your manager say?", "What would you do differently?") expose invented stories quickly.
STAR variations: CAR, SOAR and STARL
You may see other names for the same idea:
- CAR (Challenge, Action, Result): STAR with situation and task merged. Good for shorter answers and for resume bullets.
- SOAR (Situation, Obstacle, Action, Result): puts the difficulty front and centre, useful for problem-solving questions.
- STARL or STAR+L (adds Learning): ends with what you learned or would do differently. Good for failure and conflict questions.
All of them work. What matters is that your action is specific and your result is clear. If you are preparing for campus placements, combine this with the fresher interview questions guide. And since interviewers usually look at your LinkedIn before they meet you, make sure your profile shows the same results; the free profile check takes about a minute.
Questions people ask
Situation, Task, Action, Result. You set the scene briefly, say what you were responsible for, explain the specific steps you took, and finish with the outcome and what you learned.
Written by Bhavishya Singla
Founder of LinkedInRank. Writes about how recruiters search LinkedIn and what makes a profile show up.
Google Search
Add LinkedInRank as a preferred source on Google
See our new LinkedIn guides first in Google results.