How to write a resume summary

The summary sits at the top of your resume, directly under your name. That position is worth more than any other three lines on the page: a recruiter scanning a stack reads it first, and an applicant tracking system extracts it early when it builds its keyword picture of you. Yet most summaries I see fall into one of two camps — an objective ("seeking a challenging role where I can grow") that tells nobody anything, or a pile of adjectives ("dynamic self-starter") with no evidence. Both waste the spot.

A summary that works is boring in the best way: identity, level, your two or three core skills, and one quantified result. That's it. Below is the formula, when to rewrite it, and the honest-keyword rule that keeps it true for both the parser and the person.

The summary is not an objective

An objective talks about what you want. Nobody reading your resume cares what you want — they care what you can do. Cut it. Compare:

A formula that fits in three lines

Fill in this sentence, then polish it into two or three lines:

[Job title / field] with [X years] of experience in [2–3 core skills]. [One standout result with a number.]

That is the whole trick. The four parts map to the four questions a reader is asking in six seconds:

• Job title: what role are you talking about?
• Years: what level are you?
• Core skills: what do you actually do?
• One result: do you have proof?

Three lines, about 40–70 words. If it runs longer, cut adjectives before you cut nouns — the nouns are what the parser reads.

Rewrite it for every posting — this is the biggest lever

Here's the part most summary guides skip: a summary written once and sent to 50 jobs is barely better than no summary. The posting tells you exactly which words the employer's system and hiring manager are scanning for. Mirror them.

If the posting says "Project Coordinator" and your summary says "detail-oriented professional," you have failed a keyword match you could have won by copying two words. Use the employer's exact job-title wording and two or three skills from the posting, verbatim. "Excel" and "Microsoft Excel" are not always scored the same by a literal matching system — copy the posting's phrasing.

This is also why the summary is the easiest section to tailor: three lines, not three pages. And after you rewrite it, check your work — Tailr scores every tailored resume against the ATS and lists the keywords you are missing, so you can see whether your new summary actually covers the posting's vocabulary. Run a posting through the ATS checker to see the number before you send.

Honest keywords, never keyword stuffing

There is a line here, and it matters: use the posting's exact wording for skills you genuinely have. Adding tools you've never touched is lying, and it collapses the moment an interviewer asks a follow-up. A parser can rank you; only a person can hire you, and they will ask.

Our full breakdown on this is keyword matching without stuffing, but the short version applies to the summary directly:

• Include each keyword once, in a sentence that makes sense. A summary that reads like a tag cloud reads like spam to a human.
• Spell out a term then abbreviate it once — "search engine optimization (SEO)" — so you match either phrasing.
• If you don't have a metric, don't invent one. "Reduced support ticket volume 12%" is great if true; if not, name a responsibility honestly instead.

Examples for three common situations

Notice every example names a level, three-ish skills, and one concrete proof — and none of them claims a skill the person couldn't defend in an interview. For how to write the bullets underneath the same way, see our guide to writing honest, high-impact bullets.

When to skip the summary entirely

Sometimes the honest move is no summary. Skip it if:

• It would be a line of adjectives with no evidence — better no summary than "passionate results-driven professional."
• Your resume is one page and the summary would repeat your skills section word for word. Space is finite.
• You have genuinely strong projects or experience up top already (see our piece on resumes with no experience for the section order that puts evidence first).

A recruiter skips a bad summary anyway. Don't give them a reason to.

Keep it parseable

The best-written summary does nothing if the parser can't read it. Keep it in plain text in the main body of the resume — not in a header, footer, text box, or table. Many ATS parsers drop everything outside a standard single-column layout, which is also why we recommend single-column resumes. Two sentences of plain text beat a beautifully designed box the system never sees.

A three-minute summary checklist

1. Does the first line name your job title in the posting's exact words?
2. Does it state your level — years of experience or current position?
3. Does it contain 2–3 skills copied verbatim from the posting that you genuinely have?
4. Does it end with one quantified result or one concrete proof?
5. Can you defend every claim in a five-minute interview conversation?
6. Is it plain text, in the body, under 70 words?

If every answer is yes, the summary is doing its job. If not, rewrite it — three lines are cheap. That's the whole point: the summary is the easiest part of your resume to tailor to each posting, and it's the first thing scored.