The resume summary is usually wasted space
Three lines of prime real estate, usually spent saying nothing.
ResumeOn TeamResume craft
The three lines at the top of a resume are the most valuable space on the page, and most of the time they say nothing. "Results-driven professional with a passion for excellence" tells a reader only that you have seen other resumes.
Why the generic version fails
A summary is read in about four seconds, against a specific role. Adjectives do not survive that. "Detail-oriented team player" is a claim anyone can make, so a reader skips it and goes to your job titles, which is where they were headed anyway.
If deleting your summary would lose the reader nothing, it was costing you three lines.
What earns the space
A summary works when it answers the only question a reader has at that moment: what kind of candidate is this, and are they roughly the right size for this job. Three things do that:
- What you are. The role, not the aspiration. "Backend engineer" beats "technology enthusiast".
- The scale you work at. Team size, traffic, budget, or years. Numbers place you instantly.
- The one thing you want remembered. Usually your strongest, most relevant result.
A good summary is a claim a reader can check further down the page. A bad one is a claim nobody could check at all.
Before and after
| Version | Text |
|---|---|
| Generic | Results-driven engineer with a passion for building great products |
| Specific | Backend engineer, six years on payments systems. Cut checkout failures 40 percent at a 2M-user marketplace |
The second is shorter and says more. It also gives an interviewer an obvious opening question, which is usually a good thing.
When to leave it out
Skip the summary if you are early in your career and it would only restate your most recent title. In that case the space is better spent on an extra bullet under a real job. A summary earns its place when your history needs framing, not when it needs padding.