Seven fixes for generic AI answers
- Give it your résumé and the job description before you ask anything.
- Write five real stories in rough notes: the situation, what you did, the result with a real number.
- Ask for talking points, not paragraphs.
- Replace every round number with the real one, or remove it.
- Add one thing that went wrong and what you changed.
- Name the tools, teams and constraints that were actually involved.
- Rehearse out loud until the wording is yours.
The five tells of a generic answer
- Round numbers. “Improved performance by 30%” with no baseline or method. Real results are messier: “p95 went from 900 ms to 340 ms after we moved the lookup into Redis.”
- No proper nouns. Real projects involve named systems, teams and vendors.
- No cost. Every real decision gave something up. Answers with only upside sound rehearsed.
- Instant resolution. Conflicts that end after one honest conversation are rare in life and common in AI drafts.
- Corporate vocabulary. “Leveraged cross-functional synergies” is a sign nobody has said this sentence out loud.
Why models default to the average answer
A language model predicts likely text. Asked “tell me about a time you handled conflict” with no other information, the likeliest text is a blend of the thousands of example answers it has read — which is precisely what an interviewer has heard many times before. The model is not being lazy; it simply has no evidence about you. Supplying that evidence changes what “likely” means, which is why context matters more than prompt wording. See how AI uses your résumé and job description.
Before and after
| Generic draft | Specific version |
|---|---|
| I led a team to improve system performance by 30%. | Our checkout API's p95 was 900 ms. I profiled it, found a per-request config lookup, cached it in Redis, and got p95 to 340 ms in two sprints. |
| I resolved a conflict through open communication. | The data team wanted a nightly batch; we needed hourly. I proposed a two-week hourly trial with an agreed cost cap, and we kept it after the bill came in 12% over. |
| I am passionate about your mission. | I've used your API for two years at my current job; the rate-limit headers are why I picked you over the alternative. |
Turning a draft into something you can say
Paragraphs are hard to say naturally; they invite reading aloud, which interviewers notice immediately. Talking points — three or four short phrases in order — let you speak in your normal rhythm while keeping the structure. Practise each story until you can tell it from the bullet points alone, and expect at least one follow-up per story. Our guide to using AI answers in your own words has a practice routine, and customising AI answers covers settings that change tone and length.
Prompts that produce less generic drafts
Inputs matter more than wording, but a few instructions reliably help once your material is loaded. Ask the model to use only facts from your résumé and stories, and to mark anything it had to assume with brackets so you can spot it. Ask for one concrete number per answer drawn from your notes, and for the trade-off or cost of the decision. Ask for the answer in four bullet points of under twelve words each, which forces specificity and keeps it speakable. Finally, ask what follow-up question an interviewer would most likely ask next — then answer that one yourself.
- “Use only the facts in my résumé and notes; put anything assumed in [brackets].”
- “Include the real metric from my notes and what it was before.”
- “Name one thing that went wrong or one trade-off.”
- “Four bullet points, under twelve words each.”
- “What is the most likely follow-up question?”
When generic is fine
Not every answer needs a story. Definitions, standard technical explanations and process questions can be textbook-shaped without harm, as long as they are correct and you understand them. Save your effort for the questions where evidence matters: behavioural questions, “why us”, and anything about your judgement.
Where CoPilot Interview fits
CoPilot Interview is a free AI interview assistant that builds answers from the résumé and job description you load, returns them as talking points, and runs mock interviews that score your own delivery — so you can see which answers still sound generic before an interviewer does.
Disclosure: CoPilot Interview is our product, so weigh what we say about it accordingly. Everything else on this page applies whichever tool you use, or none.
Frequently asked questions
Why do AI interview answers sound fake?
Because without your résumé and real stories the model blends the most common example answers it has seen. The result has round numbers, no names and no trade-offs — the same signals interviewers use to spot rehearsed answers.
How do I make AI answers sound like me?
Give the AI your résumé, the job description and a few real stories, ask for talking points instead of paragraphs, replace any invented numbers with real ones, and rehearse out loud until the wording is your own.
Should I memorise AI-written interview answers?
No. Memorised paragraphs sound read, and they fall apart at the first follow-up. Memorise the structure and the facts of each story, then tell it naturally.
What is the biggest giveaway of an AI-written answer?
Specific-sounding numbers with no baseline or method, and answers where every decision had only upside. Real experience includes costs, constraints and something that went wrong.
See the listening loop for yourself
CoPilot Interview is a free desktop app for Windows and macOS: live captions, a structured answer in about 2 seconds, and AI mock interviews built from your résumé.
Try a practice question