Start from the bullet, not from the framework. Every achievement line you wrote is already the Result — the reason STAR answers come out hollow is that Situation, Task and Action are the three parts you never had room to write down, and a template cannot supply them because it does not know your job.
Build them from my resumeFree: full analysis plus your 3 most likely questions. $19 once for all 10 with STAR answers. No account, no subscription.
"Cut incident MTTR from 45 minutes to 20." That is a Result, stated the way resumes state results: outcome first, everything else deleted for space. It is also why so many candidates freeze when asked to expand it. The bullet is the summary of a story you have not told out loud in two years, and the parts that got cut for space are exactly the parts an interviewer wants.
So the work is backwards from the usual advice. Do not learn STAR and then hunt for examples. Take the four or five bullets most likely to be probed and reconstruct the missing three-quarters of each one.
Situation is the state of the world before you touched it, in one or two sentences with a number in them if possible. "We were running six Python services on EC2 and paging someone about latency twice a week."
Task is what you specifically were responsible for, as distinct from what the team was responsible for. This is the sentence almost nobody prepares, and it is the one that separates a credible answer from a rehearsed one — because it is where "we" has to become "I" without overclaiming. "I owned the migration plan and the rollback criteria; two other engineers did the service work."
Action is the sequence of decisions, including at least one you got wrong. An answer with no wrong turns in it sounds fictional, and senior interviewers listen for this specifically.
Result is the bullet you already have, plus the baseline it was measured against and one thing that got worse or cost more. Naming the trade-off is what makes the number believable.
The STAR guides that fill a search results page hand you a shape and a worked example from someone else's career. The shape was never the hard part — you can hold four letters in your head. The hard part is that a good answer needs the specific numbers, the specific constraint and the specific mistake from your project, and no amount of framework supplies those. That is the difference between "here is the method" and "here are your four bullets with the missing three parts drafted from what you wrote".
One rule that this tool holds to and that generic AI rewriting does not: it will not invent achievements. If a bullet has nothing underneath it, the honest output is that the bullet is weak — not a fabricated Situation to prop it up. An invented STAR answer collapses on the second follow-up question, which is worse than having no answer prepared.
Read the analysis on a published resume before uploading your own: backend engineer, fintech · product manager, B2B SaaS · data analyst to data scientist · frontend engineer, startup · growth marketer, DTC.
A drafted STAR answer is a starting point you have to make true — it is built from what your resume says, and only you know the parts that never made it onto the page. Nothing is invented on your behalf, which means a thin resume produces thin drafts and the output will tell you so. This is not an ATS scorer and issues no score. Your file is parsed in the browser; the extracted text is sent to the API for analysis, held up to 24 hours, then deleted. Strongest in English.
Resbetter · Questions your resume invites · Tell me about yourself · Explaining an employment gap · Resume checker with no signup · Privacy