Writing a professional summary that works

What a summary is, and is not

A summary is not an objective. Objectives describe what you want ("Seeking a challenging role in a growth-oriented company"). Summaries describe what you offer. The second is useful to a reader. The first is not.

A summary is also not a biography. Two to three sentences, no more. Anything longer is not being read.

A simple formula

Most strong summaries follow the same three-part structure:

1. What you are: role and years of experience.
2. What you do best: one or two specific strengths.
3. What you have delivered: one concrete outcome with a number if possible.

Example: "Product manager with six years of experience in B2B SaaS. Specialised in turning ambiguous customer problems into shipped features. Most recently led the redesign of an onboarding flow that raised week-one retention by 22%."

Examples by career stage

Recent graduate

"Computer science graduate with three internships across fintech and developer tooling. Strongest in backend systems and developer experience. Built and shipped an internal CLI used by 40 engineers at my last internship."

Mid-career professional

"Marketing manager with eight years of experience in consumer brands. Focused on lifecycle marketing and paid acquisition. Managed a $2.4M annual budget and grew email-attributed revenue by 37% year over year."

Senior leader

"Engineering leader with twelve years of experience across infrastructure and platform teams. Have scaled organizations from 15 to 90 engineers while reducing incident response times by roughly half. Most recent role owned a $30M annual infrastructure budget."

Career changer

"Former journalist moving into product management. Ten years of experience finding, framing, and telling stories for large audiences. Strongest in user research and turning qualitative insight into shipped features."

Common mistakes

• Adjectives without evidence. "Dynamic", "results-driven", "passionate" — none of these are facts.
• Buzzwords. "Synergy", "leverage", "transformational". Replace with the specific thing you mean.
• Third person. Write in first person without pronouns: "Product manager with..." not "John is a product manager".
• Long sentences. If a sentence has more than one comma, split it.
• Generic outcomes. "Improved processes" is not a fact. "Reduced onboarding time from 6 weeks to 10 days" is.

Tailoring for each application

The summary is the one section worth rewriting for every application. Change the emphasis — which strength comes first, which outcome is included — to match what the job is asking for. Everything else in the resume can stay stable.