You can't script every behavioral question, but you don't need to: nearly all of them are one of eight archetypes — conflict, failure, leadership, ambiguity, persuasion, prioritization, pressure, and initiative. Prepare six to eight real stories tagged against those archetypes and you can answer almost anything the loop asks without sounding rehearsed.
Strip the phrasing and behavioral questions collapse into: a conflict you navigated (disagreement with a colleague, stakeholder, or boss), a failure and what it changed, a time you led without or with authority, a decision under ambiguity or missing data, a time you persuaded someone senior, a brutal prioritization call, delivery under pressure or a deadline, and initiative — something you did that nobody asked for.
"Tell me about a difficult stakeholder", "describe a disagreement with your manager", and "when did you have to say no to someone important" are all the conflict archetype wearing different clothes. Once you see the archetypes, the question surface stops being infinite.
List six to eight of the most substantial things you've been part of over the last five or so years — launches, migrations, turnarounds, messes, rescues. For each, write a five-line STAR skeleton: one line of context, one of your specific role, two of your actions, one of the result with a number if it exists.
Then tag each story with the archetypes it can serve. A good story covers two or three: the failed launch is a failure story, an ambiguity story, and possibly a pressure story depending on which aspect you foreground. Six stories times two or three tags each gives you full coverage of the eight archetypes with backups — which matters, because a multi-round loop will burn through your material and repeating a story to the same interviewer weakens both tellings.
The bank only works if you can retrieve from it mid-interview. Before each round, review the tags, not the transcripts — you're refreshing the index. When a question lands, take a breath and name the mapping to yourself: this is the persuasion archetype, that's the pricing story. The three seconds of pause reads as thoughtfulness, not hesitation.
If a question genuinely maps to nothing in the bank, say so honestly and offer the nearest neighbor: "I haven't managed a direct report through underperformance, but I did coach a struggling peer through a project they were failing — is that useful?" Interviewers accept adjacent stories offered transparently; what they don't accept is a story visibly stretched to fit a claim it doesn't support.
Six to eight substantial ones, each tagged against the archetypes it can serve. Since good stories cover two or three archetypes each, that's full coverage with backups for multi-round loops where repeating material is costly.
Across different interviewers, yes — freely. With the same interviewer, avoid it: a second telling weakens both. This is why the bank needs backups per archetype rather than one story per theme.
Offer the nearest adjacent story transparently: name what you haven't done, then the closest thing you have. Interviewers accept honest adjacency. A story visibly stretched to fit a claim it can't support costs more than the gap did.
Your story bank and your resume should be the same six stories — score your resume free to check the bullets set up the interviews you want to have.
