How to write a resume summary (with examples)
The short answer
A resume summary is two or three lines at the top of your resume that say who you are professionally, what you have done and what you want next. Use the formula: your title and years of experience, your strongest relevant skills in the posting’s terms, and one specific result. Write it for each role, skip “I” and filler adjectives, and keep it under 50 words.
The summary is the first thing under your name. With a first look of about seven seconds in one eye-tracking study, it is the one place where you can say, in the employer’s terms, why you match. See The 7-second resume rule.
The formula
Three parts, in one to three lines.
- Who you are: your title or field and years of experience.
- What you do best: two or three skills that match the posting, in its words.
- One proof: a specific result, or what you are aiming for if you are changing field.
Template:
[Title] with [n] years of experience in [field]. Skilled in [skill], [skill] and [skill]. [One result, with a number if you have one].
Examples
Experienced professional
Operations manager with six years running warehouse teams of 30 or more. Skilled in scheduling, process improvement and supplier management. Cut late dispatches by rebuilding a three-shift schedule at a regional distributor.
Marketing
Content marketer with four years in B2B software. Experienced in SEO, email and product launches. Grew organic traffic to a company blog from a standing start by building a content calendar around customer questions.
Software engineer
Backend engineer with five years building payment and billing systems in Python and PostgreSQL. Comfortable owning a service from design to on-call. Reduced checkout errors by redesigning retry handling.
Career changer
Teacher with seven years in secondary education, moving into learning and development. Experienced in designing curriculum, running training and measuring progress. Built a peer-mentoring programme now used across a school of 900 students.
Recent graduate
Economics graduate with placement experience in a bank’s risk team. Skilled in Excel, SQL and writing for non-specialists. Built a loan-default dashboard used in weekly team meetings.
Returning after a break
Project manager with eight years in construction, returning after a career break of two years. Experienced in budgets, subcontractors and delivery to programme. Recently completed a project management certification.
Use your own figures. If you have no number, describe the outcome plainly: what changed because of your work.
How long should it be
Two or three lines, or 30 to 50 words. If it wraps onto a fourth or fifth line, cut. A summary that is a paragraph is read as one block or skipped.
Summary, profile or objective
The names are used interchangeably, but the content differs.
| Type | What it says | Use it when |
|---|---|---|
| Summary | Who you are and what you have done | Most cases |
| Profile | The same, a little more personal | Some UK and creative fields |
| Objective | What you want | Career change or first job, and only with a clear tie to the role |
An objective on its own, such as “Seeking a challenging position”, says nothing. Pair it with what you bring.
Writing it for a role
A summary that is the same on every application wastes its best position. Change the title and skills to match the posting, and pick the result closest to what the job needs. The change takes a few minutes and is the highest-value edit on the page. See How to tailor your resume to a job.
Use the posting’s terms for experience you really have. If it says “account management”, do not write only “client success”. Applicant tracking systems parse and rank the text, so the words matter. See Does an ATS reject resumes automatically?
What not to do
- Do not write “I”. Resume style drops the pronoun: “Managed a team”, not “I managed a team”.
- Do not use filler adjectives. “Results-driven”, “dynamic” and “passionate” tell the reader nothing.
- Do not list soft skills with no proof. “Strong communicator” needs a result behind it.
- Do not make it a paragraph. Two or three lines.
- Do not copy the posting. Use its terms for what you have really done.
- Do not leave it generic. The same summary on every application is a missed opportunity.
Getting it right for each role
Rewriting the top of the resume for every application is the step most people skip. Glide scores each role against your profile and tailors your resume to it, showing every change so you can keep or undo each one. It prepares the application, and you decide what goes out.
Common questions
Should I put a summary on my resume?
Yes if you have a clear match to describe, and especially if you are changing field or your recent titles do not show the match. If your resume is short and the match is obvious from your recent role, you can leave it out.
What is the difference between a summary and an objective?
A summary says who you are and what you have done. An objective says what you want. A summary is stronger because it gives the reader a reason to keep going.
Can I use the same summary for every application?
You can, but it works better changed for each role. Change the title, skills and result so they match the posting.
How do I write a summary with no experience?
Name your field of study or interest, two relevant skills and one project, placement or piece of work. Say what you did and what came of it.
Keep reading
Glide is the agent on your side of hiring. See what it does, how it compares and the research behind it.