Resume summary guide

What a professional summary is for

A professional summary is a short paragraph at the top of your resume that answers three questions in order:

1. Who are you? Your role and years of experience.
2. What do you specialise in? The specific slice of your field where you are strongest.
3. What is one concrete thing you have done? A proof point with a real number or outcome.

That is the entire structure. Two to four sentences. If you cover those three things, you have written a good summary. Everything else is decoration.

The structure, in detail

Let's take each sentence apart.

Sentence one: role and years

This is the sentence recruiters read to decide whether you are the right level. It should be specific enough that a recruiter can immediately say "yes, we are looking for someone like that" or "no, that is not our level".

Examples:

• “Backend engineer with 8 years of experience building payment systems.”
• “Product designer with 6 years of experience shipping data-heavy B2B interfaces.”
• “Operations executive with 18 years of experience scaling technology businesses.”
• “Final-year Computer Science student graduating with predicted First Class Honours.”

Notice that each one names the field and, where relevant, the environment. “Backend engineer” is vague; “backend engineer building payment systems” tells the recruiter you have worked on the kind of problem they might be hiring for.

Sentence two: specialisation

This sentence narrows the field further. It names the thing you are unusually good at, or the approach that defines your work.

Examples:

• “Specialises in design systems, accessibility and research-led iteration.”
• “Particular strength in post-merger integrations and organisational redesign.”
• “Focused on distributed systems reliability and observability.”
• “Comfortable owning services end-to-end, from schema design through on-call.”

The point of this sentence is to give the recruiter something specific to remember you by. Candidates who specialise are easier to place than candidates who are merely competent at everything.

Sentence three: one concrete proof point

This is the sentence that separates a strong summary from a weak one. It should be a real number, a real scope or a real outcome — not a generic claim about your working style.

Examples:

• “Led the migration of the payments ledger to a sharded design serving 12M events per day.”
• “Redesigned the reporting dashboard, cutting time-to-first-insight from 4 minutes to under 40 seconds.”
• “Rebuilt the operating model across 6 countries, reducing overhead from 41% to 28% of revenue.”
• “Built a real-time collaboration tool used daily by 30 students during testing.”

If you have three or four strong proof points, use the one most relevant to the role you are applying for. You do not need to include all of them — that is what the experience section is for.

Before and after: five real rewrites

Each pair below takes a common weak summary and rewrites it using the three-sentence structure. The content is the same; the presentation is different.

1. Software engineer

2. Product designer

3. Marketing manager

4. Graduate

5. Career changer

Phrases to avoid

These phrases appear on so many resumes that they have stopped carrying meaning. Cut them and replace them with something specific.

• “Passionate about…” — show passion through the work, not the adjective.
• “Results-driven” — every professional is results-driven by definition.
• “Team player” — say what you actually did to help a team.
• “Hard-working” — this is what a resume is supposed to demonstrate.
• “Detail-oriented” — say what kind of detail you manage and to what end.
• “Dynamic environment” — meaningless phrase, appears on thousands of resumes.
• “Proven track record” — say what you proved.
• “Seeking an opportunity to…” — the resume is not a cover letter.
• “Excellent communication skills” — say what you communicated and to whom.
• “Creative problem solver” — describe a problem you solved.

When to skip the summary

A summary is optional. Two situations where it is better to leave it out:

• You cannot write one with concrete proof. A weak summary is worse than no summary because it wastes the first ten seconds of the recruiter's attention.
• Your resume is one page and already full. If every section is packed and the summary would push the resume to two pages, cut the summary rather than cut the experience.

How long should it be?

Two to four sentences. Roughly 40 to 100 words. Shorter and it does not say enough; longer and recruiters stop reading.

If you are at two sentences, the first is role and specialisation, the second is the proof point. If you are at four sentences, the first is role and years, the second is specialisation, the third is a proof point, and the fourth is a second proof point or a scope statement.

The bottom line

A strong summary does three things in three sentences: names your role, names your specialisation and gives one concrete proof point. Write that, cut every adjective that does not earn its place, and the first line of your resume will start working for you.