How to Write a Professional Summary
3 min read·Updated 2 Nov 2025
The summary is the most-read and worst-written part of a CV. It is read because it is at the top; it is badly written because most people fill it with adjectives about themselves rather than facts about their work.
A good summary answers one question: why is this person plausible for this job? Three or four lines is enough, and the test of every line is whether a competing candidate could have written it too.
What a summary is for
It is not a biography and it is not a statement of ambition. It exists to give a reader, in a brief first look, enough to decide to keep reading.
That means it should contain: what you do and at what level, the strongest concrete fact about your recent work, and — if you are changing direction — a one-clause explanation of the pivot.
A method that works
- Write one sentence describing what you do and how long you have done it, naming the specific discipline rather than a generic title.
- Write one sentence containing the single most impressive verifiable thing from your last two years. A number, a scale, a named system, an outcome.
- Write one sentence about what you bring that the advert is asking for, using the advert's own vocabulary where it is honestly true of you.
- Delete every adjective that is about you rather than about the work. "Dynamic", "passionate", "results-driven" and "detail-oriented" all go.
- Read what is left. If it could describe five other applicants, the specific fact in step two is not specific enough.
Worked example: a mid-level developer
Weak
A passionate and detail-oriented software developer with a proven track record of delivering high-quality solutions. Excellent communicator and team player seeking a challenging new opportunity.
Stronger
Front-end developer with four years building customer-facing React applications in TypeScript. Most recent work covers a shared component library used by three product teams and a performance programme that halved load time on the highest-traffic page. Comfortable owning a feature from design review to production rollout.
The first could be about anyone. The second names the technology, the scale, a measurable result and the level of ownership — four things a hiring manager can act on.
Worked example: a career changer
Weak
Motivated professional looking to transition into data analysis. Fast learner with transferable skills and a passion for working with data.
Stronger
Pharmacy technician moving into healthcare analytics. Six years managing stock and dispensing data across four sites, including the reporting that identified £40k of annual wastage in short-dated stock. Completed the Google Data Analytics certificate and now working in SQL and Power BI daily.
A pivot needs evidence that the new skills are real and that the old ones transfer. This gives both, and the domain knowledge becomes an advantage rather than something to apologise for.
The three ways summaries fail
- Adjective stacking. A list of qualities you claim to have, with nothing behind any of them. Every reader discounts these entirely.
- Aspiration instead of evidence. "Seeking a challenging role where I can grow" tells the employer what you want; they are reading to find out what you offer.
- Restating the CV. A summary that lists your last three jobs is not a summary, it is a duplicate. It should say something the rest of the document does not.
When to leave it out
If you are a recent graduate with no work history, a summary has very little to summarise. A short profile stating what you have studied and what you are looking for is more honest, and shorter.
If you are applying through a form that already asks for a personal statement, do not repeat it. Use the space for experience instead.
Questions
Should the summary be tailored to each application?
How long should it be?
Should I write it in the first person?
The same structure, applied to a field
Each of these works through a complete fictional CV for that profession, including the conventions where the general advice above does not hold.
- AI EngineerA CV for engineers building products on top of language models, where evaluation and cost control are the hard parts.
- Banking ProfessionalA retail and commercial banking CV built around portfolio size, credit quality and regulatory conduct.
- Mobile App DeveloperA mobile CV that names shipped apps, store metrics and the platform constraints you have actually worked around.
Put this into practice
The editor keeps your CV as structured content, so the section order and wording decisions in this guide are easy to apply and easy to change again.