How to write a resume summary that recruiters actually read

The resume summary is the most expensive 50 words on your resume. Recruiters spend their first few seconds on it — and that's the window where they decide whether to keep reading or move to the next candidate. Most summaries waste it on adjectives. Yours doesn't have to.

What the summary is actually for

Think of it as the answer to a single question: "If a recruiter only reads three sentences from this resume, what do they need to know to keep reading?" That's it. Not your life story, not your career philosophy. Three sentences that make a busy person want to spend another twenty.

The three-line formula that works

• Line 1 — Who you are: your role, your years of relevant experience, the kind of company you do your best work at. ("Senior product designer with 8 years shipping consumer fintech products at high growth startups.")
• Line 2 — What you're best at: the one or two things you'd want every team you join to use you for. ("Best at turning fuzzy product bets into shipped flows that move retention metrics.")
• Line 3 — What you want next: the role you're aiming for, written so it reads as direction rather than desperation. ("Looking to lead design on a 0-to-1 product team where I can own the craft bar end-to-end.")

Four phrases to delete on sight

• "Results-driven professional" — adds zero information; recruiters skip past it.
• "Proven track record" — every resume claims this; nothing differentiates.
• "Passionate about…" — passion is invisible on a page; show it through what you've actually shipped.
• "Seeking a challenging opportunity" — replace with the specific role you actually want.

What to do instead

Replace each of those phrases with a concrete fact. "Results-driven" → name a result. "Proven track record" → say what you have a track record of. "Passionate about" → name a thing you've actually built or led that proves the passion. The difference between a generic summary and a great one is almost always the substitution of facts for adjectives.

“If a recruiter could replace your name with a competitor's name and the summary still made sense, the summary isn't doing its job.”

A worked example

Before: "Results-driven product manager with a proven track record of delivering successful products. Passionate about user experience and seeking a challenging opportunity at a forward-thinking company."

After: "Senior PM with 6 years owning subscription products at consumer SaaS companies. Best at running pricing experiments — most recently raised ARPU 24% on a flagship product without dropping conversion. Looking to lead a 0-to-1 PM team building infrastructure for SMB owners."

Same person, same length. The first version could belong to anyone. The second version makes a recruiter want to know more — which is the whole point.