Claude Job Interview Preparation Coach Prompt
Prepare for any job interview with tailored questions, STAR-format answers, and a strategy for the toughest moments.
Category
🎯 Career
Difficulty
Intermediate
Models
3
Last Updated
2026-06-29
Works with
📄 Example output
⚠️ Common Mistakes
❓ FAQ
⚙️ Fill in your variables
📋 Prompt
You are a career coach and former hiring manager who has conducted 500+ interviews.
Role: [job title and company]
Your background: [relevant experience in 3-4 sentences]
Your biggest strength for this role: [what makes you stand out]
Your biggest concern: [what might an interviewer question about your background]
Interview format: [panel/one-on-one/case study/technical/competency-based]
Task:
1. LIKELY QUESTIONS (10): Based on the role — mix of behavioural, situational, and role-specific
2. STAR ANSWERS (3): For the 3 most likely behavioural questions — Situation, Task, Action, Result
3. YOUR QUESTIONS TO ASK (5): Questions that signal preparation and strategic thinking
4. HANDLING YOUR WEAK SPOT: How to address your biggest concern proactively and confidently
5. OPENING ANSWER: Tell me about yourself — a 90-second structured response
6. SALARY QUESTION: How to handle what are your salary expectations
7. CLOSING MOVE: How to end the interview strongly and stand out
Role: [job title and company]
Your background: [relevant experience in 3-4 sentences]
Your biggest strength for this role: [what makes you stand out]
Your biggest concern: [what might an interviewer question about your background]
Interview format: [panel/one-on-one/case study/technical/competency-based]
Task:
1. LIKELY QUESTIONS (10): Based on the role — mix of behavioural, situational, and role-specific
2. STAR ANSWERS (3): For the 3 most likely behavioural questions — Situation, Task, Action, Result
3. YOUR QUESTIONS TO ASK (5): Questions that signal preparation and strategic thinking
4. HANDLING YOUR WEAK SPOT: How to address your biggest concern proactively and confidently
5. OPENING ANSWER: Tell me about yourself — a 90-second structured response
6. SALARY QUESTION: How to handle what are your salary expectations
7. CLOSING MOVE: How to end the interview strongly and stand out
LIKELY QUESTIONS:
1. Tell me about a product you built from 0 to 1 — what decisions shaped it most?
2. Describe a time you had to say no to a requested feature. How did you handle it?
3. How do you build trust with an engineering team?
4. Tell me about a product that failed. What did you learn?
5. How do you prioritise when there are competing stakeholder demands?
6. Describe your approach to defining success metrics for a new product
7. Tell me about a time you changed your mind based on user feedback
8. How do you stay close to the customer as the team scales?
9. What does good product documentation look like to you?
10. Where do you disagree with conventional product management wisdom?
STAR ANSWER: Describe a time you had to say no to a feature request
Situation: At my last role, our largest enterprise customer requested a custom reporting dashboard — our sales team was strongly advocating for it as a retention risk.
Task: I needed to evaluate the request honestly without damaging the customer relationship or caving to internal pressure.
Action: I ran a structured analysis — how many customers had requested this, what they actually needed vs what they asked for, and whether our roadmap had a better solution already planned. I presented data showing that 2 of 80 customers had requested it, and that our Q3 analytics upgrade would cover 80% of their actual need. I offered to loop in the customer directly to validate.
Result: Customer agreed to wait for Q3 release. Feature shipped to 80 customers vs being built for 2. Customer retained. Sales team alignment improved because they saw the process was principled not arbitrary.
HANDLING YOUR WEAK SPOT:
Do not wait for them to raise it — address it in your tell me about yourself. Frame it as: I have deliberately built my career at the intersection of small and large — I joined a startup after an enterprise role specifically to ship faster and own more. I am now ready to bring that velocity to a larger organisation, and I have been methodical about studying how the PM role scales.
SALARY QUESTION:
I am targeting a range of X to Y based on market data for this level in this location, and my experience leading products at this scale. I am flexible depending on the full package. What is the budgeted range for this role?
(Always give a range anchored at the top of what you want and flip the question back to them)
1. Tell me about a product you built from 0 to 1 — what decisions shaped it most?
2. Describe a time you had to say no to a requested feature. How did you handle it?
3. How do you build trust with an engineering team?
4. Tell me about a product that failed. What did you learn?
5. How do you prioritise when there are competing stakeholder demands?
6. Describe your approach to defining success metrics for a new product
7. Tell me about a time you changed your mind based on user feedback
8. How do you stay close to the customer as the team scales?
9. What does good product documentation look like to you?
10. Where do you disagree with conventional product management wisdom?
STAR ANSWER: Describe a time you had to say no to a feature request
Situation: At my last role, our largest enterprise customer requested a custom reporting dashboard — our sales team was strongly advocating for it as a retention risk.
Task: I needed to evaluate the request honestly without damaging the customer relationship or caving to internal pressure.
Action: I ran a structured analysis — how many customers had requested this, what they actually needed vs what they asked for, and whether our roadmap had a better solution already planned. I presented data showing that 2 of 80 customers had requested it, and that our Q3 analytics upgrade would cover 80% of their actual need. I offered to loop in the customer directly to validate.
Result: Customer agreed to wait for Q3 release. Feature shipped to 80 customers vs being built for 2. Customer retained. Sales team alignment improved because they saw the process was principled not arbitrary.
HANDLING YOUR WEAK SPOT:
Do not wait for them to raise it — address it in your tell me about yourself. Frame it as: I have deliberately built my career at the intersection of small and large — I joined a startup after an enterprise role specifically to ship faster and own more. I am now ready to bring that velocity to a larger organisation, and I have been methodical about studying how the PM role scales.
SALARY QUESTION:
I am targeting a range of X to Y based on market data for this level in this location, and my experience leading products at this scale. I am flexible depending on the full package. What is the budgeted range for this role?
(Always give a range anchored at the top of what you want and flip the question back to them)
🏆
💡 Pro Tips
Best model for this prompt
Claude
Claude (Opus 4 / Sonnet 4)
Prepare 5 STAR stories that can each answer multiple question types — one good story about handling conflict can also be about influencing without authority, managing ambiguity, or showing resilience
The question you ask at the end is evaluated too — ask something that signals you have thought seriously about the role, not something easily answered by reading the website
Research the interviewers on LinkedIn before the panel — knowing their background lets you tailor answers and ask better follow-up questions
Never speak negatively about a previous employer in an interview — reframe any difficult situation as a learning or a challenge you navigated professionally
STAR answers with no result — the R in STAR is where you demonstrate impact; vague or missing results lose the interviewer
Tell me about yourself that runs more than 2 minutes — 90 seconds maximum; practise it until it feels natural
Asking no questions at the end — it signals low enthusiasm and low preparation
Answering what are your weaknesses with a strength disguised as a weakness — interviewers see through this immediately; give a real area you are working on with evidence of progress
- How far in advance should I prepare?For a first-round screen: 2-3 hours. For a panel or final round: 5-8 hours across 2-3 days. The most important preparation is practising your STAR answers aloud — not just thinking about them.
- Should I memorise my answers?Memorise the structure and key points, not the exact words. Memorised answers sound mechanical and fall apart when the question is phrased differently. Know your stories well enough to tell them naturally.
- How do I handle a question I do not know the answer to?That is a great question — I want to think through that properly. Then take 10-15 seconds and give your best reasoned answer. Saying I do not know but here is how I would approach finding out is far better than bluffing.
- Best model?Claude produces more nuanced interview coaching — particularly for handling difficult questions, calibrating the right level of vulnerability on weak spots, and generating questions that signal strategic thinking.