ATS vs Human Readers: How to Write a Resume That Passes Both

Here's the part most career advice glosses over. When you submit a resume online in 2026, it isn't read by a person first. It's read by software — an Applicant Tracking System — which scans your document for keywords, parses your work history into structured fields, and ranks your application against the job description. By the time a human recruiter sees your resume, an algorithm has already decided whether you cleared the first gate.

That changes everything about how you should write the document. Your resume now has two readers in sequence, with completely different needs, and most candidates write for only one of them.

The numbers behind the gatekeeping

The ATS isn't going away. If anything, it's getting more aggressive — older systems just looked for exact keyword matches; modern ones use machine learning to evaluate context, infer seniority, and rank candidates against benchmark profiles. Australian government recruitment, large enterprise hiring, and most professional services firms now run candidates through some form of automated screening as the first step.

Which means writing a beautiful resume that an algorithm can't parse is the same as not having a resume at all.

What the ATS actually wants

An ATS isn't trying to evaluate you as a person. It's a parser. It reads your document, breaks it into structured data (name, role, dates, skills, education), and matches the parsed content against the job description's requirements. If the parser can't read your resume cleanly — or if the keywords don't match — your application gets ranked low, often invisibly.

Three things matter to an ATS:

Clean, parseable structure. Standard section headings — Work Experience, Education, Skills — that the parser recognises. Standard date formats. Single-column layouts. Plain text that lives in the document body, not inside tables, text boxes, headers/footers, columns, or graphics. Anything fancy is anything risky.

Exact-match keywords from the job description. If the ad says "stakeholder engagement" and your resume says "client management," the ATS doesn't connect those concepts. It scores you lower on a literal keyword match. The fix is to use the language in the job ad — the exact phrasing — wherever it accurately reflects your experience.

Conventional file formats. .docx and .pdf are both fine, but check the application instructions. Some ATS handle PDFs poorly (especially scanned PDFs or PDFs exported from design tools like Canva or InDesign). When in doubt, .docx is safer.

What the ATS hates

The fastest way to fail the first gate is to use design elements that look professional to a human and break the parser. The list of common offenders:

The Canva resume that looks gorgeous in your portfolio almost certainly fails ATS parsing. The colour-blocked sidebar holding your contact details? The parser may not see them at all — your application could land with no email or phone number attached. The two-column layout where your skills sit beside your experience? The parser reads top-to-bottom, left-to-right, and ends up with a scrambled mess.

Keyword extraction, with a worked example

Most "use keywords" advice stops at the principle. Here's how to actually do it. Take a real job ad, identify the keywords, and embed them into your resume where they accurately reflect your experience.

The trick is to use these phrases exactly as written, where they accurately describe what you've done. If the ad says "stakeholder engagement," don't write "client liaison." If it says "PRINCE2," don't write "structured project methodology." The ATS isn't impressed by your synonyms — it's just running a string match.

What the human reader wants — completely different

Once your resume clears the ATS and lands on a recruiter's desk, the rules change entirely. Now you're being read by a person who has 184 other applications to review for the same role, somewhere between 6 and 30 seconds to give yours, and a lot of priors about what makes a strong candidate.

The ATS wants exact keywords. The human wants substance. Specifically:

• Quantified achievements over duty lists. "Managed a team" is dead air. "Led a team of 8 to deliver a $2M project on time and 15% under budget" lands.
• A clear narrative of progression. Each role should make the next one make sense. The reader is looking for a person who's growing, not someone who jumped sideways every two years for no reason.
• Concrete numbers. Percentages, dollar values, team sizes, project timelines, customer counts. Specifics signal credibility; vague words signal padding.
• Plain professional English. No "synergised," "leveraged," "spearheaded," or "delved into." These are the signatures of AI-written or template-driven resumes, and recruiters are now actively trained to spot them.
• White space. Dense walls of text get skimmed past. Short paragraphs and concise bullets get read.

Bridging the two readers

The challenge is that good ATS optimisation can fight good human writing. Stuffing your resume with exact-match keywords from the job ad creates clunky, repetitive prose that feels obviously gamed. Writing beautifully and naturally can leave the parser without the literal phrases it's looking for.

Here's how to do both at once.

The second version contains every keyword the first version did — PRINCE2, stakeholders, APS, vendors, executive-level reporting, SES briefings — but it reads like a person describing real work. That's the whole skill: getting the keywords in and writing for the human at the same time.

Test before you submit

Most candidates write a resume, send it out, and hope. The ones who get callbacks test their resume against an ATS first.

You can do this two ways. Manually: copy your resume into a plain text editor (TextEdit, Notepad). If the result is a clean, top-to-bottom version of your content, you're probably parser-safe. If it's scrambled, contact details have disappeared, or dates are in the wrong places — the ATS sees the same mess.

Automatically: run your resume through an actual ATS-simulation tool. There are paid versions, but the simplest free option is below.

The bigger picture

The reality of modern hiring is that there are now two readers in sequence, both filtering ruthlessly, both with different needs. Most candidates write for the human and lose at the first gate. A small number write for the ATS, get through, then bore the human into rejection. The candidates who land interviews are the ones who write for both — exactly the keywords from the job ad, embedded in genuinely well-written, achievement-focused prose.

It's harder than writing for either alone. But it's the actual game now, and once you understand the dual-reader structure, it stops feeling like a trick and starts feeling like a craft.