A STAR method template is a fill-in structure that turns a work experience into a two-minute interview answer: one or two sentences of Situation, one sentence of Task, three or four specific Actions, and a Result with a number. Copy the template below, fill in one copy per story, then map your stories to the skills employers test so you have an example ready for most behavioral questions.
STAR stands for Situation, Task, Action and Result. The consulting firm DDI says it introduced the STAR method in 1974 as part of its Targeted Selection interviewing system, and interviewers still listen for those four parts today. For the background and when to use it, see what the STAR method is. This page is the practical part: the template, the prompts, an example and a planning grid.
The STAR method template (copy and fill in)
Copy this table into a document or spreadsheet and fill in one per story. The length column keeps you inside a two-minute answer.
| Section | Fill in | Length |
|---|---|---|
| Question(s) this answers | [e.g. difficult problem, used data, pressure] | 2–3 question types |
| Situation | At [company or team], I was [role] working on [project]. [What was at stake, with a number if possible.] | 1–2 sentences, about 15 seconds |
| Task | I was responsible for [what you owned]. Success meant [specific outcome, deadline or target]. | 1 sentence, about 10 seconds |
| Action 1 | First, I [verb] [what], because [reason]. | 1–2 sentences |
| Action 2 | Then I [verb] [what], which [effect or what it revealed]. | 1–2 sentences |
| Action 3 | When [obstacle or pushback], I [how you handled it]. | 1–2 sentences |
| Action 4 (optional) | Finally, I [verb] [what] so that [follow-through]. | 1 sentence |
| Result | As a result, [metric] went from [before] to [after] within [time]. [Second-order effect: who else benefited.] | 1–2 sentences, about 20 seconds |
| Lesson | Since then, I [habit you kept or would repeat]. | 1 sentence |
| Follow-up notes | What I'd do differently: [ ]. Hardest part: [ ]. Who disagreed: [ ]. | Notes only, not spoken |
The structure deliberately gives the Action three or four rows and everything else one, because the Action is where you show the skill being tested. If you want a guided version that walks you through each box, try our free interactive STAR story builder.
What should you write in each section? Worksheet prompts
A blank template is hard to start. Answer these prompts in rough notes first, then compress the answers into the template.
Situation prompts
- Where were you working, and what was your role at the time?
- What project, customer or problem was this about?
- What would have happened if nobody acted? Can you put a number on it (revenue, users, days, cost)?
Task prompts
- What exactly were you responsible for, as opposed to the team?
- Who gave you the task, or did you take it on yourself?
- What did success look like, and by when?
Action prompts
- What was the first thing you did, and why that first?
- What options did you consider and reject?
- Who did you need to persuade, inform or ask for help?
- What went wrong or pushed back along the way, and how did you respond?
Result prompts
- What changed, in numbers? Before and after, if you have them.
- What did someone else (a manager, customer or teammate) say or do because of it?
- What did you learn, and when have you used that lesson since?
A filled-in STAR template we wrote
Here is the template completed for one story. This is an example we wrote for a customer support team lead; use it as a model for the level of detail, not as wording to copy.
| Section | Example we wrote |
|---|---|
| Questions it answers | Improved a process; used data; showed initiative |
| Situation | I led a six-person support team at a payroll software company. Our first-response time had crept up to 11 hours, and two of our largest customers had complained in their quarterly reviews. |
| Task | I owned the team's service levels, and my target was to get first response under 4 hours within a quarter without adding headcount. |
| Action 1 | First, I tagged two weeks of tickets by topic, because I suspected a few repeat issues were eating most of our time. |
| Action 2 | That showed 35% of tickets were password resets and payslip reprints, so I wrote step-by-step help articles for both and added them to the auto-reply. |
| Action 3 | Two agents worried the auto-reply would feel cold, so we tested it for two weeks on one queue and reviewed customer replies together before rolling it out. |
| Action 4 | Finally, I moved the agent with the most payroll-tax experience to a dedicated queue for complex tickets so they stopped waiting behind simple ones. |
| Result | Within ten weeks, first-response time fell from 11 hours to 3.5, and ticket volume dropped by about a quarter. Both large customers mentioned the improvement at their next review. |
| Lesson | Since then, I tag a sample of work before I change any process, so the fix targets the real cause. |
Spoken aloud, those rows take about two minutes. Notice that every Action starts with “I” and a verb, the obstacle (the agents' concern) is handled rather than hidden, and the Result has three separate pieces of evidence. For more finished stories across the core competencies, see our behavioral interview STAR examples; for timing each section, see how long a STAR answer should be.
How do you build a STAR story bank?
A story bank is a short set of fully prepared stories, each tagged with the competencies it can demonstrate. Most candidates do well with 8 to 10 stories, where each story covers two or three competencies and each competency is covered by at least two stories. Here is a grid we filled in for the support-lead example above, with a mark wherever a story is a strong fit:
| Story | Problem solving | Leadership | Conflict | Failure or mistake | Initiative | Pressure or deadline | Customer focus |
|---|---|---|---|---|---|---|---|
| Cut first-response time from 11 to 3.5 hours | ✓ | ✓ | ✓ | ✓ | |||
| Billing outage weekend with 400 affected accounts | ✓ | ✓ | ✓ | ||||
| Disagreed with product on a refund policy change | ✓ | ✓ | |||||
| Promoted an agent who struggled in the new role | ✓ | ✓ | |||||
| Built a training plan for a new tax-year release | ✓ | ✓ | ✓ | ||||
| Escalated a renewal risk too late | ✓ | ✓ | ✓ |
Read the grid by column. Any competency with fewer than two marks is a gap; here, conflict has only one story, so the next step would be to find a second. Choose your competency columns from the job description, then add the ones almost every interviewer asks about: failure, conflict and leadership. Our list of the 40 most common “tell me about a time” questions is grouped by competency, which makes it a good source for column headings. If you want help finding stories in your own history, our guide to building a STAR story bank with AI has prompts for mining your résumé.
Why do STAR answers built from a template sometimes sound robotic?
A template organizes your thinking; it should not script your delivery. These are the common ways a good template turns into a stiff answer:
- Saying the labels out loud. “The situation was… the task was…” sounds mechanical. Let the structure sit under natural sentences.
- Memorizing word for word. Learn the facts and the order of actions, then say it slightly differently each time you practice. Scripts collapse when the interviewer interrupts.
- Filling every box equally. If your Situation is as long as your Action, the template has become a form to fill rather than a story to tell.
- Using “we” in the Action rows. Interviewers are scoring what you did. Credit the team in the Result, not by blurring your own steps.
- Choosing low-stakes stories. A neat template cannot rescue a story where nothing was at risk. Pick stories where the outcome could have gone the other way.
If you are early in your career, the same template works for internships, coursework, part-time jobs and volunteering; our guide to answering behavioral questions without work experience shows how.
Practice it
A filled template is a draft; the interview tests whether you can say it clearly under questioning. Once you have three or four stories written, run your stories through a free browser mock interview, answering out loud, and note where you stall or run long. In the desktop app, CoPilot Interview's Mock Interview builds behavioral questions from your résumé and the job description and scores each spoken answer out of 10 with what worked, what to fix and a model answer, so you can see which template sections need more detail.
It is free for 15 minutes a day, with no account needed. Use AI to prepare beforehand, keep the stories your own, and follow each employer's rules about AI use in the interview itself.
Turn your template into a spoken answer
Answer real behavioral questions out loud and get each answer scored out of 10, with what to fix and a model answer.
Try a free AI mock interviewFAQ
What is a STAR method template?
It is a fill-in structure for preparing behavioral interview answers. You write one or two sentences of Situation, one sentence of Task, three or four Actions and a measurable Result, then use the completed template as notes for a roughly two-minute spoken answer.
How many STAR stories should I prepare?
Most candidates do well with 8 to 10. Each story should cover two or three competencies, and each competency the job stresses should be covered by at least two stories.
Should I bring my STAR template to the interview?
Check with the employer first, and do not read from it. For an in-person or video interview, a few keyword notes are usually acceptable, but the answer should come from memory so it sounds natural and survives follow-up questions.
What is the difference between STAR and CAR or STARL?
CAR (Challenge, Action, Result) merges Situation and Task into one step. STARL or STAR+L adds a Learning step at the end. All three follow the same idea, so use whichever helps you keep the Action as the longest part.
Can I use the STAR template for questions that do not start with “tell me about a time”?
Yes. Any question asking for a past example, such as “describe a situation when” or “give me an example of,” fits STAR. Hypothetical questions like “what would you do if” need a different approach, though a short real example can strengthen the answer.
What if my result was not a success?
You can still use STAR. Describe the outcome honestly, then spend the last part on what you learned and changed. Failure and mistake questions expect exactly that kind of result.