Resume summary examples and a formula that works
The summary is the first thing under your name. It has about five seconds to answer one question: is this person a fit for this kind of role? A good one is concrete, short and aimed at the vacancy. A bad one is a list of adjectives.
- Formula: role + scope or years + two to three strengths + one proof point.
- Two to four lines, no first-person pronouns, no empty adjectives.
- Mirror the vacancy's job title and core skills honestly.
- Rewrite it for each application; it takes five minutes.
The formula
A summary that works has four parts, in this order:
- Role and level: what you are, in the words of the target job ("Backend developer", "Senior accountant").
- Scope or experience: years, domain, team or budget size.
- Two or three strengths that match the vacancy: tools, methods, kinds of problems.
- One proof point: a number or outcome you can back up.
Write in implied first person: "Builds payment APIs in Go", not "I am a developer who...". Skip filler such as hard-working, motivated or passionate; show it through results instead.
Hard-working professional with excellent communication skills looking for new opportunities.
Customer support lead with 6 years in SaaS. Manage a team of 9, own escalations and the help center; raised CSAT from 88% to 94% and cut first-response time by 35% in 2024.
Ten examples by role
Adapt the shape, not the facts: swap in your own numbers and tools.
| Role | Summary |
|---|---|
| Software developer | Backend developer with 5 years in fintech. Build and run payment services in Go and PostgreSQL. Reduced p95 API latency from 480 ms to 190 ms and led migration of 3 services to Kubernetes. |
| Marketing manager | Performance marketer with 4 years in e-commerce. Run Google Ads and Meta Ads with a 120k EUR monthly budget; lowered cost per acquisition by 23% through creative testing and landing-page experiments. |
| Sales representative | B2B SaaS account executive with 3 years closing mid-market deals. Closed 112% of quota in 2024 with an average cycle of 38 days. Strong in discovery calls and multi-stakeholder negotiations. |
| Product manager | Product manager with 5 years in B2C mobile. Own roadmap and discovery for a 1.2M-user app. Shipped onboarding changes that lifted day-7 retention from 21% to 27%. |
| Data analyst | Data analyst with 4 years in retail. Build SQL and Tableau reporting for 200 stores and run A/B tests on pricing. Cut weekly reporting time from 10 hours to 2 through automation. |
| Project manager | Project manager with 7 years in construction and fit-out. Deliver projects up to 4M EUR on time and within 3% of budget, coordinating up to 30 subcontractors. |
| Accountant | Accountant with 6 years in manufacturing. Own month-end close, IFRS reporting and VAT filings for 3 entities; shortened close from 9 to 5 working days. |
| Designer | Product designer with 5 years in B2B tools. Lead research, UX and UI in Figma for a data-heavy platform; redesigned onboarding that cut time-to-first-value by 40%. |
| Graduate | Economics graduate with a thesis on retail pricing and two internships in analytics. Skilled in Excel, SQL and basic Python; built a forecasting model that cut inventory errors in a student project by 15%. |
| Career changer | Former teacher moving into customer success. Six years of training groups of 25 and explaining complex ideas simply; completed a CRM certification and supported onboarding for 40 customers in a volunteer project. |
Rewriting your own in five minutes
- Copy the vacancy's job title and its three most repeated requirements.
- Write one sentence: your role + years + domain.
- Add one sentence naming the two or three of your strengths that match those requirements.
- Add one proof point with a number from your best recent result.
- Cut every adjective that cannot be checked.
If the number is not exact, use an honest range or a rounded value ("about 40%") and be ready to explain how you measured it.
Paste a job link, add your resume and get a requirement-by-requirement report.
A formula you can reuse
[Role + years or level] in [domain]. [Strongest result with a number]. [Second proof or tool]. [What you are looking for, tied to this role].
Example: Customer success manager with six years in B2B SaaS. Kept net revenue retention at 118% across a 60-account portfolio and cut churn by a third. Skilled in onboarding design and renewal playbooks. Seeking a team-lead role in a growing SaaS company.
Summaries for different situations
| Situation | Emphasis |
|---|---|
| Career changer | Transferable results and the new target role |
| Recent graduate | Degree, projects, tools, readiness |
| Returning after a break | Core expertise and current readiness, not the gap |
| Senior leader | Scope, team size, budget, outcomes |
| Freelancer | Specialty, clients, results, availability |
Weak lines to delete
- Hard-working team player with excellent communication skills.
- Results-driven professional seeking a challenging position.
- Passionate about learning new things.
- Responsible for various tasks.
These could be written about anyone, which is why they carry no information. Replace each with a fact: a number, a tool, a scope.
Length, tone and tense
Two to three lines, about 40 to 60 words. Write in the implied first person without "I" if you like, in the present for what you are and past for what you did. Keep it free of adjectives you cannot prove. A good test: could a competitor's candidate write this exact sentence? If yes, make it more specific.
Check it against the vacancy
Underline the vacancy's top requirements and make sure two of them appear in your summary with proof. See tailoring and how to make a resume.
Common mistakes
- Using the objective-statement style ("seeking a challenging position") that describes what you want, not what you offer.
- Writing five or six lines. Three is the target.
- Listing generic traits (team player, detail oriented) without evidence.
- Using the same summary for every vacancy.
- Claiming seniority the rest of the resume does not support.
Check the match between your summary and a real vacancy with JobAny's resume analysis; it shows what a recruiter sees first on your page.
Check your resume against a real vacancy
Add your resume and a job link. JobAny shows which requirements are covered, what is missing, what a recruiter sees first and whether the file reads cleanly. Start costs $1, no subscription.
Frequently asked questions
Should I use a summary or an objective?
A summary. It says what you offer. An objective says what you want and rarely helps.
How long should a resume summary be?
Two to four lines, about 40 to 60 words.
Can I skip the summary?
You can if the top of your experience speaks for itself, but a targeted summary is the cheapest way to show the match in the first seconds.
Do I write it in first person?
Use implied first person without "I": "Manages...", "Built...".
What if I have no numbers?
Use scope (team size, number of clients, frequency) or speed and quality indicators, and be specific.
Should the summary be in first person?
Either works; most resumes omit I and use short phrases.
Should I include an objective?
Replace it with a targeted summary.
Is a summary needed on a one-page resume?
Yes if it is specific; otherwise skip it and use the headline.
How often should I rewrite it?
For each vacancy, at least lightly.
Keep reading
