Prompting Guide
How to Prompt Claude to Prepare for a Job Interview
You already know your own work. The hard part is saying it out loud on the spot.
Anthropic's Claude is good at turning a job posting into a realistic set of interview questions and at giving you honest, specific feedback on how you answered them, which makes it useful for the kind of practice that's hard to get otherwise: rehearsing out loud, getting pushed on a weak answer, and trying it again. It can't tell you what a specific interviewer will actually ask, and practicing with it doesn't guarantee an offer. What it can do is make your fifth run-through sharper than your first, by giving you a question, hearing your answer, and telling you plainly where it was vague.
To prepare for a job interview with Claude, paste in the actual job posting and ask for the specific questions someone in that role is likely to be asked, then answer them in your own words and ask Claude to critique the answer honestly: whether it's specific enough, whether it actually answers the question asked, and how a stronger version would sound. Practicing this way does not guarantee you'll get the job; it's rehearsal, not a prediction of the outcome.
Published
Free lesson · no account neededMeet ClaudeWhy Claude?6 minStart the free lessonKey Takeaways
- Paste in the real job posting, not a generic description of the role. Questions pulled from the actual responsibilities and requirements are far more useful than generic interview-prep questions.
- Answer out loud or in writing before you ask for feedback. Reading a model answer teaches you less than trying your own and finding out where it was weak.
- Ask for the STAR structure (Situation, Task, Action, Result) specifically if your answers tend to ramble. Naming the structure you want produces more useful feedback than asking Claude to just 'make it better.'
- Treat Claude's feedback as practice, not a verdict. It can tell you an answer was vague; it can't tell you whether a specific interviewer will like you, and no amount of practice guarantees an outcome.
- Practice the questions you're dreading most, not just the ones you already answer well. The ones you're avoiding are usually the ones worth the most rehearsal time.
Copy and Paste
Prompts You Can Use Today
Generating likely questions from a real job posting
Here is the job posting for a role I'm interviewing for: [paste the full posting]. Based on the specific responsibilities and requirements listed, write ten interview questions I'm likely to be asked, covering a mix of behavioral questions, questions about specific skills mentioned in the posting, and at least two questions about gaps between my background and what they're asking for.
Paste the whole posting, not a summary; specific phrases in the listing often map directly to specific questions.
Getting honest feedback on a practice answer
Here's the question: [paste the interview question]. Here's how I'd answer it: [write out your actual answer]. Tell me honestly: does this actually answer the question that was asked, is it specific enough to be memorable, and where is it vague or rambling? Don't soften the feedback.
Write your real answer rather than a polished one; the point is finding the weak spots, not getting praised for a draft.
Turning a vague answer into a STAR-structured one
Here's my rough answer to a behavioral question: [paste your answer]. Help me restructure it using Situation, Task, Action, and Result, keeping the actual facts and numbers I gave you, but organizing it so each part is clear and the result at the end is concrete.
Give Claude real numbers and outcomes if you have them; it can't invent a result you didn't mention.
Practicing an answer to a question about a weakness in your background
This job wants [specific skill or experience from the posting], and I don't have much experience with it. Help me prepare an honest answer to a question about this gap that doesn't overstate what I know, but makes a case for how quickly I'd get up to speed, using specific examples from times I've learned something similar.
Honesty here matters more than polish; an interviewer who catches an overstated claim will trust the rest of your answers less.
A mock interview, one question at a time
Run a mock interview with me for this role: [paste the job posting]. Ask me one question at a time, wait for my answer, then give me brief feedback before asking the next question. Start with a behavioral question, not a technical one.
This works better as a back-and-forth conversation than asking for ten questions and ten answers all at once.
The Structure
What makes interview prompts useful instead of generic
The same four moves separate practice that actually sharpens your answers from a list of generic tips.
The real job posting, not a summary
Paste in the actual listing. Specific requirements and responsibilities in the posting point directly at the questions you're likely to get, in a way a generic "software engineer interview questions" list never will.
Your real answer, not a request for a model one
Answer the question yourself first, in your own words, before asking for feedback. Reading Claude's version of a perfect answer teaches you far less than finding out where your own answer went wrong.
A structure to answer within, if you want one
If your answers tend to ramble, ask specifically for the STAR structure, Situation, Task, Action, Result. Naming the format gets you more useful feedback than a vague "make this better."
An instruction not to go easy on you
Ask directly for honest, specific feedback rather than encouragement. Practice that only tells you what you're doing well doesn't fix what you're doing poorly.
What This Can't Do
Practice is not a prediction of the outcome
It's worth being direct about this before anything else: practicing with Claude does not guarantee you'll get the job, or even that you'll get a specific question right in the actual interview. An interviewer brings their own judgment, their own priorities, and their own read on how you come across in the room, none of which a practice session can fully simulate, no matter how good the questions are.
What practice like this reliably does is make your answers sharper than they were before you started, because you're hearing specific, honest feedback on a real attempt rather than guessing on your own whether an answer landed. That's a real and useful improvement. It's just a different thing from a guarantee, and treating it as the latter sets you up for a confidence that isn't matched by what the exercise can actually promise.
The honest version of this skill is using practice to reduce your own uncertainty about how you come across, not to eliminate it. You'll still walk into the real interview not knowing exactly what will be asked or how the room will read you. What you'll have is more reps at noticing when your own answer is vague, which is something you control, instead of waiting to find that out live.
Common Mistakes
What makes practice less useful than it could be
These patterns turn a practice session into something that feels productive without actually sharpening anything.
Reading a model answer instead of writing your own
Asking Claude to "give me a good answer to this question" and reading it skips the part where you find out your own answer was weak. Write your real attempt first.
Practicing only the questions you're already good at
It's tempting to rehearse the answer you already like. The question you're avoiding is usually the one that most needs the rehearsal time.
Asking for encouragement instead of critique
If every piece of feedback is positive, you're not finding your weak spots. Ask explicitly for what's vague, rambling, or doesn't actually answer the question.
Treating a generic question list as job-specific prep
A list of the ten most common interview questions is a fine warm-up, but it isn't preparation for this specific role unless you've grounded it in the actual posting.
Using The Feedback
How to actually act on what Claude tells you
When Claude flags an answer as vague, the useful next step is adding the specific detail it's missing, not just rewriting the same sentence with more confident-sounding words. If it says an answer doesn't name a concrete result, that's a sign to go find a real number or outcome from the actual project, not to write a more impressive-sounding sentence that avoids the question.
If feedback keeps pointing at the same gap across multiple questions, that's worth noticing rather than fixing one answer at a time. A pattern of vague results across several behavioral questions usually means the fix is in how you're thinking about your own accomplishments, not in any single answer's wording.
It's also fine to disagree with the feedback. Claude is working from what you told it, and it doesn't know the context of the actual room, the interviewer, or how formal the company's culture is. If a suggestion doesn't fit how you actually want to come across, trust your own read on that over a generic structural suggestion.
It helps to keep a running list of the specific examples that came up well in practice, with the exact numbers or outcomes attached, so you're not reconstructing them from memory under pressure in the actual interview. A few bullet points you can glance at beforehand, built from the answers that held up best across your practice sessions, do more for your confidence than one more full run-through of every question.
Before The Real Thing
What to do in the last practice session before the interview
Run through your weakest two or three answers one more time, out loud if you can, rather than reviewing all ten questions again from scratch. The marginal value of reviewing a strong answer a sixth time is low; the marginal value of tightening up the one you're still shaky on is high.
Check that your answers to the "gap" questions, the ones about where your background doesn't quite match the posting, feel honest rather than overstated. An interviewer who catches an exaggerated claim tends to discount everything else you say after it, so this is worth getting right even if it means admitting a real limitation. It's also worth rereading the job posting itself one more time right before the interview, since a detail you skimmed past during prep sometimes turns out to be exactly what the first question is about.
Treat this practice as rehearsal for how you answer, not as a forecast of the result; the interview itself still depends on the room, the interviewer, and plenty you can't prepare for in advance.
Practice makes your answers sharper, not the outcome certain
Getting comfortable with honest, specific feedback is a skill that carries past this one interview. Nightschool AI's free lessons walk through real workplace writing and prep tasks with Claude, not toy examples.
Frequently Asked Questions
Can Claude guarantee I'll get the job if I practice this way?
No. Practicing with Claude can make your answers more specific and better rehearsed, but it can't predict how a specific interviewer will react, and no amount of practice guarantees an outcome. Treat it as rehearsal, not a forecast.
What should I paste in to get useful interview questions?
The actual job posting, in full, not a summary or a generic role description. Specific requirements and responsibilities in the real listing point directly at the kinds of questions you're likely to be asked.
Should I read Claude's model answer or write my own first?
Write your own first. Reading a polished example answer skips the part of practice where you discover your own answer is vague or doesn't actually address the question, which is the part that actually improves your interviewing.
How do I get Claude to stop being so encouraging and actually critique my answers?
Ask directly for honest, specific feedback rather than general encouragement, and ask it to flag anything vague, rambling, or that doesn't actually answer the question asked. Naming what you want catches more than a general request for feedback.
What's the STAR method and when should I ask Claude to use it?
Situation, Task, Action, Result: a structure for behavioral answers. Ask for it specifically if your answers tend to ramble; naming the structure gets you a more organized rewrite than a vague request to "make this better."
How should I answer a question about a gap in my experience?
Honestly, without overstating what you actually know. Ask Claude to help you frame the gap alongside a specific example of how quickly you've picked up something similar before, rather than hiding or minimizing it.
Can Claude run a full mock interview with me?
Yes. Ask it to ask one question at a time, wait for your answer, and give brief feedback before moving to the next question, rather than generating a full list of questions and answers at once. This back-and-forth format feels closer to a real interview than reading a static list ever will.
What should I focus on in my last practice session before the real interview?
Your weakest two or three answers, rehearsed out loud if possible, rather than reviewing every question again from the start. Tightening up a shaky answer is worth more than polishing one that's already strong, and it leaves you calmer walking in than one more pass over material you already know cold.
Sharper answers, not a guaranteed outcome
The practice is reusable for every interview after this one. What you say in the room is still up to you.