How to Write a Resume Summary, With Six Worked Examples
A resume summary is two or three lines at the top of the page that say what you are, how long you have been doing it, in what kind of organisation, and the one thing you most want remembered. Write those four things in plain sentences and stop. Everything else in a summary is filler.
What a summary is actually for
A reader opening your resume is holding one question before any other: what is this person? Until that is answered, every bullet they read is floating. They cannot tell whether "rebuilt the reconciliation process" is impressive or routine, because they do not yet know whether you are two years into finance or fifteen.
The summary answers that question in one breath, so the rest of the page lands. It is the claim. Everything below it is the evidence.
Without one, the reader reconstructs your identity from your most recent job title, glances at your oldest one, and guesses at the shape in between. That works when your titles are standard and your path is a straight line. It works badly when your current title is internal jargon, when your best work is two roles back, when you have moved between industries, or when you are changing direction on purpose.
A summary is not a mission statement, a personality description, or a place for adjectives. "Results-driven, detail-oriented professional with a passion for excellence" tells a reader nothing, because no candidate has ever described themselves as the opposite. Put it directly under your contact details, above your experience, under a plain heading like Summary or Professional Summary so that both a person and a parser find it where they expect. Our guide to ATS friendly resume formatting covers why the boring heading matters.
The objective statement, and why it retired
The line that used to sit in this spot read something like: "Seeking a challenging position with a growth-oriented company where I can utilise my skills and contribute to organisational success."
That format made sense in its era. Resumes were posted or handed over speculatively, often with no specific vacancy attached, so the employer genuinely needed a sentence telling them which job you had in mind. The objective was a miniature cover letter stapled to the top.
Applications now arrive filed against a specific posting. The system already knows which role you applied to, and so does the person opening it. A line whose only content is "I would like this job" spends your most valuable space confirming something nobody was unsure about. Worse, the classic phrasing is framed around what you want from the employer at the exact moment the employer is deciding what they get from you.
| Objective | Summary |
|---|---|
| States what you are looking for | States what you are |
| Written about the future | Written from the record |
| Interchangeable between candidates | Only true of you |
| Cannot be checked | Backed by the bullets underneath |
There is one narrow case where direction still belongs at the top: when your reason for applying is genuinely not obvious from the page, such as a career change or a move to a new city. Even then the modern form is a summary that carries the pivot inside it, not a request. Example five below shows how that reads.
The formula that works
Four parts, in this order. It is not a rigid template, but every good summary we have seen contains all four somewhere.
- Role identity. What to call you, in the words your field uses. "Data engineer", not "technology professional". If your internal title is "Analyst II" and the world calls the job "financial analyst", use the world's word.
- Duration or level. "Six years", "since 2019", "second role in the field". Early in a career, an honest qualitative marker works: "recent graduate with two internships".
- Domain. The kind of place you have done it. B2B SaaS. A regional hospital network. A two-person marketing team inside a manufacturer. Regulated finance. This is the part most people leave out, and it carries more signal than the title does.
- The one thing to remember. Your strongest specific claim, chosen because a bullet further down the page proves it. One claim, not four.
Read as a sentence, that becomes: [Role identity] with [duration] in [domain], who [the one thing]. Then rewrite it until it sounds like a person talking.
Dynamic and results-oriented professional with a proven track record of success and extensive experience in a fast-paced environment. Excellent communication skills and a strong team player seeking to leverage expertise in a challenging new role.
Operations analyst, five years in third-party logistics, currently the only analyst supporting a network of nine warehouses. Built the weekly capacity model the planning team now runs on, and rewrote the exception reports that used to arrive three days late.
The second version is not more confident. It is more falsifiable, which is what makes it persuasive. A reader can go looking for the capacity model in the bullets below and find it.
The summary is a claim and the bullets are evidence. If a line in your summary has nothing underneath it that proves it, cut the line rather than dressing it up.
Six worked examples
Every detail in these is a placeholder. Swap in facts you can stand behind, including the numbers, which are only useful when they are yours and true.
Computer science graduate with two backend internships, both building Python and PostgreSQL services. Shipped the shift-swapping tool now used daily by staff across a four-site restaurant group, from schema to deployment. Looking for a first engineering role on a team that reviews code seriously.
Customer success manager, four years in B2B SaaS, currently holding a portfolio of sixty mid-market accounts at a payroll company. Rebuilt the onboarding sequence for new accounts and run it end to end. Strongest with technical products that non-technical buyers have to adopt.
Data engineer with nine years across two regulated industries, insurance and then healthcare. Own the ingestion layer behind clinical reporting: Airflow, dbt and Snowflake, around four hundred models a day. The person colleagues call when a pipeline has been quietly wrong for a month.
Support manager, eleven years in the function and the last four leading a fourteen-person team across two time zones at a fintech. Moved first response from a standing backlog to same day and held it there through two product launches. Hire and coach for judgement rather than script adherence.
Secondary school physics teacher moving into instructional design. Seven years teaching, including three rewriting the department's Year 12 curriculum and training six colleagues to deliver it. Completed a certificate in learning experience design and built three self-paced modules in Articulate Storyline for a local nonprofit.
Financial analyst, six years in FP&A for a manufacturing group, returning after two years out as a full-time carer. Kept CFA Level II current and spent the last year on contract budget work for two small charities. Fastest on cost modelling and variance analysis in spreadsheets nobody has maintained.
Notice what the last two do. The career changer names the pivot in the first six words, because a reader who does not know why a teacher is applying will spend the whole page distracted by the question. The returner states the gap plainly and briefly, then moves on. Neither invents anything, and neither apologises. Stretching dates to paper over a break is the one move that turns a normal, explainable gap into a reference-check problem. If you are changing fields, the summary and the career change cover letter should tell the same story in the same words.
Tailoring it to the posting
The summary is the cheapest line on your resume to tailor. It is prose, so editing it disturbs no layout, and it sits where the reader starts. Two things to change per application: the domain phrase, so it echoes the environment the posting describes, and the one-thing claim, so it matches what the posting leads with rather than what you are personally proudest of.
Screening tools and recruiter searches both run on the posting's own vocabulary, so using their word for something you genuinely do is sensible. If the posting says "revenue operations" and you have been calling it "sales ops", use theirs. What you cannot do is claim a thing because the posting asked for it. The test is mechanical: after rewriting, look for the bullet that proves the new claim. If there is no bullet, you have written fiction rather than tailoring. Our guide on tailoring a resume to a job description works through the rest of the document the same way.
A quick way to find the gap
Paste the posting and your resume side by side and list the terms it uses that yours never does. Decide one by one whether each is something you have actually done under a different name, or something you have not done. SwiftCover does that comparison automatically and shows which of the posting's keywords are still missing, but a highlighter and ten minutes gets you most of the way.
When to skip the summary entirely
A summary is optional, and a weak one is worse than none, because it spends the most valuable space on the page saying nothing. Leave it out when:
- Your titles already answer the question. An ICU nurse applying to ICU nursing roles, with standard titles and an unbroken path, gains very little. The reader knew what you were from the first line of your experience section.
- It would push real content off the page. If your resume is one line over and the choice is between the summary and a bullet that proves something, keep the bullet.
- The application form already asks. Some forms have their own short free-text "tell us about yourself" box. Writing the same paragraph twice wastes both.
- The format forbids it. Academic CVs, many public-sector and government application formats, and some agency templates prescribe a structure. Follow the prescribed structure.
- You have one job and it is the job. With a single relevant role below, a summary just restates it in different words.
The test takes five seconds. Cover the summary with your thumb, read the top third of the page, then uncover it. If you learn nothing you did not already know, delete it and let the space go to work experience.
What to cut
Most weak summaries are not badly written. They are written about the wrong thing.
The adjective pile
"Dynamic, results-driven, detail-oriented self-starter with excellent communication skills." Every word there is a claim about your character that the reader has no way to check and every other applicant has also made. Character comes through in what you did, not in how you label yourself. Delete the adjectives and the sentence usually gets shorter and better.
- No first-person pronouns, and never the third person. Not "I manage" and definitely not "Priya is a seasoned professional". Fragments starting with the verb are standard on a resume.
- No unanchored scope words. "Extensive experience" and "proven track record" mean nothing on their own. A duration and a domain mean something.
- No restating the job description back at them. They wrote it.
- No "responsible for". It describes a job that existed, not work you did. Our resume action verbs guide has replacements that carry actual information.
- Nothing longer than a short paragraph. Two or three lines. If it runs to five, it has become a cover letter that nobody asked for.
- No claim without a bullet underneath it.
One last pass: read it aloud. A summary you would be embarrassed to say out loud to a colleague is a summary that will read as boilerplate on the page, and boilerplate is invisible.