There's a section at the very top of most resumes — right below the contact info — that could be a genuinely powerful three seconds of selling yourself. Instead, for most people, it reads like this:
"Results-driven professional with 6+ years of experience in fast-paced environments, seeking a challenging opportunity to leverage my skills and contribute to a dynamic team."
That summary contains exactly zero information. It tells the reader nothing about what you do, what you've accomplished, or why they should keep reading. Every word in it could apply to literally anyone who has ever held a job.
And yet this is what most summaries say. Sometimes with the word "passionate" thrown in.
Why summaries fail
The generic summary exists because people are told they need one, they're not told what it should contain, and the path of least resistance is to write something that sounds professional without saying anything specific.
The other reason: people are uncomfortable with direct self-promotion. Writing "I increased revenue by $400K in my last role" feels braggy. Writing "results-driven professional" feels safe. But safe is invisible.
What actually works
A good summary answers three things in two to four sentences:
- 1What you do — your role, at what level, in what type of company or industry
- 2What you've achieved — one concrete, quantified result that establishes credibility
- 3What you're looking for — briefly, to signal alignment with this specific role
Before:
"Dynamic marketing professional with 4 years of experience in digital marketing, seeking to bring my passion for brand building to a growth-focused company."
After:
"Performance marketing manager with 4 years growing B2C SaaS brands. Scaled paid acquisition from $20K to $200K monthly while maintaining CAC under $35. Looking to lead performance marketing at a Series A–B company with a strong product."
The second version is specific, credible, and tells the recruiter immediately whether this person is relevant to the role. They don't have to hunt for the signal.
For new graduates
If you're early in your career and don't have big numbers to cite, the formula shifts slightly. Lead with what you studied or what you've built — projects, internships, relevant coursework. Then highlight two or three relevant skills that match the role. Then signal the type of work you're looking for.
You don't need a decade of experience to write a strong summary. You need specificity. "Recent CS graduate with internship experience in backend engineering, looking for a junior developer role at a product-led company" beats "passionate computer science graduate seeking opportunities to grow" by a mile.
The test
Read your summary and ask: could this describe someone other than me? If yes — it needs work. The goal is for a recruiter to read it and have an accurate, specific picture of who you are before they've read a single bullet point.
Most summaries fail this test. Fix yours and you're already ahead of most of the pile.