What belongs in the three lines at the top of your resume, when an objective is better, the four ways summaries fail, and examples across seven fields.
The summary is the only part of your resume you can be reasonably confident is read. It sits at the top, it is short, and a reader gets to it before deciding whether to continue.
Which makes it strange that most summaries are interchangeable.
Results-driven professional with a proven track record of success in fast-paced environments. Skilled communicator and team player seeking to leverage my expertise to drive organisational growth.
Every word of that could belong to anyone in any industry at any level. It occupies the most valuable space on the page and transfers no information at all.
What the three lines are for
A summary is orientation. It tells a reader, before they start parsing dates and employers, three things:
- What you are — function and level
- At what scale — the size of what you have handled
- What you have actually done — one concrete piece of evidence
Get those in and the rest of the resume is read with a frame around it. Miss them and the reader assembles the frame themselves from your job titles, which is slower and less favourable to you.
"Dedicated and detail-oriented operations professional with extensive experience in logistics and a passion for process improvement."
"Operations manager, eight years in third-party logistics. Ran a 40-person warehouse through a site consolidation, taking on-time dispatch from 91% to 98.6% in a year. Comfortable in environments where the process does not exist yet."
Summary or objective
A summary looks backwards: this is what I have done. Use it whenever your history speaks for itself, which is most of the time.
An objective looks forwards: this is what I am aiming at. It earns its place in exactly three situations — you are changing fields, you are returning after a break, or you are deliberately moving to a different level. In each of those, the reader is about to encounter something that needs explaining, and one sentence of explanation is worth more than another achievement.
Outside those cases, an objective spends your best three lines telling a company what you would like from them, on a page whose entire purpose is telling them what they get.
If you do write one, make it about the fit rather than the want:
Sixteen years in clinical nursing, now moving into health-tech product. Spent the last two years as the clinical lead on our EHR rollout — writing the requirements, running the pilot ward, and translating between clinicians and engineers. Looking for a product role where domain knowledge is the constraint.
That is an objective and it is still evidence-led.
The four ways summaries fail
Adjectives instead of facts. "Highly motivated", "results-driven", "detail-oriented". Nobody writes the opposite, so they carry no information and readers skip them automatically.
Length. Once a summary passes about 60 words it becomes a paragraph, and paragraphs at the top of a resume get skimmed. Everything you add dilutes what was already there.
Restating the job posting. Summaries that mirror the requirements back — "seeking to apply my skills in stakeholder management and process optimisation" — read as generated, because increasingly they are.
Vagueness about scale. "Extensive experience managing teams" could mean three people or three hundred. The number costs you two characters and changes everything.
Examples
Written to be adapted rather than copied. Note that each one contains at least one specific number and one thing the writer decided, rather than was assigned.
Software engineering
Backend engineer, six years, mostly Go and Postgres. Rebuilt the payments service at a Series B fintech to handle 4× volume without adding infrastructure spend. Prefer teams that own their services in production.
Frontend engineer with eight years across agency and product work. Led the design-system migration that cut our component duplication from 240 to 90 and shipped a 40% improvement in Lighthouse scores. Accessibility is not an afterthought for me.
Data and analytics
Data analyst, four years in retail. Built the demand forecasting that replaced a spreadsheet the buying team had used for a decade; stockouts on core lines fell by roughly a third in the first season. SQL, dbt, Python.
Analytics lead managing three analysts across marketing and finance. Spent most of last year on definitions rather than dashboards — we now have one revenue number instead of four, which was harder and more valuable than any model I built.
Project and product management
Product manager, five years in B2B SaaS. Took our onboarding from a 40% completion rate to 71% by cutting the flow in half rather than adding to it. Comfortable saying no to a roadmap.
PMP-certified programme manager, twelve years in construction and infrastructure. Delivered a £14M hospital wing refurbishment on schedule through a main-contractor insolvency.
Finance and accounting
Management accountant, seven years in manufacturing. Cut month-end close from eleven working days to four by fixing the intercompany reconciliation rather than adding people to it. ACCA qualified.
Financial analyst supporting a $200M business unit. Built the model that underpinned a pricing change worth roughly $3M in annual margin — and the case for why we should not go further.
Marketing
Growth marketer, six years, mostly paid acquisition. Moved £45K quarterly spend off Meta when cost per qualified lead stayed double LinkedIn's, bringing blended CPL down by £18. I would rather kill a channel than defend it.
Content lead who came from journalism. Rebuilt the editorial calendar around three deeply-researched posts a month instead of daily volume; organic traffic doubled in nine months and the team stopped working weekends.
Healthcare
Registered nurse, nine years, five in paediatric intensive care. Precepted fourteen new graduates and rewrote the unit's shift handover after a near-miss — handover-attributed incidents went to zero the following year. RN (Ohio), active. ACLS, PALS.
Practice manager for a five-partner clinic, 4,000 patients. Took the appointment no-show rate from 18% to 7% with a reminder system I specified and negotiated within the existing budget.
Operations and supply chain
Supply chain manager, ten years in FMCG. Renegotiated terms with eight suppliers during the 2025 shortage and held volume discounts while competitors moved to spot pricing. Comfortable with ugly data and short notice.
Warehouse operations manager, 60 staff across two shifts. Introduced a written handover and a shared exception log; dispatch accuracy went from 91% to 98.6% without replacing the WMS everyone blamed.
Writing yours
Three practical steps.
Write it last. You cannot summarise a document you have not finished. Complete the experience section first, then read it and ask what a stranger would conclude.
Pull your strongest bullet up. The single most impressive, checkable thing in your history probably belongs in the summary too. Repetition between summary and experience is fine — the summary is a trailer, and trailers use footage from the film.
Adjust it per application. Not the whole thing. One clause. If the posting emphasises multi-site operations and you have run multi-site operations, that fact moves to the front. This takes two minutes and it is the highest-return tailoring available.
Then apply the substitution test: could this summary sit on someone else's resume without alteration? If yes, it is not describing you yet — and the fix is almost always a number, or the one decision you made that someone else might not have.
For how the rest of the page fits around it, our complete resume writing guide covers the full document.
Land more interviews with ATS-optimized resume tools
Write Your SummaryFrequently Asked Questions
What is the difference between a resume summary and an objective?
A summary describes what you have done and at what level. An objective states what you want. Use a summary when continuing in your field; an objective only when the resume needs explaining — a career change, a return after a break, or a deliberate step down.
How long should a resume summary be?
Two to four lines, or roughly 40 to 60 words. Beyond that it stops being a summary and becomes an introduction people skip.
Should I write it in first person?
Neither 'I' nor 'he/she'. Use the implied-subject style conventional on resumes: 'Operations manager, eight years in logistics.' It reads naturally and avoids the awkwardness of writing about yourself in the third person.
Do I need a summary at all?
Not always. If you are early in your career with a straightforward history, the space is often better spent on projects or experience. It earns its place when it orients a reader who would otherwise have to work out what you are.
CraftMyDocs Editorial Team
Resume & Career Experts
The CraftMyDocs editorial team writes practical, tested guidance on resumes, cover letters, ATS, and job searching — drawing on recruiter feedback and the data behind thousands of resumes built on the platform.