How to write a resume summary that gets read
4 min read
A resume summary is the first thing a recruiter reads and often the only thing they read before deciding whether to continue. Most summaries waste it on adjectives. A good one is closer to a headline than a personal statement.
What it is for
The summary's job is orientation. Before reading your history, the reader wants to know three things: what you are, how senior, and in what domain. Answer those and everything below has a frame to hang on.
It is not a career objective. Objectives describe what you want; a summary describes what you offer. The reader is not yet invested enough to care about your goals.
A structure that works
Two or three lines, in this order: your role and years of experience, your strongest domain or specialisation, and one concrete proof point.
For example: 'Senior frontend engineer with 8 years building accessible, high-performance web applications. Specialises in design systems and Core Web Vitals work; led a rebuild that cut load time 48%.' Every clause earns its place.
Words to cut
Anything that every candidate claims and none can evidence contributes nothing but length.
- Hard-working, detail-oriented, results-driven, dynamic, passionate.
- 'Proven track record' with no number attached to it.
- 'Team player with excellent communication skills.'
- Third-person self-reference, and 'I' - write it as clipped fragments instead.
Tailor this part above all
If you change one thing per application, change the summary. Naming the target role in the first line - the same words the posting uses - is the cheapest, highest-impact edit available, for both the human and the keyword search.