TL;DR
Write 2-4 sentences using this formula: job title + years of experience, then your top 2-3 skills or specialisations, then what you bring to this specific employer. Mirror the keywords from the job description. Skip personal pronouns and generic phrases like "hard-working team player." A strong summary gives a recruiter enough to pass you in seconds; a weak one gives them a reason to move on.
The resume summary sits at the very top of your resume, directly under your contact details. It is the first thing a recruiter reads, often the only thing they read before deciding whether to go further. Yet most summaries are either blank, or filled with phrases so generic they could belong to anyone.
Here is the formula that works, with real examples, and a clear list of what to leave out.
What a resume summary is (and what it is not)
A resume summary is 2-4 sentences at the top of your resume that answer one question: why should this recruiter keep reading? It is not a career autobiography. It is not a list of soft skills. And it is not the same as an objective statement, which we will cover in a moment.
The summary earns its place because recruiters reviewing a pile of applicants make fast decisions. With the average corporate opening drawing around 250 applications, of which only 4-6 people are called for an interview (Glassdoor, a long-standing benchmark), the summary is the first filter. A recruiter who cannot find a reason to keep reading in the first ten seconds will not keep reading.
Context matters too: 33.5% of hiring managers say they can spot an AI-generated resume in under 20 seconds (TopResume, 600 hiring managers, 2025). A summary stuffed with generic buzzwords or clearly AI-templated language gets flagged before they reach your experience section.
Summary vs objective: quick rule
Have relevant experience? Write a summary. No experience or changing careers? Write an objective. See the comparison table below for when to use each.
The 4-part formula
Every strong resume summary has four components. None of them are optional.
Job title and years of experience
Open with the exact job title you are applying for (or your current title if it matches) and your years of relevant experience. "Senior product manager with 8 years of experience" tells the recruiter immediately whether you are in the right bracket. Do not bury this in the middle of the summary.
Top 2-3 skills or specialisations
Name the two or three skills most relevant to this specific role. Pull these from the job description: if the posting leads with "data analysis" and "stakeholder management," those are the skills your summary should name. Generic skills lists ("communication, teamwork, leadership") do not help because every candidate writes the same thing.
A specialisation or credential
Add one specific differentiator: an industry vertical, a certification, a tool, or a track record. "Specialising in B2B SaaS" or "certified PMP with a background in infrastructure projects" is more memorable than a third generic skill. This is the line that makes you stick.
An employer-specific hook
Close with one clause that connects your experience to what this employer is doing or needs. It does not have to be elaborate. "Looking to bring that track record to a scaling Series B team" or "seeking to apply enterprise sales experience to a company expanding into the US market" shows you read the job description and thought about the fit.
Before and after: 3 role examples
The formula is easier to apply with concrete examples. Here are weak summaries and what they look like rewritten with the 4-part structure.
Software engineer
Weak:
Hard-working software engineer with experience in multiple programming languages. Passionate about technology and eager to contribute to a dynamic team.
Strong:
Senior software engineer with 6 years of experience building distributed backend systems in Python and Go. Specialised in high-throughput data pipelines and microservices architecture. Seeking a principal engineer role at a company scaling its infrastructure to support rapid user growth.
Marketing manager
Weak:
Results-driven marketing professional with excellent communication skills and a passion for building brand awareness. Team player who thrives in fast-paced environments.
Strong:
Marketing manager with 5 years of experience running demand generation for B2B SaaS companies. Skilled in paid search, email nurture sequences, and attribution modelling. Looking to apply a track record of pipeline growth to an early-stage company building its first dedicated marketing function.
Registered nurse
Weak:
Dedicated nurse with a passion for patient care. Strong interpersonal skills and ability to work well under pressure. Motivated to make a difference.
Strong:
Registered nurse with 4 years of experience in acute medical wards and community care settings. BLS and ACLS certified, with a background in post-surgical patient management and care coordination. Seeking a community health role where continuity of care is the priority.
Notice what each strong version does: it names the exact type of experience (not just years), it is specific about the tools or environments, and it closes with a line that places the candidate in the context of the role they are applying for.
Summary vs objective: when to use each
The difference is straightforward, but it matters. Using the wrong one signals that you did not tailor your application.
| Format | What it says | When to use it | Example opening |
|---|---|---|---|
| Resume summary | What you bring to the employer | You have relevant experience in this field or role type | "Senior data analyst with 6 years of experience..." |
| Resume objective | What you are looking for and why | New graduate, career changer, or explaining a gap | "Recent computer science graduate targeting software engineering roles in fintech..." |
If you have 2+ years of directly relevant experience, use a summary. If you are pivoting from a different industry, a well-written objective is more honest and often more effective than a stretched summary.
The key mistake is writing an objective when you have experience. An objective that says "seeking a challenging role where I can grow" tells a recruiter what you want from them, not what you bring to the table. If you have a track record, lead with it.
Phrases to skip entirely
These phrases appear in the majority of resume summaries and add no signal to a recruiter. When every candidate writes the same thing, it is indistinguishable from saying nothing.
- Hard-working - assumed baseline, not a differentiator
- Team player - meaningless without context; every role requires collaboration
- Results-driven - what are the results? Name them instead
- Detail-oriented - show it with a specific example, not a label
- Motivated / self-motivated - again, a baseline expectation
- Passionate about [industry] - passion is demonstrated through experience, not stated
- Excellent communication skills - vague; say what kind of communication and in what context
- Dynamic team environment - no recruiter is looking for someone who prefers a static team
A useful test: if you can paste this phrase into any other candidate's summary without it feeling out of place, it should not be in yours.
Tailoring your summary per application
A generic summary sent to 50 applications is one of the clearest signals of a mass-apply approach. 62% of hiring managers say un-personalized AI resumes frequently lead to rejection (Resume Now, 925 HR workers, 2025). The summary is the highest-leverage part of your resume to tailor because it is the first thing a recruiter reads and the easiest section to adjust.
The fastest way to tailor a summary is to read the job description and extract the two or three most prominent skills or themes, then check whether those same terms appear in your current summary. If they do not, rewrite the skills clause to mirror the posting's language. This is not keyword stuffing: it is using the same vocabulary the posting uses, so the match is legible to both an ATS keyword scan and a human reader.
For a step-by-step process on matching your full resume to a job description, see our guide on how to match your resume to job descriptions. For the ATS side of keyword alignment, the ATS-friendly resume guide covers how applicant tracking systems actually read and score your document.
If you are applying to a lot of roles and find the per-application tailoring slow, a tool like MORT's resume builder can help. MORT is an AI job-matching platform for people who want to apply to more relevant jobs in less time. It scans thousands of company career pages, scores every job 0-100% for compatibility with your skills and experience, and generates a tailored resume for each application, including a summary section that mirrors the job description's keywords.
Frequently asked questions
How long should a resume summary be?
2-4 sentences, or roughly 50-80 words. Long enough to name your role, experience level, top skills, and what you bring to this employer; short enough to read in under 10 seconds. A recruiter skimming 250 applications will not read a six-line paragraph at the top of your resume.
Should I use a resume summary or objective?
Use a summary if you have relevant experience: it tells the recruiter what you bring. Use an objective if you are a new graduate, changing careers, or have a genuine gap to explain: it tells them what you are aiming for. If you have experience and write an objective, you are answering a question no one asked.
How do I write a resume summary with no experience?
If you have no professional experience, write a resume objective instead of a summary. Lead with your degree or training, name the role you are targeting, add 1-2 transferable skills backed by coursework, a project, or a placement, and close with what you bring. Keep it honest: do not claim experience you do not have. See our full guide on writing a resume for entry-level roles for the complete structure.
What keywords should I include in my resume summary?
Copy the exact phrases from the job description you are applying to: the job title, required skills, tools, and any certifications listed. ATS systems match your resume text against those terms literally, so "project management" and "programme management" may score differently even if they mean the same thing. Use the same phrasing the posting uses.
Should I write my resume summary in first or third person?
Neither. Resume summaries drop the personal pronoun entirely. Write "Senior software engineer with 7 years of experience..." not "I am a senior software engineer..." and not "She is a senior software engineer...". Dropping "I" is the standard convention and keeps the summary tight.
Tailor your summary to every application, without rewriting it from scratch
MORT generates a tailored resume for each role you apply to, including a summary section that mirrors the job description's keywords. It scores every job 0-100% for compatibility with your profile, so you know which roles are worth applying to before you spend time on them.
Sources
- Glassdoor, "50 HR & Recruiting Stats" (~250 applicants per corporate opening; 4-6 interviewed; a long-standing benchmark): glassdoor.com
- TopResume AI-in-hiring survey, 2025 (33.5% of hiring managers can spot an AI resume in under 20 seconds; 600 hiring managers surveyed): topresume.com
- Resume Now AI Applicant Report, 2025 (62% of hiring managers say un-personalized AI resumes frequently lead to rejection; 925 HR workers surveyed): resume-now.com