Tool 01 · Interview Prep
STAR Story Builder
Write your STAR story in the four boxes. Get a real-time strength score that catches vague verbs, missing metrics, and weak impact framing — before the interviewer does.
Advertisement — natural in-content placement
How to use this tool
- Pick one specific accomplishment. Don't try to write your whole resume.
- Draft each box in 1-3 sentences. The tool will catch over-writing.
- Watch the strength score as you type. The overall number is a heuristic — it catches the four patterns that sink most STAR stories.
- Iterate until you hit 75+. That puts you above the typical candidate bar for NYC mid-level roles.
- Save the resulting story. Rehearse it out loud. Time yourself — most STAR answers should land in 90-120 seconds.
What this is good for
- Catching vague verbs ("helped", "worked on", "was involved in")
- Forcing quantified outcomes — the #1 differentiator in NYC hiring
- Spotting "we" overuse in the Action box
What this cannot do
- Tell you if this is the right story for a specific role
- Replace human feedback on tone, authenticity, or fit
- Score behavioral answers that are deliberately concise (some roles value brevity)
Frequently asked questions
What are the common mistakes when using STAR Story Builder?
Most common mistakes come down to four habits: entering 20 when the field expects 0.2 because the field is a percentage; leaving a field blank and accepting the default without checking what it stands for; changing one input and reading a result that was calculated before the change; and quoting the output as an exact figure when the page describes it as a reference estimate. Press calculate again after any edit, and treat the number as a reference point rather than a final answer.
Where does STAR Story Builder stop being useful?
Paste your Situation/Task/Action/Result story, get a 0-100 strength score with feedback on specificity, metrics, and impact. Put another way, this page answers one narrow question: given the numbers you typed, what does a quick estimate look like. It is not for looking up authoritative data, checking official documents, reviewing a contract line by line, or making a professional judgement call. If a decision depends on money, a signature, or a commitment to somebody else, go back to the source material and confirm the numbers there first.
How do I read the result from STAR Story Builder?
Read the final figure first, then come back to this section for the conditions behind it: Paste your Situation/Task/Action/Result story, get a 0-100 strength score with feedback on specificity, metrics, and impact. Keep two things apart: the number itself, which comes from the values you typed, and the assumptions it depends on, which decide whether that number is meaningful. The page sets out what a higher or lower result means for your case, so check that direction as well as the magnitude.
Can I act on the STAR Story Builder result directly?
Treat it as one reference sheet before you decide, rather than as the answer itself: Paste your Situation/Task/Action/Result story, get a 0-100 strength score with feedback on specificity, metrics, and impact. The output describes a magnitude under the conditions you entered. It does not include what it actually costs to act, what might change while you act, or how the other side behaves. Before you commit, compare the result against reality and note which assumptions do not hold where you are.
What inputs does STAR Story Builder need?
STAR Story Builder takes 4 inputs: S ituation — Set the scene、T ask — What was the specific challenge?、A ction — What YOU specifically did (use 'I', not 'we')、R esult — Quantified outcome with numbers. They are listed in the order they feed the calculation, so an earlier value can change a later one. Do not skip a field you do not recognise - work out what it means first, because a silently guessed value produces a number that looks reasonable and is not. Before typing anything, make sure every figure uses the same unit and the same time period.
What should I check before I run STAR Story Builder?
Three checks pay for themselves. First, confirm the question you need answered is really inside the scope of this tool rather than a neighbouring one. Second, confirm that the figures you have are drawn from the same source and the same period - mixing monthly and annual numbers, or two different definitions of the same quantity, quietly distorts the result. Third, keep the key inputs written down, so that later you can tell which set of numbers produced a figure you are about to quote.