A resume summary is the two or three sentences at the top of your resume that a recruiter reads before deciding whether the rest is worth their time. Most are useless - generic enough to apply to anyone, saying nothing that couldn't be inferred from the job title alone. Here's how to write one that isn't.
The formula: who you are + what you've done + what you're aiming for
A workable structure: your professional identity (role + years or level of experience), one concrete highlight or specialization, and what you're looking for or bring to the specific role. Kept to two or three sentences, not a paragraph.
Generic (avoid): "Hardworking and dedicated professional seeking a challenging position where I can utilize my skills and grow within the company."
Specific (better): "Marketing coordinator with 3 years of experience running paid social campaigns for e-commerce brands, including one that grew a client's Instagram-driven revenue by 34% in six months. Looking to move into a broader growth marketing role."
The difference isn't length - it's that the second version contains information a reader can actually use to judge fit.
Match the summary to the job you're applying for, not a single fixed version
If you're applying to meaningfully different types of roles, your summary should shift emphasis accordingly - the same experience can be framed toward a "growth marketing" angle or a "brand marketing" angle depending on what the specific posting emphasizes. This is one of the few sections worth actually customizing per application rather than reusing verbatim.
Skip these words entirely
"Hardworking," "team player," "detail-oriented," "results-driven," "passionate," "dynamic" - these appear on a large share of resumes precisely because they're vague enough to claim without evidence. If you want to communicate that you're detail-oriented, demonstrate it through a specific accomplishment instead of asserting the adjective.
If you don't have much experience yet, lead with what you've built or studied
See our fresher resume guide for a fuller version of this, but the short version: "Computer science graduate who built three full-stack applications during coursework, including one deployed with 200+ active users" works better than any variation of "seeking an entry-level opportunity."
A quick before-and-after checklist
Before you finalize your summary, check it against these:
- Could this sentence apply to almost anyone in your field? If so, cut it or make it specific.
- Does it contain at least one concrete number, tool, or outcome?
- Does it match the language of the specific job description you're applying to?
Frequently asked questions
Is a resume summary required? Not strictly, but a strong, specific one adds real value at the top of the page - the alternative is usually a generic objective statement, which adds less.
How long should it be? Two to three sentences, or a short 3-4 line paragraph at most. It's a preview, not a cover letter.
Should I write my summary first or last? Last - it's much easier to summarize your resume accurately once the rest of it (experience, skills, projects) is already written.
Once you've drafted a summary, CVIEX's ATS Resume Checker will tell you whether it's actually hitting the keywords a specific job posting is looking for.