How to write a résumé summary that gets read

What the summary is for

The summary is the two to four lines directly under your name and contact details. It is the first thing a recruiter reads after the job title, and it is read before anything else because people read documents top-down and stop when they have an answer. The question a reader is answering is simple: is this person plausibly a fit for the role I am filling? Your summary either answers yes in their words, or it leaves them to work it out from the rest of the page.

That makes it a compressed argument, not an introduction. It should state who you are professionally, what you are good at that this employer needs, and one piece of evidence. It should not state what you want from them; that is what the old-fashioned objective did, and it gives the reader nothing to evaluate.

When to skip it

Skip the summary when it would only repeat your current title and first bullet. A second-year accountant whose most recent job is titled Accountant does not need a line saying they are an accountant with two years of experience; the reader will see that in the same glance.

Write one when the page needs framing: you are changing fields, your titles do not describe what you actually did, you have a gap you want to put in context, or the posting asks for a combination that your job history only shows in pieces. In those cases the summary is the only place where you can connect the dots for the reader before they draw their own.

The three-part structure

A summary that works has three parts, usually in this order. First, an identity line: the role in the words the posting uses, your years of experience, and your domain. Second, two or three strengths that the posting actually asks for, written as things you have done rather than qualities you claim. Third, one proof point: a number, a named product, a recognisable outcome.

Keep the parts in that order because the reader is scanning for the role name first. If the first words are an adjective, the match is delayed by a line.

Replace adjectives with evidence

Words like results-driven, detail-oriented, passionate and team player carry no information, because every applicant can write them and no reader can check them. They also take up the most valuable space on the page. Go through your draft and, for each adjective, ask what made you want to write it. Then write that instead.

“Detail-oriented” usually hides something like “caught a pricing error before a 40,000-unit print run”. “Strong communicator” might really be “presented monthly to the executive team” or “wrote the onboarding guide the department still uses”. The specific version is longer by a few words and more persuasive by a lot.

Match the posting's language

Recruiters search their database and skim pages for the terms in the job description, so use those terms, spelled the way the posting spells them. If your last title was Customer Happiness Lead and the posting says Customer Support Manager, open with “customer support manager” and keep your official title in the experience section. Pick two or three requirements from the top of the posting and address them directly.

There is a limit. A summary that lists twelve tools reads as a keyword dump and tells the reader nothing about what you did with them. Put the full list in the skills section and keep the summary to what you are strongest at.

Length and form

Two to four lines, around 40 to 70 words. Most summaries omit the pronoun (“Backend engineer with…” rather than “I am a backend engineer…”); either convention is fine if you keep it consistent, and third person (“She is…”) is not. Use a standard heading such as Summary or Profile so that both people and parsing software recognise the section.

Avoid the headline-plus-paragraph pattern where a bold line says “Senior Project Manager” and the paragraph underneath begins “Senior project manager with…”. Say it once.

Summaries for particular situations

The structure holds, but the emphasis shifts.

• Changing fields: name the target role first, then the transferable part of your past in concrete terms. “Data analyst moving from five years in retail operations; built the stock-forecasting models a 12-store chain still runs on; completed a statistics MSc in 2025.”
• New graduate or student: this is a profile rather than a summary. Lead with your field of study and the strongest thing you have built or done, and name the role you are applying for.
• Returning after a break: state the role and skills as usual; the break belongs in the experience section as a dated line, not in the summary.
• Senior roles: give scope early: team size, budget, revenue, geography. “Led a 60-person engineering organisation across three countries with a $9M budget” tells the reader your level faster than any list of skills.

Check before you save

Read the summary once more against the posting and check the following.

• The first line names the role using the posting's words.
• At least one number or named outcome appears.
• Every claim is something you could expand on for two minutes in an interview.
• No adjective is doing work that an example should do.
• It is under 70 words and does not repeat the first bullet of your current job.
• A stranger reading only this paragraph could say what you do and what level you are at.