← Back to all posts
loading…
A resume objective is the two or three lines at the top of a resume that tell a recruiter, in plain language, what you're looking for and why you're worth reading further. For most experienced candidates it's the wrong move. A summary of your actual record does more work in the same space. But in a handful of specific situations, an objective still beats every alternative, and writing one badly is one of the fastest ways to get skipped.
This post is for those specific situations. I'll explain when an objective makes sense, when it doesn't, what a good one looks like in three parts, and then 14 examples you can lift almost verbatim. Most job seekers copying "resume objective examples" from the top of Google are pasting something written in 2014 that reads like a mad-lib. You can do better in about ninety seconds.
You should write an objective instead of a summary when a recruiter reading your work history would have a legitimate question about why you're applying. That narrows it to four cases:
Outside those four, a summary is almost always stronger. A summary is a distilled version of your record. An objective is a claim about what you want. If you've already done the work in the target field, leading with the want is weaker than leading with the evidence.
If you're experienced in the field you're applying to, write a summary. Three lines, the numbers that matter, the stack or specialty, the scale you've operated at. No wish list.
Here's the same person in both formats so the difference is visible:
Objective (weaker for this candidate): Experienced software engineer seeking a senior role at a fast-growing company where I can contribute to scalable systems and grow my leadership skills.
Summary (what this person should actually use): Senior software engineer, 7 years across fintech and healthtech. Led the migration of a $40M/yr payments platform off Stripe Connect to a dual-rail Adyen + ACH setup, cutting processing fees 18% and hitting 99.98% success rate. Comfortable owning both the service and the on-call.
The first one could belong to anyone. The second one couldn't. Recruiters hire the second one faster because they don't have to read between the lines to know what they're getting.
Every resume objective I've seen that works has the same three parts, roughly in this order:
Part 1: who you are right now. One phrase. "Recent marketing grad." "Career changer from teaching." "Returning to software after a two-year caregiving break."
Part 2: the role you're targeting, specifically. Not "a challenging position in marketing." The actual title band. "Entry-level product marketing at a B2B SaaS company." "Mid-level data analyst role, preferably on a product analytics team."
Part 3: one concrete thing you bring. The most specific skill, credential, or accomplishment that maps to the target role. This is the line that saves you from sounding like every other career-changer on the page.
Three sentences, tops. Two if you can pull it off. If it runs longer than that, you're writing a summary, and the objective format is working against you. Kill the fluff. "Passionate team player with strong communication skills" adds nothing a reader can verify. Replace it with one line that proves the thing.
Each of these is written to fit a real job posting. You're meant to swap the role title and the company type to match what you're applying to, then tune the third line so the specific thing you bring matches what the posting actually wants.
1. Marketing grad, entry-level B2B role
Recent marketing graduate (BBA, University of Texas 2026) targeting an entry-level content marketing role at a B2B SaaS company. Ran the @utausten.ecom TikTok from 400 to 42k followers as an independent project, with a 6% average engagement rate across 120 posts.
2. CS grad, software engineering
Computer science graduate (BS, May 2026) looking for a junior software engineering role on a small product team. Shipped two full-stack React/Node side projects with 200+ GitHub stars each, and placed third in my cohort's capstone showcase on a real-time collaboration tool.
3. Teacher to product manager
Career changer moving from 5 years of middle-school math teaching into product management. Targeting an associate PM role at a mid-stage ed-tech company where domain knowledge of the classroom is a hiring plus. Shipped a lesson-planning side tool used by 380 teachers across three districts in the last two years.
4. Accountant to data analyst
Senior accountant with 6 years in close and FP&A, pivoting into data analytics. Completed the Google Data Analytics certificate and two portfolio projects in SQL + Tableau in Q1 2026. Looking for a junior analyst role on a finance or operations team where reading a P&L is part of the job.
5. Retail manager to operations role
Retail store manager (Target, 4 years, two-store lead) moving into corporate operations. Looking for a mid-level ops analyst role at a logistics, fulfillment, or consumer product company. Owned a $6.2M annual P&L and cut shrink by 31% across my two stores over the last 18 months.
6. Sales to customer success
Six years in mid-market SaaS sales (quota: $1.8M, attainment: 112% average across three years). Moving into customer success because retention is the problem I actually enjoy solving. Targeting a senior CSM role at a PLG company, ideally one where the expansion motion is customer-led.
7. Mom returning after caregiving
Software engineer returning to full-time work after a three-year caregiving break. Stayed current through two open-source contributions to the Next.js ecosystem in the last year (merged PRs in the rewrite of the App Router examples). Looking for a senior frontend role at a stable, async-friendly company.
8. Post-recovery professional return
Returning to full-time product design after a two-year health gap. Pre-gap: 7 years at Series A/B startups, including Lead Designer at Chord (acquired 2023). Targeting a senior product designer role on a small, ship-often team. Up to date on the current Figma plugin ecosystem and the 2026 design-system work from Linear and Vercel.
9. Undergrad, first internship
Second-year computer science student at Cal Poly, looking for a software engineering internship for summer 2026. Two completed web projects in Next.js and Postgres, both live, both used by a small real user base. Strong preference for a team that reviews PRs on the work of their interns.
10. MBA internship
First-year MBA candidate (Kellogg 2027, background in consumer healthcare marketing) looking for a summer 2026 product management internship at a B2B or consumer software company. Pre-MBA: brand manager at Unilever, owned a $24M shampoo line across four countries.
11. Nurse to clinical informatics
Registered nurse (ICU, 5 years at UCSF Medical Center) moving into clinical informatics. Currently completing the AMIA 10x10 program. Targeting a clinical informatics analyst role at a hospital system or EHR vendor where bedside experience is more than a nice-to-have.
12. Lawyer to compliance
Corporate attorney (6 years, M&A and commercial contracts) moving into in-house compliance. Targeting a senior compliance role at a public SaaS or fintech company. Led the contract redlining playbook used firm-wide at [redacted firm], which cut average deal cycle from 34 days to 21.
13. Mid-level engineer targeting a senior role
Software engineer (4 years total, last 18 months at senior-adjacent scope: owning a service, on-call rotation, and 2 direct mentees). Looking for the formal senior title at a product-led company where I can own a full domain. Most recent shipping: the credit-decision service at [redacted fintech], 99.99% uptime over the last year.
14. Junior shifting specialty
Junior frontend engineer (2 years React) moving into accessibility specialist work. Completed IAAP CPACC certification in Q1 2026. Targeting a mid-level a11y-focused frontend role where most of the work is audits, remediations, and component-library fixes. Ran the accessibility reviews on the last two features at [current company] and cut keyboard-trap issues to zero.
Look at all 14. None of them start with "Seeking." None of them use the word "passionate" or "dynamic." Every one names the role they want, in the exact language a recruiter would use. Every one has a concrete piece of evidence as the third line. Every one is under 60 words.
Those four rules will catch most of the mistakes people make with objectives.
Too vague. "Seeking a challenging role where I can grow my skills and contribute to a dynamic organization." I cannot tell if you want to be a recruiter or a nuclear engineer. This sentence is a placeholder, not an objective.
Too me-focused. "Looking for an opportunity that will help me develop my career." The company's job is not to develop your career. Their job is to solve a problem, and they hire the person who will solve it fastest. Lead with what you give, not what you want to get.
Buzzword soup. "Results-driven, detail-oriented team player." Four words, zero content. Anyone can claim any of those. Replace the cluster with one sentence that proves one of them.
Too long. If your objective is five lines, it's a summary. Compress it or switch formats.
Wrong target. If your objective says "marketing role" and your bullets are all about engineering, the recruiter assumes the resume is recycled and moves on. The objective has to match the bullets. If it doesn't, cut the objective.
Generic company-speak. "Contribute to organizational success." Every single organization wants people who contribute to its success. Name the specific thing you'd contribute.
Three formats get used at the top of a resume. They do different jobs.
Objective. Best for career changers, recent grads, long-gap returners, or a very different target role. Two to three sentences. Content: where you are now, the role you want, one concrete asset that maps to it.
Summary. Best for anyone experienced in the target field. Three to five sentences. Content: years and specialty, two or three measurable wins, the scale you've operated at.
Profile. A hybrid, more common in Europe and creative fields. Three or four sentences. Content: identity, craft, one recent proof point.
Most US-based postings don't care which one you pick as long as it's tight and relevant. Ask yourself one question before writing either: "If a recruiter reads only this section, can they tell in five seconds whether to keep reading?" If no, rewrite.
If you want to pressure-test whether the rest of your resume matches the objective, paste it and a target job description into resimay.ai/try. The tool shows you which keywords from the posting already appear in your resume and which are missing, which is often where the objective and the bullets start to drift apart.
For most experienced candidates, yes. A summary does the job better because it leads with evidence instead of a wish. But for career changers, recent grads, returners, and people targeting a very different kind of role, an objective is still the cleanest way to orient the reader in two or three lines.
The ATS itself doesn't care. It reads the whole document. The human reviewing the shortlist does care. If your top-of-document section is a vague objective, you read as less prepared than the candidate whose top section is a three-line summary with specific numbers. When in doubt, write a summary.
Two to three sentences. No more. Forty to sixty words is the sweet spot. Anything longer is either a summary in disguise or padding.
You can, but it will hurt you. The role-targeting sentence should match the actual posting. Swap the title, the company type, and the specific skill in the third sentence so it lines up with whatever posting you're sending it to. Five minutes per resume, and the match rate jumps noticeably.
Not in practice. Some people write "Career Objective" as the section header and some write "Objective." Recruiters and ATS parsers read both as the same thing. Pick whichever reads cleaner to you.
Usually yes. If you're a student with no full-time experience and one internship is the thing you're applying for, an objective tells the reader exactly what bucket to put you in. See examples 9 and 10 above.
The headline is where the role-targeting goes. The About section functions more like a summary. You can run a version of your objective as the first line of your About, but the format on LinkedIn leans heavily toward summary, not wish list.
Ready to check whether the objective you just wrote actually matches the rest of your resume? Paste both at /try. Free, no signup, results in under a minute.
Paste a job description and a resume at /try. No signup, tailored resume in under a minute.