Prepare me for a [INTERVIEW FORMAT] interview for [TARGET ROLE] at [COMPANY]. Use [JOB POSTING], [MY EXPERIENCE NOTES], and [INTERVIEW CONTEXT] as the only sources for factual claims. Do not invent accomplishments, technical knowledge, motivations, company facts, or answers. If an example lacks a result or detail, label the gap clearly. First, identify the six most important capabilities this interview is likely testing. Separate functional expertise, judgment, collaboration, communication, and role-specific risks. Then build a practical preparation pack with these sections: 1. “Role thesis” — 100 words explaining why my supported experience fits the role, including one honest gap and how to address it.
2. “Likely questions” — 12 questions: 4 role-specific, 4 behavioral, 2 judgment or prioritization, and 2 questions that test the biggest gap. For each, explain what the interviewer is trying to learn. 3. “Story bank” — 5 STAR outlines drawn from my notes. Include Situation, Task, Action, Result, the skill each story demonstrates, and missing facts to verify. Keep the Action specific to what I did, not just what the team did. 4. “Answer practice” — model answers for the three highest-risk questions, 90–150 words each, with a direct opening, evidence, and concise takeaway. 5. “Questions for them” — 6 questions that reveal success measures, priorities, decision rights, team interfaces, and the first 90 days; do not ask questions answered plainly in the posting. 6. “48-hour plan” — a short practice sequence. Before answering, check that every story has a clear personal contribution and that all company or role claims come from the supplied materials. Ask up to 3 clarifying questions only if a required input is missing.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [INTERVIEW FORMAT] | State the format, such as recruiter screen, hiring-manager interview, case interview, or panel. | 45-minute hiring-manager video interview |
| [TARGET ROLE] | Enter the job title and level. | Senior Product Marketing Manager |
| [COMPANY] | Enter the employer name. | Northstar Payroll |
| [JOB POSTING] | Paste the job description or essential responsibilities and qualifications. | Own positioning and launches for payroll products, partner with product and sales, use customer research, and report pipeline impact. |
| [MY EXPERIENCE NOTES] | Paste verified accomplishments, projects, challenges, outcomes, and career history. | At BeaconHR, led payroll analytics launch; 1,200 demo requests in Q1. Interviewed 18 customers for messaging. Built sales battlecard with account executives. Earlier content marketing role at LumenDesk. |
| [INTERVIEW CONTEXT] | Add interviewer names or roles, timing, known topics, and any concerns you have. | Hiring manager is the VP of Marketing. Recruiter said launch leadership and cross-functional work will be discussed. Interview is next Tuesday. |
How to use
- Paste your work notes in enough detail to distinguish your personal actions from your team's work.
- Name the interview format and interviewer role; a recruiter screen requires different preparation than a case or technical panel.
- Practice answers aloud with a timer, then replace vague phrases with the decision, trade-off, or result you can verify.
- Follow up with: “Act as the VP of Marketing and ask the 10 toughest questions one at a time; wait for my answer and critique it.”
Variations
Behavioral interview
Use when the interview emphasizes leadership, collaboration, and past behavior.
Create a behavioral interview practice set for [ROLE] using [EXPERIENCE NOTES] and [JOB POSTING]. Select six stories that demonstrate the role’s core competencies, including one failure, one conflict, one ambiguous decision, and one measurable win only if supported. Output STAR outlines, likely follow-up questions, and 90-second spoken-answer versions. Mark missing details rather than inventing them. Check that every Action describes my contribution and every Result has a stated basis.
Technical interview
Use for a technical screen or system-design discussion.
Prepare me for a [TECHNICAL INTERVIEW TYPE] for [ROLE] using [JOB POSTING], [TECHNICAL BACKGROUND], and [INTERVIEW DETAILS]. Create a prioritized study map, 12 likely questions, and answer frameworks that state assumptions, trade-offs, failure modes, and validation steps. Include only technologies and claims supported by my background. Output a 60-minute mock interview agenda. Check that no model answer claims production experience I have not supplied.
Salary conversation
Use before discussing compensation after the employer shows interest.
Help me prepare for a compensation conversation for [ROLE] at [COMPANY] using [OFFER OR RANGE], [MY PRIORITIES], and [MARKET EVIDENCE]. Draft a short opening, responses to three common pushbacks, and questions about base pay, bonus, equity, benefits, review timing, and level. Separate facts from preferences and do not present market estimates as verified without sources. Check that the draft makes no commitment to accept or decline.
Tips
- Prepare stories around decisions and trade-offs, not just successful projects; interviewers often use follow-ups to find out what you personally did.
- For a 45-minute interview, have five adaptable stories rather than memorizing separate scripts for every possible question.
- Use the job posting to predict questions, but research the interviewer and company separately before repeating claims about their strategy or culture.
- When you do not know an answer, use a structured response: clarify the goal, state an assumption, explain how you would investigate, and name the trade-off.
FAQ
Should I memorize the model answers?
No. Memorize the facts, sequence, and takeaway of each story. Scripted wording tends to collapse when an interviewer asks a follow-up.
How many STAR stories do I need?
Five to seven versatile stories are usually enough if each can demonstrate more than one capability. Include a setback and a conflict, not only wins.
Can AI conduct a mock interview?
Yes. Ask it to use the posting, question you one at a time, challenge vague answers, and avoid supplying facts that are not in your notes.