A summary that says 'results-driven professional with passion for excellence' is a score hit. A summary that names your level, years, domain, and most defensible outcome is the line a recruiter copy-pastes into the hiring manager DM.
Level: Senior, Staff, Principal, Director, VP, Head of. Years of experience: 5+, 9+, 14+. Domain: backend at scale, fintech, B2B SaaS growth, K-12 education, oncology nursing. Most defensible outcome: the line a board member or hiring manager would underline.
Skip anything that doesn't fit one of those four buckets. 'Strong communicator', 'team player', 'passionate about X' are all noise. They read like CV padding.
Each summary names level, years, domain, and a defensible outcome.
Recommended above mid-career (4+ years of experience). Below that, an Objective is dated and a Summary often reads thin. Lead with experience instead.
Two to four lines. Long enough to name level, years, domain, and outcome. Short enough that the recruiter reads it before scanning to the experience section.
Implicit first person. Skip the 'I' pronoun. 'Senior backend engineer with 9 years' reads cleaner than 'I am a senior backend engineer with 9 years'.
Summary names what you've done and the level you're at. Objective names what you want next. Objectives are dated; use a summary instead, and let the cover letter handle the 'what I want next' framing.
Yes, organically. Name the technologies, methodologies, or domains the JD asks for. Don't stuff. The ATS keyword filter counts hits across the document; a clean summary contributes naturally.
Free. See how it parses and how the keyword density reads.
Check my CV →