The core difference
A professional summary sells what you have already accomplished. It is a two-to-four line highlight reel of your experience, strongest skills, and biggest wins, framed for the job you want. It is employer-focused: here is the value I bring.
An objective states what you are looking for. It describes your goals and the kind of role you want. It is candidate-focused: here is what I want. That single difference — value delivered versus value sought — is why the summary has largely won.
Why summaries usually win
Recruiters spend seconds on the first pass and read top to bottom. A summary uses that space to make an immediate case for you; an objective spends it telling them something they can infer from the fact that you applied. For anyone with experience, the summary is almost always the stronger choice.
The old objective ("Seeking a challenging position where I can grow my skills") is also cliché and adds no information. If you use those lines at all, make every word earn its place.
When an objective still makes sense
Objectives are not dead — they are just situational. They work when you have little relevant experience to summarize, or when you need to explain a transition the recruiter would otherwise question.
- First job or new graduate with no professional history to highlight.
- Career changers who need to signal a deliberate pivot and why.
- Relocating to a new city, where stating the target location helps.
- Applying for a role that looks like a step down or sideways and needs context.
Even in these cases, lead with value, not just desire. Pair your goal with what you bring: "Career changer moving from teaching to UX, bringing five years of user research and stakeholder communication."
How to write a summary that works
Keep it to two to four lines. Open with your title and years of experience, name one or two areas of expertise, and include at least one quantified achievement. Then tailor it to the specific job by mirroring the language of the posting.
Strong example: "Data analyst with 6 years turning messy datasets into decisions for SaaS teams. Built dashboards that cut reporting time 70% and shaped a pricing change worth $1.2M in annual revenue. Fluent in SQL, Python, and Tableau."
Weaker example to avoid: "Hardworking professional seeking a role to leverage my skills in a dynamic environment." It says nothing specific and could belong to anyone.