Summary vs objective — the difference
A summaryanswers "what do you offer?" — your experience and strongest relevant skills, condensed. An objectiveanswers "what do you want?" — the role you're targeting. The right choice depends on where you are.
When to use a summary
If you have experience to summarise, use a summary. It lets a recruiter grasp your value in two lines before they read further.
EXAMPLE — SUMMARY
Backend engineer with 4 years building high-throughput APIs in Go and PostgreSQL. Cut p95 latency 38% on a payments service; comfortable owning a feature from schema to deploy.
When to use an objective
If you're a fresher or changing careers, an objective signals direction a summary can't — because you don't yet have a track record in the new field to summarise.
EXAMPLE — OBJECTIVE
Final-year CS student seeking a backend developer role, with hands-on projects in Node.js and PostgreSQL and a 2-month data internship. Eager to ship production code on a small team.
For freshers, also see the full fresher-resume guide.
When to use neither
If you can't make it specific to the job, skip it. A generic line — "Hardworking professional seeking a challenging role to utilise my skills" — is worse than nothing; it burns your best space saying something true of everyone. The space is better spent on a strong first experience bullet.
How to write one that works
- One to three lines. It's a hook, not a bio.
- Lead with role + years (or, for freshers, field + standout project).
- Tailor it to the job. The one strength you highlight should be the one this listing most wants.
- Include a real keyword or two from the JD — naturally.
- No fluff adjectives. "Results-driven", "dynamic", "passionate" say nothing.
Because the best summary changes per job, my-resume tailors the top of your resume to each JD's language along with the rest.
FAQ
Summary or objective?
Summary if you have experience to offer; objective if you're a fresher or career changer signalling direction.
Do I need one at all?
It's optional. A specific, tailored one helps; a generic one wastes space.
How long?
One to three lines — a hook, not a paragraph.
Related guides
Build a JD-tailored résumé in 5 minutes.
No credit card. Paste any JD, let the pipeline restructure your résumé. Free today.