The anatomy of a Claude prompt that works the first time
Most disappointing answers come from prompts that are missing one of five parts. Here is what each part does, with a before and after you can copy.
Practise for a real interview. One question at a time, a score for each answer, and a stronger version of what you actually said.
Run a mock interview with me for this job. Role: [JOB TITLE AND LEVEL] Company, or the kind of company: [COMPANY] The job description: <job> [PASTE THE JOB DESCRIPTION] </job> My background in a few lines: [YOUR EXPERIENCE] How I'd like it to go: - One question at a time, then wait for my answer. Mix behavioural questions with ones about the actual work in the job description. - After each answer, give me a score out of 5 and tell me what an interviewer would have noticed, good and bad. Be blunt. I'd rather hear it from you. - Then show me a stronger version of my own answer, using only facts I gave you. Don't invent achievements for me. - If I was vague, ask the follow-up a real interviewer would ask before you score it. - After five questions, tell me straight: would you put me through to the next round, and what are the two things to fix first? Go ahead with the first question.
Question 2 of 5. Tell me about a time you disagreed with a decision your manager made. What did you do?
Your answer: "My manager wanted to ship the redesign before the holidays and I thought it was too early. I told her, we talked about it, and in the end we shipped it in January."
What an interviewer hears. You disagreed, and things worked out. That is the skeleton of a good story, but every interesting part is missing. Why was it too early? How did you raise it? What changed her mind? Right now it could also be read as "I complained and got lucky".
The follow-up they would ask: What did you base "too early" on?
Your reply: "We had only tested it with 4 users, and 3 of them could not find the export button."
"My manager wanted to ship our redesign before the holidays. I was worried, because we had only tested it with four users and three of them could not find the export button, which is the feature our customers use most. I did not want to simply say it was too early, so I showed her the recordings and suggested one more week of testing with the fix in place. She agreed. We shipped in January, and export related support tickets did not go up after the launch."
Why it works better. It has a reason (the test result), an action (you brought evidence and a proposal, not a complaint) and an outcome. If you have the real number for support tickets, use it.
Ready for question 3?
NoteThis is an example. Results change between runs and model versions. Claude Prompts is a fan project and is not affiliated with Anthropic.
Use it in the week before the interview, once you have the real job description. Two or three short sessions beat one long one, because you get time in between to work on what came up.
Answer the way you'd talk, not the way you'd write. If you polish each answer before sending it, the feedback ends up being about your writing. The rule about only using facts you gave is there to protect you. A "stronger" answer built on an achievement you never had will fall apart at the first follow-up in the real room.
Use the copy button above. The full text is included, nothing is cut off.
Everything highlighted in yellow is a placeholder. Swap it for your own topic, audience or data.
If the result helped, press the heart. Votes decide which prompts make the weekly top 10.
Subject: Re: Offer for Senior Product Designer Hi Priya, Thank you for the offer, and for the conversations over the last few weeks. I enjoyed meeting the team and I'd like to make this work. Before I accept, I'd like to ask...
Paste the offer, what you'd accept and what you know about the market, and get a short reply that says you're pleased, asks for one specific change with a reason, and keeps the door open, plus what to send if they meet you halfway or say no.
Most disappointing answers come from prompts that are missing one of five parts. Here is what each part does, with a before and after you can copy.
One vote per prompt, a fresh count every Monday, and a simple tie-break. Everything about how prompts reach the top three, in plain words.