Resume summary examples that say something only the summary can
A summary exists to do one job the rest of the page cannot: state what you want and give the single strongest reason to believe it. Most summaries fail because they restate the CV — the job title, the years, the duties — in longer sentences.
Before: Results-driven finance professional with a proven track record of delivering value in fast-paced environments. Skilled in analysis, reporting and stakeholder management. Seeking to leverage my experience. After: Finance analyst in subscription billing, six years across reporting and revenue reconciliation. Rebuilt the monthly close pack so it ships in two days instead of five; now looking for a senior analyst role in a subscription business.
Three lines, three jobs
Line one says what you are, concretely: role, years, domain. Line two gives the strongest verifiable proof — one number or one named artefact. Line three says what you want next, so the reader does not have to infer it.
- What you are: "Registered nurse with six years on a medical-surgical unit."
- The proof: "Ran charge shifts for a six-nurse team and cut medication-documentation misses at handoff."
- What you want: "Looking for a charge-nurse role in a teaching hospital."
Examples by situation
The shape stays the same; the proof changes with what you actually have.
- Career changer: "Operations coordinator moving into data analysis. Built the scheduling workbook three warehouses now use, and completed a SQL and Python certificate."
- Recent graduate: "Mathematics graduate with a focus on applied statistics. Dissertation modelled commuter demand for a regional transport authority; looking for a first analyst role."
- Returning after a break: "Project manager returning after two years of family care. Previously delivered three system migrations for a 200-person company; available full time from March."
- Overqualified applicant: "Operations manager with twelve years in logistics, applying for a hands-on coordinator role. Deep experience in carrier negotiation and route planning."
- Contractor: "Interim finance consultant, six consecutive engagements in manufacturing. Specialises in cleaning up reconciliations after an ERP migration."
- Internal promotion: "Support team lead applying for the service manager role. Ran the queue redesign that cut first-response time and coached four new starters."
What to cut
Every phrase below has been read a thousand times and no longer carries information. They also cost you the two lines you need for the proof.
- "Results-driven", "detail-oriented", "passionate", "proven track record".
- "Seeking to leverage my skills in a dynamic organisation".
- A restatement of the job title you already listed.
- Your address, your age, your marital status, your photo — in most markets these invite bias rather than prevent it.
When to skip the summary entirely
If you are applying through a portal that parses the page, a summary is optional — the sections below already carry the facts. Skip it when your strongest evidence is visual (a portfolio), when you have under a year of experience and nothing to prove yet, or when the only thing you can write is a sentence of adjectives.
Questions about this page
- How long should a resume summary be?
- Two to three lines, roughly 30 to 50 words. Anything longer is a cover letter, and a reader deciding whether to continue will skim past it.
- Should the summary be written in first person?
- Both work, but fragments without "I" are the convention: "Registered nurse with six years…". Pick one and stay consistent across the page.
- Does the summary change for every application?
- The last line should — the role you want and the domain. The proof line only changes when a different achievement is more relevant to that posting.