- A summary is four sentences: who you are, what you have done, what you are good at, what you are looking for.
- Specifics beat adjectives. "Nine years" beats "extensive". "Fifty-person team" beats "large team".
- Cut anything that could be said by any applicant for the same role.
- Adapt, do not rewrite. Two or three words usually change enough to fit a new role.
Why a summary at all?
Every resume element has to justify its space. The summary earns its place for two reasons.
First, it lets you name the role you are applying for and describe yourself in the language of that role. A recruiter who is skimming thirty resumes for a "Senior Backend Engineer" position will see your title and your seniority in the first line. If that matches what they are looking for, they will read the rest of the page carefully. If it does not, they will skim.
Second, it gives you control over the frame. Without a summary, the reader's first impression comes from the top of your most recent role, which might be a less relevant role, an unusual title, or a company they have not heard of. A summary lets you present the narrative you want them to have in mind as they read the details.
A summary is not the right place for your career objective or for personal adjectives. Both of those will actively hurt you. The right place is the middle ground: a short, factual statement of your background, written in the language of the job you are applying for.
The four-sentence structure
The structure that consistently works, across industries and levels, is this:
- Who you are, and how long you have been doing it. "Senior product designer with nine years of experience in SaaS and fintech." A number beats an adjective. A named industry beats "various industries".
- What you have done that matters. One sentence describing scope or a strong recent achievement. "Led end-to-end design for a small business lending product serving 12,000 active accounts."
- What you are good at, concretely. Two or three capabilities that match the role you are targeting. "Comfortable with research, design systems, and shipping alongside engineering teams."
- What you are looking for. A short line about the role or type of company. "Looking to join a product team where design is part of the decision-making, not a service at the end."
Four sentences is the target. Three is fine for early-career candidates with less to say. Five is the maximum; beyond that, the summary stops reading as a summary and starts reading as a cover letter.
The three clichés to cut
Certain phrases have been used so often on resumes that they carry no information and quietly harm the resume by making it look like every other one. The three worst offenders:
"Results-driven professional." Every candidate claims to be results-driven. The claim is unverifiable and does not distinguish you. If you want to demonstrate that you are focused on results, do it in your bullet points, by describing results.
"Passionate about [field]." Passion is not a differentiator either. Worse, it is usually used to describe a field so broad that it means nothing: "passionate about marketing", "passionate about technology". If you genuinely want to demonstrate interest in a specific area, show it through the choices you have made — the projects you have taken, the skills you have developed, the communities you are part of.
"Detail-oriented team player." These are the two most generic adjectives in the resume vocabulary. They are the default assumption for any candidate. Including them signals that you do not have anything more specific to say.
None of this means you cannot describe yourself in positive terms. It means the description must be specific enough to be verifiable. "Nine years of experience building distributed systems" is specific. "Experienced team player" is not.
Adapting the summary for each role
You do not need to write a new summary for every job you apply for. You need to adjust two or three words.
The first sentence usually stays the same except for the title. If you are applying for both "Product Designer" and "Senior Product Designer" roles, the title changes but the years and the industry stay the same. If you are applying for roles in a slightly different industry — say, moving from SaaS to healthcare — the industry phrase in the first sentence changes, and often the description of scope in the second sentence changes as well.
The third sentence, describing your capabilities, is where most of the adaptation happens. For a "Product Designer" role that emphasises systems and collaboration, list systems and collaboration. For a role that emphasises research and user insight, list research and user insight. These are likely both true of you; the summary just chooses which to lead with.
The fourth sentence, describing what you are looking for, changes the least. If you are targeting a specific type of company — a small team, a scaling startup, an established enterprise — you can say so. If you are open, say less and let the earlier sentences carry the summary.
Two worked examples
Here is a summary that would typically be written badly:
Results-driven marketing professional with a passion for storytelling and a proven track record of delivering growth in fast-paced environments. Detail-oriented team player with strong communication skills and a can-do attitude.
Every claim in that paragraph is either unverifiable or could be said by any other candidate. There is no industry, no scope, no number. If a recruiter swapped your name for someone else's, the paragraph would still "work", which is the tell that it says nothing about you.
Here is the same candidate, written specifically:
Content marketing manager with six years of experience running editorial programmes for B2B SaaS. Grew organic traffic from 40k to 128k monthly sessions in eighteen months through a focused SEO and editorial programme. Comfortable owning strategy, production, and measurement, and pairing closely with demand generation on pipeline impact. Looking to join a marketing team where content is treated as a growth channel rather than a cost centre.
The second version names the industry, the years, a specific outcome, the scope of the role, and the type of team the candidate wants to join. It is four sentences and it fits on four lines. It is also far more useful to a recruiter than the first version, because it lets them decide in ten seconds whether to read further.
Notice that in the strong example, no sentence contains an adjective about the candidate's personality. The adjectives you would want to use — driven, meticulous, collaborative — are all demonstrated by the facts, not asserted.
Summary checklist
- Does your first sentence contain a number? Years of experience, team size, or scope. If not, add one.
- Does your second sentence contain a specific outcome? A metric, a launch, a piece of scope. If not, replace it with one.
- Does your third sentence name skills that match the target role? If not, swap them for the ones that do.
- Does your fourth sentence say what you are looking for? If not, add a short line.
- Could this summary be applied to any other candidate? If yes, make it more specific until it could not.