← Paws & Reflect
Illustration of a young girl in a headscarf looking up at a tall, friendly-looking robot with big round eyes on a city street
TIPS & TRICKSAugust 19, 2026

How to Tailor Your Resume Using AI (Without Looking Fake)

49% of hiring managers now dismiss a resume the moment they flag it as AI-written. 78% of people who used ChatGPT on theirs got an interview anyway. Both numbers are true at the same time.

I’m not the person who tells you to close the laptop and write it longhand. I code my own prototypes with Claude most weeks.

AI is not the problem here. The problem is treating it like a vending machine: drop in a job description, pull out a finished resume, submit it without a second look.

That instinct is spreading fast. iHire’s 2025 State of Online Recruiting survey found 29.3% of job seekers had used AI to write or customize a resume or cover letter in the past year, up from 17.3% just one year before. Nearly a third of everyone applying right now is running some version of the same prompt against the same job postings, which is exactly why so many resumes are starting to sound identical.

Here’s where those two numbers come from. Back in 2023, ResumeBuilder.com surveyed people who’d used ChatGPT on their application materials and found 78% got an interview and 59% got hired, numbers good enough that 88% said they’d keep doing it.

The 49% comes from a more recent Resume.io analysis of 3,000 hiring managers, the ones who now automatically dismiss a resume the moment they flag it as AI-written.

AI-assisted resumes can work, and AI-detected resumes can get you rejected on sight. The difference isn’t whether you used the tool. It’s whether the result still sounds like a specific person did the work.

The 3-step version, if you’re mid-application right now
01
Feed it your real bullets and the job post together.Find the overlap, don’t invent it
02
Rewrite whatever it hands back in your own sentence structure and your own numbers.Too smooth usually means too generic
03
Read it out loud, then run it through a free ATS checker before you send it.Tone and formatting, checked separately

That’s the whole workflow. Everything below is why each step matters, starting with what actually tips a recruiter off.

What actually gives an AI-tailored resume away

Recruiters aren’t guessing. Laurie Chamberlin, who heads LHH Recruitment Solutions, has said flatly that a good recruiter can spot an AI-written application from a mile away. Bonnie Dilber, a recruiter at Zapier, puts the number at roughly a quarter of everything landing in her inbox, and describes the tell the same way most recruiters do: it sounds robotic, and it’s thin on the specifics that would actually prove someone can do the job.

BuzzwordWhy it reads as filler
”Proven track record of success”Proven where, doing what, over how long. The sentence never says.
”Leveraged cross-functional synergies”A phrase pattern-matched from job postings, not pulled from anything you actually did.
”Strategic thinker who thrives in fast-paced environments”A trait, not a task. Nothing here a hiring manager can point to.
”Extensive experience driving key initiatives”Which initiatives, how many years, what changed. All three go unanswered.

Buzzwords standing in for evidence are the easiest tell to catch. “Results-driven,” “team player,” “detail-oriented self-starter”: phrases so generic they’d fit any candidate for any role. If a sentence could survive getting pasted into a competitor’s resume unchanged, it isn’t saying anything about you.

Tone is the subtler one. AI output tends to drift between formal, “cut turnaround time across the team,” and generically upbeat, “delivered measurable results,” within the same document, because it’s pattern-matching phrasing section by section instead of speaking in one consistent voice. A resume one person actually wrote reads like one person actually wrote it, start to finish.

What costs the most trust, though, is the resume that looks identical from one posting to the next. When the same generic draft, tools reshuffled to match whatever’s in the listing, goes out to a dozen unrelated roles, it reads as mass-produced instead of considered. Recruiters who see volume all day catch that pattern fast, and once they catch it, they read the rest of the page more skeptically too.

None of that means skip AI. It means make sure you’re the last set of eyes on the page.

The line between tailoring and lying

Harvard’s Mignone Center for Career Success has some of the clearest guidance I’ve seen on this, and it matches what I’d tell anyone I was screening: generative AI shouldn’t be the primary author, not least because its output tends to be generic by default. Their advice is to use whatever it generates as a suggested edit, not a final draft, adjust the language until it’s an accurate depiction of what you actually did, read the result aloud to catch anything that doesn’t sound like you, and make sure you can speak to every line if an interviewer asks about it.

That last one is the real test. If a bullet describes a metric, a tool, or a scope you can’t explain in your own words in an interview, it doesn’t belong on the page, whether AI wrote it or you did. This is the same logic behind how I tell people to structure a resume in the first place: specificity is what a recruiter and a parser both key off, and a sentence you can’t defend under a follow-up question was never really specific to begin with.

It’s also worth knowing the tool cuts both ways. I’ve written about what a University of Washington study found when researchers ran millions of resumes through AI screening systems: the screening side of AI is inconsistent and, in that study, measurably biased by name alone.

Knowing that, the instinct to fight AI screening with AI-stuffed keywords makes sense on paper. In practice it just stacks one unreliable system’s guesswork on top of another’s, and it’s the specific failure mode Kathleen Walch, Director of AI Engagement at the Project Management Institute, has been warning about: resumes tuned to match a posting too precisely are starting to read as suspicious rather than impressive.

Her read on it is direct. Tune it too hard and you’re probably not getting the interview, because you’ve traded your actual voice for a keyword match a hiring manager has learned to distrust on sight.

A workflow that actually sounds like you

Here’s the workflow I use myself, and the one I’d hand anyone tailoring a resume with AI.

A four-step loop — generic enough to reuse for any AI-assisted writing pass

Input

Feed it your real bullets and the job post together, and ask where they already overlap.

Draft

Rewrite whatever it hands back in your own sentence structure and your own numbers.

Voice check

Read it out loud. A line that snags on the way out of your mouth trips a reader the same way.

Format check

Check the mechanics separately: layout, fonts, parsing. A formatting problem isn't a writing problem.

Steps 2 and 3 repeat. Snags on the read-aloud pass? Rewrite it again before you move on to the format check.

Start with your real bullets. Paste your actual experience and the job description into Claude or ChatGPT together, and ask it to identify where your existing background already overlaps with what the posting is asking for.

That’s a research task AI is genuinely fast at. Asking it to invent achievements from nothing is a different task, and it’s the one that gets people in trouble.

Keep your own sentence structures and your own numbers. If the tool hands you a rewrite that sounds better than anything you’d write yourself, that’s usually a sign it sounds like nobody in particular. Take the overlap it found, and write the sentence yourself.

Read it out loud before you send it, exactly as Harvard’s guidance suggests. If a line makes you wince or trips on the way out of your mouth, a recruiter is going to feel the same friction reading it silently.

Then check the mechanics separately from the writing. A resume can be honestly written and still fail for reasons that have nothing to do with tone: a two-column layout an ATS can’t parse in order, a decorative font that doesn’t extract as real text, a missing standard section header. That’s a formatting problem, not a writing one, and it’s worth running the finished draft through my free ATS resume checker before you submit it anywhere, the same way I’d tell you to start from a template that’s already built to parse cleanly instead of fighting your formatting and your wording at the same time.

Reflective Coda

The actual skill here was never prompting. It’s knowing your own experience well enough to tell a good suggestion from a generic one when the tool hands it back to you.

AI can find the overlap between your career and a job posting faster than you’d find it scrolling through your own resume at midnight. It cannot tell the truth about what you did, whether a number is real, or whether you’d be comfortable explaining a line to a stranger across a table. That part was always going to stay yours.

Use the tool for what it’s actually good at: surfacing the connections you might skim past when you’re tired and just want the application done. Then go back through every line it gave you and make sure you’d say it out loud in an interview without flinching.

Three lines from before you ran anything through ChatGPT are worth more than a paragraph the tool smoothed over. Build the tailored version around those.

Sources