Objective vs summary: lead with what you offer, not what you want

The difference in one line

An objective states what you want (“Seeking a challenging position…”); a summary states what you offer (“Support engineer with 5 years in SaaS, cut median ticket time 40%”). Recruiters scan for evidence, so the summary wins for almost everyone.

Why objectives fell out of favor

An objective spends your most valuable lines — the top of page one — describing your wishes, which every applicant shares. It adds no screening signal: no skills, no scope, no numbers. Most modern templates and career centers dropped it years ago.

The exceptions where an objective still works

A one-line, specific objective can help when your target is not obvious from your history: career changers (“Transitioning from teaching to instructional design; built 12 online courses”) and new grads targeting a niche role. Even then, pack it with evidence, not aspiration.

How to write a summary that scans

2–3 lines: role + years, the strongest quantified result you can claim honestly, and the skills that mirror the posting. No first person, no buzzword chains (“results-driven team player”), no claims you cannot back in an interview.

Tailor it per application

The summary is the easiest section to tailor: swap the emphasized skills to mirror each posting’s language. Save a named copy per job in the builder so version A for one company never overwrites version B for another.

Check the result

Paste the posting into our free ATS checker to see whether your summary and skills actually mirror the keywords screening filters look for — before you send it.

Summary examples by stage

New grad: “CS graduate with three shipped web projects; strongest in React and Python.” Mid-career: “Ops manager, 8 years in logistics; cut fulfillment errors 35% across 4 warehouses.” Executive: “VP Engineering; scaled a 12-to-80 person org through two funding rounds.” Each is two lines of checkable facts.

Objective examples that still earn their line

“Transitioning from nursing to clinical-informatics; Epic-certified, led my unit’s EHR rollout.” “New grad targeting embedded firmware; built two shipping IoT products in coursework and internships.” The pattern: name the target, then immediately prove it.

When to skip both

If your last job title matches the target role and the posting’s keywords already lead your experience section, a summary can be redundant — a straight-to-experience resume is fine, especially at one page. The summary earns its lines only when it adds evidence or explains a pivot.

Common summary mistakes

Buzzword chains with no facts (“dynamic, results-oriented professional”), first person (“I am a…”), restating the resume’s first bullet, exceeding three lines, and claims you cannot defend for two minutes in an interview. Every phrase should survive the question “says who?”.

Headline + summary, not either/or

A one-line headline under your name (“Senior Data Engineer · Python · AWS”) plus a two-line summary is the modern top-of-page: the headline feeds keyword screens and the recruiter’s first glance, the summary adds the evidence. Our builder’s title field renders exactly this headline.

The 7-second test

Read only your name, headline and summary for seven seconds, then ask what a stranger now knows: target role, seniority, strongest result. If any of the three is missing, rewrite before touching anything else — nothing below gets read until this passes.