Claude · Prompts

The interview story bank: 7 Claude prompts

Seven Claude prompts that pull every usable story out of your last five years of work, tag each one by the competencies hiring managers score, and file them so you never freeze on "tell me about a time when" again.

QQuentin Megevand
September 4, 2026 · 10 min read

You do not forget your work. You stop noticing it. Five years of projects collapse into three resume lines, and when a recruiter asks "tell me about a time you handled a conflict," you reach for the same two stories you always use. The stories are still there. Nobody has pulled them out and written them down.

This guide does the pulling for you, with Claude, in one 45 minute session.

At the end you have one Claude Project holding 15 to 30 tagged career stories, each written to be spoken out loud in 90 seconds, plus a named list of the competencies you currently have no evidence for, and what to go collect to close each one. It works in interviews, performance reviews, LinkedIn posts and cover letters. Same story, four lengths.

Claude AI Lab

The Claude AI Lab is my Skool community where I share my Claude systems and the more advanced modules. Access is $67/month.

Join the Lab →
✅What you need
1
A Claude account with Projects. The prompts work once in a normal chat. The Project is what makes the bank last, because Claude stops asking who you are every time you open a new conversation.
2
45 quiet minutes for the first run. Prompt 1 is an interview, not a form. Rush it and everything after it comes out thin.
3
Your resume and your last reviews, but not yet. You add them to the Project after prompt 1, never before. Loaded first, Claude anchors on the compressed version instead of interviewing you.

How to use this guide

Run the seven prompts in order, in one Claude Project, in one sitting if you can. Prompt 1 is a conversation: answer it the way you would if someone asked you out loud, and do not rush. Everything after it is built on what you said, so a thin extraction gives you a thin bank. Budget 45 minutes for the first run, then 10 minutes a month with the loop at the end of this article.

Start here

4
Open Claude and create a new Project called "Career story bank".
5
Paste the Project instructions from the "Project setup" section further down this article.
6
Run prompt 1 and answer properly. It is the only prompt that needs real effort from you.
7
Run prompts 2 to 7 in order, in the same conversation.
8
File the output in the story card template at the bottom of this article, one card per story.
1

The extraction

💬 claude.ai, inside your Project

This is the only prompt where you do the talking. Everything else is built on what comes out here.

Act as an interviewer building my career record. Interview me one question at a time about the last five years of my work: the projects, the problems, the people I had to convince, the things that went wrong. Do not write anything until you have the full picture.
Why it works
One question at a time stops Claude from dumping a questionnaire on you. You answer conversationally, and conversation surfaces details a form never gets.
⚠️
Mistake to avoid
Pasting your resume and calling it the extraction. Your resume is already the compressed version. Feeding it back gives you the same three lines with better adjectives.
✅
You know it worked when
Claude follows up on something you mentioned in passing and you have to stop and think about the answer.
2

The story mining

🔎 same conversation

Claude reads back what you said and finds the shapes you did not notice.

From everything I told you, pull out every moment that has a clear before, a specific action I took, and a result. List all of them. Include the small ones I skipped past.
Why it works
"Include the small ones I skipped past" is the whole prompt. The stories you undervalue are often the ones with the cleanest structure, because you were not performing when you told them.
⚠️
Mistake to avoid
Deleting anything at this stage because it feels too minor. Filtering happens in prompt 3, not here. A 12 item list you trimmed yourself is a worse bank than a 30 item list you sorted.
✅
You know it worked when
At least three items on the list are things you would never have thought to bring to an interview.
3

The competency tag

🏷️ same conversation

Interviews are scored against a rubric. This maps your stories onto it.

Tag each story with the competencies a hiring manager actually scores: ownership, influence, judgment under pressure, conflict, ambiguity, delivery. One story can carry more than one.
Why it works
You stop preparing "stories" and start preparing coverage. When the question comes, you are not searching your memory, you are picking from a labeled shelf.
⚠️
Mistake to avoid
Letting one story carry all six tags. If it covers everything it demonstrates nothing. Ask Claude to keep the two strongest tags per story and justify each.
✅
You know it worked when
You can name your strongest competency and your thinnest one without counting.
4

The rewrite

🎙️ same conversation

A written story and a spoken story are different objects. This converts one into the other.

Rewrite each story to be told out loud in 90 seconds: the situation, what I did, what changed, and one number if a real one exists. Cut anything I would not say in a normal conversation.
Why it works
"If a real one exists" blocks the invented metric. "Anything I would not say in a normal conversation" strips the corporate register that makes rehearsed answers sound rehearsed.
⚠️
Mistake to avoid
Accepting a number you cannot defend. If Claude writes "improved efficiency by 30 percent" and you cannot say where it came from, cut it. One unsupported figure costs you the whole answer.
✅
You know it worked when
You read one out loud and it sounds like you talking, not like a cover letter.
5

The gap check

🕳️ same conversation

The most valuable prompt in the set, and the one everyone skips.

Which competencies have no story behind them? Tell me what kind of evidence I need to go collect in the next three months to close each gap.
Why it works
It turns interview prep into a plan. A gap you know about is a project you can start on Monday. A gap you discover mid interview is a rejection.
⚠️
Mistake to avoid
Reading the gap list as a reason to feel behind. It is a shopping list. Pick the gap closest to the roles you want and go get the evidence.
✅
You know it worked when
You have one concrete thing to volunteer for at work that exists purely to close a named gap.
6

The reuse map

🗺️ same conversation

The same story, resized for four different surfaces.

For each story, tell me where it belongs: interview answer, performance review, LinkedIn post, cover letter paragraph. Same story, different length and framing.
Why it works
The bank stops being interview only. A performance review and a LinkedIn post both need evidence, and you just built a stocked shelf of it.
⚠️
Mistake to avoid
Publishing the LinkedIn version word for word. Claude gives you the angle and the structure. The voice has to be yours, or it reads like every other post on the feed.
✅
You know it worked when
At least two stories have a post version you would actually be willing to publish.
7

The pressure test

🔥 same conversation

The stories that break in the room are the ones nobody challenged in advance.

Pick my three weakest stories and ask me the follow up questions a sharp interviewer would ask. Keep going until the story holds up.
Why it works
Interviewers rarely reject your first answer. They reject the third follow up, when the story runs out of substance. This is where you find out which ones do.
⚠️
Mistake to avoid
Stopping when it gets uncomfortable. The point of discomfort is the exact spot the interviewer will press. Push through it once here and it never surprises you again.
✅
You know it worked when
One story collapses under questioning and you either fix it or drop it. That is the prompt working, not failing.

Project setup

The prompts work once. The Project is what makes the bank last: Claude stops asking who you are every time you open a chat. Paste this into the Project instructions.

You are maintaining my career story bank.

Context:
My role and level: [fill in]
My industry: [fill in]
The kind of role I am aiming at next: [fill in]

Rules:
Never invent numbers, results, titles or dates. If a figure is missing, ask me or leave it out.
Write everything in the voice I use when I speak, never in corporate register.
Every story must have a clear before, a specific action I took, and a result.
Tag every story against: ownership, influence, judgment under pressure, conflict, ambiguity, delivery.
When I add a new story, tell me which existing story it is stronger than, and why.
Order matters
Add your resume and your performance reviews to the Project knowledge after you run prompt 1, never before. Loaded first, Claude anchors on the compressed version instead of interviewing you properly.

The story card template

One card per story. Keep it in the Project so it grows instead of resetting.

🏷️
Title
Five words you would use to find it fast.
🎯
Competencies
Two tags maximum, the strongest two.
⏮️
Situation
The before state, in one sentence.
🛠️
Action
What you specifically did, not what the team did.
📈
Result
What changed, plus one real number if you have one.
🎙️
Spoken version
The 90 second version from prompt 4.
🛡️
Holds up under
The follow ups it survived in prompt 7.
🔁
Reuse
Interview, review, post, cover letter.

The monthly loop

Ten minutes, once a month, and the bank never goes stale.

Here is what I worked on this month: [paste]. Add any new stories to the bank, tag them, and tell me which existing story each one is stronger than. Then update my gap list.

Why this changes everything

Interview prep feels awful for one precise reason: you always start from zero, the week you need it, under pressure. Run this system once and you never start from zero again. Then run the monthly loop and the bank quietly gets better while you do nothing.

Run prompt 1 tonight. It is the one that does the work.

Want to go further?

And day-to-day, I post one reel a day on Instagram: @quentin_iamarketing