STAR interview story bank builder: the coverage table is the output, and the empty rows are the point

---
name: star-interview-story-bank-builder
description: Builds a reusable bank of interview stories from a career history, indexes each one against every competency it can serve, and produces the coverage table naming the competencies with no story behind them. It grades stories by whether the candidate actually made the decision, sets a spoken-length budget so one story serving four competencies gets four different tellings, and changes the approach when the interview is recorded and analysed by software. This skill should be used when preparing for a competency-based or behavioural interview loop, or before a one-way recorded video interview where no follow-up prompt is possible.
---

# STAR interview story bank builder

## The claim this skill is built on

The framework is not the scarce thing. Situation, task, action, result takes ninety seconds to learn, and any competent writer produces a clean STAR answer to a question handed to them. What goes wrong is upstream: people prepare answers instead of building an asset.

Preparing answers means one answer per likely question. It produces exactly as much coverage as the list had questions, cannot be recombined, and fails on the first question that was not on it. It also draws on whichever incidents came to mind, a biased sample: what comes to mind is the crisis and the launch, so the bank ends up dense in heroism and empty in the ordinary competencies most loops score, such as working inside a constraint you disagreed with.

The asset is a small set of stories, each indexed against every competency it can serve, plus the coverage analysis naming the competencies with nothing behind them. Eight to twelve stories, properly decomposed, cover thirty or forty prompts. The value is not the stories, which you already lived. It is finding out at your desk that you have no story about disagreeing with your manager, while you can still go and remember one.

## Why behavioural questions exist, which changes how you answer them

Almost no interview advice cites the research it stands on. Knowing why a question is asked tells you what is being written down.

The lineage is specific. Flanagan (1954, *Psychological Bulletin*) set out the critical incident technique, defining a job by collecting observed instances of effective and ineffective behaviour rather than by listing traits. That is where competency lists come from: someone gathered incidents from people doing the job and grouped them. Latham, Saari, Pursell and Campion (1980, *Journal of Applied Psychology*) built the situational interview from those incidents, scored against behaviourally anchored scales written in advance. Janz (1982, same journal) asked about past behaviour instead, comparing patterned behaviour description interviews against unstructured ones. Those are what "tell me about a time when" actually is, and STAR is a candidate-side container for answering them.

On whether structure helps, McDaniel, Whetzel, Schmidt and Maurer (1994, *Journal of Applied Psychology*) meta-analysed 245 validity coefficients from a total sample of 86,311 individuals and found structured interviews more predictive of job performance than unstructured ones. Sackett, Zhang, Berry and Lievens (2022, same journal) re-examined those accumulated estimates, argued earlier corrections for range restriction had been applied inappropriately, and revised most published figures downwards. Structured interviews stayed among the strongest predictors and the advantage persisted. Take the direction, not a coefficient: the figures in circulation rest on different correction assumptions, and quoting one as settled is how this literature gets misused.

The mechanism matters more than the coefficient. Campion, Palmer and Campion (1997, *Personnel Psychology*) identified fifteen components of interview structure, re-reviewed by Levashina, Hartwell, Morgeson and Campion (2014, same journal). The ones that change your behaviour in the room:

- **Questions come from a job analysis**, so the competencies are fixed before you arrive and are not adjusted to your CV.
- **Every candidate gets the same questions in the same order**, which makes charm worth less than it feels.
- **Prompting is limited.** Nobody rescues an incomplete answer, so one omitting the result is scored as having no result.
- **Each answer is rated on its own anchored scale, with notes taken live.** The interviewer is filling in a form, not forming an impression.
- **Multiple interviewers, and they debrief**, so stories travel between rounds and one favourite told three times is a scoring problem, not an efficiency gain.

## Step one: build the competency list before you touch the career history

Order matters here more than anywhere else. Harvest first and derive competencies from the stories, and you get a list your stories happen to cover, which makes the coverage table a tautology. Build the target list first, from outside your memory. Sources, in order of reliability:

1. **The recruiter's own words.** If a scheduling email names the rounds, those names are the competencies. "Round two: cross-functional influence" is not a hint, it is the rubric leaking.
2. **The verbs in the responsibilities section**, not the adjectives in the profile. "Owns the quarterly forecast" and "runs the vendor review" are competencies. "Dynamic self-starter" is not, and preparing for it produces a story about enthusiasm that scores nothing.
3. **The level.** Below senior the list leans towards execution and reliability; at senior and above, towards judgement under ambiguity, influence without authority, prioritisation and developing others.
4. **The discipline's standard set**, last, to fill holes: handling failure, receiving criticism, conflict with a peer, disagreement with a manager, working under a constraint you thought was wrong.

Stop at 8 to 12. Fewer does not cover a real loop; more and everything shows as thin. Mark each high, medium or low probability, where high means it appears in a round name or twice in the posting. That marking sets the coverage requirement later.

## Step two: harvest incidents without filtering them

Now dump raw material, and deliberately do not check it against the list you just built. Checking now means you recall only what fits, which is how the ordinary competencies stay empty.

Work backwards through the last three roles, three to six incidents each, one line apiece. Prompt memory with artefacts rather than introspection: your calendar for the period, performance reviews, retrospectives, decision documents, ticket history. Aim for fifteen to twenty lines and include the ones that went badly, because failure competencies are where banks are emptiest and a real failure with a real lesson beats a fourth success.

## Step three: the admission test, and what to do when you cannot tell

Each incident faces four questions. **Agency:** can you name a decision you personally made, and the alternative you rejected? **Evidence:** is there a number or named artefact, and can you say how it was measured? **Specificity:** can you place it in time and name the constraint? **Tellable:** can it run two minutes without naming a client, an unlaunched product, or a figure under a confidentiality agreement?

Then grade it. **A:** you made the call and the outcome has a number or named artefact behind it. **B:** you made the call, but the outcome is qualitative or fairly the team's. **C:** you contributed, someone else decided.

**Decision rule, with the branch that matters.** Name your decision and the rejected alternative, and it grades A or B on evidence. If the call was demonstrably someone else's, grade C and use it only as support. **If you cannot tell whose call it was, because it was a group and the memory has smoothed over, do not guess in either direction. Reconstruct from an artefact: a document with your name on it, a message where you proposed the thing, a ticket you opened, a decision log.** Let the artefact set the grade. If none survives, grade C, mark the mapping unverified, and in the room name what the group decided and then the part you owned. Never resolve it with an unqualified "we", the first pattern a trained interviewer probes.

## Step four: index one story against every competency it can serve

Do not ask what competency a story demonstrates. That returns one answer, usually the obvious one, and it is why people believe they need one story per competency. Ask five decomposition questions instead, each pointing at a different beat scored by a different competency:

1. **What did you decide while the information was still incomplete?** Judgement, ambiguity.
2. **Who disagreed, and what happened next?** Influence, conflict, disagreeing upwards.
3. **What did you stop doing to make room for this?** Prioritisation, saying no.
4. **What went wrong inside it, and what did you change?** Failure, learning, resilience.
5. **Who else was better off afterwards, and how?** Mentoring, leadership without authority.

Grade every mapping separately: a story can be grade A on delivery and C on influence, if you executed the plan but somebody else won the argument.

**Ratio check.** Ten qualified stories should produce roughly 25 to 40 mappings. Under about 20 means single-beat incidents that collapse under any follow-up. Over about 45 means you are stretching to competencies the story merely touches, and the coverage table is lying to you.

## Step five: how many stories, and why that number

A loop is typically three to five interviews with two to four behavioural questions each, so 8 to 15 prompts against 8 to 12 competencies. At three mappings per story, seven to nine stories cover the list once.

Once is not enough where you marked high probability, because panels debrief and a story used in round two is on the record by round four. So: **8 to 12 qualified stories, with a hard floor of two independent stories behind every high-probability competency and one behind the rest.** Independent means different projects, ideally different years; two tellings of one project are one story.

There is a ceiling too. Past roughly twelve, recall under pressure degrades and you start searching the bank mid-question, which reads as hesitation. Trim to twelve by grade, not by affection.

## Step six: the coverage table, which is the actual deliverable

One row per competency in probability order: probability, best mapping grade, story identifiers, whether a second independent story exists, verdict. **Covered:** grade A or B, plus a second independent story where probability is high. **Thin:** grade B with no second story on a high-probability row. **Uncovered:** no mapping at all, **or grade C only**. A story you were merely present for is not coverage, because the first follow-up dismantles it, so report C-only as uncovered rather than thin. That is the rule most self-assessment gets wrong, and why people are surprised in the room.

Close with the gaps as named competencies plus one instruction, usually another harvest pass rather than a rewrite of what you have.

## Step seven: four competencies, four tellings

One story mapped to four competencies needs four tellings, and the difference is not the words. It is which beat gets the detail.

A spoken answer runs 90 to 120 seconds, which at an ordinary conversational pace of roughly 140 words a minute is about 200 to 300 spoken words. That is the whole budget, split by default about 15 per cent situation and task, 60 per cent action, 25 per cent result. Re-split per competency:

- **Handling ambiguity.** The situation expands to perhaps 30 per cent, because ambiguity lives in the setup: what you did not know, what was missing, what the deadline was. The action compresses to the decision itself.
- **Influence or conflict.** The action expands into a conversation: who objected, what the objection actually was, what you conceded, what changed their mind.
- **Results orientation.** The result carries the measurement method, baseline and period. "Cut handling time" becomes "cut median handling time from eleven minutes to seven, over the following quarter against the same ticket mix".
- **Failure or learning.** The result becomes the change you made afterwards and where it has since applied, not the outcome of the original project.

Two rules govern all four. **Nothing gets deleted, only compressed**, because an answer with no result is scored as one however good the action was. And the facts stay identical across tellings, since the same panel may hear two of them.

## Step eight: rehearsal that does not destroy the story

Levashina and Campion (2007, *Journal of Applied Psychology*) developed and validated a scale for measuring faking behaviour in employment interviews, and reported that deceptive impression management was common among job-seeking candidates in both mock and real interviews. That is why the probing follow-up exists, and why an answer that sounds performed is discounted even when it is true.

So rehearse anchors, never sentences: five to seven per story, being the constraint, the decision, the rejected alternative, the objection, the number, the measurement method and the change afterwards. Say it aloud three times, letting the wording differ. Then two checks. **Cold recall:** a week later, name the anchors without looking. **Variance:** record two tellings, since near-identical wording means a memorised script and it will read as one.

## When the interview is recorded and analysed by software

A recorded, AI-assessed interview is a different situation from a conversation with a person, and both your rights and your tactics change.

**Decision rule.** Told in writing that AI will analyse the recording: you have notice, and are probably in a jurisdiction that required it. One-way, recorded, timed, limited retakes, no live human: treat it as AI-assessed whether or not anyone said so. **If you cannot tell, because it is a live call on a vendor platform carrying only a recording notice, ask one written question beforehand: will any automated tool analyse the recording, and if so, what general types of characteristics does it assess.** If the answer is no or evasive, prepare as though a person is scoring, and keep the structure clean anyway.

**What you can actually ask for, with dates.** In Illinois, since 1 January 2020, an employer using artificial intelligence to analyse a recorded video interview must notify you beforehand, explain "how the artificial intelligence works and what general types of characteristics it uses", and obtain consent, and "may not use artificial intelligence to evaluate applicants who have not consented". On request the recording must be deleted within 30 days, a duty extending to every recipient and all backup copies. Be honest about its strength: the Act carries no penalty and no private right of action, so the value is having the request on the record, not a remedy behind it.

Maryland, since 1 October 2020, requires consent by signed waiver before a facial template is created during an interview. That is narrower than usually described: it bites on facial template creation specifically, so software scoring your speech, pace or word choice sits outside it.

**What changes in the answers.** No interviewer to read and no follow-up to rescue you, so every answer must be self-contained, and ambiguity in the prompt gets resolved out loud in one clause before you answer it. Because a hard timer truncates you mid-sentence, the beat at risk is the result, the one the scale rewards. State the outcome briefly in the first fifteen seconds and again properly at the end, so truncation costs you elaboration rather than substance.

## Worked example, compressed

A candidate is interviewing for a senior operations manager role at a subscription billing company. The responsibilities section yields four competencies: owns the escalation process, runs the vendor review, reduces manual reconciliation work, partners with engineering on tooling. The scheduling email names round three "influencing without authority". With the standard set added, nine competencies, three high probability.

The harvest returns six qualified incidents. Take one: a reconciliation backlog that grew to three weeks during a pricing migration. It indexes four ways. Judgement under ambiguity, grade A: the data was incomplete, the candidate cleared oldest-first rather than by value, and can name the rejected alternative. Influence, grade C: engineering built the tool that fixed it, and the artefact search finds no message where the candidate proposed it, so it takes the cannot-tell branch and lands at C, unverified. Prioritisation, grade A: the vendor review was paused six weeks and the candidate can say who agreed. Results, grade B: the backlog cleared, but the number is the team's.

Coverage across the six stories: seven of nine competencies covered, four at grade A. **Prioritisation has two independent stories. Influence without authority is grade C only across the whole bank, so it reports as uncovered on the competency the recruiter named as a round. Disagreement with a manager has no mapping at all.**

**Verdict: the bank is not ready, and the fix is not more writing.** Two named gaps, one with its own round. The instruction is a second harvest pass over the vendor renegotiation period, where an influence story probably exists and probably left artefacts, not a rewrite of the six already qualified.

## Failure modes

**The result-free story.** The answer ends on the action, or on "and it went really well". The box on the interviewer's form stays empty, and under an anchored scale an answer with no result caps in the middle band however strong the action.

**The passenger story.** Every verb is "we". The tell is the follow-up: asked what you personally did, the answer restates the group's work in different words rather than adding a fact. Interviewers ask it because it separates the two cases.

**The over-rehearsed answer.** Fluent, unhesitating, word-identical on the second telling, no self-interruption, no dates, no named artefacts. It reads as recitation rather than recollection and collapses on any question the script did not anticipate. Anchors survive that; sentences do not.

**The all-crisis bank.** Every story is an outage, a rescue or a heroic weekend. Coverage looks strong until the ordinary competencies arrive: planning, mentoring, saying no. The symptom is a candidate impressive for two rounds, blank in the third.

**The one-story overload.** One strong story used in three rounds. Panels debrief, so the third interviewer arrives holding the note. It surfaces as an interviewer saying a colleague already heard this one, which is a scoring event, not small talk.

**The unfalsifiable metric.** "Improved efficiency by 40 per cent", with no baseline, no measurement method, no period. The follow-up asking how it was measured has no answer, and the damage is not confined to the number: the story's credibility goes with it.

**The confidentiality overreach.** Naming a client, an unlaunched product or a figure under agreement to make a story land harder. The interviewer notes it and draws the obvious inference about what you will say about them.

## What this skill does not do

- It cannot verify a single thing you tell it. An inflated story is indexed exactly like a true one, and the inflation surfaces at the follow-up rather than here.
- It does not know the employer's real rubric, and will miss internal values scored explicitly and published nowhere.
- It deliberately does not produce scripts, because a script is what stops a story sounding like a memory.
- It does not coach delivery, which one mock interview with a person who interrupts you fixes faster, and it gives no legal advice: the statutes cited are dated, jurisdiction-specific and narrower than they sound.
- It does not cover technical, coding or case interviews, where what is scored is a solution produced live rather than a recollection.