Interview answers from your real experience
STAR answers built from what you actually did, with the follow-ups you will be asked. Written for Claude, free to copy, with every placeholder explained below.
The prompt
<role>
You prepare interview answers from a candidate's real experience. You never invent
achievements.
</role>
<context>
Role applied for: {{role}}
Job description highlights: {{jd_highlights}}
My experience: {{experience}}
Where I am weakest: {{weak_areas}}
</context>
<task>
Prepare answers for the questions most likely to be asked.
</task>
<constraints>
- Use only my stated experience. If I have no example for a likely question, say so
and suggest what I could draw on instead.
- Structure each answer as situation, task, action, result — but written as speech,
not labelled.
- Under 90 seconds spoken, which is roughly 200 words.
- For each answer, give the two follow-up questions an interviewer would ask next.
- For weak areas, give an honest answer that does not pretend the gap is a strength.
</constraints>
Now prepare the answers.Open this in the prompt builder to adapt it, score it, and re-render it for a different model.
What to replace
| Placeholder | What to put there |
|---|---|
| {{role}} | The role. |
| {{jd_highlights}} | Key requirements from the advert. |
| {{experience}} | Your real examples, in rough notes. |
| {{weak_areas}} | Where you genuinely lack experience. |
Why this prompt works
- Follow-up questions included
- Interviews are lost on the second question, not the first. Preparing the follow-up is what turns a rehearsed answer into a conversation.
- Honest weak-area answers
- The "my weakness is perfectionism" answer is transparent. Requesting honesty produces something an interviewer can respect.
- Spoken-length cap
- Written answers run long. 200 words is roughly 90 seconds, which is the practical limit before an interviewer disengages.
More prompts
- CV bullet points from your responsibilities — Achievement-shaped bullets built only from things you actually did.
- Blog post from an outline — Turn a rough outline into a full draft that keeps your structure and does not pad.
- Rewrite for clarity without changing meaning — Tighten prose while keeping the author's voice and every factual claim intact.
- Summarise a document without distorting it — A summary that separates what the source says from what it implies.
- Code review for correctness only — Findings with a triggering input, ranked by severity — and permission to find nothing.
- Debug from an error and stack trace — Ranked hypotheses with a test for each, instead of one confident guess.
Browse the full prompt library, all career & job search prompts, or read the guides.