Summary vs objective: which do you need?
Resume summary: 2–4 sentences at the top of your resume that describe who you are professionally, what you're best at, and what you're looking for. Written in third-person present tense (no "I"). Best for: experienced candidates (3+ years), career continuers, people who know what role they want.
Resume objective: 1–2 sentences describing what you're hoping to achieve in the role. Written from your perspective. Best for: career changers (where the objective explains the pivot), new graduates with no professional experience, people returning to the workforce after a long gap.
The reason summaries have largely replaced objectives is that objectives are employer-focused only on the candidate's desires, while summaries lead with value to the employer. Most hiring managers prefer summaries for anyone with relevant professional experience.
The 3-sentence summary formula
A strong summary answers three questions in order:
1. Who are you professionally?
"[X]-year [role/specialty] with expertise in [domain/industry]..."
2. What's your strongest evidence of impact?
"...including [quantified achievement or career highlight]..."
3. What are you seeking / what value do you bring to this role?
"...now seeking a [target role type] where I can [specific value you bring]."
Example (software engineer, 7 years):
"Software engineer with 7 years of experience building scalable backend systems in Python and Go. Reduced API latency by 60% at [Company] by re-architecting the data pipeline. Seeking a senior engineering role on a product-focused team where reliability and performance are first-class concerns."
Three sentences. Specific experience level, specific skills, one quantified achievement, one clear direction.
What to avoid in your summary
Fluffy adjectives. "Dynamic," "passionate," "results-driven," "motivated self-starter," "detail-oriented" — these words are in almost every resume summary and communicate nothing. Every candidate describes themselves as passionate and results-driven. Remove them all.
First-person pronouns. Don't start with "I am a..." The convention for resume summaries is omitting the subject — "Software engineer with 7 years" not "I am a software engineer with 7 years."
Generic statements. "Excellent communication skills" and "strong team player" are hollow without evidence. If you're going to mention communication skills, demonstrate them: "Presented quarterly product roadmap to a 200-person company all-hands."
Restating your job title and years without adding context. "Marketing professional with 5 years of experience" tells the recruiter nothing more than your job title and tenure already do. Use those sentences for something with more signal.
Making it about what you want. The summary should lead with what you offer — not what you're looking for. "Seeking a challenging role" is the weakest possible opening.
Tailoring the summary to each role
A generic summary is better than a bad summary, but a tailored summary is better than a generic one. For each application, spend 5–10 minutes adjusting your summary to reflect the specific role and company.
Swap in keywords from the job description. If the JD says "cross-functional collaboration" and you have experience with that, mirror the language.
Adjust the achievement you lead with. If the role emphasises revenue growth, lead with a revenue achievement. If it emphasises technical depth, lead with a technical achievement.
Adjust the "what I'm seeking" sentence. Name the specific type of role or challenge described in the JD. This signals to the recruiter that you read the description — not just sent a generic application.
The LoopCV tell-me-about-yourself generator can help you draft and tailor both written summaries and verbal interview answers from the same inputs.
Summary examples by seniority level
Entry level (0–2 years, recent graduate):
"Marketing graduate with internship experience in content creation and social media management at a mid-size B2B SaaS company. Grew Instagram engagement by 34% over a 3-month campaign. Seeking a content marketing coordinator role where I can develop full-funnel campaign experience."
Mid-level (4–7 years):
"Product manager with 5 years of experience shipping consumer mobile features at growth-stage startups. Led the payments flow redesign that increased checkout completion by 18% and contributed $2.4M in additional annual revenue. Seeking a senior PM role on a consumer product team."
Senior level (10+ years):
"Engineering leader with 12 years of experience building and scaling backend infrastructure for consumer internet products serving 10M+ users. Grew and managed a team of 22 engineers across 3 time zones at [Company]. Looking for a VP Engineering role at a Series B or C company building for scale."