Nearly every resume template includes a block of text at the top — and most job seekers fill it with whichever of these two their last template suggested, without knowing there's a difference. There is, and picking the wrong one (or writing either one badly) wastes the most-read real estate on the page.
This guide explains what summaries and objectives actually are, when each one earns its place, when to skip both, and how to write them with real examples.
What a summary is
A professional summary (also called a profile or summary statement) is 2–4 lines at the top of your resume describing what you bring: your experience level, your core strengths, and one or two proof points. It answers the reader's question: who is this person, professionally?
Good example:
"Customer support lead with 6 years resolving escalations for a SaaS company. Cut average response time 35% by rebuilding the triage process; trained a team of 9. Fluent in English and French."
Notice what it does: years, domain, two quantified results, one differentiator. No adjectives about being "passionate" or "results-driven" — the results do that work.
What an objective is
A career objective states what you want: the role you're seeking and what you're looking for. It answers a different question: what is this person after?
Good example:
"Recent accounting graduate seeking an entry-level staff accountant role where I can apply internship experience in month-end close and reconciliation."
Objectives get a bad reputation, and most of it is deserved — the classic "Seeking a challenging position where I can utilize my skills" says nothing and helps no one. But a specific objective has a legitimate job: it tells the reader what lane you're in, which matters when your background doesn't make it obvious.
Summary vs objective: which one do you need?
Use a summary when you have experience that speaks for itself — generally 2+ years in the field. Your track record is the selling point, so lead with it.
Use an objective when your experience doesn't obviously point at the role: career changers, recent graduates, people returning after a gap. In these cases the reader's first question is "why is this person applying?" and a clear objective answers it in one line. If you're changing fields, our project manager resume guide shows how to frame transferable experience alongside a targeted objective.
Skip both when the rest of your resume already makes the case and you're tight on space. A strong work history with quantified bullets needs no introduction — and a generic filler paragraph actively weakens the opening. This is the most underused option. Nobody ever got hired because of a summary; plenty of people have been skimmed past because theirs was bland.
A quick decision rule: if deleting the top block would leave the reader confused about what you want, keep an objective. If it would leave them unsure what you've done, keep a summary. If neither, delete it and give the space to another bullet.
How to write a summary that works
Use this formula: [years] + [role/domain] + [1–2 quantified wins] + [differentiator].
Bad: "Results-driven marketing professional with a passion for growth and a proven track record of success seeking new opportunities." Every word is filler. "Results-driven" is claimed, not shown. "Proven track record" proves nothing.
Good: "Digital marketer with 5 years in B2B SaaS. Grew organic pipeline from 12% to 31% of revenue; managed $400k annual ad spend across Google and LinkedIn."
The difference: the good version contains four checkable facts. A recruiter can picture this person. The bad version could describe anyone.
Two more rules:
- No first person, no pronouns. "I" and "my" are implied. "Marketing manager with 5 years…" not "I am a marketing manager…"
- Keep it to 3 lines max. A summary that runs to a full paragraph becomes the thing recruiters skip. If you need more than 4 lines, you don't have a summary — you have a cover letter.
How to write an objective that works
The bar is specificity. Name the role, name what you bring, name what you're targeting:
Bad: "Seeking a challenging position in a dynamic company where I can grow my career."
Good (career changer): "Former restaurant manager pursuing front-end development roles. Completed a 6-month bootcamp with 4 shipped projects in React; seeking a junior developer position."
Good (new graduate): "Biology graduate with 2 lab internships and coursework in data analysis, seeking an entry-level research assistant role."
Each good version does the same job: it connects the dots the reader couldn't connect alone. For teachers making a similar pivot, see our teacher resume guide for how to present classroom experience to non-school employers.
The honest test
Read your top block and ask: could this describe 10,000 other applicants? If yes, rewrite it with numbers, names of tools, and specifics only you could claim. "Customer support lead, 6 years, cut response time 35%" describes one person. "Dedicated professional seeking growth" describes everyone.
Put it on a template that leads with strength
Your opening block only works if the reader actually sees it — clean hierarchy, no graphics competing for attention. The Nomad template and Pivot template both open with a strong summary area in single-column layouts that parse cleanly. Build your resume free and read just the top third with fresh eyes: does it earn the next 30 seconds?
FAQ
Can I include both a summary and an objective? Almost never. Pick the one that fits your situation. Using both reads as indecisive and burns space you need for proof.
Do I need to tailor my summary for each application? Yes — lightly. Swap the differentiator and one proof point to mirror the posting's priorities. Thirty seconds of editing per application is enough; the structure stays the same.
What if I have less than 2 years of experience? Use an objective, or a hybrid: one line of direction plus one line of proof ("Recent graduate seeking data analyst roles. Built 3 portfolio projects in Python and SQL, including a churn model with 82% precision.").
Should the summary mention my career goal? Only if the goal isn't obvious from the application itself. You're applying for the role — restating "seeking a marketing position" on a marketing application wastes words. Save goals for the objective case, where your background needs explaining.
Is "Professional Summary" the right heading? It's fine, or use no heading at all — the block's position at the top makes its purpose clear. Avoid cutesy headings; this is not the place for creativity.