How to write a professional resume summary.

1. What a summary is for

A summary is not a mission statement. It's not a personality profile. It's a short pitch that answers a question the reader is already asking: who is this person, and should I keep reading?

It should do three things in two to four sentences:

1. Name your professional identity — what role or field you're in.
2. State your strongest evidence — a concrete achievement, technology, or experience that proves it.
3. State your target — what kind of role you're aiming for, in a way that matches the job you're applying for.

If a sentence in your summary doesn't contribute to one of those three things, cut it.

2. A three-line formula that works

Before showing examples, here's the underlying formula. Adapt it to your situation, don't copy it verbatim.

Sentence 1 — Identity: [Role] with [X years/months of experience] in [field/domain].
Sentence 2 — Evidence: [1–2 concrete things you've done, built, shipped, or led].
Sentence 3 — Target: Looking for a [role] at a [type of company or team] where [specific contribution].

It reads mechanical in the abstract, but when you fill it in with real content, it produces a summary that is informative rather than decorative.

Example, filled in:

Backend developer with four years of experience building payment and account systems for fintech products. Shipped a Stripe integration used by 40,000 monthly customers and reduced a legacy reporting pipeline's runtime by 60%. Looking for a mid-senior backend role where I can keep working on reliable, well-tested services.

That summary tells the reader: role, domain, evidence (two concrete achievements with numbers), and target. If you were hiring for a backend role, you'd keep reading.

3. Entry-level summaries

When you don't have much experience, the "evidence" sentence can come from education, projects, or internships — but it still needs to be concrete. Avoid "eager to learn" and "quick learner" entirely.

Weak:

Motivated recent graduate with a passion for technology and a strong work ethic, seeking an entry-level software development position where I can contribute and grow.

Stronger:

Computer science graduate with hands-on experience building full-stack web applications in React and Node.js. Completed three self-directed projects, including a task manager with authentication and a live demo. Looking for a junior developer role on a team that values clean code and code review.

The difference is specificity. The stronger version names the technologies, the projects, and the type of team.

4. Mid-career summaries

At mid-career, your strongest evidence is usually a specific outcome from a specific role. Name the outcome and the scale. Don't lead with your years of experience as if that's the main qualification — it's context, not the pitch.

Weak:

Experienced marketing professional with 8+ years of experience across multiple industries and a track record of delivering results.

Stronger:

Content marketing lead with eight years of experience in B2B SaaS. Grew organic traffic by 340% over two years at a mid-stage startup, and built a content team of four writers and one editor. Looking for a senior content role where I can own strategy end-to-end.

Notice the second version states the years of experience but leads with the outcome and the specific sector. That's what makes it useful for a hiring manager scanning fast.

5. Career-change summaries

When you're moving between fields, the summary is the single most important paragraph on the resume, because it's where you explain the connection between your past and your target. If you don't explain it, the reader will assume the transition is unexplained.

Structure for career changes: what you did before, what you've done recently that's relevant, and what you're aiming for now.

Example (teacher to UX designer):

Secondary school teacher moving into UX design after completing a nine-month design program and shipping three portfolio projects, including a literacy app for early readers. Bringing eight years of classroom experience — observing real user behaviour, simplifying complex information, and designing for people with very different needs. Looking for a junior UX role where research and design work closely together.

That summary does the work: it explains the transition, shows recent relevant activity, and frames old experience as an asset rather than a liability.

6. Phrases to cut

These phrases appear on thousands of resumes. None of them help you:

• "Passionate about..."
• "Results-driven professional"
• "Team player with excellent communication skills"
• "Seeking a challenging role where I can grow"
• "Proven track record of success"
• "Detail-oriented and highly motivated"
• "Self-starter who thrives in fast-paced environments"

None of these are actionable. They could appear on anyone's resume, so they distinguish no one. Replace every single one with a specific fact about your work.

7. Length and placement

Keep it to two to four sentences (typically 40–80 words). Longer summaries lose their impact and read like padding. Shorter summaries don't have room for the three lines the formula needs.

Place it directly below the header and contact details. It should be the first block of prose the reader sees. Don't wrap it in a box or hide it inside an "Objective" section — that label signals old-fashioned resume conventions to most readers.

8. Final checklist

• Does the summary name a specific role or field?
• Does it include at least one concrete piece of evidence (an outcome, a technology, a project)?
• Does it state the target role clearly?
• Have you removed every cliché phrase from the list above?
• Is it 40–80 words?
• Does it match the job you're applying for?