Resume Writing: A Practical Guide for 2026

We build resume screening software, so we spend time looking at what happens to resumes after they are sent - how documents parse, how evidence is surfaced, and where information can be lost. This guide shares that product perspective; employer requirements and local conventions still vary.

Some resume advice is recycled from a decade ago. Not all of it fits every modern application workflow.

What changed, and what did not

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

Not universally true:

• "Cram it onto one page." Length should match the relevant depth of your experience and the norms of your field.
• "Match keywords exactly." Many screening systems use more than exact word matching. Use the employer's vocabulary only where it accurately describes your experience.
• "Use a creative design to stand out." Multi-column layouts and graphic skill bars can make text harder for some systems to extract.
• "Always include an objective." A concise summary is often more useful when it explains your relevant experience.

Newly true:

• Many application workflows convert a resume into structured data before or alongside human review, and that conversion can fail in specific ways.
• A skill shown only as a graphic - four filled dots next to "Python" - may not be captured as usable text.

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. Keep contact details in a clear text area rather than relying only on a page header, because some parsers handle header regions inconsistently.

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.

Less useful:

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

The second is generic and gives a reviewer little evidence to evaluate.

Experience

The bulk of the document, and the section where most of your relevant evidence should appear.

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 where you can. Scale, volume, percentage, money, and time can make a claim more specific and easier to evaluate.

Use ownership verbs honestly. "Led", "owned", "built", "designed", and "ran" signal responsibility. "Contributed to", "involved in", and "helped with" signal participation. Use the stronger word only where it is true.

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

Dates as month and year. "Jan 2021 - Present" is clear. Abbreviated or seasonal dates can be less consistently interpreted by people and software.

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.

Avoid relying only on proficiency graphics. Skill bars and rating dots may not expose useful text to a parser. Include the skill as plain text as well.

Formatting: the part that silently loses you interviews

Some application systems convert resumes into fields before or alongside human review. When extraction fails, the record a reviewer sees can be incomplete.

Common parsing risks:

The 60-second check. Open your PDF, select all, and paste it into a plain text editor. This is a quick indication of whether the document's text order is sensible, not a substitute for testing the actual application system.

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 targeted resume can make relevant evidence easier to find than a generic version. Targeting does not have to mean rewriting; it can mean reordering and clarifying details 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 unless they are expected or requested in the application location and context.
• 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.