The summary is the first thing read after your name, and the last thing most people write — which is why so many of them are filler. Done properly it takes three lines and tells the reader what you are, at what level, and why you are worth thirty more seconds.
Summary or objective?
A summary describes what you bring; an objective describes what you want. Employers are reading to answer their own question, so the summary wins in almost every case. The narrow exception is a graduate or career changer with no relevant history, where a single line of direction genuinely helps — and even then, frame it around what you can already do.
The three-line structure
- Line one: your professional identity and level — the title you are applying for, plus years of experience.
- Line two: your strongest evidence, with a number in it.
- Line three: your focus or specialism, ideally echoing the posting's own language.
Results-driven professional with a proven track record of success seeking a challenging position where I can leverage my skills.
Senior data analyst with 7 years turning product and marketing data into decisions. Built the retention model that cut churn-forecast error 38% and own 30+ dashboards used daily by 200 stakeholders. Focused on experimentation and metrics design for subscription businesses.
Examples by situation
Experienced professional
"Project manager, PMP-certified, with 11 years delivering cross-functional programmes in aerospace and defence. Delivered a $14M systems-integration programme three weeks early and 6% under budget, leading a team of 35. Strongest on complex, multi-vendor delivery with hard regulatory deadlines."
Career changer
"Operations manager moving into product, with 8 years owning process and customer outcomes in logistics. Rebuilt the returns workflow used by 300 staff, cutting handling time 40% and complaints by half. Now applying that discovery-and-iteration approach to product roles in supply-chain software."
Recent graduate
"Computer science graduate (First Class, University of Manchester) with two internships in backend development. Built and shipped an internal API used by 40 colleagues during a six-month placement at a fintech. Looking for a backend role in a team that reviews code seriously and ships weekly."
Common failures
- Adjective stacking — "dynamic, motivated, detail-oriented" — which asserts what evidence should demonstrate.
- Writing in the third person. It reads as a biography written by someone else.
- Six lines. It is a summary; if it needs a paragraph, it needs an edit.
- Naming a target role that does not match the job you are applying for. Retarget it every time — this is the one section that must change per application.