How to Write a Resume Summary

Most summaries say nothing. A good one earns the next thirty seconds of attention, and it does that with specifics rather than adjectives.

From the team behind PassATS. Free to read, no email required.

Three lines, and what goes in each

Line one: what you are and for how long. "Product manager, eight years, consumer fintech." Not "results-driven professional with a passion for excellence."

Line two: the strongest evidence you have. One outcome with a number in it. The thing you would lead with if you had ten seconds in a lift.

Line three: what you are looking for, only if it is not obvious. Skip it when you are applying for the same role you already do.

The adjective test

Read your summary and delete every adjective. Motivated, passionate, dynamic, detail-oriented, results-driven, hard-working.

If what remains still says something, the adjectives were decoration and you can leave them out. If nothing remains, the summary was never saying anything, and the space belongs to your Experience section instead.

Two versions of the same person

Before: "Results-driven marketing professional with a proven track record of delivering impactful campaigns in fast-paced environments."

After: "Growth marketer, six years, B2B SaaS. Took paid acquisition from £180 to £62 CAC across four quarters at a Series B. Looking for a senior role with budget ownership."

The second is shorter in adjectives and longer in evidence. It also gives a recruiter three things to ask about, which is the actual job of a summary.

When to leave it out entirely

If you are early in your career and the strongest thing about you is your most recent role, lead with the role.

A summary that repeats the job titles directly beneath it costs you five lines at the top of the page, which is the most valuable space you have.

What it does for parsing

A summary is a dense, natural place for the terms a role expects, so it carries real keyword weight in most scoring.

That is a reason to write it well, not a reason to stuff it. A list of technologies with no sentence around them reads as a Skills section in the wrong place, and a human will treat it as one.