6.6 — Mock Interviews With Claude | AI for Real Life

Mock interviews with AI.

What makes Claude unusually good at this isn't the standard list of behavioral questions: that exists everywhere. It's that Claude actually listens to your answer and asks the unexpected follow-up that a real interviewer would ask. "You said the project lead 'eventually came around':what specifically changed their mind?" That's the move you can't drill against alone.

Use voice mode if you can

Read the prompts in this lesson, but practice them out loud. The whole point is rehearsing the way you actually sound under live conditions. Voice mode (Lesson 1.3) closes the gap between "sounded great in my head" and "fumbled the third sentence":which is exactly the gap real interviews surface. Set your phone down. Talk to it like a person across the table.

The setup: your Interview Cowork Project, the interviewer persona prompt.

You can run mock interviews from your existing Applications Cowork Project, or create a sub-project for a specific role. Either way, the move is the same: brief Claude on the company, role, and your background once, then run as many interview rounds as you want.

The mock-interview setup

Open a new chat in your Applications Cowork Project. Claude already has your Application Profile, master resume, and Voice Profile in knowledge.
Build a short Interview Brief. Paste the role title, the company, the job description, and 2–3 things you've researched about the team or the interviewer if you have them. Save it as a file in the Cowork Project (e.g., interview-brief-CompanyX-RoleY.docx).
Paste the Mock-Interviewer persona prompt below. Pick your question budget and question mix.
Switch to voice mode. Set your phone down. Begin.
Run the after-action review prompt at the end (screen 4). Don't skip: the review is where the practice actually pays off.

The Mock-Interviewer persona prompt: paste at the start of every practice run

You are running a mock interview for me. The role is in the Interview Brief in this Project's context. Behave like a real interviewer at that company. Specifically: 1. Ask ONE question at a time. Wait for my full answer before moving on. 2. After my answer, do ONE of three things: pick whichever a real interviewer would actually do: a. Ask a sharp, specific follow-up about something I said. Pull from the actual content of my answer: quote me back where useful. ("You said the lead 'eventually came around':what specifically changed their mind?") b. Give me a tiny push when I'm being too vague or too short. ("Can you walk me through the specific thing YOU did? You're describing the team's actions.") c. Move to the next question only when this thread is done. 3. Sometimes ask the unexpected curveball: the question a real interviewer would ask that isn't on the standard list. Don't telegraph these. 4. Use a realistic interviewer pace and tone for THIS company: be slightly more casual at a startup, slightly more formal at a Big Four firm. 5. DO NOT give me feedback during the interview. Don't tell me my answer was good or bad. Just keep interviewing. 6. After [X] questions OR when I say "wrap it up," end the interview with a normal close ("any questions for me?") and stop. We'll do the after-action review separately. Format constraint: Don't break character to ask if I'm ready or to explain what you're doing. Just run the interview. If I genuinely need to pause, I'll say "pause." Question budget for this run: [pick one: Quick: 4 questions / Standard: 8 questions / Full: 12 questions / Stress: 15+ questions including curveballs] Question mix: [pick one: Behavioral only / Behavioral + light technical / Mixed including curveballs / "Tell me about yourself" intro practice only] Ready when I am: start with the standard "tell me about yourself" or jump in with question 1, your call.

The three flavors of mock interview: when to run each.

Don't run every flavor every night. Match the flavor to where you actually need work.

Flavor 1: "Tell me about yourself" intro practice

Do this first. The opening of any interview is the answer to "tell me about yourself." If your intro is good, the rest of the interview runs calm. If it's bad, you spend the rest of it trying to recover. Set the question mix to "intro practice only," do 3–5 reps in a row in voice mode, and work toward a clean, focused version that doesn't ramble.

Flavor 2: Behavioral / STAR practice

The meat of every interview round. "Tell me about a time you…": these dominate internship and early-career interview rounds. STAR (Situation, Task, Action, Result) is the answer shape. Set the question mix to "behavioral only" and run a full 8–12 question round, pulling from the stories in your Application Profile.

Flavor 3: Curveball / stress practice

The polish round. "What's a weakness you're actively working on?" "Why are you applying here over [direct competitor]?" "Walk me through how you'd approach [open-ended problem]?" The point isn't memorizing answers: it's getting used to the feeling of an unexpected question without freezing. Run this once a week leading up to a real interview.

Behavioral push prompt: when your answers are too vague

For this practice run, when my answer is vague or doesn't follow STAR (Situation, Task, Action, Result), DO NOT tell me to use STAR. Instead, do one of these: - Ask the specific question that forces me to give the missing element ("What did YOU specifically do, as opposed to the team?"). - Quote my answer back to me and ask "what does 'helped a lot' actually look like in this story?" - Ask "what was the outcome: even if it was small or messy" when I forget the result. Do NOT walk me through the framework. Real interviewers don't. They just keep asking until I either give them the substance or fall apart trying. After the full interview, in the after-action review, you can name what I missed. Continue the interview now.

The after-action review: where the practice actually pays off.

Five minutes after your mock, while it's still fresh, switch Claude out of interviewer mode and into coach mode.

Post-interview after-action review prompt

The mock interview is over. Now switch out of interviewer mode and into coach mode. Be sharp, specific, and honest. I want to know what to drill before the real interview. Walk me through: 1. STRONGEST ANSWER: Which of my answers was strongest? Why specifically: was it the structure (STAR), the specificity, the voice, the way I handled the follow-up? 2. WEAKEST ANSWER: Which was weakest? Quote my actual answer (or summarize what I said). Tell me specifically what was off: too vague, no result, lost the thread, defensive tone, ran long, ran short, missed the question entirely. 3. STAR DIAGNOSTIC: For each behavioral question, mark which STAR elements I hit (S/T/A/R) and which I dropped. Tell me which element I'm chronically dropping across the interview: that's the one to drill. 4. VERBAL TICS: In voice mode, did I have a recurring filler / hedge / tic? ("Um," "kind of," "I guess," nervous laugh, trailing off, restarting sentences.) Tell me the top 1–2. 5. STORY POOL: Out of my Application Profile stories, which 2–3 did I pull most? Was that the right pool for this role? Are there 1–2 stories I'm not using that I should be using more? 6. THE CURVEBALL READ: How did I do on the unexpected questions? Where did I freeze, deflect, or pivot away? Quote. 7. THE 3 SPECIFIC THINGS TO DRILL before my next mock or the real interview. Make them specific. "Practice answering question X type" is too vague. "Re-tell the food-drive story without mentioning the team's contribution until the second sentence" is right. 8. THE ONE FIX: If I had time for ONE thing before the real interview, what would matter most? Don't be polite. Don't be cruel. Be the version of a coach who actually wants me to land this.

The "I have a real interview tomorrow" cram prompt

My real interview for [role at company] is tomorrow at [time]. I have [X] hours tonight. Help me make the best use of them. Based on: - The Interview Brief in your knowledge - My Application Profile - The mocks we've done in the last [N] days (you'll remember the gaps and the weak answers) Build me a 4-step prep plan for tonight, in priority order: 1. The most important question to drill. Why it's the one. The exact angle to drill on. 2. The 3 stories from my profile that should be at the front of my brain. For each, the 2 sentences I want to be ready to say if asked. 3. 4–6 specific questions I should have for the interviewer. Pull from the Interview Brief: make them specific to this team / company / role, not generic ("what's the culture like"). 4. The single anxiety-management move for tomorrow morning. (Sleep, eat, what to wear, when to leave, what to read on the way.) Be practical, not preachy. Don't over-cram. Cap the plan at things I can actually do tonight without staying up late.

The line between practicing and cheating.

Mock interviews are firmly on the green side of every line. That said, the real-time use of AI during an interview is a fast-moving area where the line is sharp and getting sharper. Read this list once before your first real interview. The bottom card is the one that gets people blacklisted.

Practicing with AI vs. running AI during the interview

Honest: Mock interviews with Claude beforehand. Hundreds of reps. Reviewing weak answers. Drilling specific stories.
Honest: Reviewing notes / story bank in the 30 minutes before a phone screen. Same as flashcards before an exam.
Borderline: A notes doc open during a phone screen with bullet reminders. (Common, generally tolerated: just don't read aloud from it.)
Not honest: An AI tool that listens to the interviewer's question and feeds you suggested answers in real time. Even when not against the company's rules, it produces detectable awkward pauses, dead-eye delivery, and answers that don't match your written voice. Several companies have explicitly banned these and most others now ask you to share your screen specifically because of this.
Not honest at all: AI deepfakes, voice clones, "answer-for-me" tools during the actual conversation. The fastest way to get blacklisted from a company and from any company that talks to them.

The interview is the part nobody can do for you

Honest Work Code · Rules 1 and 3. The interview is the one moment in the application process that exists specifically because the company wants to talk to you, not your written record. Practicing with Claude is running drills: universally fair, frequently encouraged. Letting Claude answer for you in real time is bringing your AI tutor to take the test. The Dinner Table Test for interviews is even simpler: could you say the same thing, the same way, in the same room, without the laptop hint? If yes, you're prepared. If no, you're set up for a bad result the second the question shifts. Drill until "yes." Then go in calm.

Up next: the underserved skill that opens (or closes) doors.

Recommendation letters are the one piece of your application that you don't write: but you absolutely shape. Most students ask awkwardly, give the recommender nothing useful, and end up with a generic letter that says "Sarah was a good student in my class." Lesson 6.7 is the underserved skill of asking the right person, at the right time, with the right brag sheet: so the letter your recommender writes is the one that actually moves the needle.

Continue to 6.7 → Recommendation Letters & How to Ask