How to Write a Resume (Step-by-Step, With Examples)

A mid-career professional drafting a resume on a laptop

Writing a resume that gets read is not about fitting your whole career onto one page. It is about making one clear claim about the value you bring, then proving it with evidence a stranger can scan in the time it takes to read a headline. This guide builds that document in order: the claim, the top third, the evidence bullets, the cuts, the tailoring pass, and the test that tells you whether it works.

Why most resumes fail before a person reads them

A resume has two readers, and they want different things. The first is a filter: software that compares your document against the language of the job posting. The second is a person with forty other documents open, looking for a reason to stop reading. Most resumes are written for neither. They are written as a history - every job, every duty, in the order it happened.

A history answers the question "what have you done?" A resume that gets interviews answers a different question: "what will you do for us, and what is your evidence?" That is a shorter document, and it is built in a different order.

The reframe: a resume is an argument, not an archive

Think of the page as a one-page argument: a claim at the top, proof underneath. The claim is the role you are aiming at and the value you bring to it. The proof is the evidence that you have already done something like it. Everything that is neither claim nor proof is noise, and noise is what makes a reader stop.

Once you hold that frame, the editing decisions get simple. Does this line support the claim? Keep it. Does it only describe what you were assigned? Rewrite it as evidence, or cut it.

Step 1: Write the claim before you touch the layout

Before you open a template, write one sentence: "I am a [role] who [specific value] for [type of team]." It will not appear on the page word for word. It is the test every other line has to pass, and it is the reason the rest of the build goes quickly.

Mine your last three wins. Not your job description - the three moments in the last two years when something got measurably better because you were there. Those are your evidence.
Name the outcome, not the activity. "Ran the onboarding program" is an activity. "Cut new-hire ramp time from twelve weeks to seven" is an outcome.
Pick the target before the template. A resume aimed at everything is aimed at nothing. Choose the role you are actually applying for this month and build for it.

Step 2: Build the top third first

The top third of the page is where the decision gets made. A reader who gets past it will read the rest; a reader who does not will never see the rest. Build it before you write a single bullet.

Name and target title. Your name, then the role you are aiming at - not a generic label like "Professional". The target title is the first piece of tailoring.
A three-line summary. Who you are, the value you bring, and one proof point. Three lines, no more.
A skills block that mirrors the posting. Eight to twelve skills, drawn from the language of the job, not from a list of everything you have ever touched.
Your most recent role, with two strong bullets. The reader should be able to stop here and already know what you do.

If the top third is doing its job, the rest of the page is confirmation rather than discovery.

Step 3: Turn duties into evidence

The bullet is the unit of proof, and most bullets are wasted on duties. "Responsible for the quarterly report" tells a reader what you were assigned. It says nothing about whether you were good at it.

The shape that works is action, object, and change: what you did, to what, and what was different afterwards. Keep the verb first and the change last, because the change is the part the reader is scanning for.

Before and after. "Rebuilt the intake process" becomes "Rebuilt the intake process, cutting handoffs from six to two."
Scale as context, not decoration. Team size, budget, and volume are useful when they explain the difficulty of the work - and noise when they are there to impress.
One number per bullet, at most. A bullet with four numbers reads as a spreadsheet. Pick the one that shows the change.

Step 4: Cut the noise

Most resumes get better by subtraction. These are the lines that cost you space and buy you nothing:

Objective statements. They describe what you want. The reader is asking what you offer.
"References available on request." Assumed, and it spends a line.
Every duty from every role. Keep the two or three that support the claim; the rest is archive.
"Responsible for." It is the weakest opening in the language. Start with the verb.
Hobbies and interests. Unless they are directly relevant to the role, they are a line you could spend on evidence.
Formatting tricks. Columns, graphics, and text boxes can break the filter that reads your file before a person does.

Step 5: Tailor without rewriting

Tailoring has a reputation for being a two-hour job per application. It is not. Three moves get you most of the way, and they take ten minutes.

Mirror the language. If the posting says "stakeholder management", use that phrase rather than a synonym. The filter is matching words, and the reader is matching vocabulary.
Reorder, do not rewrite. Move the bullet that matches the posting's first requirement to the top of the role. Same words, different order, different read.
Swap one line. Replace the weakest bullet with one aimed at the posting's biggest ask. One line, once per application.

Step 6: Test it before you send it

Three tests, five minutes, and they catch almost everything.

The ten-second test. Hand the page to someone for ten seconds, take it back, and ask what you do and what you are good at. If they cannot answer, the top third is not working.
The filter test. Save as a plain document format, then copy the text into a blank file. If the order scrambles or the sections merge, the filter will read it the same way.
The read-aloud test. Read each bullet out loud. Anything you would not say to a colleague is a line to rewrite.

How long should it be?

One page is the right answer for most mid-career applications, and it is not a rule about your worth - it is a rule about attention. A reader who is scanning forty documents will read one page and skim two. If you have more than a decade of directly relevant work, two pages is fine, provided the second page is evidence rather than archive.

The test is not length, it is density. A one-page resume with twelve strong bullets beats a two-page resume with twenty weak ones, every time.

If you are changing fields

A career change resume does the same job with one extra move: it translates. Instead of leading with the job titles you held, lead with the outcomes you produced and the skills that carry across. The reader is not asking whether you have done this exact role before; they are asking whether the thing you did before predicts success in this one.

That usually means a summary that names the pivot directly, a skills block weighted toward the new field, and bullets that describe the transferable part of the work rather than the industry it happened in. The one-page pivot worksheet is the companion exercise if the direction itself is still fuzzy.

The resume build sheet

Fill this in before you open a template. Five rows, one page - a resume is an argument, not an archive.

Part	What you write	The test it has to pass
The claim	One sentence: the role you are aiming at and the value you bring to it.	Does every line on the page support it?
The top third	Target title, a three-line summary, a skills block drawn from the posting, and two strong bullets on the most recent role.	Could a reader stop here and already know what you do?
The evidence	Bullets shaped as action, object, change - verb first, the change last.	Does each bullet end in something that measurably changed?
The cuts	No objective statement, no duty lists, no "responsible for", no formatting tricks.	Is every remaining line either claim or proof?
The tailoring pass	Mirror the language, reorder the bullets, swap one line.	Did it take ten minutes rather than two hours?

The pre-send checklist

The target role is named in the top third, in the posting's own vocabulary.
The summary makes a claim about value, not a description of the job title.
Every bullet leads with a verb and ends with a change.
The skills block mirrors the posting instead of listing everything you have touched.
The strongest evidence sits in the top third, not on page two.
The file survives a copy-and-paste into a plain document.
The page is one page, or two with the second page carrying evidence rather than archive.
You tailored it in ten minutes rather than rewriting it from scratch.

Where people get stuck

Stuck because you have done a lot of different things. That is a targeting problem, not a resume problem. Pick the one role you are applying for this month and build the page for it; the other experience is not deleted, it is just not the claim. A resume aimed at everything is aimed at nothing.

Stuck because the numbers are not yours to share. Then describe the change without the figure: what got faster, simpler, cheaper, or less error-prone, and what your part in it was. Evidence does not require a number - it requires a change a reader can picture.

Stuck because the template looks better than the plain version. Distinctive templates often break the filter that reads your file first, and the filter decides whether a person ever sees the design. Keep the layout plain and spend the effort on the claim and the evidence instead.

Common mistakes

Writing one resume for every application, then wondering why none of them land.
Leading with duties instead of outcomes, so the page reads like a job description.
Burying the strongest evidence on page two, where the reader never arrives.
Using a template that looks distinctive but breaks the filter that reads it first.
Listing every tool and technology you have touched, which dilutes the ones that matter.
Leaving the summary as a restatement of the job title instead of a claim about value.
Sending the file without checking that the text survives a copy-and-paste.

What good looks like

The target role is visible in the top third, in the reader's own vocabulary.
The summary makes a claim, not a description.
Every bullet leads with a verb and ends with a change.
The skills block mirrors the posting rather than listing everything.
The page is one page for most mid-career roles, and every line earns its place.
The strongest evidence sits in the top third, not at the bottom.
The file survives a copy-and-paste into a plain document.
The document was tailored in ten minutes, not rewritten from scratch.

Where this fits

The resume is one surface in a system. If the summary is the part you keep rewriting, the resume summary guide goes deeper. If the skills block is where you stall, the skills section guide has the method. And if you are applying without traction, the tailoring walkthrough is the next ten minutes to spend.

None of this is about making the page beautiful. It is about making the claim obvious and the proof easy to find. Do that, and the resume stops being a document you send and starts being the reason the conversation begins.

Quick answers

Short answers to the questions this piece gets asked most.

How do I write a resume that gets past the filters?
Lead with a claim, not a history. Put the target role and a three-line summary in the top third, mirror the posting's own vocabulary in the skills block, and keep the file in a plain format so the text survives a copy-and-paste. The filter matches words; the reader matches evidence.

How long should a resume be?
One page for most mid-career applications, two if you have more than a decade of directly relevant work. The test is density, not length: a one-page resume with twelve strong bullets beats a two-page resume with twenty weak ones.

How do I turn my duties into strong resume bullets?
Use action, object, change: what you did, to what, and what was different afterwards. Keep the verb first and the change last, and use at most one number per bullet - the one that shows the change.

How do I tailor my resume without rewriting it for every job?
Three moves, about ten minutes: mirror the posting's language rather than using synonyms, reorder the bullets so the one matching the posting's first requirement sits at the top, and swap one weak bullet for one aimed at the posting's biggest ask.

Read next:You've Sent 300 Applications. Why Haven't You Heard Back? — Why volume applications fail, and the targeting shift that fixes it.You Sent 50 Applications and Got Silence. Here's Why — What actually happens to your application after you hit submit.The Experience Paradox Is a Lie. Here's How to Break In — How to break in without years of experience, and what entry level really means.

LaunchPath Careers tool: want to build this with structure instead of guesswork? LaunchPath Careers has a Resume Value Proposition Worksheet and a Resume & Applications Roadmap. Start at LaunchPathCareers.com.

LaunchPath Careers by UFO Chaser® helps job seekers build a strategy-first job search. Learn more at LaunchPathCareers.com.

Search This Blog

Cosmo's Career Strategy Blog