The two-line summary at the top of a resume is one of the most over-debated and most poorly-written elements on the page. Some career advice tells you it's essential — your hook, your elevator pitch, the recruiter's first read. Other advice tells you to delete it entirely — recruiters skip it, ATS systems ignore it, it just takes up space that could go to bullets.

Both camps have a point. A strong summary earns its real estate. A weak one is space the recruiter has to wade through to get to the substance. The question isn't whether to include one — it's whether what you'd put there is strong enough to be worth the lines.

The case for a summary

The summary works when:

• You're a senior candidate and want to frame the read of your work history. A great summary tells the recruiter what story they're about to see in the bullets.
• You're a career changer and need to contextualize why your work history is what it is.
• You have a long career and the recruiter would otherwise scan for context they have to construct themselves from titles and dates.

In each case, the summary saves the recruiter mental work. They read two lines, form a picture, then read the bullets to verify. The bullets confirm the summary's claim, and the candidate moves up the shortlist.

The case against

The summary fails when:

• It's generic. "Results-driven professional with a passion for excellence" tells the recruiter nothing they didn't already assume from the fact that you applied. It's filler.
• It's a buzzword stack. "Cross-functional team player with strong communication and problem-solving skills." Same.
• It's contradicted by the bullets. "Senior leader" in the summary, junior individual-contributor work in the bullets. The mismatch tells the recruiter you're either inflating or aspirational.
• It's untailored. The same generic two lines on a resume sent to thirty different roles. Recruiters read enough resumes to recognize the pattern.

In each case, the summary is making the candidate look worse than the bullets do alone. Removing it is an upgrade.

Strong vs. weak — same person

The cleanest way to see the difference is with examples from real candidates:

Strong summary vs. weak summary

Same person, two attempts

Strong

• 'Senior product manager with 8 years building B2B SaaS, leading cross-functional teams through ambiguous problem spaces.'
• 'Backend engineer specializing in payment systems — shipped Stripe integration at three companies, owns the migration to event-sourcing.'
• 'Data analyst with 5 years in healthcare — built the patient-cohort dashboard now used by every clinical lead at the hospital.'

Weak

• 'Results-driven professional with a passion for excellence and a track record of success.'
• 'Highly motivated team player seeking new challenges to leverage skills and grow professionally.'
• 'Hardworking individual with strong communication and problem-solving abilities.'

The bullets on the right are what most resumes look like at the top. They're not lies — they're true descriptions of someone who's results-driven and a team player. They're just not informative. A recruiter reading them learns nothing about the candidate that helps them decide whether to keep reading.

The bullets on the left are the same length but deliver a specific picture: a role, a domain, a scope of work. The recruiter forms a mental shape of the candidate before they hit the work history.

How to write a summary that works

The four-step rewrite for any existing summary:

Rewrite your summary in four steps

Workflow

1. 01
   01
   Strip the buzzwords

   Cross out 'results-driven', 'passionate', 'highly motivated', 'team player'. They appear on every resume; they communicate nothing.

2. 02
   02
   State your role + specific scope

   Senior PM. Backend engineer. Data analyst. Then add the specific area: 'B2B SaaS', 'payment systems', 'healthcare analytics'.

3. 03
   03
   Add one concrete proof point

   A scope ('shipped X at three companies'), a scale ('5 years'), or an outcome ('built the dashboard now used by every clinical lead').

4. 04
   04
   Cut to two lines

   If it doesn't fit in two lines, you have two summaries fighting. Pick the stronger one. Aim for ≤ 30 words.

The hardest part is step 1 — actually deleting the buzzwords. Most candidates feel naked after stripping "results-driven, highly motivated team player" because the resulting sentence is shorter and feels less impressive. It isn't less impressive. It's specific. Specificity wins over volume of adjectives every time.

What a good summary scores on

When auditing your own summary, four dimensions decide whether it's earning the space:

What makes a summary score well

Anatomy

80/100

A summary that earns its space scores high on these four dimensions.

Role specificity25/25

Concrete proof point22/25

Tailored to target role18/25

Length discipline (≤ 30 words)15/25

The single highest-leverage one is role specificity. A summary that opens with a vague role title — "experienced professional" — is doing nothing for you. A summary that opens with a precise role and domain — "senior product manager building B2B SaaS" — has already done most of the work. The reader knows what they're looking at.

Concrete proof point is the second lever. One specific number, scope, or outcome elevates a summary from competent to memorable. The trick is to pick the proof point that matters for the role you're applying to, not the most impressive one in your career.

Tailoring is the cheapest move. The same summary across thirty applications is undermining each one. Two minutes of edits to align with the specific posting's emphasis is worth more than rewriting from scratch.

Length discipline is the test for whether you actually had a strong summary or padded it. A great summary is two short sentences. If yours is four lines, you have two summaries fighting. Pick the stronger one.

Specific summary patterns that work

A few templates, not as scripts but as shapes:

The role + scope + proof:

Senior backend engineer specializing in payment systems — shipped Stripe integration at three companies, owns the migration to event-sourcing.

Role (senior backend engineer), scope (payment systems), proof (specific work at companies). Twenty-eight words.

The progression:

Marketing leader who's grown through every channel from email to paid social to brand. Most recent role: scaling demand-gen at a $20M ARR B2B startup.

Role (marketing leader), scope (cross-channel), proof (specific scale + role context). Twenty-seven words.

The pivot:

Data analyst pivoting from healthcare to climate tech. Five years on patient-cohort modeling; recently shipped a methane-emissions dashboard that's now in production at two energy clients.

Role (data analyst), pivot (healthcare → climate), proof (specific projects on both sides). Thirty words.

The senior generalist:

Engineering manager with 12 years across infrastructure, payments, and consumer products. Built and managed teams of 4–18 across three startups.

Role (eng manager), scope (cross-domain), proof (team sizes + count). Twenty-five words.

In each case, the summary picks one or two specific facts and puts them in front of the recruiter immediately. Buzzwords are absent. The reader knows what they're looking at within five seconds.

When to skip the summary entirely

A few cases where omitting the summary is the right call:

• Early career, strong recent role. If your most recent job tells the story for you (Junior PM at notable company), the bullets do the work. Adding a summary just adds words.
• Highly technical role with a clear stack. A skills section + recent project + work history can be more useful than two lines of prose framing.
• One-page resume that's tight on space. If you need every line for bullets, the summary is the cut.
• You can't write a strong one. If your draft summary is generic-sounding even after the four-step rewrite, the candidate is better off without it. A bad summary actively subtracts.

The default for most senior candidates is "include a strong summary." The default for entry-level and highly technical candidates is "skip it unless you have something specific to say." The bad outcome is a generic summary on every resume — that's worse than either alternative.

A test before you submit

Read your summary aloud, then read the same words about a stranger's resume. Does it sound like a real person describing their work? Or does it sound like every other resume in the pile?

If it sounds like every other resume, rewrite or cut it. The summary should be the most distinctive sentence on the page, not the most generic.