How to write a resume summary that gets read

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.

The formula behind every good one

Role and years, then domain, then a proof point, then what you are aiming at. Two or three lines, no pronouns, no adjectives that cannot be checked.

Operations manager with eight years in third-party logistics across the UAE and KSA. Cut warehouse pick times by a third on a 40-person floor. Looking for a regional operations role in e-commerce fulfilment.

Examples by situation

The shape stays the same; what changes is which part carries the weight.

• Graduate: Computer science graduate with a first in software engineering. Built a booking platform used by a local charity to replace phone bookings. Looking for a junior backend role in Python or Node.
• Career changer: Secondary teacher of nine years moving into instructional design, having built the digital curriculum used across a twelve-school trust. Certified in Articulate Storyline.
• Returning after a break: Finance manager with eleven years in FMCG, returning after a year of family care. Led a five-person team and closed month-end in three days. Available immediately.
• Senior: Engineering leader with fifteen years building payment systems, nine of them managing managers. Scaled a platform from 200 to 4,000 transactions per second and grew the team from 6 to 34.

What makes a summary useless

Three habits account for nearly every weak summary: describing traits instead of evidence, describing what you want instead of what you offer, and using words that every other applicant also used.

Hard-working, detail-oriented team player seeking a challenging opportunity says nothing that a recruiter can act on. If a sentence could sit on anyone else's resume, delete it.

Where the summary sits, and when to skip it

Put it directly under your contact details, above experience. It is the one part of the page you can be confident gets read, so it is the right place to set the frame for everything below.

Skip it only when you have almost nothing to summarise - a first resume with one part-time job is better served by using that space for education and projects.