How to Use Claude for Interview Preparation

Choose the role and interview stage

Start by naming the role, seniority, interview stage, format, time limit and what you already know. A recruiter screen, technical interview, case exercise and final panel require different preparation. Paste the complete job description when permitted and mark confirmed text versus recruiter language. Ask Claude to list competencies and unknowns, not predict the exact questions. Define one session goal: understand the role, select stories, practise concise answers, prepare questions or identify a gap. A narrow goal gives you something observable to improve. Keep the final answer in your voice and ask Claude to flag wording you would not naturally say.

Create a verified experience bank

Record the situation, your responsibility, actions, constraints, result, evidence and what you would change. Add dates, team size, tools and metrics only when you can support them. Label each item VERIFIED, NEEDS DETAIL, TEAM RESULT or DO NOT USE. Ask Claude to map examples to requirements and identify weak evidence, using [ADD VERIFIED DETAIL] instead of filling gaps. Keep the original notes beside the output. If a bullet sounds impressive but you cannot explain how you know it, remove it. Your resume, application, LinkedIn profile and spoken story should agree where they overlap; preparation is partly a consistency exercise.

Map requirements to evidence

Ask Claude for requirement, wording from the posting, evidence you can discuss, confidence, likely follow-up and gap action. Separate must-have responsibilities from preferred qualifications and generic employer language. Choose three or four themes you want the interviewer to remember. High-importance, low-confidence items deserve an honest plan: review a project record, complete a small exercise, ask a former colleague for factual detail or prepare an explanation of what you are learning. Do not turn a gap into a claim. If the role asks for an unfamiliar tool, practise how you would approach the first week and what related experience transfers.

Research the employer from openable sources

Give Claude the employer's official site, job posting, product documentation, public filings or dated announcements that you have opened. Ask it to separate QUOTED FACT, SOURCE DATE, OPEN QUESTION and INFERENCE. Check product names, markets, leadership, locations and current priorities yourself. Turn the brief into useful questions about team problems, success measures and the first 90 days. Avoid pretending to know private plans. Mention a public detail only when it helps a real question. Save the source URL and retrieval date for claims that matter. A research brief should improve judgment, not create an illusion of inside knowledge.

Draft answer outlines, not speeches

Ask for a short outline using context, challenge, action, result, reflection and relevance to the role. Require one concrete detail, one decision and one trade-off. Then rewrite in your own words. A memorised paragraph breaks under follow-up; an outline helps you stay accurate while adapting. Ask Claude to highlight missing role, evidence, impact or learning. For technical or case questions, request a reasoning checklist and solve a fresh example yourself. Never ask it to manufacture a failure, conflict, leadership moment or metric. If the story is ordinary, make the decision and learning clear instead of adding drama.

Run a one-question mock interview

Ask Claude to act as an interviewer, ask one question, wait for your answer and give feedback on relevance, evidence, clarity and follow-up risk. Answer aloud, record yourself if appropriate and paste a rough transcript for review. Set a rubric first: did you answer, state your role, give evidence, explain a trade-off, stay concise and sound like yourself? Ask for a second attempt and compare the two. Claude's preference is not an objective hiring standard, so treat it as a coaching perspective. Ask a trusted person or domain expert to review high-stakes technical preparation.

Practise uncertainty and follow-ups

Ask for follow-ups about scope, alternatives, failure, stakeholders, measurement, ethics and what you learned. Practise saying “I do not know yet” followed by how you would find out. For technical work, explain assumptions before proposing a solution. For management or customer work, distinguish what you observed from what you inferred. If a result was shared by a team, say so. If you cannot disclose a client name, explain the context safely and focus on your role. A clear limitation followed by a credible method is more sustainable than an invented success story.

Use Claude's structure without flattening your voice

Claude's prompting guidance supports clear instructions, examples and structured output. Use that control for the rehearsal format, not for a fake personality. Give it a sample of your writing or speaking notes and ask it to preserve your vocabulary and formality. Request a 30-second version, a two-minute version and a deeper follow-up. Read each aloud and keep the one you can remember without performing it. If Claude becomes too polished, request plainer verbs and a change log. The aim is to make real experience legible, not to sound like a model.

Handle privacy and disclosure

Redact names, contact details, health information, compensation, internal client data and confidential projects unless the account and workflow are approved for that material. Do not paste a recruiter thread simply because it contains useful wording; extract only the relevant facts. Ask Claude to describe work without revealing client identities, trade secrets or personal information, then inspect the output for accidental disclosure. Decide your own policy about AI assistance in applications or assessments; employer rules vary and an assessment may require unaided work. Follow the employer's instructions.

Build a seven-day rehearsal loop

Day one: extract requirements and build the evidence matrix. Day two: choose stories and fill factual gaps. Day three: research the employer from openable sources. Day four: practise behavioural answers aloud. Day five: practise technical or case reasoning. Day six: run a timed mock interview and review notes. Day seven: shorten answers, prepare questions and rest. Keep a correction log for invented wording removed, dates clarified, examples that ran long and questions you could not answer. Ask Claude to turn the log into the next practice set. Stop when your stories are accurate, concise, adaptable and connected to the role.

Copy-paste prompt for Claude practice

Use this with a redacted job description and fact bank: <role>You are my interview-preparation coach. Help me organise truthful evidence and practise; do not invent experience, metrics, titles, employers, tools, company facts or questions.</role> <context>Role: [title]. Stage: [stage]. Format: [format]. Job description: [paste].</context> <facts>Use only these verified notes: [paste]. Label VERIFIED, TEAM RESULT, NEEDS DETAIL or DO NOT USE.</facts> <workflow>First build a requirement-to-evidence matrix and list gaps. Then ask one question at a time. After each answer, review relevance, evidence, clarity, structure and follow-up risk. Ask for a second attempt. Use [ADD VERIFIED DETAIL] when missing.</workflow> <voice>Keep my wording plain and natural. Give an outline, not a speech. End with three questions I can ask and a checklist against my resume.</voice>

Worked example: prepare one story without inventing it

Imagine a posting asks for cross-functional delivery, stakeholder communication and measurable improvement. Your notes say that you coordinated a website migration with design, engineering and support; the launch reduced a recurring support question, but you do not know the exact percentage. Give Claude those notes and ask for a requirement matrix. A safe output maps the story to each competency, identifies the missing measure and proposes follow-ups such as “What changed in support volume?” or “Which part did you own?” It does not turn “the team reduced questions” into “I reduced questions by 35%.”

Now ask for a 90-second outline: context, problem, your actions, collaboration, result, evidence and lesson. Put [ADD VERIFIED RESULT] where the number belongs. Read the outline aloud and replace model language with words you use. If the interviewer asks how you measured the result, practise saying what you know, what you do not know and how you would check it. If the story involved a disagreement, explain the decision process without blaming a colleague or revealing confidential information. A credible answer can say the work had a mixed result and still show learning.

Run the story twice. The first pass checks factual accuracy; the second checks whether the answer responds to the role rather than becoming a biography. Ask Claude for three follow-ups, then answer them without looking at the outline. Compare your recording or notes with the fact bank. Remove any sentence that adds a title, tool, metric or responsibility you did not supply. Finally, write one question for the interviewer about how the team measures the competency. This turns a generic behavioural rehearsal into evidence you can defend under pressure.

Final interview-preparation checklist

The day before an interview, do a source and truth pass rather than another wholesale rewrite. Open the job description and confirm the role, location, stage, format, time zone and any instructions about tools or assessments. Read your evidence matrix and choose a small set of stories you can adapt. For each story, check the dates, your actual responsibility, the team context, the result and the lesson. Mark any detail that needs a placeholder or a safe explanation.

Review the employer brief against the original sources. Remove claims that came only from Claude or an undated summary. Prepare questions that show you understand the work, not questions designed to perform enthusiasm. Practise your introduction, one technical or case answer, one behavioural story and a “I do not know” response aloud. Test your camera, audio, documents and quiet space if the interview is remote. Do not keep prompting until you sound artificial. A useful final check asks: can I explain this answer without the screen, would I say it to a person, and can I defend every important detail? If yes, close the chat and rest.

After the interview: learn without rewriting history

Use Claude after the interview to organise your own notes, not to invent what the interviewer meant. Record the questions you remember, the answers you gave, points you want to clarify, and any follow-up you promised. Label each item MEMORY, QUOTE, INTERPRETATION or UNKNOWN. Ask for a concise thank-you outline that mentions one real conversation point and does not make a new claim about the team. Open the original email or calendar details before sending.

For the next interview, ask Claude to turn the notes into practice prompts: where you ran long, where you lacked evidence, which question surprised you and which answer did not sound like you. Do not infer rejection or enthusiasm from a short message. Hiring processes vary and the model cannot read a recruiter's intent. Keep your preparation record factual, protect confidential details and update the fact bank only with information you can support. This closes the loop without turning uncertainty into a story.