The summary is the 2–3 lines under your name — and in a 7-second resume scan, it's one of the few things a recruiter actually reads. Done right, it answers "who is this and why are they relevant?" before they scroll. Done wrong, it's a paragraph of adjectives that answers nothing.
The formula
Every summary that works is some arrangement of four parts:
[Title + years] + [specialty or scope] + [one or two quantified wins] + [the skill the target job cares about most]
No "I". No "passionate". No "seeking a challenging position" — objective statements died a decade ago because they describe what you want, and the reader only cares what you can do.
Examples by role
Software engineer: "Backend engineer with 5 years building payment and billing systems in Java and Go. Cut checkout latency 40% and led a 3-service migration to Kubernetes with zero downtime. Strong in system design and observability."
Sales: "B2B account executive, 6 years in SaaS. Closed $1.4M ARR last year at 118% of quota; grew the mid-market segment from 12 to 47 accounts. Comfortable owning the full cycle from cold outreach to signature."
Customer support: "Support specialist with 4 years in fintech help desks. Held 96% CSAT across 8,000+ tickets and cut average first-response time from 4 hours to 40 minutes by rebuilding the macro library. Fluent in Zendesk and Intercom."
Marketing: "Growth marketer focused on lifecycle email and paid search. Doubled trial-to-paid conversion (11% → 23%) for a B2C subscription app and managed $35k/month in ad spend at 3.1x ROAS."
Project manager: "PM with 7 years delivering software projects for retail clients. Shipped 14 releases across 3 concurrent teams, 92% on schedule; introduced a risk process that cut late-stage scope changes by half. PMP certified."
Career changer: "Former teacher moving into instructional design, with the transferable core already proven: built a 12-module curriculum used by 400 students and raised course completion 28%. Trained in Articulate 360 and ADDIE."
The mistakes that make summaries invisible
- Adjective stacks. "Results-driven, detail-oriented professional" — contains zero information. Every trait you claim should be replaced by the number that proves it.
- First person. "I am a manager with…" — resumes are written in implied first person, no "I".
- One summary for every job. The last slot of the formula — the skill the target job cares about — changes per application. That's the 30-second edit most people skip.
- Length. Over 3 lines, it stops being a summary and starts being the thing people skip.
Tailoring the summary per job
The summary is prime keyword real estate for applicant tracking systems: it sits at the top of the document and recruiters' searches hit it first. Mirror the posting's job title and its top skill in your summary — honestly — and you cover both the human skim and the database query in one stroke. (Full method here: how to tailor your resume in 10 minutes.)