STAR
For anything where you did something and now have to prove it.
What is STAR?
STAR structures an account of something you did: Situation, Task, Action and Result. It is the standard answer shape for behavioural interviews, and it works just as well for performance reviews, promotion cases, case studies and CV bullets — anywhere the job is to make a past action legible to someone who was not there.
STAR exists to fix one specific failure, and knowing which one is most of using it well. Asked "tell me about a time you handled conflict", most people describe the situation at length, gesture at what happened, and never say what they personally did or what changed as a result. STAR forces the two halves people skip. Its real discipline is not the four letters — it is the ratio: Situation and Task together should take about a quarter of the answer, and Action and Result the rest.
Where STAR Came From
Behavioural interviewing, 1970s
STAR comes out of behavioural interviewing, developed by industrial and organisational psychologists in the 1970s on a simple premise: what someone actually did before predicts their behaviour better than what they say they would do. That is why the questions all start "tell me about a time" rather than "what would you do if".
Why the acronym has a Task slot
The odd slot is Task, and it is there for a reason rooted in the method. Interviewers kept hearing team accomplishments told in the first person plural — "we reduced downtime" — which reveals nothing about the candidate. Task exists to pin down your responsibility inside the situation, so that the Action that follows is unambiguously yours.
It was never about interviews only
The same structure had already been in use for performance documentation and case studies, because it answers the same question: what changed, and what did this person have to do with it. Treating STAR as an interview trick understates it — it is a general format for making a contribution legible.
The 4 Slots, One at a Time
Each slot is a decision. Leave it out and the model still makes it — just without you.
The slot people over-write. Situation is scene-setting, and scene-setting is not the answer — it is the run-up. A good Situation gives only what is needed to understand why the Task was hard. If it is longer than two sentences spoken, it is too long.
The slot that exists to stop "we". Task should name your role and, crucially, the constraint that made it hard: no authority, no budget, no time. A Task with the difficulty removed makes the Action sound easy, which is the opposite of what you want.
The heart of the answer and usually half its length. Every sentence should start with "I". Watch for the drift into what the team did or what generally happens — the interviewer is trying to assess you, and a passive Action defeats the whole method.
The most commonly truncated slot. A Result without a consequence is an anecdote. If you have no metric, use a concrete outcome instead — "one documented owner per service" is worth more than a vague "it went well". Never invent a number; a fabricated metric is the one thing that will actually cost you the offer.
One Task, Before and After
The task: Answer "tell me about a time you handled conflict" in a senior engineering interview. Both prompts below are scored by our free prompt checker — paste either in and you will get the same number, because the scoring is deterministic.
Help me answer a question about handling conflict in an interview.
Eleven words, and the lowest-scoring starting point on any of these pages. The model has no situation, no role, no outcome — so it will invent all three, and you cannot use an invented story in an interview.
You are helping me rehearse for a senior engineering interview. Situation: Two teams I worked across disagreed about who owned incident response for a shared service. It had been unresolved for months and outages were being handled twice or not at all. Task: I was tech lead on one of the teams and needed a working agreement without authority over either team. Action: Convening one session, mapping the actual incidents from the previous quarter, and proposing ownership by service rather than by team. Result: One documented owner per service, and mean time to acknowledge halved the following quarter. Think through which details a hiring manager would actually probe before you draft. Then write it as a spoken answer of 200-250 words in four short paragraphs, one per STAR element, first person and past tense. Spend roughly a quarter of the length on Situation and Task together and the rest on Action and Result. Open in the style of 'Two teams I worked across had been arguing for months about...' rather than restating the question. Do not invent metrics beyond the one given, and do not claim authority I did not have.
Note what the prompt supplies and what it withholds. You bring the facts; the model brings the shaping. That division is what keeps the answer true.
The instruction that matters most is not one of the four letters
Eighty is a strong score, and the lines doing the heavy lifting are the ones outside the STAR structure entirely. Three of them are worth copying into every STAR prompt you write:
"A quarter on Situation and Task together, the rest on Action and Result." Without it, models write a beautiful scene and a thin outcome — the same failure the method exists to prevent in humans.
"Do not invent metrics beyond the one given, and do not claim authority I did not have." A model will happily upgrade you to the decision-maker. In an interview that is a lie you then have to defend.
Giving a sample opening stops the answer beginning "That is a great question" or restating the prompt — the two things that make a rehearsed answer sound rehearsed.
The general lesson: STAR tells you what to include, not what to leave out, and the leaving-out is where answers are won. Four labelled slots with no ratio and no fabrication rule will reliably produce a 400-word answer that is 60% setting — technically correct STAR, and unusable in a room.
Copy-Paste Prompt Template
Replace the bracketed placeholders with your specific details.
Situation: [The context, in one or two sentences. Only what makes the Task make sense] Task: [What YOU specifically were responsible for, and the constraint that made it hard] Action: [What you did, step by step, first person singular] Result: [What changed. A number if you have one, a concrete outcome if you do not] Write this as [a spoken interview answer / a CV bullet / a review entry] of [N] words. Spend about a quarter of the length on Situation and Task together and the rest on Action and Result. Do not invent metrics beyond those given.
When STAR Fits — and When It Does Not
- Behavioural interview answers — the use it was designed for.
- Performance reviews and self-assessments, where the Result slot does the arguing.
- Promotion cases: Task is where you evidence scope beyond your title.
- CV and LinkedIn bullets — a compressed STAR is exactly what a good bullet is.
- Client case studies, with the company as the subject instead of you.
- Anything hypothetical. STAR is for what happened; a future plan has no Result. Use SMART.
- Analysis and comparison — it is a narrative shape, not a reasoning one. Use SCQA or MECE.
- Persuasion copy. Use AIDA or PAS; STAR sells a person, not a product.
- Situations where you genuinely did not do much. Forcing STAR onto a thin story exposes it.
10 Ready-Made STAR Prompts
Every prompt below was produced by the Frompting generator with STAR selected — not written by hand for this page. Each is scored by our prompt checker; the median is 80/100. Click one to open it, then copy.
Interview answer: handling conflict 77
You are an experienced interview coach. Help the user craft a concise, compelling response to the interview question “Tell me about a time you handled conflict.” First, describe the context in which the conflict occurred, including the relevant setting, team composition, and the nature of the disagreement. Next, explain what you were expected to achieve or resolve in that situation. Then, detail the specific steps you took, emphasizing the skills, communication tactics, and decision‑making processes you employed. Finally, summarize the outcome, quantifying the impact where possible (e.g., improved team cohesion, project timeline saved, stakeholder satisfaction increased). Write the answer in a single paragraph of **150–200 words**, using clear, active language and avoiding generic buzzwords. Ensure the response: - Shows personal responsibility and leadership. - Highlights measurable results or concrete improvements. - Reflects a professional tone appropriate for a job interview. Exclude any mention of the STAR framework or its component names. [INDUSTRY: specify the industry or sector of the role] [ROLE: specify the job title or position you are interviewing for] [CONFLICT TYPE: specify the kind of conflict (e.g., interpersonal, project‑deadline, resource allocation)] If any of the placeholders are unknown, state your assumption and proceed, or ask up to three clarifying questions before finalizing the answer. Write this for [AUDIENCE: who will read the output, and how much they already know]. Match the depth, vocabulary and examples to that reader.
Resume bullet: leading a project 84
You are a professional resume writer who crafts concise, impact‑focused bullet points for senior‑level candidates. Your task is to create a single resume bullet point that showcases the candidate’s leadership of a project. The bullet point must be written in the style preferred by hiring managers for technology/leadership roles, limited to **one sentence (12–15 words)**. Include the following elements in order: 1. Briefly describe the context of the project (e.g., department, product area, or challenge). 2. State the specific responsibility the candidate held. 3. Detail the key actions taken to drive the project forward. 4. Quantify the outcome with a clear metric or business impact. **Quality criteria**: - Uses strong action verbs and active voice. - Highlights measurable results (percentage, revenue, cost, time, or user impact). - Avoids vague language and filler words. **Boundary**: Do not exceed one sentence or include any personal anecdotes beyond the project leadership narrative. If any essential detail is missing, ask up to three clarifying questions (e.g., project scope, metric type, industry). [PROJECT CONTEXT]: brief description of the project’s domain or challenge [ROLE TITLE]: the candidate’s exact title during the project [KEY ACTIONS]: primary steps the candidate took to lead the effort [RESULT METRIC]: specific quantitative outcome achieved Write this for [AUDIENCE: who will read the output, and how much they already know]. Match the depth, vocabulary and examples to that reader.
Self-assessment for an annual review 92
You are a professional HR writer tasked with crafting a concise self‑assessment for an annual performance review. First, describe the context in which you worked during the review period, including the department, primary responsibilities, and any major projects or initiatives you were involved in. Next, explain the specific objectives you were assigned or set for yourself, highlighting the goals that were most critical to your role. Then, detail the steps you took to address those objectives—methods, collaborations, tools, and any innovative approaches you employed. Finally, summarize the outcomes of your efforts, providing measurable results, impact on the team or organization, and any recognition received. The assessment should be written for a senior manager reviewing your performance, using a professional yet personable tone. Limit the total length to **300–350 words**. Quality criteria: 1. Clear, concrete examples that illustrate each part of the narrative. 2. Quantified results or specific evidence of impact wherever possible. 3. Language that is confident but realistic, avoiding hyperbole. Exclude any speculative claims or unverified data. If any essential details are missing, state your assumptions explicitly and ask up to three clarifying questions (e.g., specific metrics, project names, timeframes) before finalizing the assessment. Before writing the final answer, work through the problem step by step and weigh the main trade-offs; present only the reasoned conclusion, not your working notes.
Interview answer: describing a failure 74
You are an experienced interview coach. Help the candidate craft a concise, compelling response to the interview question “Describe a time you failed.” First, set the scene by briefly describing the context in which the failure occurred. Next, explain what was expected of the candidate in that situation. Then, detail the specific steps the candidate took to address the challenge, including any adjustments made after the initial setback. Finally, summarize the outcome, highlighting what was learned and how the experience led to improved performance or a positive change. Write the response in plain, engaging prose of **150–200 words**. Ensure the answer: - Clearly follows the logical flow of context → expectation → actions → learning/outcome. - Shows self‑awareness, accountability, and a growth mindset. - Uses concrete details without vague generalities. [ROLE: Specify the candidate’s job title or functional area] [INDUSTRY: Specify the industry or sector of the example] [FAILURE TYPE: Briefly describe the nature of the failure (e.g., missed deadline, project overrun, client loss)] If any of the placeholders are unknown, state your assumption and proceed, or ask up to three clarifying questions before completing the response. Write this for [AUDIENCE: who will read the output, and how much they already know]. Match the depth, vocabulary and examples to that reader.
LinkedIn recommendation for a colleague 78
You are a professional writer crafting a LinkedIn recommendation. Write a concise recommendation (approximately 150–200 words) that highlights the colleague’s impact and suitability for future opportunities. First, describe the context in which you worked together, including the project or environment and your role relative to the colleague. Next, explain the specific responsibilities or challenges the colleague was tasked with during that time. Then, detail the actions they took, focusing on the skills, initiatives, and behaviors that set them apart. Finally, illustrate the outcomes of their work, using measurable results or clear benefits to the team or organization. The recommendation should be warm, specific, and written in a tone appropriate for a professional networking platform. [COLLEAGUE NAME]: full name of the person being recommended. [YOUR RELATIONSHIP]: brief description of how you know the colleague (e.g., manager, peer, mentor). [KEY ACHIEVEMENT]: one or two notable accomplishments to emphasize. [CORE STRENGTHS]: top qualities or skills to highlight. Ensure the text is free of jargon, uses varied sentence lengths, and ends with a strong endorsement statement. If any bracketed detail above is left unfilled, choose a sensible value from the context, state that assumption in one line before you begin, and continue — do not ask for it and stop. Before writing the final answer, work through the problem step by step and weigh the main trade-offs; present only the reasoned conclusion, not your working notes.
Making the case for a promotion 87
You are a professional career strategist tasked with crafting a compelling promotion case for the user to present to their manager. First, gather the context of the current role and recent achievements: - [CURRENT_ROLE: brief title of the user's position] - [KEY_PROJECT_OR_RESPONSIBILITY: one major initiative or responsibility the user has handled] Next, describe the challenge or opportunity that arose in the workplace: - [SITUATION_DESCRIPTION: concise overview of the business context or problem] Then, specify the objective the user was assigned to address: - [TASK_DESCRIPTION: clear statement of the goal or expectation set for the user] Outline the steps the user took to meet that objective, emphasizing leadership, initiative, and impact: - [ACTION_DETAILS: bullet points of the most significant actions, methods, and collaborations] Finally, quantify the outcomes and highlight the value delivered to the organization: - [RESULT_METRICS: measurable results, such as revenue growth, cost savings, efficiency gains, or stakeholder feedback] Produce a promotion case of approximately 300 words, written in a confident yet professional tone, suitable for a formal presentation to a manager. Ensure the narrative flows logically from context to outcome, uses concrete details, and avoids vague language. Include a brief concluding paragraph that directly requests consideration for promotion, linking the demonstrated results to the next level of responsibility. Do not include any placeholders in the final output; replace them with the user‑provided information. If any of the required details are missing, state the assumption you are making and ask up to three clarifying questions before completing the case.
Interview answer: influencing without authority 80
You are an experienced interview coach who helps professionals craft compelling, concise answers to behavioral interview questions. Your task is to produce a polished response to the question “Tell me about a time you influenced without authority.” Write the answer as a single, cohesive narrative that naturally follows the order of context, challenge, personal initiative, and outcome. Keep the response between 150 and 200 words, using a professional yet personable tone suitable for a hiring manager. The answer should: - Clearly describe the situation and why influence was needed. - Explain the specific goal or responsibility you were addressing. - Detail the actions you took to persuade or guide others, highlighting any techniques or communication styles used. - Quantify the result or impact, mentioning any measurable improvements or feedback received. [INDUSTRY: specify the industry or sector] [ROLE: specify the job title or function you were performing] [KEY METRIC: specify a measurable outcome, e.g., percentage increase, cost saved, time reduced] Do not include any fictional claims; if any detail is uncertain, state the assumption explicitly. If you need clarification on any of the placeholders, ask up to three concise questions before drafting the answer.
Client project case study 77
You are a professional case‑study writer. Your task is to produce a concise, compelling narrative that documents a client project your organization delivered. First, describe the background and context of the engagement, including the client’s industry, the business environment, and any relevant challenges they faced. Next, explain the specific objective or problem the client needed solved, outlining the scope and desired outcomes of the project. Then, detail the approach your team took: the methodology, key activities, resources deployed, and any innovative solutions or adaptations made during execution. Finally, summarize the measurable results and impact of the project, highlighting quantitative improvements, qualitative benefits, and any follow‑up actions or client feedback. The case study should be written for [AUDIENCE: specify the intended readers, e.g., prospective clients, internal stakeholders, marketing materials] and be no more than 350 words. Quality criteria: - Clear, logical flow that naturally guides the reader through the four sections. - Use concrete data and specific examples; where exact figures are unavailable, note them as estimates. - Maintain a professional yet engaging tone appropriate for business storytelling. Exclude any internal proprietary processes or confidential details not approved for public use. If any essential information (e.g., client name, project timeline, key performance metrics) is missing, state your assumptions explicitly and ask up to three clarifying questions before completing the case study.
Performance review for a direct report 90
You are an experienced HR professional tasked with drafting a concise performance review for a direct report. Write a review that follows a clear narrative flow: begin by describing the context in which the employee worked during the review period, then outline the specific responsibilities they were expected to fulfill. Next, detail the actions they took to meet those responsibilities, and conclude with the outcomes of those actions, highlighting both strengths and areas for growth. The review should be addressed to **[RECIPIENT: manager’s name]** and focus on the employee **[EMPLOYEE: name]**, who holds the position of **[ROLE: job title]**. Cover the review period **[PERIOD: dates]**. Include at least two concrete examples of achievements, one example of a development opportunity, and two short-term goals for the next period. Produce the review in plain text, approximately 375-495 words. Ensure the tone is professional, balanced, and supportive, using specific, measurable language where possible. Quality criteria: 1. Clear, logical progression from context to responsibilities, actions, and outcomes. 2. Specific examples with measurable results. 3. Constructive feedback that includes actionable next steps. Exclude any personal opinions unrelated to job performance and avoid mentioning the review framework or its components. Write this for [AUDIENCE: who will read the output, and how much they already know]. Match the depth, vocabulary and examples to that reader. If any bracketed detail above is left unfilled, choose a sensible value from the context, state that assumption in one line before you begin, and continue - do not ask for it and stop. Before writing the final answer, work through the problem step by step and weigh the main trade-offs; present only the reasoned conclusion, not your working notes.
Interview answer: biggest achievement 73
You are an experienced interview coach. Help the user craft a compelling answer to the interview question “Describe your biggest achievement.” First, gather the context of the achievement: - [ACHIEVEMENT CONTEXT: brief description of the situation, organization, and challenge] - [ROLE AND RESPONSIBILITIES: the specific position or duties you held] Next, clarify the goal you were tasked with and why it mattered. Then, outline the steps you took, emphasizing the skills, strategies, and decisions you applied. Finally, detail the outcome, including measurable results, impact on the organization, and any recognition received. Produce a concise, polished response of 150–200 words, written in a confident yet authentic tone suitable for a professional interview. Ensure the narrative flows logically from context through goal, actions, and results, and avoid generic statements. If any of the required details are missing, state your assumptions clearly and ask up to three targeted questions to fill the gaps before finalizing the answer.
Scores range from 73 to 92. They are shown as generated rather than cherry-picked — a library where every entry scores in the nineties tells you it was curated, not measured.
STAR vs the Alternatives
STAR with Task folded into Context. Faster, and it loses the slot that pins down what was specifically yours — which is the whole reason Task exists.
Use SCQA when you are making a case rather than recounting a contribution. It ends on a recommendation; STAR ends on an outcome.
The forward-looking counterpart. SMART sets a goal, STAR reports one. Use SMART in the objectives half of a review and STAR in the achievements half.
Better for a short verbal answer where you need the conclusion first. STAR withholds the Result until the end, which suits a story and not an argument.
Unrelated despite the name, and frequently confused with it. CO-STAR is a general writing framework; STAR is a narrative structure for a past achievement.
Five Ways People Get STAR Wrong
The single most common failure, in prompts and in rooms. Aim for a quarter on Situation and Task combined. Say it explicitly in the prompt or the model will not do it.
The interviewer cannot assess a team. Instruct first person singular and check the output — models drift back to the plural because it sounds more collegial.
An answer that stops at what you did is an anecdote. If there is no metric, name a concrete change: a policy that exists now, a process that stopped.
Give it your numbers and forbid new ones. A model asked for an impressive Result will produce an impressive Result, and you will be asked about it.
"Tell me how you would handle..." is not a STAR question. Answering it in STAR produces a fictional past, which interviewers notice.
STAR Questions
What does STAR stand for?
Situation, Task, Action, Result. Situation sets the scene, Task names your specific responsibility, Action is what you did, Result is what changed.
Where does the STAR method come from?
Behavioural interviewing, developed by industrial and organisational psychologists in the 1970s. The premise is that past behaviour predicts future behaviour better than hypothetical answers do, which is why the questions all begin "tell me about a time".
How long should a STAR answer be?
Two minutes spoken, roughly 200 to 250 words. The proportions matter more than the total: about a quarter on Situation and Task together, the rest on Action and Result.
What is the difference between Situation and Task?
Situation is what was happening. Task is what you were on the hook for. The distinction exists because candidates kept describing team achievements in the first person plural, which tells an interviewer nothing about them.
What if I do not have a number for the Result?
Use a concrete outcome instead — something that is true now and was not before. That is far better than inventing a metric, which is the one mistake that can actually cost you the job when you are asked to expand on it.
Is STAR the same as CO-STAR?
No. The names collide but they are unrelated. CO-STAR is a general-purpose writing framework; STAR is a narrative structure for recounting something you did.
Generate a STAR Prompt Instantly
Skip the manual template — Frompting applies STAR to your topic in one click.
Try it FreeFramework Details
| Name | STAR |
| Stands for | Situation-Task-Action-Result |
| Domain | People & Teams |
| Steps | 4 |
| Access | Free |