A resume summary works when it follows one formula: lead with your title and years in the domain, follow with two quantified achievements that prove scope, and close with the skills that map to the target job description. That's it. A summary that opens with 'results-driven professional' and lists soft adjectives tells the recruiter nothing; a summary that opens with 'Backend engineer with 7 years scaling Go services, cutting p99 latency 40% on an 8K rps payments platform' tells the recruiter exactly what you've done and whether to keep reading. The tailoring guide covers how to fit a summary to each application; the examples below show the formula in action across roles. Role names link to the matching resume guides by role, where you'll find the JD keywords each summary should mirror.
The formula
Every strong summary has four components in this order. First, your title and years: '[Role] with [N] years in [domain].' This anchors the recruiter — they know within the first five words whether you're at the level they're hiring for. Second, your two strongest quantified achievements: pick the outcomes that map most directly to the JD's priorities, and attach numbers (scope, result, or both). Third, the headline skills the JD asks for, written in the JD's exact terms — this is where the ATS keyword match happens. Fourth, optionally, one line on what you're looking for in the next role, which signals direction without taking up much space.
The components are deliberately ordered by what a recruiter scans for in those first six to eight seconds. Title and years tell them if you're roughly the right seniority. Quantified achievements tell them if you've done work at the scale they need. Skills tell them if you have the specific tools their team uses. Direction tells them if your trajectory aligns with the role. Get all four in two to four lines, and the summary does its job: it earns the recruiter's attention for the rest of the page. Anything that doesn't serve one of those four jobs — adjectives, mission statements, hobbies — is padding and should go. Find the right keywords for your target role before you draft the skills line.
Examples by role
Each example below is a fictional person written to show the formula in action. Read the example, then the one-line note on why it works, then adapt the structure to your own role and outcomes. The roles link to their role-specific resume guides so you can pull the exact ATS keywords for your target job.
Software engineer: Backend engineer with 7 years scaling Go services for high-throughput platforms. Cut p99 latency 40% on an 8K rps payments system by re-architecting the caching layer, and led the migration of 12 services to Kubernetes with zero customer-facing downtime. Strong in distributed systems, Postgres, and observability (Prometheus, Grafana). Why it works: title and years anchor the level; both achievements are quantified and map to a senior-backend JD's priorities (latency, scale, migration); the skills line mirrors exactly the hard-skill keywords a backend posting repeats.
Registered nurse: Registered nurse with 9 years in acute-care and telemetry units. Maintained a 98% patient-satisfaction score across two regional hospitals and reduced fall rates 30% on a 32-bed unit by leading a new hourly-rounding protocol. BLS, ACLS, and charge-nurse experience. Why it works: 'acute-care and telemetry' mirrors the JD's domain; both numbers (satisfaction, fall rate) are metrics nursing JDs name; certifications are listed by their official acronyms so they parse cleanly.
Marketing manager: Marketing manager with 6 years owning paid-acquisition pipeline across B2B SaaS. Grew qualified leads 65% QoQ by restructuring Google Ads and Meta Ads spend, and cut CAC 22% through landing-page A/B testing. Strong in HubSpot, Segment, and multi-channel campaign management. Why it works: 'paid-acquisition pipeline' mirrors the JD's outcome language; the metrics (pipeline, CAC, QoQ) are exactly what a growth-marketing JD leads with; the tools (HubSpot, Segment) appear by the product names the JD uses.
Data analyst: Data analyst with 5 years turning raw event data into decisions for product and growth teams. Built a self-serve dashboard in Tableau adopted by 40+ stakeholders, and identified a checkout funnel leak that lifted conversion 12% after the fix. SQL, Python (pandas), A/B testing, and dbt. Why it works: the audience ('product and growth teams') signals cross-functional scope; both wins are quantified and one names a business outcome (conversion); the skills line lists the exact tooling stack a modern analyst JD asks for.
Project manager: PMP-certified project manager with 8 years delivering cross-functional software launches on time and on budget. Led a 14-month, $2.4M platform migration from initiation to release with zero scope creep, and stood up the team's first Scrum-of-Scrums cadence across 4 squads. Strong in Jira, risk management, and stakeholder alignment. Why it works: PMP leads with a credential the JD explicitly asks for; both wins quantify scope (timeline, budget, squad count); the skills line pairs a tool (Jira) with the soft-skill verbs (risk management, stakeholder alignment) the JD repeats.
Customer service representative: Customer service representative with 4 years in high-volume SaaS support. Held a 4.6/5 CSAT across 60+ weekly tickets and cut average first-response time from 9 hours to 3 hours by writing a reusable macro library. Zendesk, Intercom, and basic SQL for ticket trend analysis. Why it works: 'high-volume SaaS support' mirrors the JD's environment; the metrics (CSAT, response time) are exactly what support JDs name; the macro-library win shows initiative without overstating seniority.
Teacher: State-certified teacher with 11 years in 4th and 5th-grade classrooms. Lifted district standardized math scores 18% over two cohorts by introducing a small-group rotation model, and mentored 6 student teachers through their practicum year. Strong in differentiated instruction, project-based learning, and family communication. Why it works: 'state-certified' mirrors a credential JDs require; the score lift is quantified and tied to a specific intervention (rotation model); the mentoring line signals leadership without claiming an administrative title.
Sales representative: Enterprise sales representative with 6 years closing SaaS deals in the 6-figure range. Achieved 118% of quota three years running and grew the financial-services vertical from $0 to $1.8M ARR by landing 3 named-account logos. Salesforce, MEDDPICC, and outbound prospecting. Why it works: '6-figure range' quantifies deal size, which enterprise JDs screen for; the quota and ARR numbers are the metrics a sales JD leads with; the methodology (MEDDPICC) is named verbatim because sales JDs name it verbatim.
Summary vs objective
A summary describes what you've done and what you can do — it's outcome-anchored and works for almost every candidate with experience. An objective describes what you're looking for — 'Seeking a senior backend role where I can scale distributed systems' — and works mainly for new graduates, career changers, and anyone whose past titles don't obviously map to the role they're targeting. For everyone else, the objective is dead weight: it tells the recruiter what you want, which they already know (you applied), instead of telling them what you can do, which is what they're scanning for.
The line between them blurs when you tailor. A tailored summary ends with a forward-looking clause that does the work an objective used to do — 'Strong in distributed systems and looking to bring that to a platform team scaling 10x' — without the filler of a standalone objective. Use a pure objective only when your past titles genuinely don't signal fit (career changer, new grad with no relevant titles) and you need one sentence to frame the pivot. Otherwise, summary wins, and the tailoring guide shows how to point a summary at a specific JD without rewriting it from scratch.
Tailoring your summary to each JD
A summary that isn't tailored to the JD is the most common reason an otherwise strong resume gets skipped. The fix is mechanical: read the JD, identify the two or three headline terms it leads with, and rewrite the skills clause and the achievements clause of your summary so they mirror those terms. If the JD leads with 'Go, Kubernetes, observability,' your summary names Go, Kubernetes, and observability — not 'backend infrastructure.' If it leads with 'pipeline, CAC, paid social,' your summary names pipeline, CAC, and paid social. Same person, same outcomes, different vocabulary.
Tailoring takes two or three minutes per application once you have a master summary drafted. Keep a master version with your strongest material, then for each application produce a tailored copy: swap the skills clause to mirror the JD's terms, reorder the two achievements so the one closest to the JD's priorities leads, and adjust the title clause if the JD uses a different title than yours ('Backend engineer' vs 'Platform engineer' — mirror the JD's title where your titles allow it). The JDMatcher matcher automates this — paste the JD, get the keywords mirrored into your summary and bullets in one pass — and the ATS keywords reference by role lists the terms parsers look for in your target job before you even open a specific posting.