How to Write an ATS-Friendly Resume in 2026 (Without Making It Ugly)

Most advice on this topic is either five years out of date or written to sell a template. The underlying situation is simpler than either suggests: your resume gets converted into structured data before anyone reads it, and that conversion fails in specific, knowable ways.

Design for the conversion and you are fine. You do not have to make the document ugly.

What actually breaks

Multi-column layouts

This is the big one. A PDF does not store "column" — it stores text with coordinates. The parser reconstructs reading order, and with two columns it can interleave them. Your skills sidebar gets woven through your employment history and the result is a record where nothing attaches to the right thing.

If you keep two columns, test it: copy all the text out of your own PDF and paste it into a plain text editor. What you see is roughly what a parser sees. If it is scrambled for you, it is scrambled for them.

Contact details in the page header

Templates love putting your name and email in the header region. Plenty of parsers skip that region entirely, and a resume with no contact details is a resume nobody can act on even if it scores well.

Put them in the body, at the top.

Text inside graphics

Skill bars, rating dots, infographic timelines. Five filled circles next to "Python" contains no text and conveys nothing to a parser. If a skill only appears as a graphic, it does not exist.

Tables used for layout

A table is a structural hint and usually the wrong one. Dates in a left column and descriptions in a right column frequently parse as two unrelated lists — so your roles lose their dates, and with them any calculation of your seniority.

Non-standard headings

"Where I've Made an Impact" is a nicer heading than "Experience." Parsers look for the boring ones. Use conventional section names — Experience, Education, Skills — and put personality in the content.

Creative date formats

"Jan 2021 – Present" parses. "'21–now", "Winter 2021" and "2021 to date" progressively do not. Dates matter more than most fields because seniority is computed from them.

What stopped mattering

Some advice you can drop.

Exact keyword matching. Screening has largely moved from string matching to language models. "Led a team of six engineers" satisfies a people-management requirement without containing the words "people management." Write naturally in the vocabulary of your field.

Hidden keyword stuffing. White text on white background, keyword blocks in 1pt font. This never worked as well as claimed and now actively harms you — it is detectable, and when a human sees it the read is dishonesty.

Rigid one-page rules. Length should match the depth of what you have done. Two pages for ten years of experience is normal.

Avoiding all formatting. You do not need a plain text document. Bold, headings, bullets and reasonable typography are all fine. It is structure that has to stay simple, not style.

A layout that works

[Name]
[Email · Phone · City · LinkedIn/portfolio URL]

SUMMARY
Two or three lines. What you do, at what level, in what domain.

EXPERIENCE
[Job Title] — [Company]
[Month Year] – [Month Year]
· Achievement with a number in it
· Achievement with a number in it

EDUCATION
[Degree] — [Institution], [Year]

SKILLS
Comma-separated list, plain text.

Single column, real text, standard headings, dates the parser can read. Everything else is styling.

If you work in a visual field

The advice above is genuinely irritating if you are a designer, and pretending otherwise is unhelpful. The workaround is two documents:

• A plain, parseable resume for the application form.
• A designed portfolio you link to from within it.

The link survives parsing. The layout does not. You lose nothing, because the person who is going to be impressed by your layout will click through — and the parser that would have mangled it never sees it.

Making the content strong once it parses

Getting read is necessary, not sufficient. Once your resume is structured properly, the content has to hold up.

The single highest-return change is putting numbers on outcomes. "Improved onboarding" is a claim. "Cut onboarding from 3 weeks to 8 days" is evidence. Scale, volume, percentage, time — any of them turns an assertion into something checkable.

Mirror the language of the posting where it is genuinely accurate. If they call it "demand planning" and you called it "forecasting", use theirs — not to game a matcher, but because the person reading is looking for their own vocabulary.

And put the relevant thing first. Reverse chronological order is the convention, but within each role the first bullet should be the one closest to the job you are applying for.

The 60-second test

Before you submit:

1. Open your PDF, select all, copy.
2. Paste into a plain text editor.
3. Read it.

Is your name there? Your email? Is each job attached to its own dates? Are your skills a readable list rather than fragments interleaved with something else?

That is approximately what the screening system receives. If it reads badly there, fix the layout — not the content.

What happens on the other side

If you want the full picture of what your resume goes through after you upload it — parsing, scoring, then ranking — we wrote it up in AI resume screening: how it works. Knowing the mechanism makes the formatting advice above feel less arbitrary.

And if you have been rejected quickly and repeatedly, the causes are usually narrower than people assume — see why your resume gets rejected.