Help me prepare truthful, role-specific answers for an interview. Role and company: [ROLE AND COMPANY] Job requirements: [JOB DESCRIPTION] My relevant experience: [EXPERIENCE NOTES] Likely interview questions: [LIKELY QUESTIONS] My goals or concerns: [INTERVIEW GOALS] First, identify the 5–7 requirements or signals the interviewer is most likely testing, separating must-have skills from preferences. Then write answers for each likely question.
For behavioral questions, use a natural STAR structure: briefly set the context, state my specific responsibility, explain the actions I personally took, and give a measurable or observable result. Keep the situation and task short; spend most of the answer on judgment, tradeoffs, collaboration, and outcome. For motivation questions, connect my actual experience and interests to this role without claiming I am passionate about things not supported by my notes. For technical or case-style questions, explain the reasoning process, assumptions, and how I would validate an answer. Output: 1. A table with the question, the skill being assessed, and the strongest evidence from my notes. 2. A spoken answer for each question, 90–150 seconds when read aloud. 3. Two concise follow-up details I can use if asked to go deeper. 4. A short list of questions I should ask the interviewer that relate to the team’s work. Do not invent achievements, metrics, tools, employers, or responsibilities. Before answering, check that every factual claim comes from my notes and flag weak answers that lack a concrete action or result. Ask up to 3 clarifying questions only if a required input is missing.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [ROLE AND COMPANY] | Enter the job title, employer, team if known, and interview stage. | Customer Success Manager at Acme Analytics, second-round interview with the VP of Customer Success. |
| [JOB DESCRIPTION] | Paste the relevant responsibilities and qualifications from the posting. | Own a portfolio of mid-market SaaS customers, lead renewals, reduce churn, and partner with product on customer feedback. |
| [EXPERIENCE NOTES] | List your relevant roles, projects, actions, results, tools, and examples. | At Northstar HR, managed 42 accounts worth $1.8M ARR; built a renewal-risk tracker; raised renewal rate from 84% to 91%; led monthly product feedback calls. |
| [LIKELY QUESTIONS] | Paste questions from the recruiter or list questions you expect. | Tell me about a difficult renewal; how do you prioritize a large book of business; why this company? |
| [INTERVIEW GOALS] | State what you want to emphasize and any areas you are worried about. | Show I can work strategically with data, while being honest that I have not managed enterprise accounts. |
How to use
- Paste the job description and use bullet points for your real examples, including results you can defend.
- Read each answer aloud and replace wording you would not naturally say.
- Confirm every number, title, and outcome before practicing it.
- Follow up with: “Make the answer to question 2 more conversational and keep it to 75 seconds without losing the result.”
Variations
Panel interview
Use this when several interviewers will assess different parts of the role.
Prepare a panel-interview answer map for [ROLE], based only on [EXPERIENCE NOTES] and [JOB DESCRIPTION]. Group likely questions by interviewer perspective: hiring manager, cross-functional partner, and executive. For each, write a 60–90 second answer with one concrete example, the decision I made, and the result. Include a one-sentence bridge when a question falls outside my direct experience. Do not invent facts. Flag any requirement with no supporting example.
Technical interview
Use this when you need to explain a technical decision or system design clearly.
Help me answer technical interview questions for [ROLE] using my actual background in [TECHNICAL EXPERIENCE]. Based on [JOB DESCRIPTION], create five likely questions. For each, give a structured answer that states assumptions, constraints, approach, tradeoffs, validation, and operational risks. Keep examples truthful and distinguish what I built from what my team built. End with questions I should ask about the company’s architecture or engineering practices.
Career-change answers
Use this when your past work does not match the target role exactly.
Draft interview answers for my move from [CURRENT FIELD] to [TARGET ROLE]. Use only [TRANSFERABLE EXPERIENCE] and [JOB DESCRIPTION]. Explain the transition through demonstrated skills, not vague enthusiasm. Write answers to “Why this change?”, “Why should we hire you without direct experience?”, and “What will you need to learn?” Include a credible 30-60-90 day learning plan, but do not promise outcomes I cannot control. Flag gaps that need a direct, honest answer.
Tips
- Prepare one example each for a success, a setback, a conflict, a prioritization decision, and an improvement you initiated; interviewers often test these separately.
- Use “I” for your actions and “we” only when describing the team context, so your contribution remains clear.
- A result can be a retained customer, reduced turnaround time, adoption change, decision made, or lesson applied later; do not force a metric that did not exist.
- Keep a one-line version of every story as a memory cue, then practice expanding it without memorizing a script.
FAQ
Should I use AI-written answers word for word?
No. Use them as a structured practice draft, then rewrite phrases that do not match how you speak. Memorized wording often sounds less credible in follow-up questions.
What if I do not have a strong example for a question?
Use a smaller but real example, explain the constraint, and describe what you learned. Do not invent a larger project or result.
How long should an interview answer be?
Most behavioral answers work in 90–150 seconds, with a shorter version ready for fast-paced screens.