How to write a resume objective (and when to use one instead of a summary)

A resume objective sits at the top of the resume, just under your name and contact details, and it answers one question: what are you aiming at, and why should this employer care? Most objectives fail because they answer a different question instead. They describe what the applicant wants ("a challenging role where I can grow and develop my skills") and say nothing about the role in front of them. A reader learns nothing from that sentence, and a sentence that teaches nothing is a sentence the reader skips.

The test for a good objective is simple. Cover up the job title and the company name. If the sentence still makes sense for every job you might apply to, it is too vague. A good objective only makes full sense for the posting it was written for, because it names the work, the evidence behind it, and the direction you are heading in.

Objective vs summary: which one do you need?

An objective looks forward. A summary looks back. That single difference decides which one belongs on your resume.

• Use an objective when your past does not yet explain your target: you are a new graduate, you are changing field, you are returning after a break, or you are applying for a role that is a step sideways rather than a step up.
• Use a summary when your recent experience already matches the target role, and the reader mainly needs to see the shape of that experience in three lines. The structure for that is in how to write a resume summary.
• Use one, not both. An objective followed by a summary repeats the same claims in two voices, and the second one is the one the reader skips.
• Use neither when the resume is already strong on its own: a long, directly relevant work history with clear results in the first few bullets does not need an introduction, and a weak introduction only delays the evidence.

One more distinction matters. An objective is not a cover letter in miniature, and it is not a list of skills. Its job is to aim the resume. The skills, the results, and the reasoning belong in the sections below it, where they can be checked.

The two-sentence structure that works

Keep the objective to one or two sentences, and give each sentence one job.

Sentence one: who you are, with evidence. Name your current position or your most relevant qualification, plus one concrete piece of evidence: a degree, a project, a skill you have actually used, or a result you can defend. Adjectives without evidence do not count. "Detail-oriented" is a claim; "accounting graduate with a final-year project on cash-flow forecasting" is a fact the reader can use.

Sentence two: the target role, and what you will do for the employer. Name the role type, and say what you bring to it in terms of the employer's problem, not your own ambition. The posting itself tells you what that problem is: read the first paragraph and the first three requirements, and mirror their language only where it is honestly true of you.

The second version is longer by only a few words, but it does four things the first one does not: it names a real qualification, it names real evidence, it names a real role, and it connects the evidence to the role. Nothing in it is invented, and every claim in it can be expanded on in the sections below.

Tailor the objective to each posting

An objective written once and sent everywhere is, by definition, the vague kind. The tailoring does not need to be a rewrite from scratch. Change three things per posting, and leave the rest alone:

1. The role title. Use the posting's own title, or the closest honest equivalent, rather than a generic label like "entry-level position".
2. The evidence you lead with. Pick the qualification, project, or experience that matches this posting's top requirements, even if it is not the one you would lead with for a different posting.
3. The employer's problem. One clause that names the work this role actually does, taken from the posting, not from a template.

This is the same discipline as tailoring the rest of the resume, covered in how to tailor your resume to a job description: match the evidence to the posting, and never invent evidence to fill a gap. If a posting asks for a skill you do not have, the honest move is to leave that skill out of the objective and let the rest of the resume speak, not to claim it in the first two sentences where it will be checked first.

Examples for the three cases where objectives help most

New graduate. Lead with the degree and the most relevant project or placement, then the role. "Marketing graduate with a dissertation on email campaign testing and a summer placement writing social copy for a local charity. Seeking a junior marketing role focused on campaign testing and measurement."

Career changer. Name the direction, not the old field, and use the transferable evidence. The fuller framing for a pivot is in how to write a resume for a career change, but the objective version is one sentence: "Support analyst moving into product analytics, with three years of customer data work and a completed analytics certificate. Seeking an analyst role where that reporting experience covers the product reporting the posting describes."

Returning after a break. Do not explain the break in the objective; that belongs in a short, plain note elsewhere on the resume. The objective only needs the direction and the evidence: "Former project coordinator returning to operations work, with five years of scheduling and supplier coordination before a two-year break. Seeking an operations coordinator role where scheduling and supplier work are the core of the job."

In each example, notice what is missing: no adjectives doing the work of evidence, no claim about a skill that is not shown somewhere else on the resume, and no sentence about what the applicant hopes to gain. The objective points outward, at the role, and the rest of the resume proves it.

Five mistakes that sink most objectives

• Writing about yourself only. "I am looking for an opportunity to grow" tells the employer what you want, not what you offer. Flip every clause so the employer is the subject: what problem of theirs does your evidence help with?
• Listing adjectives instead of evidence. Hardworking, motivated, passionate, and detail-oriented appear on almost every resume, which means they distinguish no one. Replace each adjective with the fact that was supposed to support it, or delete it.
• Claiming skills you do not have. The objective is the first thing read and the first thing checked. A claimed skill that the rest of the resume cannot back up damages the whole application, not just the opening lines.
• Writing three or four sentences. An objective that long is a summary with the wrong name, and it delays the work history the reader came to see. Two sentences is the limit; one is often enough.
• Keeping the same objective for every application. A generic objective is not a time saver, it is a signal: this applicant sent the same resume everywhere. Change the role title, the lead evidence, and the employer's problem for each posting, even when the rest of the resume stays the same.

The 60-second objective audit

Before you send any application, run this check:

1. Is it one or two sentences? Longer than that, cut it.
2. Does it name a specific role? If it fits every job, it fits none of them.
3. Is every claim backed up below? Each skill, qualification, and result should appear again, with detail, in the body of the resume.
4. Does it point at the employer, not at you? The last clause should be about the work, not about your growth.
5. Would it survive being read aloud? Read it once, out loud. If it sounds like a template, it reads like one too.

An objective is a small piece of writing with a large effect: it is the first claim a reader tests, and a specific, honest one makes every section below it easier to believe. Write it last, after the rest of the resume is done, so that every claim in it is something you have already proved on the page. One practical check before you send: run the draft through Tailr's ATS checker and see whether the skills your own experience proves are the skills the posting is actually asking for.