Should I put a summary on my resume?

Only when it does work the rest of the page can't. UCLA's career center is explicit that professional summaries "are not a required element of a resume," and names three occasions to include one: the employer isn't asking for a cover letter, your degree doesn't immediately suggest you're a good fit for the role, or summaries are the norm in the field you're targeting. Skip it if you're a student or new grad squeezing onto one page, or if what you'd write is a string of adjectives. That block is the most valuable space on the résumé, and a generic summary wastes it — there's no penalty for leaving it off.

What is the difference between a resume objective and a resume summary?

A summary says what you bring; an objective says what you want. For almost everyone the summary is the right choice. The Rockwell Career Center at the University of Houston's Bauer College calls adding an objective "generally considered as outdated and unnecessary" and advises people new to the workforce to replace it with a two-to-three-line summary. UCLA puts the reason plainly: a professional summary "is not a career objective—the employer will automatically understand your career objective because of the job to which you are applying." If your goal genuinely isn't obvious from your history, name the target role in the last clause of your summary rather than labeling a section "Objective."

How long should a resume summary be?

Two to four lines. UCLA's career center specifies 2–4 lines, and the University of Arizona's Center for Career Readiness puts it at two to three sentences kept to two or three lines on the page. Write it without first-person pronouns — Arizona says to drop "I," "me," and "my" — and use the posting's own wording for the job title and tools. If yours runs longer than that, Arizona suggests converting it into a bulleted "Summary of Qualifications" section instead of letting a paragraph sprawl.

How do I write a resume summary for a career change?

Name the destination in the first few words, then use the old job as the evidence for it instead of apologizing for it. A teacher moving into instructional design opens with the move itself, then cites the curriculum shipped, the pilot run, and the tooling learned — the old role becomes the qualification. Mirror the posting's exact job title in that opening phrase, and close with one clause on the role you're targeting. Don't label the block "Objective"; write it as a summary that leads with transferable proof.

What should my resume summary say if I have an employment gap or was laid off?

State it once, in a single clause, and spend the rest of the space on competence. "Operations manager returning to full-time work after three years as a family caregiver" beats any euphemism, and naming a layoff as a structural reduction beats "seeking new opportunities following an unexpected transition" — vagueness reads worse than the fact. The University of Arizona's career readiness team also recommends listing years rather than months in your experience section so short breaks don't dominate the timeline, and treating a gap longer than a year as its own dated entry. If you're available immediately, say so; it's a genuine advantage over employed candidates.

Résumé Summary Examples (And When to Skip One)

TL;DR — A résumé summary is two to four lines at the top of the page that tell one specific employer why you fit one specific job. It's optional — UCLA's career center calls a summary "not a required element of a resume" — and a generic one is worse than none, because it spends your best real estate on adjectives. Write one when your background doesn't obviously match the posting, when there's no cover letter, or when it's the norm in your field. Skip the objective; it's the older, weaker version of the same idea.

The top of a résumé is the one part you can count on being read closely. Whatever sits there argues for you before anyone reaches your job history — which is the case for writing a summary, and equally the case against writing a bad one. Three lines of "results-driven professional with a proven track record" burn the best space on the page saying nothing. Below: what a summary is for, when to leave it off, the objective question, a formula, and a bank of examples across the situations people actually write from.

What is a résumé summary for?

A summary is a short, tailored block at the very top of the page. UCLA's Career Center defines them as "short, tailored descriptions that lay out your qualifications for a specific job, typically located at the top of your resume between your header and your education."

It has exactly one job: close the gap between what the posting asks for and what your résumé shows. If a reader has to assemble that story from your bullet points on their own, they may not bother. The gap is usually wide in three situations:

Your titles don't match the target title — a career change, a military background, a promotion into a function your old job description never named.
Your best qualification is buried — it's on page two, or inside a role from four years ago.
Your dates need context — a gap, a layoff, a return to work.

If there's no gap — a staff nurse applying to a staff nurse job with current experience — a summary just tells the reader what they'd already worked out.

Should you include a résumé summary, or skip it?

UCLA is direct that summaries "are not a required element of a resume," and names three occasions to write one: the employer isn't asking for a cover letter, your degree "does not immediately suggest that you are a good fit for the role," or professional summaries "are the norm for the field that you're targeting."

Write one when:

No cover letter is accepted, so nothing else frames you before the bullet points.
Your résumé doesn't explain itself — you're changing fields, coming back after time away, or holding a title that undersells the work.
You're senior enough that "what kind of engineer/marketer/nurse are you" genuinely needs an answer.
Your field expects one.

Skip it when:

You're a student or new grad on a one-page résumé and the space would do more work as another project or bullet. Our guide on writing a résumé with no work experience covers what to put there instead.
You'd write it once and send it to everything. A summary is either the most tailored block on your résumé or it's dead weight.
Every claim in it repeats the line directly beneath it.
It would be made of adjectives.

The honest version of the debate: a targeted summary earns its space, and a generic one is the single most-skipped block on the page. There's no penalty for leaving it off.

Résumé objective vs. summary — which one do you need?

For almost everyone: the summary. An objective says what you want; a summary says what you bring. The Rockwell Career Center at the University of Houston's Bauer College calls adding an objective "generally considered as outdated and unnecessary," and advises people new to the workforce to replace a career objective with a summary of two to three lines. UCLA puts the reason plainly: a professional summary "is not a career objective—the employer will automatically understand your career objective because of the job to which you are applying."

The one place goal-shaped language still earns its keep is when your goal isn't obvious from your history — a career change, a return to work, a move to a new city. Even then, don't label the section "Objective." Write a summary that leads with transferable proof and names the target role once, at the end. Several examples below do exactly that.

How to write a résumé summary: the three-sentence formula

Keep it to two to four lines (UCLA) or, as the University of Arizona's Center for Career Readiness frames it, two to three sentences that "synthesize your most relevant qualifications into a clear summary that ties your experiences together." Then fill those lines in this order:

Who you are, in their words. The title or level from the posting, plus years or a credential. Arizona's guidance: incorporate words and phrases from the job description.
The proof. One or two accomplishments with a number, a scope, or a name attached to them.
The aim. One clause on what you're bringing to this role — never on what you hope to get from it.

A few mechanics that separate a real summary from filler:

No first person. Arizona says to drop "I," "me," and "my." Sentence fragments are fine and read tighter.
Mirror the posting's nouns. Use their job title and their tool names, not your internal ones — the same discipline covered in résumé keywords and the ATS.
Numbers beat adjectives, every time.
If it runs long, Arizona suggests converting it into a bulleted "Summary of Qualifications" section rather than letting the paragraph sprawl.

Here's the formula assembled:

"Bilingual customer support lead with four years in high-volume SaaS support. Handles 60+ tickets a day at 96% CSAT and authored the Spanish-language macro set now used across the team. Ready to bring an escalation-first approach to a technical support role."

Résumé summary examples for 8 situations

Read these as patterns, not scripts. Swap in your own numbers, tools, and certifications, and rewrite the opening phrase to match the exact title on the posting.

New grad

"Recent finance graduate (B.S., May 2026) with two commercial banking internships and coursework in valuation and financial modeling. Built the credit-review model a four-person team used to process 40+ small-business files last summer, and served as treasurer of a 200-member student organization with a $28,000 annual budget. Seeking a credit analyst role."

Leads with the credential, then two pieces of real evidence — one from an internship, one from an activity. If you have neither yet, spend the space on projects instead.

Career changer

"High school math teacher moving into instructional design after six years building curriculum. Designed a 30-lesson algebra sequence adopted across three campuses, ran the district's first blended-learning pilot for 180 students, and completed self-directed training in Articulate Storyline and Camtasia this year. Bringing classroom evidence of what holds an adult learner's attention to corporate L&D."

The destination appears in the first seven words, which stops the reader from mentally filing you under "teacher." Everything after that reframes the old job as the qualification rather than the obstacle.

Returning after a career gap

"Operations manager returning to full-time work after three years as a family caregiver. Previously ran a 22-person warehouse team through a WMS migration that cut pick errors 31%. Recertified as a Lean Six Sigma Green Belt in 2026 and current on NetSuite. Ready for a floor-level operations role."

The gap is stated once, in a single clause, with no apology — then the rest is competence. Arizona's career readiness team also recommends listing years rather than months in your experience section so short breaks don't dominate the timeline, and treating a gap longer than a year as its own entry (their example: "Full-time parent, Los Angeles, CA, 2018-2021").

Laid off

"Data engineer, four years at a Series C fintech until a March 2026 reduction eliminated the platform team. Owned the Airflow pipelines behind revenue reporting — 200+ DAGs at 99.9% on-time delivery — and cut warehouse spend 18% by rewriting the heaviest jobs. Available immediately."

One clause names the layoff as structural and moves on. Resist "seeking new opportunities following an unexpected transition" — the vagueness reads worse than the fact. And "available immediately" is a genuine advantage over employed candidates, so say it.

Senior individual contributor

"Staff backend engineer, nine years in distributed systems, currently technical owner of a payments service handling 4M transactions a day. Led a monolith migration across six teams with no customer-facing outage and wrote the on-call runbooks now used org-wide. Interested in staff-level platform and reliability work, not people management."

At this level the summary answers what your titles can't: scope and specialization. The final clause is doing real work — ruling out the management track prevents a mismatch nobody discovers until the third interview.

Manager

"Engineering manager of two teams (14 engineers) at a 400-person health tech company, promoted from tech lead in 2024. Cut median PR review time from three days to eight hours, hired six engineers with zero regretted attrition over two years, and shipped the FHIR integration that unblocked three enterprise contracts. Looking for a manager-of-managers role at similar scale."

Management summaries live on span of control, retention, and what the team shipped. Put the headcount in the first line — it's the first thing anyone hiring a manager wants to know.

Hourly and service work

"Shift lead with six years across restaurant and retail, currently opening and closing a store doing $40,000 a week. Trains every new hire on POS and food safety (ServSafe certified), builds the schedule for a 12-person rotation, and held full staffing through two holiday seasons. Seeking a full-time assistant manager role with daytime availability."

The trap here is underselling. "Cash handling, inventory, scheduling" is management work — name the dollar figure, the headcount, the certification. Availability goes in the last clause, because for these roles it's often the deciding factor.

Military to civilian

"Logistics supervisor with eight years in the U.S. Army (Sergeant, 92Y), accountable for $4.2M in equipment across a 60-person unit with zero losses over four inventories. Rebuilt the parts-request process, cutting average turnaround from nine days to three. Seeking a supply chain or warehouse operations role in the Atlanta metro."

Every military term is either translated or dropped. VA Careers recommends using O*NET OnLine to find "specific examples of how your military experience can apply to a civilian job"; its Military Crosswalk, published by the Department of Labor's Employment and Training Administration, maps an MOS, AFSC, or rating to matching civilian occupations — which is where the vocabulary for your first line comes from. Keep the rank and code as a parenthetical if the employer values them, but lead with the civilian title.

What if you're freelance, or applying internally?

Two more patterns that come up constantly.

Freelancer consolidating into a full-time role:

"Front-end developer, five years freelance, delivering 20+ React builds for agencies and direct clients including a 40-page marketing site that cut load time 60%. Comfortable owning scope, estimates, and client communication end to end. Looking to trade project churn for one product and a team."

Internal candidate applying to a different function:

"Four years in customer success here, now applying for the product operations opening. Ran the onboarding program for the top 30 accounts (94% retention) and built the churn-signal dashboard the product team uses in its quarterly review. Already knows the customers, the data, and the roadmap."

What makes a résumé summary bad?

Adjective soup. "Detail-oriented, results-driven professional with a proven track record of success." It describes no one.
It's about you, not them. "Seeking a challenging position that allows me to grow." Every applicant wants that.
It restates the line beneath it. If your summary paraphrases your current title and bullets, cut it and give the space back.
First person. No "I," "me," or "my," per Arizona's guidance.
It's too long. Four lines is the ceiling; beyond that, convert it to a bulleted Summary of Qualifications.
It's the same everywhere. One summary blasted at forty postings is functionally no summary. Rewriting the opening phrase to match each posting's title is the fastest tailoring move there is, and tailoring a résumé with AI turns it into a two-minute job instead of a chore you skip.

Here's the test. Cover everything else on the page and read only those three sentences. Would someone who saw nothing else know which job to hand you? If yes, keep it. If not, fix it or cut it and let the rest of the résumé work — an empty top beats a wasted one. And if you're building the document from scratch, start with how to write a résumé and come back to the summary last: summarizing a page that already exists is far easier than writing the summary first and trying to live up to it.

Sources

UCLA Career Center — How and When to Write a Professional Summary
University of Arizona Center for Career Readiness — Writing a Resume Summary Statement
University of Arizona Center for Career Readiness — How Do I Explain Employment Gaps on My Resume?
Rockwell Career Center, C. T. Bauer College of Business, University of Houston — Difference Between Resume Summary & Objective
VA Careers, U.S. Department of Veterans Affairs — Translate Your Military Skills to a Civilian Career
O*NET OnLine, U.S. Department of Labor Employment and Training Administration — Military Crosswalk Search