How long should a résumé summary be

Three or four lines. The checker on this site treats a summary of roughly eighteen words or more as substantive, and a reader stops paying attention somewhere around sixty.

A summary describes what you have done, an objective describes what you want. Most readers prefer the first. The comparison, with the cases where an objective still earns its place, is in the objective guide.

Should I write in the first person

Either works. What matters is consistency down the page. Many people drop the pronoun entirely, which reads as brisk rather than cold.

Does the summary need keywords

It needs the words you would use about your own work. A summary stuffed with terms from a posting reads badly to a person and earns nothing extra from the check here, which measures evidence rather than keyword density.

Yes. The completeness part of the check records a missing summary as ten points of its hundred, so a page without one can still score well. A good experience section carries more weight than a weak paragraph above it.

Guide · Résumé

The résumé summary, and four worked examples

A summary is a compression of the rest of the page. Three or four lines, written last, saying what you do, for how long, and what you are known for.

ConxfolioPublished 2026-09-12

— write it after the experience section, never before.

A summary is the paragraph at the top of a résumé that tells a reader what they are about to look at. Three or four lines is the working length. It is written last, after the experience section exists, because a summary is a compression of that section and compressing something unwritten produces the vague opening everybody recognises.

What goes in

Three things, in whatever order reads best. The work you do and the years you have done it. The kind of organisation you have done it in. The one thing you are known for, stated plainly enough that a colleague would agree with it. Everything else is detail that belongs lower down the page, where the evidence for it sits.

What stays out

Adjectives about your character. A list of every technology you have touched. A sentence about the position you are applying for that you rewrite for each application and eventually forget to change. The phrase "results-driven professional", which appears on a great many pages and distinguishes none of them.

Four worked examples

These four people are invented. They exist to show a shape rather than to be copied.

Seven years in one field. "Backend engineer with seven years on payment systems and data pipelines. Works on reliability, cost and the parts of the stack nobody volunteers for."
Changing field. "Six years running restaurant operations, now working in supply analytics. Brings scheduling, stock and margin work from a place where a bad forecast is visible the same evening."
First job. "Economics graduate with a statistics minor and two research placements. Comfortable with survey data, cleaning it and explaining what it does and does not support."
After a gap. "Ward nurse with nine years in acute care, returning after two years of full-time caring at home. Current registration, and two refresher placements completed this year."

Each one names the work, the length of the work, and something specific. None of them claims a quality. The specific clause is the part a reader remembers, and it is the part that cannot be written by anyone else.

Write it in the builder, above what it summarises

In the résumé builder the summary has its own section in the editor rail, directly under the personal details and above the experience. The page on the right redraws as you type, so you see the line breaks the export will produce rather than guessing at them. If you imported a file, whatever it read as a summary is already in the field and can be replaced.

How the check treats it

The ATS checker looks for a substantive professional introduction and counts it in the completeness dimension, which is 30 per cent of the score. A summary of roughly eighteen words or more under a recognised heading counts as present. A one-line heading with nothing beneath it does not, and an empty heading costs you elsewhere as well, because the parseability rules look for headings with real content under them.

The check has no opinion about how good the paragraph is. No public checker can have one, and this one prints what it measured rather than a judgement it cannot support.

A test before you send it

Read the summary on its own and ask whether it could sit on the page of anyone else in your field. If it could, it is describing your job rather than your work. Put back the one clause that only applies to you, even if it is small: the system you rebuilt, the region you covered, the shift nobody else wanted. That clause is the summary.

When it is right, the rest of the page has to earn it. A summary that claims something the experience lines do not show is the most common weakness in an otherwise good résumé, and it is the one a careful reader spots first.

Three situations that need a different opening

Changing field. Name the new field first and the old one second, with the transferable work in between. A reader who meets six years of restaurant operations before they meet the word "analytics" has already filed you under restaurants.

Returning after time away. State the current position plainly, including the gap, and put the most recent proof of currency next to it: a refresher course, a registration still in date, a short contract. A summary that skirts the gap makes the reader hunt for it, and they always find it.

First application. You have no years to count, so count something else. The degree, the placements, the tools you have actually used on real data. Specific beginner work reads far better than an aspiration, and the section order still holds.

Length, tested on paper

Four lines of text at ordinary résumé sizes is roughly sixty to eighty words. Beyond that the paragraph stops being a summary and starts competing with the experience section for attention. Write it in the builder rather than in a word processor, because the page beside the editor shows the real line breaks: a summary that is four lines in your draft can be six in the design you chose, and six lines at the top of a page is a wall.

Write yours in the builder

The summary sits in its own section of the editor, above the experience it compresses, and the live page beside it shows the line breaks as they will print.

Open the résumé builder Check what a parser reads

Questions

How long should a résumé summary be: Three or four lines. The checker on this site treats a summary of roughly eighteen words or more as substantive, and a reader stops paying attention somewhere around sixty.
Summary or objective: A summary describes what you have done, an objective describes what you want. Most readers prefer the first. The comparison, with the cases where an objective still earns its place, is in the objective guide.
Should I write in the first person: Either works. What matters is consistency down the page. Many people drop the pronoun entirely, which reads as brisk rather than cold.
Does the summary need keywords: It needs the words you would use about your own work. A summary stuffed with terms from a posting reads badly to a person and earns nothing extra from the check here, which measures evidence rather than keyword density.
Can I skip it: Yes. The completeness part of the check records a missing summary as ten points of its hundred, so a page without one can still score well. A good experience section carries more weight than a weak paragraph above it.

Conxfolio is a free set of four career tools: a résumé builder with 37 rendered layouts, an ATS résumé checker that prints its own arithmetic, a cover letter builder that traces every proof paragraph back to the line it came from, and a portfolio builder with 20 authored designs. There is no account to create, nothing is held back for a paid plan, and no language model is used anywhere in the product, so the readers, the score and the letter are deterministic code you can check.