How to Write a Professional Summary

A 2–4 sentence opening that tells the ATS and the recruiter exactly what role you're targeting and why you qualify.

The summary sits below your name and above everything else. It's the second-most-read section after your most recent job — and the first place recruiters look when they're asking, "Is this person even in the right ballpark?"

David was a generalist project manager applying to both construction and SaaS roles with the same vague opener: "Results-driven professional seeking new challenges." It parsed fine. It matched nothing. After rewriting one sentence to name the target role and three tools from each posting, his callback rate on SaaS applications tripled — same experience, different framing.

Structure formula

Line 1: Title + years of experience + industry/domain
Line 2: 2–3 core competencies or technologies
Line 3 (optional): One measurable achievement or differentiator

Example (software engineer)

Software engineer with 6+ years building scalable web applications in fintech. Proficient in TypeScript, React, Node.js, and AWS. Led migration of monolith to microservices, reducing deployment time by 40% and improving uptime to 99.95%.

Example (marketing manager)

Marketing manager with 8 years driving B2B demand generation for SaaS companies. Expertise in content strategy, marketing automation (HubSpot, Marketo), and SEO. Grew marketing-qualified leads by 120% year-over-year while reducing cost-per-lead by 25%.

Writing rules

Third person without pronouns ("Experienced analyst…" not "I am an analyst…")
Tailor keywords to each job posting — mirror their language where honest
Keep to 50–80 words — dense paragraphs get skipped
Skip objective statements ("Seeking a challenging role…") — they date your resume