When an AI Summary Promotes You

The summary at the top of a resume is where AI drafting goes furthest wrong, because it is the only section with no specific event underneath it. A bullet is anchored to a project; a summary is anchored to nothing, so the model fills it with the most impressive general description that fits. The result is a paragraph claiming a seniority the dates immediately below it contradict. Check the summary against the timeline before anything else.

Why this section drifts hardest

Every other part of a resume constrains the language. An experience bullet has a real project behind it, so an overstatement is at least tethered to something. A summary is a request for self-description in the abstract, and the training data for that request is full of confident, senior-sounding paragraphs.

So a two-year career becomes “experienced professional with a proven track record.” A specialist becomes “strategic leader.” Someone who has held one job becomes someone with “a decade of cross-industry expertise,” which is not even internally consistent, and it appears above a work history that shows otherwise. This is the most extreme version of the drift that affects generated drafts generally, concentrated in the section a reader looks at first.

The words that signal a promotion happened

Read your summary for these and ask what each one is claiming:

Seasoned, veteran, extensive. All claims about duration. Compare against the dates.
Strategic, executive, senior. Claims about level. Compare against your titles.
Proven track record. A claim that results exist and are attributable. If the resume does not show them, the summary should not assert them.
Cross-functional leader, transformation lead. Claims about authority over other people.
Expert, specialist, authority. Claims about depth. Fine if the evidence follows; hollow if it does not.
A decade of, years of. Check the arithmetic. This one is checkable in five seconds by anyone.

None of these words is banned. Each is a claim, and a claim in the summary carries more weight than the same claim lower down because it frames everything after it.

The consistency test

Read the summary, then read the first two experience entries, then read the summary again. Ask a single question: does the history below support the description above?

Common failures:

Summary says ten years; dates add to six.
Summary says leadership; every title is an individual-contributor title and every verb is “supported.”
Summary claims a breadth of industries; the history shows one.
Summary claims a specialism the experience never demonstrates.

Each of these is visible to a reader in the time it takes to glance down the page, and the effect is not that they mildly discount the summary. It is that they start reading the rest of the page as sales copy.

What a summary should do instead

A useful summary tells a reader what kind of work you do and what you are looking for, at a level of specificity that could not describe anyone else. That is a different objective from sounding senior, and it is achievable in three sentences.

The elements worth including: your actual domain, the kind of problem you work on, one concrete thing you have done, and where you want to go next. The last of these is the part generated summaries almost always omit, and it is the part a reader most wants, because a resume otherwise only describes the past.

Where you have a career shape that needs explaining — a change of field, a return after a break — the summary is the right place to state it briefly. Better there, in your own words, than left for the reader to infer from the dates.

Whether to have one at all

A summary is optional, and a weak one is worse than none because it occupies the most valuable space on the page. The existing discussion of whether a resume should have a summary covers that decision. What is worth adding here is that “the AI generated one so I kept it” is not a reason to have one. If you cannot write three sentences that say something specific, delete the section and let the experience start at the top.

Writing it last

Write the summary after everything else, from the finished page. Then it can only describe what is actually there, which makes the consistency problem nearly impossible to create. Generated summaries are usually produced first, or from a prompt describing your career in general terms, which is precisely why they float free of the evidence.

If you do use a tool, give it the finished resume and ask it to summarise that, rather than asking it to describe you. The difference in output is substantial, and the result can be checked line by line against the page it came from.

Then check what it commits you to

A summary claiming leadership will be tested in conversation like anything else — every claim on the page invites a question, and a summary claim invites the broadest one available: tell me about yourself. If the answer you give in that first minute does not match the paragraph, you have set up your own contradiction in the opening exchange. Write the summary you would give as that answer, and the two will always agree.