Every Number on Your Resume Is a Question You Will Be Asked

Should you keep a number the AI invented?

Not unless you can trace it. A resume builder that generates "increased efficiency by 30 percent" in the same pass that writes the sentence around it has invented a measurement, and a measurement you cannot trace back to a count, a date and a comparison is a guess wearing the clothes of a fact. It reads as one until someone asks the obvious next question.

A three-part check before any number stays in:

• Trace it or cut it. Can you name what was counted, over what period, against what baseline? If not, the number isn't yours yet.
• A close paraphrase is not tracing. "Roughly a third faster" is still invented if nobody ever measured a before and an after.
• When in doubt, downgrade to scope. Team size, ticket volume, meeting cadence: anything you can state without inventing a comparison.

The distinction matters because the evidence on AI and writing quality is real, just narrower than it usually gets quoted. A large randomized study on an online freelance labor market found that giving new jobseekers there algorithmic writing assistance on their own resume text raised how often they were hired by 8 percent ³. The tool tested edited sentences that already existed; it did not generate new claims from an open prompt ⁴. That is the version of "let AI help with your resume" the evidence actually supports: cleaning up what you wrote, not inventing what you didn't.

A worked example makes the line clearer. You know you closed support tickets faster after a process change, but you never pulled the before-and-after report. "Cut average ticket resolution time by 30 percent" is invented, because you cannot name where 30 came from. "Rebuilt the escalation checklist that the team still uses, and closed the same tickets I used to hand off" is not invented. It names a real artifact and a real change in what you personally did, and neither claim needs a number you don't have.

What happens when the number gets questioned in an interview?

The follow-up on a fabricated number rarely announces itself as a trap. An interviewer checking understanding asks a version of three questions: which alternative did you rule out, what would you have done if a constraint moved, what would have to be true for the answer to be wrong. Read the follow-up questions that expose whether someone understands their own answer; every one assumes the number came from somewhere real. An invented figure has nowhere to point.

What actually happens in the room, roughly in order:

• The number gets named back to you. "Walk me through the 30 percent."
• The specifics don't arrive, because none exist to arrive.
• The rest of the resume gets reread with suspicion, including the parts that were true.

The cost is not symmetric. In the one study that measured disclosure, non-disclosure and getting caught side by side, a professional whose undisclosed AI use was exposed by someone else was trusted less than one who had disclosed it himself, and both were trusted less than the matched case where nothing came up at all ¹. That scenario was a professional's AI use, not a resume figure, and what transfers is the ordering rather than any magnitude: being exposed cost more trust than owning the fact up front ever did. A number you cannot explain sits at the exposed end of that ordering the moment someone asks.

Sound confident about real work you actually did, whether or not you can put a number on it. Put that confidence on the description of what happened, not on a decimal point somebody's model chose for you. A candidate who says "I don't have an exact figure, but here's what changed and how I know" reads as more credible in the room than one holding a number they cannot explain, because the first answer keeps going under pressure and the second one stops.

Use scope when you don't have a metric

Scope is the honest substitute for a metric you never tracked: size, frequency, duration, who depended on it. "Managed a $40,000 budget" is scope. "Ran the weekly standup for a team of six for a year" is scope. Neither claims a result you can't prove, and both give an interviewer something specific to ask about that you can actually answer without inventing anything on the spot.

Three kinds of scope, none of them requiring a measurement you never took:

• Size. How many people, accounts, dollars, or tickets.
• Frequency. How often the task recurred, and for how long.
• Dependency. Who relied on the output, and what they used it for.

Specificity is also what employers say they notice most. In a June 2026 ZipRecruiter survey of over 1,000 hiring decision-makers, 24 percent said they can almost always tell when a candidate used AI in an application, and another 60 percent said they can sometimes tell ². That belief measures confidence, not accuracy, but it points at the same thing this article is arguing: a stock phrase reads as generated whether or not it was, and a specific, checkable detail doesn't. A resume line claiming daily AI use gets the same treatment a number does. Verifying "uses AI daily" in ten minutes works the same way as verifying a metric: ask for the artifact, not the adjective, and keep your own notes ready before anyone has to ask.

Keep those notes somewhere you will actually find them again, not just in your head the week you wrote the resume. A short document with the real number, the date you counted it, and how you counted it turns a defensible claim into an easy answer six months later when the interview finally happens and the details have gone soft in your memory.

See a sample report >