How to Write a Resume Summary: A Three-Sentence Formula

To write a resume summary, write three sentences at the top of your resume. The first says who you are professionally: your role, your years of experience and your area. The second proves it with one or two specific results. The third says what you bring to the job you are applying for, in the words that job posting uses. Keep it to about 50 to 80 words, write it without “I”, and include nothing the rest of your resume cannot back up.

That is the whole formula. The rest of this guide shows each sentence in detail, gives worked examples for different situations, lists the lines worth cutting, and shows how to re-aim the same summary for each new application in a couple of minutes.

What a resume summary is for

A recruiter looks at the top of a resume first and decides from there how carefully to read the rest. The summary is the part they read in that first look. Its job is to answer one question quickly: is this person worth reading closely for this role?

That makes the summary different from every other section. Your experience section is a record of what you did. The summary is a short argument about which parts of that record matter for this job. It is also where an applicant tracking system often finds its first matches for the posting’s key terms, so the vocabulary you choose here counts twice.

Summary or objective?

An objective says what you want (“seeking a role where I can grow”). A summary says what you offer. Recruiters are hiring for their needs, so a summary is almost always the stronger choice. The one exception is a short line of context when your situation would otherwise confuse the reader, such as a career change. Even then, frame it around what you bring.

How to write a resume summary in three sentences

Sentence 1: who you are

Lead with your professional identity: the job title you hold or are targeting, how long you have done this kind of work, and the area you specialise in.

Registered nurse with six years in emergency and critical care.
Data analyst with four years of experience in retail pricing and demand forecasting.
Customer service lead with a background in high-volume phone and chat support for software products.

Use the title the posting uses where it is honestly yours. If the job says “Customer Success Manager” and your title was “Account Manager” doing the same work, describe the work in their terms without claiming a title you did not hold.

Sentence 2: the proof

Pick one or two results from your experience section that best match what this job cares about. Specific beats general. A number is good if you have a real one; a concrete scope works when you do not.

Led triage for a 40-bed department and trained 12 new nurses on sepsis protocols.
Built the weekly forecasting model the pricing team uses to plan promotions across 300 stores.
Cut average first-response time on the chat queue by redesigning the ticket routing rules.

Only use figures you can defend in an interview. If you do not know the exact number, describe the scope (“across three regions”, “for a team of eight”) and leave the percentage out.

Sentence 3: what you bring to this role

Close by connecting your strengths to the posting. Read the job description, pick the two or three things it asks for most, and name the ones you genuinely have.

Brings calm prioritisation under pressure, strong patient communication and experience with Epic documentation.
Strong in SQL, Python and stakeholder reporting, with a focus on turning analysis into decisions.

This sentence is the one that changes most between applications. The first two sentences mostly stay the same.

Resume summary examples

Here is how the formula plays out across common situations.

Situation	What to lead with	Example opening
Experienced, same field	Title and years	”Project manager with eight years delivering construction projects.”
Career change	Transferable skill and the new target	”Former teacher moving into instructional design, with five years building curriculum.”
Student or new graduate	Degree, focus and one practical result	”Accounting graduate with an internship in accounts payable and audit support.”
Returning after a gap	Experience first, gap not mentioned	”Office manager with ten years running operations for small medical practices.”
Senior or leadership	Scope of responsibility	”Operations director who has led teams of 60 across three sites.”

A full example: experienced professional

Marketing manager with seven years in B2B software, focused on demand generation and content. Grew inbound pipeline for two product launches by building the webinar and email programme from scratch. Brings hands-on experience with HubSpot, campaign analytics and cross-team planning with sales.

A full example: no work experience

Computer science student in the final year of a degree, with a focus on web development. Built and shipped a class scheduling app used by students in the department, working in a team of four. Comfortable with JavaScript, React and Git, and keen to contribute to a front-end team.

When you have no paid experience, your proof sentence can draw on projects, coursework, volunteering or part-time work. What matters is that it is specific and true.

A full example: career change

Retail store manager moving into HR, with six years hiring, scheduling and training teams of up to 25. Ran the store’s onboarding programme and handled employee relations issues end to end. Brings practical experience in recruitment, conflict resolution and people processes.

Mistakes worth cutting

Most weak summaries share the same few problems. If yours has any of these, the fix is usually to delete words.

Adjectives with no evidence. “Hard-working, passionate, detail-oriented team player” tells the reader nothing, because everyone writes it. Replace each adjective with the result that proves it, or cut it.
Writing in the first person. Resume convention drops “I” and “my”. “Led a team of five” reads cleaner than “I led a team of five”.
Too long. More than four lines at the top of a resume starts to look like a paragraph nobody will read. Three sentences is plenty.
A generic summary sent everywhere. A summary that would fit any application to any company is doing half its job. The third sentence exists to be changed.
Claims the resume cannot back up. If the summary mentions a skill, the experience section should show where you used it. Recruiters check, and interviews ask.
Keyword stuffing. Listing every term from the posting reads badly to a person and helps little with software. Name the few that are really yours.

How to aim your summary at one job

Tailoring the summary is the fastest high-value change you can make to an application, because it is short and sits where the reader looks first. For each posting:

Read the job description and write down the three things it asks for most, in its own words.
Check sentence 1. If the posting uses a different but accurate name for your role, use theirs.
Swap the proof in sentence 2 for the result that best matches the posting’s top need.
Rewrite sentence 3 around the skills from step 1 that you genuinely have.
Read the summary against the posting once more. Anything that could be sent to any employer can probably be sharper.

This works best alongside the rest of the resume. Our guide on how to tailor a resume to a job description covers the bullets and skills list, and how to write a cover letter uses the same approach for the letter.

When writing it by hand is enough

If you are applying to a handful of similar jobs, the manual method above is all you need. Write one strong summary, then spend a couple of minutes changing sentence 3 for each posting. The thinking you do in choosing which result to lead with is valuable in itself, because it is the same thinking you will need in the interview.

Doing it by hand also makes sense when your background is unusual enough that you want full control over every word.

A faster way when you are applying to many jobs

When you are sending many applications, re-aiming the summary each time becomes the part that gets skipped. That is the job instaresume is built for. You paste your background, and optionally the job posting, and it writes a summary drawn from what you actually did, with keywords taken from the posting and only claimed where your background supports them.

Free, no account: the resume summary tools, for example the software engineer resume summary generator or the registered nurse version, give you 3 generations a day without signing up. You can tick “Tailor to a specific job posting” and paste the job description. Browse the rest on the tools page.
With a free account: the app saves your results and adds cover letters and bullet points from the same background, with PDF and DOCX export. Plans are on the pricing page.

Treat what it writes as a draft. Read it against the formula above: does sentence 1 name you accurately, is the proof specific and true, and does the close match the posting? Edit anything that does not sound like you.

Frequently asked questions

How long should a resume summary be?

Three sentences, or roughly 50 to 80 words. On a one-page resume that is three to four lines.

Do I need a resume summary at all?

It is optional, but useful for most applicants because it controls what the reader sees first. It matters most when you have several years of experience, are changing careers, or are applying to roles where your fit is not obvious from your last job title.

Should the summary be different for every job?

The first two sentences can usually stay the same across similar roles. Change the third, and swap the proof in the second when a posting cares about something different.

Can I use the same summary on LinkedIn?

As a starting point, yes. A LinkedIn “About” section can be longer and written in the first person, because it speaks to a wider audience than one job. Keep the resume version short and aimed at the role.