The resume summary section has a bad reputation because 80% of them are bad. The typical summary reads like it was translated from LinkedIn into English and back: "Passionate, results-driven professional with a proven track record of delivering high-impact outcomes in fast-paced environments."
That sentence could be about a dentist or a DJ. It says nothing. It's also the most prominent text on your resume — above the first job, before the eye leaves the top third of the page. Wasted.
A good summary does one thing: it tells the reader, in under three lines, who this resume is. Not your aspirations, not your personality, not your values. Who you are professionally.
When to skip the summary entirely
Counterintuitive but real: most resumes don't need a summary. If the top role on your resume already tells the story ("Senior Backend Engineer, Stripe, 2020–Present"), a summary that says "Experienced backend engineer" is redundant.
Skip the summary when:
- Your most recent role already telegraphs what you are.
- You have a clean, linear career story in a single field.
- You're applying for a role that is exactly the role you're doing now.
Write a summary when:
- You're switching industries, functions, or levels.
- Your job titles don't match what you actually do ("Software Engineer II" meaning "designs product, leads a team, writes code").
- Your recent roles don't obviously connect — and you want to draw the line before the reader does.
- You're early-career and the top of your resume is Education, not Experience.
If the reader's first glance at your resume doesn't immediately answer "what are they?", write a summary. If it does, skip it and reclaim the space.
The three-part structure
A summary that works has three components, in this order:
- Identity: what you are. Your role, level, domain.
- Proof: one specific achievement or scope marker.
- Direction: what you're optimizing for next (optional).
Identity: Staff product engineer, 10 years across consumer and B2B, strongest in real-time collaboration and sync.
Proof: At Relay, led the rewrite of the sync engine — p99 down 62%, unlocked multi-device editing across 4 surfaces.
Direction: Looking for a senior IC role where I can set technical direction on a small platform team.
In practice you merge these into two tight sentences:
Staff product engineer with 10 years across consumer and B2B, strongest in real-time sync. At Relay, led the rewrite that cut p99 latency 62% and unlocked multi-device editing across four surfaces — looking for a senior IC role setting technical direction on a small platform team.
Notice: no adjectives. "Passionate," "results-oriented," "proven track record" — all gone. The proof does the work the adjective tried to do, and does it better.
Examples across career stages
Recent grad (CS)
Recent computer science graduate seeking a challenging software engineering role where I can apply my skills and grow as a developer.
CS grad (UIUC '26) with systems coursework and two production internships — shipped a retry-safe queue library at Klaviyo, and owned the cache layer for a course-staff tool used by 40 TAs. Looking for a new-grad role on a platform or infra team.
Career switcher (journalism → UX research)
Looking to transition from journalism into UX research. While my background is in writing, I believe the skills transfer and I'm passionate about user experience.
Former investigative reporter (Bloomberg, 6 years) moving into UX research — 200+ long-form interviews conducted, two published data investigations, synthesis and pattern-finding are my day job. Recent UX research certification; freelance research for two seed-stage startups this year.
Mid-level marketer
Growth marketer, 6 years in B2B SaaS. Built lifecycle programs at two Series B companies — both saw demo-request growth north of 3× YoY under my ownership. Strongest at the intersection of lifecycle, content, and paid search. Looking for a Senior or Lead role with end-to-end demand-gen ownership.
Senior engineering manager
Engineering manager, 8 years leading teams of 6–14 across infrastructure and developer tools. Most recently rebuilt a struggling platform team at Segment — incident rate −72%, on-call attrition to zero, two promotions to senior in 18 months. Looking for a director-level role with a multi-team remit and a platform focus.
Returning to work after a break
Product designer, 9 years in consumer + SaaS (Meta, Notion). Recent two-year break for caregiving; returning with a refreshed portfolio and freelance work for two seed-stage startups. Looking for a Senior/Staff IC role focused on onboarding and activation.
Staff engineer with technical direction
Staff engineer, 14 years in backend and platform. Last four years focused on distributed storage — primary author of the multi-region replication layer at Vercel (16+ services, 200M+ requests/day). Looking for Staff/Principal IC work on a data or platform team — not management.
Writing yours now?
The LuckyResume editor has a Summary block built in — and the auto-fit page will keep everything on one page as you iterate.
"Objective" vs. summary vs. profile
Three terms, mostly the same idea, with subtle differences:
- Objective — what you want. ("Seeking a position where I can…") This form is out of fashion for good reason: it centers the candidate's wants, not the employer's needs. Skip.
- Summary — what you are, grounded in proof. The main form worth using.
- Profile — basically a summary with a different label. Fine.
Use "Summary" as your header, or skip the header and let the text run directly under your name.
Anti-patterns to avoid
The adjective parade
"Dynamic, innovative, results-driven self-starter with strong attention to detail." Delete every word of this. None are provable, and the reader tunes out by "dynamic."
The LinkedIn fanfiction
"I live at the intersection of creativity and strategy, building bridges between ideas and execution." Keep for LinkedIn if you must. Keep off the resume.
The "wants" summary
"Looking for a role that will challenge me and help me grow." This is about you, not them. A single line about what you're looking for next is fine at the end of the summary — not the whole summary.
The CV dump
A five-sentence summary that repeats your resume. The summary is a compression, not a preview. Say something the bullets don't.
The lie by omission
"Senior engineer with 15+ years of experience in distributed systems" — when 12 of those 15 years were in WordPress plugins and 3 were peripheral to anything you'd call distributed systems. The interviewer will find out in 10 minutes.
FAQ
How many lines should a summary be?
Two to three. Never more than four. If you're at four, cut; you're restating yourself.
Should I write it last?
Yes. The summary is an abstract, and you can't abstract a document you haven't written. Draft the bullets first, then write the summary.
Do I need to mention years of experience?
Usually yes, if it's a meaningful number. For senior candidates, "14 years" or "12 years" positions you; for mid-level, "6 years" does the same. For under 3 years, skip the count and let the bullets carry it.
Do I put it above or below contact info?
Below name, above Experience. Sometimes merged with a one-line role tag under the name. Never above name.
Does a summary help with ATS?
Marginally, through natural keyword density. Don't stuff it with keywords — the recruiter will notice before the ATS does. More on what ATS actually checks →
The short version
- Skip the summary if your top job already answers "what are you."
- If you keep one: identity, proof, direction. Two or three lines.
- No adjectives. Let the proof do the adjective's job.
- Write it last.