The average resume summary reads like this: "Results-driven professional with a proven track record of delivering value across multiple industries. Passionate about leveraging data to drive strategic outcomes."
That sentence could be pasted onto almost any resume in any industry. It contains no information. The reader learns nothing except that you can generate corporate prose.
A summary that works does the opposite. It contains three things: scope, evidence, and a specific next step.
Start with scope
Scope tells the reader what level you operate at. Not "senior software engineer" — every senior software engineer says that. Instead: "Nine years building distributed systems and leading infrastructure at companies from 40 to 400 engineers."
Scope is usually one of: years of experience, team size managed, revenue or budget owned, scale of systems, size of companies worked at, number of people impacted.
A good opening sentence establishes scope in a way that immediately sets expectations about what kind of evidence will follow.
Add one piece of evidence
The second sentence should be a single, specific achievement. Not a list of every achievement. One that represents your strongest proof of capability in the role you are applying for.
For example: "Led migration of a 40-service platform to Kubernetes, cutting infrastructure cost by 32% and improving deploy frequency from weekly to daily."
This is not a summary of what you do. It is a specific, verifiable, quantified result. It tells the reader what kind of impact you have had, which gives them a filter for the rest of the resume.
Signal a next step
The third sentence, if you include one, should suggest what you are looking for next. Not in a needy way — in a "here is why I am applying to this role specifically" way.
For example: "Looking to move into a staff engineering role where I can mentor at a larger scale and set technical direction across multiple teams."
This is optional. If it feels forced, leave it out. The scope + evidence combination is already strong.
The test: could your summary be pasted onto someone else's resume without anyone noticing? If yes, it needs to be more specific. Replace every abstract claim with a concrete one.
Three examples
Engineer: "Senior software engineer with 9 years of experience building distributed systems and developer tooling at scale. Led migration of a 40-service platform to Kubernetes, cutting infrastructure cost by 32% while improving deploy frequency from weekly to daily. Comfortable moving between deep backend work and cross-functional product decisions."
Marketing manager: "Marketing manager with 7 years of experience running brand, content, and lifecycle campaigns for B2B SaaS companies. Grew organic traffic from 12K to 180K monthly visitors in 24 months, and built a content team that shipped 8 posts per month at the same cost as a single agency retainer."
Graduate student: "Final-year Computer Science student at the University of Manchester, graduating June 2026. Two internships, one national hackathon win, and a portfolio of shipped side projects. Looking for a graduate software engineering role where I can grow into systems work."
How long should it be?
Two to four sentences. Two sentences is tight and confident. Four sentences is more common when there is more scope to establish. Anything longer than four sentences stops being a summary and starts being a paragraph.
Two sentences is the strongest length for most candidates. It forces you to only include information that earns its space.
When to skip the summary entirely
The summary is optional. Skip it if:
- Your strongest evidence is in your experience section and would be redundant in the summary.
- You cannot write a specific one without inventing information.
- You are applying for a role where the experience section is what matters most.
A missing summary is better than a generic one. A generic summary signals that you had space and filled it with noise.
Write a summary that reads like evidence
Our editor has dedicated guidance for every section — including the summary.