How to write a CV summary that is not filler

The summary is the most-read and least-considered part of a CV. Most are interchangeable, which means most are wasted.

The test

Cover your name and hand your summary to a friend. If it could describe a thousand other people, it is not a summary — it is decoration.

"Hard-working and detail-oriented professional with a proven track record of delivering results in fast-paced environments" describes nobody. It is four lines that say nothing.

A structure that works

Three sentences:

1. What you are, with a number. Role and years, or role and scale.
2. The strongest evidence you have. One concrete thing you did.
3. What you are looking for. Direction, so the reader can place you.

Worked example:

> Registered nurse with six years in intensive care, currently precepting new > staff on a 24-bed unit. Led the line-care protocol revision that cut > catheter-associated infections across the department. Looking for a senior > ICU post.

Another:

> Backend engineer, five years, mostly Python and PostgreSQL. Built the > payments reconciliation service that settles daily transaction volume for > three merchant banks. Interested in platform and infrastructure work.

Neither uses an adjective about the person. Both are specific enough that only one person could have written them.

Words to cut

Hard-working. Detail-oriented. Team player. Passionate. Dynamic. Results-driven. Self-starter. Proven track record. Fast-paced environment. Think outside the box. Synergy. Leverage. Spearheaded.

Every one of these is a claim with no evidence, and a reader who sees three of them stops reading. If you delete one and the sentence still means the same thing, it was doing nothing.

Tailor the third sentence

The first two sentences are stable. The third — what you are looking for — should change per application, and it is the highest-return thirty seconds of editing available to you.

If the advert is for a senior ICU role, your third sentence names a senior ICU role.

If you have no experience yet

The structure still holds. Substitute evidence you do have:

> Computer science graduate focused on backend development. Built and deployed > three full-stack projects during my degree, including a booking system still > used daily by a 40-room guesthouse. Looking for a junior backend role.

That reads as someone worth interviewing.

Length

Three to four lines. Never more. A summary that runs to a paragraph is an introduction, and nobody reads introductions.

Write yours in the builder — the summary field sits at the top of the Content panel, with a live preview so you can see how it sits on the page.