Recruiters can spot an AI-written resume on sight. Not because the AI was bad. Because the patterns are now famous.
“Results-driven professional with proven expertise in driving impactful outcomes.” Skim. “Spearheaded cross-functional initiatives leveraging strategic insights.” Skim. The brain learns the shape and starts pattern-matching past it the way you skip ad copy.
That doesn’t mean the answer is “stop using AI.” A first draft from ChatGPT or Claude is genuinely faster than staring at a blinking cursor. The answer is to know the three specific failure modes those tools produce, recognize them on your own page, and finish the job yourself.
These are the three.
Failure mode #1: Verb inflation
AI was trained on a lot of resumes. The ones that ranked highest in its training data, the ones it now imitates, were full of upgraded verbs. “Helped” became “spearheaded.” “Worked on” became “orchestrated.” “Built” became “architected.” Stack these and the page starts to sound like a press release for a movie that doesn’t exist.
The recruiter’s brain has a filter for this. After enough resumes, “spearheaded” stops registering as evidence and starts registering as filler, the same way “synergy” did fifteen years ago. The verb that was supposed to elevate you flattens you. We catalogued the worst offenders in 7 AI-Written Resume Phrases Recruiters Auto-Reject.
Before (AI):
Spearheaded cross-functional initiatives to optimize operational workflows, driving substantial improvements in team velocity.
After (human-finished):
Cut the deploy pipeline from 40 minutes to 8 by replacing the legacy CI runner. Three squads moved off Jenkins.
What changed: a real verb (cut), a real number (40 → 8), a real thing (CI runner), a real outcome (three squads moved). Nothing sounds heroic. It doesn’t have to. The numbers do the work.
The fix: open your resume, find every verb that sounds like a promotion announcement (spearheaded, orchestrated, championed, propelled, drove transformative) and replace it with the verb you’d use telling the story to a friend at dinner. Built. Cut. Shipped. Wrote. Fixed. Killed. If the friend would laugh at “spearheaded,” the recruiter will skim past it.
Failure mode #2: Metric fabrication
AI loves numbers. Because resumes-that-rank-well have numbers in them, an LLM rewriting your bullet will reach for one whether or not the actual data exists. So you end up with statements like “increased team productivity by 30%” or “reduced costs by 22%” that don’t trace back to anything. Including, often, anything you actually did.
A recruiter who interviews you will catch this with one follow-up question. “Tell me about that 30% productivity increase. How did you measure it?” If the answer is silence or “…it was kind of a vibe,” the entire resume’s credibility collapses. Worse: a recruiter who’s seen this trick before will assume every other number on the page is also fake, even the ones that aren’t.
Before (AI):
Streamlined onboarding workflow, reducing new-hire ramp time by 40% and increasing engineer satisfaction by 25%.
After (human-finished):
Rewrote the engineer onboarding doc and replaced the setup checklist with a one-command script. Our last four hires shipped their first PR on day 3. Before that it took two weeks.
What changed: a metric you can walk someone through replaced a metric that only sounds impressive. Every piece of this is checkable and you can talk about all of it: what the doc said, what the script does, which four hires, what used to go wrong in week one. “40% reduction” gives an interviewer nothing to ask about except where the number came from.
The fix: for every percentage on your resume, ask: if a hiring manager asked me to defend this number on a phone screen, could I? If the answer is yes, keep it. Recruiters screen for numbers, and quantified impact does more work on your page than almost anything else. If the answer is no, don’t delete the achievement. Make the number defensible instead: trace it to a real source, or swap it for the concrete artifact you can point at (the doc, the script, the dashboard, the day count). Specifics beat statistics only when you can’t source the statistics.
Failure mode #3: Paragraph-shaped bullets
Resumes use bullets because the recruiter’s eye is doing pattern-matching, not reading. A bullet should read in under two seconds. AI, trained on prose, defaults to long sentences with subordinate clauses, and produces bullets that are paragraphs in disguise: three lines of text that make the eye slow down precisely when you need it to skim and decide.
The eye that slows down doesn’t slow down to appreciate. It slows down to bail. Long bullets register as “this person doesn’t know how to be concise.” Which is the opposite of the impression you wanted.
Before (AI):
Led a team of seven engineers across three time zones in the design and implementation of a new microservices-based payments platform, collaborating closely with product and design partners to ensure alignment with company OKRs while delivering on aggressive quarterly milestones.
After (human-finished):
Led seven engineers across three time zones building the new payments platform. Shipped the first revenue-generating service one quarter early.
What changed: same scope, half the words. The recruiter still gets the size signal (seven engineers, three time zones), still gets the impact signal (revenue, ahead of schedule), and the bullet now reads in two seconds instead of seven.
The fix: for every bullet over two lines, ask what the one thing the bullet is actually telling the recruiter is. Cut everything else. If you genuinely have two stories worth telling about that role, they’re two bullets, not one paragraph.
Where AI helps, and where it needs you
None of this is an argument against using AI on your resume. We build an AI resume tool, and we’d make the same argument about ours: a language model is very good at producing shape, structure and phrasing, and it has no way of knowing which of your accomplishments actually mattered. That’s not a flaw to route around, it’s just the division of labour. The model drafts. You decide what’s true and what’s worth saying.
So the useful question isn’t “AI or no AI.” It’s which half of the work you’re handing over.
What AI does well:
- Generating the first version of a bullet you can’t start. Staring at a blank field for “what did I do at this job” is the worst part of resume writing. AI gives you something to react to. The trick is treating its output as a draft, not a finish. Overwrite half of every line.
- Finding bullets that don’t pull weight. Paste your resume into any LLM and ask “which of these bullets are interchangeable with a generic candidate’s resume?” You’ll get a useful list. Half of it will be wrong; the half that’s right will be obvious in retrospect.
- Tightening verbs and phrasing on a sentence you already wrote. “Make this shorter” or “make this less corporate” are the prompts where LLMs shine, because you’ve supplied the substance and the model is only adjusting the wrapper.
- Tailoring to a job description. AI is good at scanning a JD, finding the keywords and phrasing the role uses, and surfacing where your existing bullets do or don’t echo that language. This is closer to copy-edit than rewrite, which is where AI is most useful.
What you have to bring:
- The accomplishments themselves. Ask a model to invent one and it will. Don’t ask. A number you can’t source will come up in the interview, and you won’t have a good answer.
- The context only you have. AI doesn’t know whether your “team of seven” was a tight strike force or a herd-cats nightmare. It will pick the more flattering framing every time, even when the unflattering one is the more interesting story.
- Your voice. Left to its own defaults, a model writes in a flattened, pleasant register, which is fine but generic. If your own writing is sharper or more specific, that’s the version worth keeping. A resume that reads like everyone else’s won’t hurt you, it just won’t stand out, and standing out is the entire job.
The mental model that works: AI produces clay, you produce shape. If you ship the clay, the recruiter notices the clay. If you reshape it, even quickly, they notice the shape.
This is also what shifted going into 2026. AI-speak on a resume used to read as laziness. Now it reads as a preview of how you’ll write once you’re hired, through the Slack messages and the customer emails and the design doc. What’s being screened for is whether you can tell when the model is wrong and override it.
A small thing about AI dashes
One side note. Recent LLMs love the em-dash — like this — to set off clauses. It’s grammatically fine. It’s also become a tell. When recruiters see three em-dashes on a resume that was clearly never going to use them in a printed cover letter, they index it as “AI-written, lightly edited.” Doesn’t kill you on its own. Worth knowing.
If you wrote your resume yourself and you genuinely use em-dashes in your own writing, ignore this. If you didn’t, two seconds with find-and-replace turns most of them into commas or periods without changing the meaning.
How to run the three checks
- Verb pass. Skim your bullets and circle any verb that sounds like a movie trailer. Replace each with the verb you’d use telling the story to a friend.
- Metric pass. For every number on the page, decide if you can defend it on a phone screen. Keep the ones you can. Source or replace the ones you can’t, using the concrete artifact instead (the doc, the script, the day count).
- Bullet length pass. Any bullet over two lines either gets cut to one or split into two. No paragraphs disguised as bullets.
You’ll cut words on every one of those passes, and the page will look thinner. That’s not a bug. The recruiter has about six seconds to read it, and thinner reads faster. Faster reads further. Further means more of your resume gets seen.
What we do differently
The reason we built Resumes Coach is that the three failure modes above (verb inflation, metric fabrication, paragraph bullets) are exactly what generic AI rewrites produce by default. Ours is tuned against all three. It suggests concrete action verbs instead of promotion-announcement verbs. It caps every bullet at one or two lines. And it will not put a number in a bullet that your own text doesn’t support: when there’s no real metric to work from, it hands back a version without one rather than inventing something you’d have to defend later.
It still can’t tell you which of your accomplishments mattered most. Nothing can. That part stays yours.
Try the free resume score: it scans your resume for these exact patterns in seconds. However you get there, the test is the same. Not “does it sound smart,” but “would a friend recognize you in this paragraph?” If yes, ship it.