Why Your AI Writing Sounds AI-Written — and How to Fix It
Recruiters flag it, clients feel it, colleagues quietly discount it. Here's why AI writing defaults to generic — and the prompt techniques that fix it: voice anchoring, specificity injection, banned-phrase lists, and a two-pass edit, with before/after examples.
TL;DR. AI writing sounds AI-written because the model's default output is the average of its training data — and everyone else using the same prompt gets the same average. Readers have learned the tells: the rhythm, the stock phrases, the suspicious absence of specifics. The fix is four moves: anchor your voice with samples of your real writing, inject specifics the model can't invent, ban the clichés explicitly, and edit in two passes — one for facts, one for voice. AI for assembly; you for everything that makes it yours.
The rejection is rarely announced. A recruiter skims your cover letter, catches "I am excited to leverage my passion for driving impactful results," and moves to the next candidate. A client reads your email, feels vaguely like they received a template, and replies a little more coldly than usual. Nobody says "this was AI." They just trust the document a bit less — and you a bit less with it.
This is now measurable. A March 2026 Robert Half survey found 67% of HR leaders say AI-generated applications are actively slowing their hiring — not because candidates use AI, but because so many applications now read identically. And it's not just hiring: the Stanford–BetterUp "workslop" research found that when colleagues receive AI-generated work that looks polished but says nothing, 42% view the sender as less trustworthy afterward. Generic AI writing carries a reputational tax whether it's a resume, a marketing email, or a status update.
Here's the good news: the problem isn't AI. It's the default settings of AI — and defaults can be overridden.
Why the default output is generic
A language model predicts the most probable next words given your prompt. Feed it a thin prompt — "write a cover letter for a marketing manager role" — and the most probable output is the statistical center of every marketing cover letter it has ever seen. That center is smooth, positive, structurally correct, and utterly interchangeable. The model isn't failing; it's answering the question you actually asked, which was "what does the average version of this document look like?"
Thin prompt in, average out. Every fix below is a way of asking a less average question.
The tells readers have learned
Before the fixes, know what you're fixing. Experienced readers now pattern-match on:
- Stock phrases: "in today's fast-paced world," "I'm excited to leverage," "seamlessly," "delve into," "unlock the full potential," "it's important to note," "game-changer."
- The uniform rhythm: every paragraph three sentences, every list three items, every sentence medium-length and medium-enthusiastic. Human writing is lumpier.
- Praise without evidence: "proven track record of driving results" (which results?), "passionate about innovative solutions" (name one).
- Hedged symmetry: "While X has advantages, it's important to consider Y" — the model's way of never committing to a point.
- The missing fingerprint: nothing in the text that could only have been written by you, about this recipient, on this occasion. This is the master tell; all the others are symptoms.
Fix 1 — Anchor the voice with your own writing
The model can't sound like you if it's never seen you. So show it — before it writes a word:
Below are three emails I've actually sent [or: two paragraphs from my old resume / a post I wrote]. Study the voice: sentence length, formality, how I open and close, words I favor and avoid. Write the following document in that voice, not your default one. Voice samples: [paste]
Two or three genuine samples are enough to shift the output dramatically — sentence rhythm, warmth, directness all move toward yours. Keep a "voice file" of 3–4 representative samples and paste it at the top of any writing prompt. (Sanitize client names and confidential details first; and if the samples are old, pick ones that still sound like the way you want to sound.)
Before (no anchor): "I hope this email finds you well. I wanted to reach out regarding the upcoming project deadline and ensure we are aligned on deliverables."
After (anchored to a direct, warm sender): "Quick one before Thursday — I want to make sure we're saying the same thing to the board about the timeline. Two things I need from you by Wednesday noon:"
Same message. Only one of them sounds like a person the recipient knows.
Fix 2 — Inject specificity the model can't invent
The model doesn't know your numbers, your clients, or what happened last Tuesday — so left alone, it writes around the gaps with abstractions. That's where "proven track record of driving results" comes from. The cure is to load the specifics into the prompt:
- Resume bullet, before: "Responsible for managing social media accounts and increasing engagement through innovative content strategies."
- What you tell the AI: "Grew the company Instagram from 3,200 to 19,000 followers in 14 months; a UGC campaign in March produced our best-ever month of inbound demo requests (62); I run a 2-person content team on a $4K/month budget."
- After: "Grew Instagram from 3,200 to 19,000 followers in 14 months; March UGC campaign drove a record 62 inbound demo requests — on a $4K/month budget with a team of two."
Notice the AI's actual job shrank to compression and rhythm. That's the right division of labor: you supply what happened; AI supplies the sentence. A useful rule — five minutes listing raw specifics before you prompt beats thirty minutes of regenerating vague output. This is the same principle behind our consultant-focused deep dive, why your AI-generated SWOTs sound like every other consultant's: the priors and particulars are the work; AI accelerates the writing layer around them.
And a warning that belongs in every specificity discussion: never let the model fill a gap you left. If you don't supply the number, it may invent one — confidently. That's not a voice problem, it's a hallucination problem, and in a resume or client deliverable it's disqualifying.
Fix 3 — Ban the clichés explicitly
Models respond well to negative constraints. Add a standing block to your prompts:
Banned: "leverage," "seamless(ly)," "delve," "robust," "innovative," "passionate," "excited to," "in today's [anything] world/landscape," "game-changer," "unlock," "elevate," "it's important to note," "I hope this finds you well." Also banned: starting consecutive sentences the same way, three-item lists of adjectives ("fast, reliable, and scalable"), and any sentence that praises without a concrete example. If a banned pattern is genuinely necessary, rewrite the sentence so it isn't.
Build your own list over time — every time you catch a phrase that makes you wince, add it. The list does double duty: it blocks the worst output and trains your own eye for the next fix.
Fix 4 — Edit in two passes (and write two lines yourself)
No prompt eliminates the need to edit; the goal of Fixes 1–3 is to make the edit short. Do it in two passes so each read has one job:
- Facts pass. Verify every name, number, date, and claim against reality. (Our 5-point AI output checklist is the fuller version of this pass.)
- Voice pass. Read it aloud — the fastest AI-detector available. Anything you'd never say, rewrite in the words you'd actually use. Cut any sentence that could survive, unchanged, in someone else's document; if it isn't specific to you and this reader, it's filler.
Then the highest-leverage 60 seconds in this entire guide: write the first and last lines yourself. Openings and closings are where AI is at its most formulaic and where the reader's judgment forms. A human first line buys goodwill for everything that follows.
The final test for any document, any profession: could this exact text have been sent by someone else, to someone else? If yes, it's not done.
What this doesn't fix
Honest limits. If the underlying content is thin — no results worth citing on the resume, no real point in the email — no prompt technique will conceal that, and AI's fluency may even highlight it. These fixes also take more effort than one-shot generation; that's the deal, and it's still far faster than writing from scratch. And detection asymmetry cuts both ways: some readers will suspect AI even in fully human writing, so the goal isn't passing a detector — it's writing that's specific and useful enough that the question stops mattering. Finally, if you find heavy AI editing more tiring than expected, that's a real documented cost — see why AI makes you more productive and more tired for the workflow patterns that keep it sustainable.
The one-line summary: AI's default voice belongs to everyone, which means it belongs to no one. Feed it your voice, your facts, and your standards — then edit until the fingerprint is yours.
Sources
- Robert Half: 67% of HR leaders report AI-generated applications are slowing hiring (March 2026)
- Forbes: AI Resumes Are Sabotaging The Hiring Process, 67% Of Managers Reveal
- Harvard Business Review: AI-Generated "Workslop" Is Destroying Productivity (BetterUp Labs × Stanford Social Media Lab, September 2025)
See Claude set up for your job
Skip the theory — pick your profession and get the real workflows, ready-to-use prompts, and exact setup for your work.
See Claude set up for your job
Real workflows and ready-to-use prompts, profession by profession.
Frequently asked questions
Why does AI writing sound generic?+
Because a language model's default output is the statistical average of how millions of people write about your topic. Unless you give it your voice, your specifics, and your constraints, it produces the most probable phrasing — which is, by definition, the phrasing everyone else gets too. Generic output isn't a malfunction; it's the default you haven't overridden.
Can recruiters and clients actually tell when something is AI-written?+
They can tell when it's generically AI-written. A March 2026 Robert Half survey found 67% of HR leaders say AI-generated applications are slowing their hiring because so many read alike. What gets flagged isn't AI use itself — it's the absence of specifics: no numbers, no named projects, no detail that couldn't have come from anyone else's prompt.
What are the fastest fixes for AI-sounding text?+
Four moves: anchor the voice by pasting 2–3 samples of your own writing and asking AI to match them; inject specifics (names, numbers, dates, constraints) into the prompt before generating; give it a banned-phrase list of AI clichés to avoid; and run an editing pass where you rewrite the first and last lines yourself and cut every sentence that could appear in anyone else's document.
Should I stop using AI for writing altogether?+
No — the evidence points at generic use, not AI use. AI is genuinely good at structure, first drafts, and tightening. The failure mode is shipping the default output. Supply the voice and the specifics yourself, use AI for the assembly, and edit the result until it passes one test: could this exact text have been written about anyone else? If yes, keep editing.
Related Guides
AI Cost Allocation Template for Teams and Products
A copy-paste AI cost allocation template for FinOps teams: required fields, direct versus shared spend, showback versus chargeback, a worked example, and monthly-close checks.
AI Subscription Audit: Find Unused and Overlapping Tools
A practical AI subscription-audit process for IT, procurement, finance, and FinOps teams: inventory vendors, collect rosters and usage, assign owners, find overlap, manage renewals, and protect valuable power users.
How to Calculate Cost per Successful AI Task
A practical method for calculating cost per successful AI task, including retries, tools, infrastructure, human review, quality guardrails, and before/after optimization tests.