Interview Preparation
Interview Prep for a Specific Loop
Build a prep pack: likely questions, STAR stories from your resume, and questions to ask them.
The Prompt
interview-prep-for-a-specific-loop.md
Coach me for this interview. Use only my experience. Company: {{company}} Role: {{role}} Interview format: {{format}} Job description: {{job_description}} My resume / stories: {{resume}} Produce: 1. 12 likely questions (mix of behavioural, role, and one curveball) 2. For the 6 most important: a STAR outline using my stories - label which resume bullet it came from 3. 8 questions I should ask, ranked (role, team, success metrics, not "what's the culture") 4. A 60-second "tell me about yourself" script 5. Red flags to listen for in their answers If my stories do not cover a likely question, say "no story yet" and tell me what anecdote to collect.
Negative prompt
Included when you copy the prompt
Do not invent employers, projects, or metrics not in {{resume}}. Do not fabricate STAR stories - mark "no story yet" and say what to collect. Do not fill question lists with vague culture fluff. Do not give generic prep that ignores {{company}}, {{role}}, and {{format}}. Do not coach dishonest answers or resume inflation.
Fill in your details below - this prompt updates as you type, then copy it.
Fill in your details
0 of 5 filled. Preview updates as you type - then copy the finished prompt (negative prompt included when present).
interview-prep-for-a-specific-loop.md
Prompt preview
Coach me for this interview. Use only my experience. Company: {{company}} Role: {{role}} Interview format: {{format}} Job description: {{job_description}} My resume / stories: {{resume}} Produce: 1. 12 likely questions (mix of behavioural, role, and one curveball) 2. For the 6 most important: a STAR outline using my stories - label which resume bullet it came from 3. 8 questions I should ask, ranked (role, team, success metrics, not "what's the culture") 4. A 60-second "tell me about yourself" script 5. Red flags to listen for in their answers If my stories do not cover a likely question, say "no story yet" and tell me what anecdote to collect.
Examples
Example input
Company: Stripe Role: Technical Program Manager Interview format: Recruiter screen + 4x45 (TPM skills, cross-functional, tech depth with EM, bar raiser) Job description: Drive multi-team launches, risk management, write crisp specs, comfort with APIs/payments domain a plus Resume: TPM at fintech - led KYC vendor migration across Eng/Compliance/Support; cut launch defects by coordinating test plan; wrote RFC for rate-limit changes; no direct payments API ownership
What you should get
1. 12 questions spanning behavioural (conflict, influence), TPM (risk, timeline), tech (API/vendor), plus one curveball. 2. Six STAR outlines tied to KYC migration / test plan / RFC bullets; payments-API deep dive marked "no story yet - collect a time you debugged an integration or read API docs under deadline." 3. Eight ranked questions on success metrics for first 6 months, team topology, launch ownership, incident process - not "what's the culture." 4. 60-second pitch: fintech TPM → cross-functional launches → why Stripe. 5. Red flags: unclear DRI for launches, "heroics expected," no written specs culture.
When to use this prompt
Use it when
- You need help with job seekers.
- You need help with internal mobility.
Skip it when
- You only need a one-line ask with no constraints, format, or context.
- You cannot supply the fill-in details the template asks for.
- A different category or tool-specific workflow fits the job better.
How to get a good result
Done when
1. 12 questions spanning behavioural (conflict, influence), TPM (risk, timeline), tech (API/vendor), plus one curveball. 2. Six STAR outlines tied to KYC migration / test plan / RFC bullets; payments-API deep dive marked "no story yet - collect a time you debugged an integration or read API docs under deadline." 3. Eight ranked questions on success metrics for first 6 months, team topology, launch ownership, incident process - not "what's the culture." 4. 60-second pitch: fintech TPM → cross-functional launches → why Stripe. 5. Red flags: unclear DRI for launches, "heroics expected," no written specs culture.
Common mistakes
- Leaving company, role, format vague - the model then invents placeholders.
- Asking ChatGPT, Claude, or Gemini for a shorter answer after a long structured prompt - that throws away the format rules.
- Stopping when the first draft appears instead of checking it against the success criteria below.
FAQ
- What do I fill in before I copy this prompt?
- Replace these placeholders with your details: company, role, format, job_description, resume. Required fields are marked on the page. The prompt text updates as you type.
- Which AI tools is this prompt written for?
- It works best with ChatGPT, Claude, Gemini. Copy the filled prompt and paste it into the tool you already use.
- What should a good result look like?
- 1. 12 questions spanning behavioural (conflict, influence), TPM (risk, timeline), tech (API/vendor), plus one curveball. 2. Six STAR outlines tied to KYC migration / test plan / RFC bullets; payments-API deep dive marked "no story yet - collect a time you debugged an integration or read API docs under deadline." 3. Eight ranked questions on success metrics for first 6 months, team topology, launch ownership, incident process - not "what's the culture." 4. 60-second pitch: fintech TPM → cross-…
- What are common mistakes with this prompt?
- Leaving company, role, format vague - the model then invents placeholders. Asking ChatGPT, Claude, or Gemini for a shorter answer after a long structured prompt - that throws away the format rules. Stopping when the first draft appears instead of checking it against the success criteria below.
Best for
- Job seekers
- Internal mobility
Related Prompts
More prompts like this — same topic and style.
