Resume Writing: A Practical Guide for 2026

We build resume screening software, which means we spend a lot of time looking at what happens to resumes after they are sent — how they parse, what scores well, and what quietly disappears. This guide is written from that side of the process.

Most resume advice is recycled from a decade ago. Some of it is now actively wrong.

What changed, and what did not

Still true: clarity beats cleverness, numbers beat adjectives, and relevance beats completeness.

No longer true:

• "Cram it onto one page." Length should match depth. Two pages for ten years is normal and expected.
• "Match keywords exactly." Screening moved to language models that read meaning. "Led a team of six" satisfies a people-management requirement without the phrase.
• "Use a creative design to stand out." Multi-column layouts and graphic skill bars are the single most common cause of a strong resume arriving as a thin, low-scoring record.
• "Always include an objective." Nobody reads for what you want.

Newly true:

• Your resume is converted into structured data before a human sees it, and that conversion fails in specific, knowable ways.
• A skill shown only as a graphic — four filled dots next to "Python" — contains no text and does not exist to the software.

Structure

Use this order unless you have a specific reason not to:

Name
Email · Phone · City · LinkedIn or portfolio URL

SUMMARY
Two lines: what you are, at what level, in what domain.

EXPERIENCE
Job Title — Company
Month Year – Month Year
· Achievement with a number
· Achievement with a number

EDUCATION
Degree — Institution, Year

SKILLS
Plain, comma-separated list.

Single column. Standard headings. Real selectable text. Contact details in the body, not the page header — many parsers skip the header region entirely, and a resume with no contact details is unusable no matter how well it scores.

Section by section

Contact details

Name, email, phone, city, and one link. Full street address is obsolete and a mild privacy risk. The link should be LinkedIn or a portfolio — pick the one that helps.

Use a professional email. This still matters and people still get it wrong.

Summary

Two lines. What you are, at what level, in what domain, plus your single strongest piece of evidence.

Operations analyst, six years in e-commerce logistics. Built the demand-planning model that cut stockouts 40% at a £30M retailer.

Not:

Results-driven professional with a proven track record of delivering value in fast-paced, dynamic environments.

The second says nothing and every reader knows it says nothing.

Experience

The bulk of the document, and where nearly all the decisions get made.

Lead with outcomes, not duties. "Responsible for the content calendar" is a job description. "Grew organic traffic from 12k to 47k monthly sessions over 18 months" is evidence.

Put a number on it. Any of scale, volume, percentage, money, or time. Numbers are the difference between a claim and an achievement, and most people underuse them badly.

Use ownership verbs honestly. "Led", "owned", "built", "designed", "ran" signal responsibility. "Contributed to", "involved in", "helped with" signal participation. Use the stronger word only where it is true — but most people systematically undersell here.

Four to six bullets for recent roles, one to two for older ones. Relevance decays.

Dates as month and year. "Jan 2021 – Present" parses. "'21–now" and "Winter 2021" progressively do not, and dates matter more than most fields because seniority is calculated from them.

Education

Below experience once you have two years of it. Degree, institution, year. Drop your GPA after your first job unless it is exceptional and recent.

If you are a career changer or recent graduate, this can sit above experience — but only for the first couple of years.

Skills

A plain text list. Group logically (Languages, Infrastructure, Tools). List only what you would be comfortable being interviewed on.

No proficiency graphics. Skill bars and rating dots contain no text. A skill shown only that way is invisible to every parser, which is one of the most common ways strong candidates lose credit for things they can actually do.

Formatting: the part that silently loses you interviews

Your resume gets converted into fields before anyone reads it, and when that fails it does not report an error — it returns a thinner record, and a thin record looks like a thin candidate.

What breaks it:

The 60-second check. Open your PDF, select all, copy, paste into a plain text editor. That is roughly what the software receives. If it is scrambled there, it was scrambled for them.

Full detail in why good resumes come out blank and how to write an ATS-friendly resume.

If you work in a visual field, keep two documents: a plain parseable resume for the application form, and a designed portfolio you link to from it. The link survives parsing; the layout does not.

Tailoring

A generic resume sent to forty employers loses to a targeted one sent to twenty. Targeting is not rewriting — it is reordering and re-wording, about twenty minutes once you have a master resume to draw from.

The method, with a before-and-after example, is in how to write a targeted resume.

Things to stop doing

• "References available upon request." Assumed. Wasted line.
• An objective statement. Replace with a summary.
• Photos in US/UK/CA/IE/AU markets.
• Age, marital status, nationality unless legally required where you are applying.
• Hidden keyword blocks. Detectable, and read as dishonesty.
• Every job since you were sixteen. Ten to fifteen years, then compress.
• Buzzword stacking. "Results-driven, detail-oriented, dynamic self-starter" describes nothing, so it scores nothing.

The final pass

1. Copy-paste test — does it survive extraction?
2. Does every recent bullet contain a number?
3. Would a stranger know what you do from the summary alone?
4. Is the most relevant experience in the first third of the page?
5. Have you spell-checked names of companies and technologies specifically? (Spell-checkers miss "Kubernetes" and "PostgreSQL".)
6. Is the file named sensibly — Firstname-Lastname-Resume.pdf, not resume-final-v3.pdf?

If you want help

If you want a person to write it, that is a service rather than software, and there are long-established firms that do it well — we cover the name overlap with one of them here.

If you want automated feedback on a draft, Resume Worded and the alternatives covers that category honestly, including when you do not need it.

And if you are on the other side — receiving applications rather than sending them — that is what we build.