How to Write a Resume Summary That Actually Gets Read
Two or three sentences at the top of your resume. Done well, it hooks the recruiter in eight seconds. Done badly, it wastes a third of the only real estate you have.
The resume summary is the first thing a recruiter reads, and for a non-trivial number of your applications, the only thing they read. Get it wrong and the rest of the page is wasted. Get it right and you earn the next twelve seconds.
What a resume summary actually is
Two to three sentences, top of the page, in your own voice. Not a list of skills. Not a bullet-pointed paragraph of buzzwords. Not "seeking opportunities to leverage synergies." It's a compressed narrative: who you are professionally, what you've shipped, what you're good at.
The three rules
- Lead with the outcome, not the title. "Built the payments layer that processes $200M/year" beats "Senior Engineer at Acme."
- Be specific. "Shipped the disputes engine now used by 40% of enterprise customers" beats "experienced in backend engineering."
- Omit what everyone else also claims. "Team player, hard worker, results-oriented" is noise — the recruiter has seen it 10,000 times this month.
Before and after
Weak summary (actual average)
Before
Hard-working software engineer with 8 years of experience looking for a challenging role at a fast-growing company. Team player with strong communication skills and a passion for technology.
After
Senior engineer, 8 years shipping payments and identity infra at scale. Built the idempotency layer now handling 14M/day charge retries at Stripe. Rust and Go; bias for small diffs and honest estimates.
Tailor it to the role
Every job you apply to should have its own summary. Five minutes of editing your top three lines is the highest-leverage change you can make to a resume. If the JD mentions "distributed systems," and you genuinely have that experience, the word should appear in your summary.
Common mistakes
- Writing in the third person ("John is a motivated engineer…") — it reads like a press release
- Including your objective ("seeking a role where I can…") — recruiters don't care about your goals, they care about what you bring
- Listing every skill you've ever touched — that's the Skills section's job, not the summary's
- Opening with a cliché ("Passionate professional…") — instantly tunes recruiters out
Write less than you think you should
Recruiters spend an average of 7.4 seconds on the initial scan. If your summary runs five lines, they're skipping it. Keep it to three tight lines. If you have one killer fact — "rebuilt the search engine, cut latency 62%" — sometimes one sentence is enough.
Ready to put this into practice?
Build a one-page resume that enforces these rules for you — AI bullet rewriter, ATS match, forced one-page layout.
Try onepage.bio — free