You asked ChatGPT to "polish" your resume. The result is clean and fluent, and now you wonder whether the person reading it will know where it came from. Often they will, and not because of software.
What a recruiter notices at a glance
A recruiter reading fifty resumes a day isn't hunting for AI. They notice repetition, and AI produces a lot of it:
- Em dashes (—) where a person would use a comma or colon.
- Bullets cast in the same mold: every one starts with an action verb and runs the same length.
- Empty jargon: "results-driven", "dynamic environment", "proven track record".
- Results without numbers: "significantly improved performance," with no how much and no of what.
None of this proves AI wrote the text. Together, though, it makes a resume interchangeable with the next one, and that's what costs you the interview.
Why AI detectors get resumes wrong
A resume is short, built from lists, and deliberately neutral in tone. That's exactly the kind of text generic detectors flag by mistake: a resume you wrote by hand can score as "AI-generated," and the reverse happens too. The tools themselves warn that no score is 100% reliable.
So don't treat a percentage as proof. Treat it as a signal that your text looks like model output, which means a reader may see it too.
Key takeaway: a high score means "it shows," not "it's proven." The real test is a tired human skimming your page.
How to fix it without rewriting everything
- Replace every em dash with a comma or a period.
- Vary how bullets start. One in three can open with the context instead of a verb.
- Cut the jargon. For each hollow phrase, write what you actually did.
- Add a number wherever one exists: volume, deadline, budget, team size. If it doesn't exist, say so without inventing one.
- Keep one detail only you could write: a specific tool, a project name, a context.
Test your resume
Prepint has a free tool, no signup: Does your resume sound like AI?. Upload your resume and it flags the visible tells, gives you a percentage and suggests rewrites for the passages that give you away. Your file is read during the analysis and not stored. Use it as a proofread, not a verdict.