How to check an answer
- Paste the question and the answer. Put the behavioral question in the first box if you have it. Paste the answer you would actually say in the second box. Scoring runs in the browser as you type.
- Read the four scores. Situation, Task, Action, and Result each get a score out of 100. Action and result count more than scene-setting. The overall number is a weighted blend, not a grade from an interviewer.
- Fix the note that is actually wrong. Typical notes are no measurable result, too much situation and not enough action, using we instead of I, and a spoken length outside 60 to 90 seconds. Change that part and the scores update.
- Use the tightened draft, then say it. The draft reorders your own sentences into STAR order and drops filler. It does not invent a metric. Say the draft out loud once. If a number feels fake, delete it.
What STAR actually is
STAR is not a personality type and it is not a script you memorize word for word. It is an order. Situation is the smallest amount of context a stranger needs: when, which team, what was already going wrong. Task is the piece that was yours, including the constraint you were under. Action is the sequence of things you did, in the order you did them, with the word I. Result is what was different afterward, with a number if you have one you can say out loud without flinching.
Interviewers reach for “tell me about a time” because a claim like “I am a strong leader” cannot be checked. A story can. They are listening for whether you were the person who made the call, whether you can leave a scene out, and whether the ending is a change in the world rather than a change in how you felt. A tidy STAR answer is easier to follow up on. That is a feature. The follow-up is where made-up numbers fall apart, so the checker will not invent one for you.
The four parts are not equal. Situation is a ramp. If the ramp is longer than the drive, the interviewer has learned where you worked and almost nothing about how you work. Action is the job. Result is the proof. Task is the sentence that stops the story from being something that happened near you. “We decided” is not a task. “I was responsible for the date we told sales” is.
A strong answer and a weak one
Here is a failure story with the shape this page looks for. It is specific, it is yours, and the result has a count.
In March 2024 the checkout team was double-charging customers after a tax change I had shipped on a Friday. I was responsible for the tax flag and for telling support what to say while the charges were unwound. I reproduced the bad total in staging, paused the flag, and wrote a refund script keyed off the order id. I then posted a timeline in the incident channel and paired with finance so the refunds went out in one batch. The result was 1,200 orders refunded within 18 hours, and tax incidents fell from 3 that quarter to 0 the next, because the flag now needs a second reviewer.
Situation is one sentence and it has a month. Task says what you owned, not what the team hoped. Action is two sentences of verbs. Result has 1,200 orders, 18 hours, and a before-and-after on incidents. You could be asked “why Friday?” or “what did the second reviewer check?” and still have somewhere to stand.
Here is the same kind of incident told the way most drafts start:
We were working on this project and there were a lot of issues. We kind of all jumped in and tried our best. I think we did a good job and the manager was happy. It was a really challenging time for the team and we learned a lot.
Nothing in there is checkable. The word we does the work that I should do. There is no task, so a listener cannot tell whether you owned the flag, the refunds, or the snack order. There is no number. “The manager was happy” is a mood. Paste that paragraph into the checker and you should see no measurable result, we instead of I, and a missing task. That is the draft the tool is for. You already lived a better story than that paragraph. The work is cutting it down until a stranger can retell it.
Common ways these answers go wrong
Too much situation, not enough action. You explain the company, the reorg, the predecessor, and the vibe. By the time you arrive at what you did, the minute is gone. Keep situation to one or two sentences. If a detail does not change the action, it is not situation. It is color.
No measurable result. The story ends on effort: we worked hard, the launch happened, people were aligned. Effort is not a result. A result is a count, a duration, a rate, or a decision that stuck. If you genuinely do not remember the number, say what you measured and that you do not have the figure in front of you. Do not borrow a number from a slide you half remember. Interviewers ask how you got it.
We instead of I. Teams ship. Interviews hire a person. You can mention the team in the situation and still say which part you did. “We shipped” becomes “I wrote the refund script and finance sent the batch.” If the honest answer is that you only watched, tell a different story. This checker flags a draft where we outnumbers I.
The wrong length. Spoken aloud at about 150 words per minute, a 150-word answer is one minute. A 400-word answer is a monologue, and the interviewer has started planning the next question. A 40-word answer is a claim with a costume. The page shows the estimate next to the score so you can hear the length before you are in the room.
A lesson instead of a story. “I learned to communicate better” is a poster. The story is the Monday you started sending the outline before anyone coded. Lessons are fine as a last clause. They are not a substitute for the action.
A story you cannot repeat. If you only have one incident, you will tell it for failure, conflict, and leadership, and the second interviewer will notice. Keep a short list: one failure, one disagreement, one time you set direction, one time you were under a real clock. The links under this guide are the prompts those stories usually answer. Related reading on this site: why the action should be the long part, a failure story, a conflict story, and a leadership story.
How this checker scores
The score is a heuristic, not a model of a particular company. Each sentence is tagged Situation, Task, Action, Result, or unclear, using cues a careful reader would use: a date and a team for situation, “I was responsible” for task, “I” plus a verb for action, and an outcome with a number for result. You can see the tags under the bars. If a sentence is in the wrong bucket, the bars are wrong too, and you should trust your ear over the tag.
The overall number weights action at 40 percent and result at 25 percent. Situation is 15. Task is 20. A beautiful description of the office will not carry a draft that never says what you did. Missing a part does not zero the whole answer. It pulls that bar down and adds a sentence of feedback. The tightened draft keeps your sentences, drops filler such as “I think” and “kind of,” and puts the remaining lines in STAR order. It will not add “increased revenue by 20 percent” because that number was not in what you wrote.
Tighten with AI is optional. When the server has a key, it asks for a shorter version under the same rule: no new facts. When it does not, the page keeps the on-page draft and says so. Either way you can practice without an account.
A 90-second outline
Fill this in before you decorate it. In [month], [team] was [problem, with a number if you have one]. I was responsible for [the piece you owned]. I [first action]. I then [second action]. The result was [count, time, or before-and-after]. One more sentence is allowed if it says what you changed so the same thing is harder to repeat. Then stop. Read it once at conversation speed. If you run past 90 seconds, delete the sentence you like most. That sentence is usually the situation.
Questions to practice
The prompts below are the ones people search before a behavioral round. Each page has an example answer already in the checker, so you can see a scored story and then replace it with yours. Use a different incident for each prompt. Five solid stories, retold cleanly, cover more loops than a document full of half-remembered ones.
- Tell me about a time you failed
- Tell me about a conflict with a coworker
- Tell me about a time you showed leadership
- Tell me about a time you disagreed with your manager
- Tell me about a time you missed a deadline
- Tell me about a time you worked on a team
- Tell me about a time you handled a difficult stakeholder
- Tell me about a time you made a mistake
- Tell me about a time you went above and beyond
- Tell me about a time you had to learn something quickly
- Tell me about a time you persuaded someone
- Tell me about a time you dealt with ambiguity
- Tell me about a time you received critical feedback
- Tell me about a time you improved a process
- Tell me about a time you mentored someone
- Tell me about a time you worked under pressure
- Tell me about a time you had to prioritize
- Tell me about a time you influenced without authority
- Tell me about a time you solved a difficult problem
- Tell me about a time a customer was unhappy