Write a resume summary that gets read

Three sentences at the top of the page: what you do, what you are known for, what you want next. Six examples, from a first job to a director, none of them results-driven.

By Miserably UnemployedUpdated 15 October 20263 min read

The summary is the three sentences under your name, and it is the only part of the resume everyone reads. The first sentence says what you do and for how long. The second says the one thing you are known for, with a number. The third says what you want to do next, in the posting's words. Write it last, after the experience section, because it is the experience section in three lines. Here are six, by level, and the formula they share.

Key points

  • Three sentences. What you do, what you are known for, what you want next.
  • Write it last. It is the experience section, compressed.
  • One number. The second sentence carries it.
  • The third sentence is tailored to the posting. The first two change less.
  • No adjectives about yourself. "Results-driven" is a word the reader has read four thousand times.

The formula

Sentence Says Example
One What you do, how long, in what "Product designer, seven years, logistics and healthcare."
Two The one thing you are known for, with a number "Led the dispatch console redesign that cut route assignment from four minutes to forty seconds."
Three What you want next, in the posting's words "Looking for a design systems role at a scale I have not worked at."

Sentence one is a label. Sentence two is proof. Sentence three is the reason this resume is on this desk.

A summary is not about you. It is about the match between you and the posting, in three lines.

Six examples

A recent graduate

Communication design graduate, June 2026, with a final project in usability research on hospital intake forms. Two summers at a small studio, shipping client sites that are still live. Looking for a junior product design role on a team that tests with users every week.

The number is "two summers" and "still live". A graduate's proof is that things shipped.

A career changer

Registered nurse, nine years, the last three on an intake team where I redesigned the forms nobody else would. Completed a UX certificate in 2025 and a year of freelance work on clinical software, two products shipped. Looking for a product design role in healthcare tooling, where I have filled in the form on a night shift.

The old career is the first sentence, not a secret. The reason it matters is the third.

A mid-level engineer

Backend engineer, five years, in payments and logistics, mostly Go and Postgres. Rebuilt the settlement pipeline at Northwind to handle twelve times the volume at the same cost. Looking for a senior role on a team that owns its infrastructure.

A senior designer

Product designer with seven years across logistics and healthcare, focused on the operational tools people use all day. Led the dispatch console redesign that cut route assignment from four minutes to forty seconds. Looking for a design systems role at a scale I have not worked at.

A manager

Engineering manager, four years, after six as an engineer, currently leading a team of eleven across two time zones. Took the team's release cadence from monthly to weekly in 2024 without a change in headcount. Looking for a role leading two or three teams where delivery is the problem to solve.

A director returning after a gap

Director of operations, twelve years in logistics, most recently running a 300-person distribution network. Eighteen months out in 2025 for family care, during which I advised two startups on fulfilment. Returning to a senior operations role, in person or hybrid, in the Northeast.

The gap is in the second sentence with what was done during it, and then the summary moves on.

What to cut

Three things show up in most first drafts and come out in the second.

  • Adjectives about yourself. Passionate, driven, dynamic, detail-oriented. The reader has seen each one four thousand times and has stopped seeing them. A number does what the adjective was trying to do.
  • Lists of skills. The skills section is for that. A summary that reads "Figma, Sketch, user research, prototyping" is a skills section in the wrong place.
  • The word "seeking". "Looking for" is what people say. "Seeking" is what resumes say.

Tailoring the third sentence

The first two sentences change little between applications. The third changes every time, because it names the role. "Looking for a design systems role" becomes "Looking for a role leading research" when the posting leads with research. The tailoring guide has the fifteen minute method, and the third sentence is minute six.

Tailor on this site rewrites the summary against the posting and keeps the first two sentences honest: nothing goes in that is not in the resume.

Questions

Is a summary the same as an objective?

No. An objective said what you wanted. A summary says what you have done and then what you want. The objective is gone.

Two sentences or four?

Three. Two leaves out the proof or the direction. Four is a paragraph, and a paragraph at the top of a resume does not get read.

First person or third?

Neither, in the sense of pronouns. No "I" and no "Alex is". Sentences that start with the noun or the verb: "Product designer, seven years." "Led the redesign."

Does the summary name the company I am applying to?

No. The cover letter does that. The summary names the role, in the posting's words, and that is enough to show you read it.

Can I skip it?

For a very junior resume with nothing to summarise, yes. For everyone else, no. It is the only part that is read in full.