What a summary actually does
A professional summary is two to four sentences that tell the reader three things: who you are, what you're good at, and what value you bring. It's not an autobiography. It's a positioning statement that sets expectations for the rest of the resume.
Recruiters typically scan a resume in six to ten seconds. The summary is where they decide whether to keep reading.
The four-sentence formula
- Sentence 1 — Role and years. "[Role] with [N] years of experience in [domain]."
- Sentence 2 — Focus. "Specialized in [area] with a track record of [specific outcome type]."
- Sentence 3 — Proof. One concrete achievement with a metric.
- Sentence 4 — Target. "Looking to [goal] in a [specific type of role/company]."
Adjust the order if you want to lead with the achievement. What matters is that the summary is specific, not generic.
Example: mid-level software engineer
Software engineer with six years of experience building production web applications. Specialized in backend APIs and distributed systems, with a record of improving performance on high-traffic platforms. Reduced average API response times by 38% at a company serving 2M+ monthly users. Looking to join a product-focused team where I can lead platform work.
Example: marketing manager
Marketing manager with seven years of experience leading demand generation and content programs in B2B SaaS. Owned a $1.2M annual paid budget, cutting cost per qualified lead by 45%. Comfortable leading small teams and collaborating closely with product and sales. Seeking a growth-focused role where I can build a pipeline engine from the ground up.
What to avoid
- Buzzwords without specifics — "results-driven professional with strong communication skills."
- Third person — write in first person with "I" implied, not "John is a developer who..."
- Multiple unrelated goals — pick one target and stick to it.
- Generic adjectives — "hardworking," "passionate," "dynamic."
- Long summaries — anything over four sentences gets skimmed and skipped.
When to use a summary vs an objective
Use a summary when you have direct experience in the role you're targeting. Use an objective when you're a recent graduate, changing careers, or returning after a break. The objective is forward-looking: "Seeking a role in X where I can apply Y."
Frequently Asked Questions
Do recruiters actually read the summary?
Yes. It's the most-read part of a resume after the name and job titles. Even a recruiter in a hurry will glance at the top three lines.
Should I include numbers in the summary?
At least one, if you have one that matters. Numbers are the fastest way to demonstrate credibility and separate yourself from candidates who only describe responsibilities.
Can I use the same summary for every application?
You can, but tailoring it for each role is worth the effort. Adjust the focus sentence and the target sentence to align with the specific job.
How long should a summary be?
Two to four sentences, or roughly 40 to 80 words. Anything shorter feels thin. Anything longer stops being read.