How to Write a Resume in 2026: A Step-by-Step Guide

Updated August 16, 2026 · 18 min read

Write a resume in seven steps: choose reverse-chronological format, write a functional header, draft experience bullets as evidence (verb, specific action, measurable result), build a searchable hard-skills section, add education and certifications, write the 2-3 line summary last, then tailor per application.

A resume has two readers, and you have to satisfy both. The first is software: an applicant tracking system that parses your file into a database recruiters search. The second is a human whose first look is brutally short: recruiters spent an average of 7.4 seconds on their initial screen of a resume in the Ladders 2018 Eye-Tracking Study, which recorded how 30 recruiters read candidate documents over 10 weeks. Everything in this guide serves one of those two readers, usually both.

This is the full walkthrough: what goes on the page, in what order, and how to write each part so it reads as evidence rather than self-description. If you already have a draft, jump to the section you're weakest on; the steps stand alone.

Step 1: Choose the reverse-chronological format

Unless you have a specific reason not to, use reverse-chronological format: most recent job first, working backward. It's what recruiters expect, it's what parsers extract most reliably, and it answers the reader's first question, what are you doing right now, immediately.

The alternatives have narrow uses. A functional (skills-based) resume hides your timeline, and recruiters know it; many treat it as a red flag. A hybrid format, which leads with a strong skills section before a full chronological history, is legitimate for career changers. The full comparison lives in the best resume format for 2026.

Layout matters as much as order. A single-column layout parses cleanly through tracking systems; tables and sidebars are the most common reason a good resume turns into scrambled data. Every ATS-Verified template we offer is single-column for exactly this reason. If you want the details, read how ATS parsing actually works.

Step 2: Write a header that's pure function

Your header needs five things: your name, a professional headline, a phone number, an email address, and your city and state. Add a LinkedIn URL or portfolio link if it strengthens your case, and make sure the profile matches the resume before you do.

The headline under your name deserves more thought than it usually gets. Use the title you're applying for, or the closest true version of it, plus one credential or specialty: 'Registered Nurse, BSN | Medical-Surgical' or 'Project Manager, PMP' (see the headline in action in our nurse and project manager resume examples). Recruiters search databases by title; a headline that matches the job's language surfaces you.

Leave out what employers no longer expect: a photo, your full street address, date of birth, and 'References available upon request'. None of it helps, and in the US, photos actively work against you because many companies discard them for compliance reasons.

Step 3: Write the summary last, but place it first

The 2-3 line professional summary at the top is your skim-reader insurance: if the recruiter reads nothing else, this paragraph has to carry your case. Structure it as title and years, one or two proof points with numbers, and the specialty or credential that matches the posting.

Write it after you've written everything else. It's a distillation, and you can't distill a document that doesn't exist yet. A working formula: first sentence, title plus years in a concrete context; second sentence, your strongest quantified achievement; third, the credential or specialty aligned with the target job. Then delete every empty adjective that crept in.

One caution: 'hardworking professional with a passion for excellence' says nothing an employer can verify. If a sentence could appear on anyone's resume, it's not doing work on yours. Steal structures, not sentences, from these resume summary examples.

Step 4: Turn your experience into evidence

The experience section is the resume. For each job, list title, employer, location, and dates in a consistent pattern, then 3-5 bullets. The bullets are where most resumes fail, because most people write job descriptions ('responsible for managing social media accounts') instead of evidence ('grew Instagram engagement 40% in six months by shifting to short-form video').

Each bullet should follow the same deep structure: a strong verb, the specific thing you did, and the measurable result or scale. Numbers are the fastest credibility signal a resume has: money, percentages, time, volume, people. Almost every job produces them, even ones that don't feel numeric; quantifying your bullet points shows how to find yours.

Give your most recent role the most space and the most impressive bullets. A job from eight years ago can survive on two lines; a job from last year cannot. And start every bullet with a verb that means something ('led', 'built', 'cut', 'negotiated'), not 'assisted with' or 'was responsible for'. A full list is in action verbs that actually work.

Step 5: Build a skills section recruiters can search

The skills section exists for two audiences: the recruiter scanning for must-haves and the database query looking for exact keywords. Serve both with a compact list of hard skills (tools, technologies, certifications, languages, methodologies), grouped by category if you have more than eight.

Two rules keep it honest and effective. First, list only skills you could discuss in an interview tomorrow; a skills section is a promise, and the phone screen collects on it. Second, mirror the job posting's exact vocabulary for skills you genuinely have, including both spelled-out and abbreviated forms ('customer relationship management (CRM)') so any search matches.

Soft skills mostly don't belong in this list; 'communication' as a bullet point convinces no one. Show them inside experience bullets instead ('presented monthly results to executive stakeholders'). The full treatment is in the resume skills section guide.

Step 6: Education, certifications, and everything optional

For most experienced candidates, education is short: degree, institution, graduation year (optional after a decade), listed after experience. Recent graduates flip the order and expand it: relevant coursework, GPA above 3.5, honors, and substantial projects can carry a thin experience section.

Certifications and licenses get their own clearly-labeled section whenever they matter to the job, and in fields like healthcare, trades, finance, and transportation, they're the first thing screened. List the exact name, issuer, and date. 'Certifications' as a heading parses reliably; don't bury a nursing license inside a skills list.

Optional sections (volunteer work, projects, publications, languages) earn their space only by supporting your candidacy for this job. A projects section is often the strongest card for developers and students; an interests line is almost never the best use of its space.

Step 7: Tailor, cut, and proofread

A resume is finished per application, not per lifetime. Before each submission, spend fifteen minutes aligning it to the posting: match the headline to the target title, reorder bullets so the most relevant lead, and cover the posting's key skills in your words for things you've actually done. The efficient version of this process is in how to tailor your resume to a job description.

Then cut. One page is right for most people under ten years of experience; two pages are fine when the second page is genuinely strong (the length question, settled). Every line you cut makes the remaining lines more likely to be read.

Finally, proofread like it's a work product, because to the reader, it is. Read it aloud, run a spellchecker, and have one other person look at it. A typo in 'attention to detail' is a joke recruiters share, and hiring managers report discarding resumes over a single careless error.

Before and after: real bullets rewritten

The fastest way to internalize the evidence structure is to watch weak bullets become strong ones. Each pair below keeps the same underlying job; the only thing that changes is what the writer chose to say about it. Notice that every rewrite does three things: swaps a duty verb for an action verb, names the specific thing, and attaches a number or a scale.

  • Before: "Responsible for handling customer inquiries." After: "Resolved 40-60 customer inquiries daily across phone and chat, holding a 92% first-contact resolution rate." The before version describes the job posting; the after version describes you.
  • Before: "Helped with social media marketing." After: "Wrote and scheduled 5 posts weekly across three channels, growing engagement 40% in six months by shifting the mix toward short-form video." "Helped with" hides your actual contribution; the rewrite claims exactly what you did and what happened.
  • Before: "Managed a team." After: "Led a team of 8 support agents, cutting average response time from 6 hours to 90 minutes over two quarters." Team size and the before-and-after numbers turn a title into a result.
  • Before: "Worked on the company website." After: "Rebuilt the checkout flow in React, reducing cart abandonment 18% and support tickets about payment errors by half." Name the technology, name the outcome, and the bullet works for both the keyword filter and the human.
  • Before: "Duties included inventory management." After: "Ran weekly cycle counts across 4,000 SKUs, cutting inventory variance from 3% to under 1% in one year." Even the most routine-sounding duty contains a measurable standard; the rewrite states it.
  • Before: "Excellent communication skills." After: "Presented monthly performance reviews to executive stakeholders and translated the findings into team priorities." Claimed qualities convince no one; shown behavior does. This is also why soft skills live in the experience section, not the skills list.

Before and after: the summary

The same transformation applies to the summary, where the stakes are higher because it is read first. Here is a typical draft: "Hardworking and motivated professional with excellent communication skills and a passion for customer service, seeking a challenging position in a dynamic company." Thirty words, zero facts. It could top any resume in the pile, which means it does nothing for this one.

The rewrite, using the formula from Step 3: "Customer service team lead with 6 years in high-volume SaaS support. Cut average first-response time 60% while covering 3,000+ tickets per quarter, and trained 12 new agents on the escalation playbook. Zendesk administrator, fluent in Spanish." Same person, same history: but this version gives the recruiter a title to classify you by, two numbers to believe, and two searchable credentials.

If your draft summary survives the swap test (could a stranger in your field claim this paragraph word for word?), it is not finished. Every phrase that any candidate could claim gets deleted or replaced with something only you can claim. More worked patterns by field and level are in these resume summary examples, and if you have no experience to summarize yet, a two-line objective does the job instead: resume objective examples shows the difference.

How the resume changes with your experience level

The seven steps hold at every career stage, but the weight each section carries shifts dramatically. Calibrating to your level is the difference between a resume that looks right and one that looks borrowed.

No experience yet: build the page from adjacent evidence

With no work history, the experience section is replaced, not left thin: coursework with concrete outcomes, capstone and class projects, volunteering, club leadership, and part-time or seasonal work in any field all produce legitimate bullets when you write them in the same verb-action-result shape. "Coordinated a 12-person fundraiser that cleared $4,000" is evidence, whoever paid for it. Education moves above experience, expands to include relevant coursework and GPA if it is above 3.5, and a projects section often becomes the strongest block on the page.

One page, always, and resist the urge to pad: a focused half-empty page beats a full page of filler that a recruiter has to dig through. The full framework, including what to do in the summary slot, is in how to write a resume with no experience, and the first job example shows a finished page built this way.

Early career, 1-5 years: promote work, demote school

The first real jobs now carry the page. Experience moves back on top, each role gets 3-5 quantified bullets, and education shrinks to degree, school, and year. The common early-career mistake is keeping student-era content past its expiry: the semester project that anchored your first application should give way to what you shipped at work, and high school disappears entirely once a degree or two years of work exist.

This is also the stage where the headline starts working for you. "Marketing Coordinator" under your name, matched to the posting's title, gets found in recruiter searches that "recent graduate" never will.

Mid-career, 5-15 years: select, compress, quantify harder

By now the problem is abundance. The fix is a deliberate gradient: your current and previous role get the most space and your best numbers; roles older than ten years compress to a title, employer, and dates, or a single line each. Two pages are legitimate once the second page is genuinely strong, a judgment call covered in how long a resume should be.

Mid-career bullets should also climb a level of abstraction: less "what I did daily", more "what changed because I was there": budgets owned, processes replaced, revenue affected, people developed. If your title history does not match the direction you want next, the hybrid structure in the best resume format guide reorders the emphasis without hiding the timeline.

Senior and executive: scope first, tasks never

Senior resumes are read for scope and trajectory: the size of the teams, budgets, and outcomes you were trusted with, and whether each move expanded them. Lead every role with one line of scope ("led a 40-person engineering org across three product lines, $12M budget") before the achievement bullets, and cut task-level content entirely; a VP resume that mentions calendar management undermines itself.

Two pages are standard, a third is almost never earned, and the summary becomes a positioning statement: the throughline of a 20-year career in three sentences, aimed at the specific mandate you want next. The senior software engineer and operations manager examples show the register.

The mistakes that cost interviews

Recruiters reject most resumes in seconds, and usually for one of a short list of preventable reasons. Check your draft against each of these before it goes anywhere:

  • Duties instead of evidence. The single most common failure. If a bullet could be pasted from the job description, it proves employment, not performance.
  • A layout that fights the parser. Tables, text boxes, two columns, and headers containing your contact details all scramble extraction in tracking systems. Single column, standard headings, no exceptions for portal applications.
  • One resume for every job. Unmatched titles and missing keywords lose to tailored competition every time. Fifteen minutes per application is the going rate for interviews.
  • The empty summary. "Motivated professional seeking opportunities" wastes the most-read lines on the page. Facts or nothing.
  • Keyword stuffing. Listing skills you cannot discuss, or pasting the posting into white text, fails at the phone screen if not before. Parsers have gotten better at detecting it, and interviewers always could.
  • Unexplained gaps. A silent two-year hole invites a worse assumption than almost any truth. One neutral line handles it: employment gaps on a resume shows the phrasings.
  • Typos and inconsistent formatting. Mixed date formats, drifting fonts, and a misspelled skill read as carelessness in miniature. Hiring managers report discarding resumes over a single error; proofread aloud, then have someone else read it.
  • The wrong file. A .pages file, a photo of a resume, a PDF exported as an image, or final-v7-REAL.pdf as a filename. Text-based PDF, named Firstname-Lastname-Resume.pdf, every time.
  • Decoration doing the work. Skill bars, star ratings, headshots, and icon fonts communicate nothing verifiable and parse as noise or worse. Spend the same space on one more quantified bullet.

The formatting specs, settled

Formatting questions consume a disproportionate share of resume-writing time, and almost all of them have boring, settled answers. Here they are, so you can spend the hours on content instead:

  • Font: one professional typeface for the whole document. Calibri, Arial, Helvetica, Georgia, and Garamond all read well on screen and parse cleanly; novelty fonts and script faces do neither. Never mix more than two.
  • Size: 10.5 to 12 points for body text, 13 to 15 for section headings, larger only for your name. If you are shrinking to 9.5 to make it fit, the problem is word count, not typography.
  • Margins: 0.5 to 1 inch on every side. Below half an inch the page reads as cramped and some parsers clip the edges of the text block.
  • Line spacing: 1.0 to 1.15 within entries, with a visible gap between sections. White space is not wasted space; it is what makes a 7-second skim land on the right lines.
  • Dates: one format everywhere, month and year ('Jan 2023 - Present' or 'January 2023 - Present'). Years alone are acceptable for roles older than a decade, but never mix the two styles within the recent history.
  • Color: black text on white. One restrained accent color on headings is fine in most industries; text in light gray is the most common self-inflicted readability wound.
  • File format: a text-based PDF unless the posting explicitly demands .docx. PDF locks your layout on every screen; the test for 'text-based' is whether you can select and copy the text in a viewer. If you cannot, the parser cannot read it either.

Special situations, briefly

Three situations bend the standard advice enough to deserve their own guides. Career changers should keep the reverse-chronological skeleton but lead with a skills block that reframes their history toward the target field; the mechanics are in the career change resume guide. Anyone returning after time away should address the gap in one factual line and spend the resume on evidence, not explanation: employment gaps on a resume covers the phrasing and where the cover letter helps.

And if you are writing your very first resume, the entire experience-section problem is different in kind, not degree: how to write a resume with no experience rebuilds the seven steps for a page with no jobs on it. For every situation, the finished-product references are the same: browse resume examples by job title and steal the structure of the one closest to your target.

The order of operations, condensed

  1. Pick reverse-chronological format and a single-column, parseable layout
  2. Write the header: name, target-title headline, phone, email, city, and one link if it helps
  3. Draft experience bullets first (verb, specifics, measurable result), with the most space on recent roles
  4. Build the skills section from the job posting's vocabulary, hard skills only, honestly
  5. Add education, then certifications with exact names and dates
  6. Write the 2-3 line summary last, distilling your strongest evidence
  7. Tailor to the posting, cut to length, proofread aloud, export as PDF named Firstname-Lastname-Resume.pdf

Frequently asked questions

How long does it take to write a good resume?
Plan for two to four focused hours for the first complete draft, spread over two sittings: one to collect the raw material (jobs, dates, numbers, certifications) and one to write bullets and the summary. The gap between sittings matters, because numbers you could not remember on Tuesday surface by Thursday. After that, budget fifteen minutes of tailoring per application, which is where most of the interview-rate difference actually comes from.
Should I use an AI tool to write my resume?
As a drafting assistant, yes; as a ghostwriter, no. AI is genuinely useful for turning your raw facts into tighter phrasing, suggesting verbs, and cutting filler. It fails when it invents: generic AI-written resumes converge on the same phrases, and any claim you did not supply is a claim you cannot defend in an interview. Feed it your real numbers and edit what comes back, and make sure the result still sounds like a person who did the work.
Do I need a different resume for every application?
You need one master resume and a tailored variant per application, which is much less work than it sounds. The master holds everything: all roles, all bullets, all skills. Tailoring is subtraction and reordering: match the headline to the posting's title, lead each role with the most relevant bullets, and mirror the posting's vocabulary for skills you actually have. The tailoring guide turns this into a repeatable fifteen-minute routine.
What should I leave off a resume in 2026?
Photos, date of birth, marital status, and full street address (city and state are enough); "References available upon request"; an objective statement if you have any experience to summarize instead; high school once you have a degree or two years of work; skills everyone claims (Microsoft Word, email); and any job older than about fifteen years unless it directly serves the target role. Every one of these either adds legal risk for the employer, wastes space, or dates you without helping you.
How far back should my work history go?
Ten to fifteen years of detailed history is the working standard. Roles inside that window get full entries with bullets; older roles that still support your candidacy compress to a one-line entry (title, employer, dates) under a heading like 'Earlier experience', and roles that add nothing simply come off. This is not about hiding your age, though it helps with that too: it is about relevance density. A recruiter deciding in seconds should spend those seconds on what you have done recently, and a 1998 job described in four bullets steals space from the evidence that actually wins the interview.
Do resume templates hurt your chances with applicant tracking systems?
Badly built ones do; well built ones do not. Templates fail when they rely on tables, text boxes, multiple columns, or graphics to create their layout, because those structures scramble the reading order when a parser flattens the file to text. A template that keeps a single column, standard section headings, and real text everywhere parses exactly like a plain document while looking considerably better to the human reader. We tested this mechanically across parsing engines in the 2026 ATS template study, and every template that passed is marked ATS-Verified in the template gallery.
Resume or CV: which one am I writing?
In the US and Canada, employers asking for either almost always want the 1-2 page achievement-focused document this guide describes. A true CV (the multi-page academic document listing publications, grants, and teaching history) is expected only in academia, research, medicine, and some international applications. In the UK, Ireland, and much of Europe, "CV" is simply the local word for a resume, and the same writing rules apply.

Sources

Facts, prices, and policies verified on August 16, 2026. They can change; vendor checkout pages are the final word.

Build yours in minutes

Pass the bots

Every template is built single-flow and parse-tested. ATS View shows you exactly what an applicant tracking system extracts from your resume, before you send it.

AI that sounds like you

Our writing suggestions start from your real experience, not a phrase library. You keep your voice; the AI handles structure, verbs, and cut-the-fluff editing.

One document, every tool

Your resume powers everything: the ATS report, the job-match analysis, and a cover letter in the same design. Switch templates any time and your content reflows without retyping.

Create my resume, no sign-up needed

No sign-up required to start. Import your old resume or build from scratch, and see exactly what the bots read on your finished PDF.