Get Past the ATS Without Sabotaging the Human Read

Two Readers, One Layout

The 75% Myth, and What Actually Happens

The "75% rejected by ATS" claim has no traceable methodology behind it. What is verifiable, from actual recruiter interviews conducted in late 2025, is the opposite: 23 of 25 recruiters said their ATS was not configured to auto-reject on formatting or content at all¹.

The two exceptions had strict, disclosed rules ("match less than 75% of required skills," "fewer than 7 of 10 must-have skills present"). That is not the invisible black-box rejection the myth implies.

What is really happening is closer to this. Almost every recruiter, 99.7% of the 384 surveyed in Jobscan's 2025 report, uses the ATS to filter a large candidate pool down to a shortlist². Three-quarters of them filter by skills first; more than half use job titles as keyword filters².

The resumes that don't clear those filters aren't rejected. They're just not surfaced.

The distinction matters because it changes what you optimize for. You are not writing a resume to trick a rejection algorithm that mostly doesn't exist. You are writing a resume that shows up in the recruiter's filtered results and, once it does, survives seven seconds of human attention.

Harvard Business School's Hidden Workers study makes the size of this filtering effect concrete: 88% of employers agree qualified high-skills candidates are vetted out because they don't match the exact criteria in the job description; the number climbs to 94% for middle-skills roles⁶.

The filter is real. Beating it is not about beating a robot. It is about naming the same things the job description names, in a format both readers can extract.

What the Parser Sees vs. What You Sent

Take Ravi Patel, a mid-career mechanical engineer applying to a manufacturing lead role. He built his resume in a template he liked: two columns, a sidebar with icons for each skill, his name and contact info sitting inside the document header, and a small photo of himself top-right. It looked designed. He was proud of it.

He got no callbacks in six weeks.

The parser at the other end of his submission was doing one job: extract a name, contact info, and a stack of company / title / dates blocks into structured fields.

Greenhouse's own documentation lists five things that reliably break that extraction: graphics and photos, contact info trapped in a header or footer, tables, columned layouts, and any resume uploaded as an image rather than a document³. Ravi's resume had four of the five.

The record the ATS handed the recruiter had a blank Name field: Ravi's name lived in the page header, which the parser skipped. It had a Company field that read "Data Science," which was actually his sidebar's skills header, misread as an employer once the columns collapsed.

And it had a Skills list with three of his nine actual skills. A recruiter searching "mechanical engineer, GD&T, Solidworks" never saw him. His profile didn't match, not because he wasn't qualified, but because the fields the search ran against were empty or wrong.

I have made the same mistake. Two years into my career I paid a designer $200 for a two-column resume with a colored sidebar and small icon glyphs next to each skill. I applied to fifteen roles and got one reply.

When I finally pasted the PDF into a plain-text converter to see what the parser was seeing, my work history had merged into a single unreadable paragraph with the sidebar text interleaved line-by-line. Every application I had sent for two months had landed in the ATS as gibberish.

Ravi's fix took an hour. Single column. Contact info in the document body, not the header. No sidebar, no icons, no photo. Section headings in ALL CAPS so the parser could find the boundaries⁷. Skills listed as plain text separated by commas.

Nothing else changed. Same content, same bullets, same numbers. Callback rate went from zero in six weeks to three in ten days.

Five Steps to a Two-Reader Resume

1. Move to a one-column layout. No sidebars, no tables, no text boxes. Contact info in the document body directly under your name, not in the page header. This one change fixes the majority of parse failures³⁷.

If you built your resume in a template, the fastest fix is to open a blank document and rebuild the content in a single flowing column. Your bullets are already written. You are only changing the container.

2. Strip the decoration. No embedded graphics, no photo, no icon skill-meters, no colored shading behind section headings. Use one standard font (Arial, Calibri, or Times New Roman) at 10–12 point⁸.

ALL-CAPS section headings ("EXPERIENCE," "SKILLS," "EDUCATION") give the parser unambiguous section boundaries⁷. Spell out acronyms on first use so a filter search on the spelled-out form still matches. This is not a design chapter. It is a legibility chapter.

3. Mirror the job posting into your Summary and Skills. Open the job description. Copy the exact phrases in the "must have" section, for example "SQL," "Python," "root-cause analysis," "cross-functional program management," and make sure each one appears verbatim in either your Summary line or your Skills list².

Do not paste the whole job description; recruiters see the same trick every day. Weave the keywords into the bullets they belong to; a skill listed in an achievement outranks one buried in a comma-separated list⁷.

4. Save as PDF and DOCX, then send whichever the posting asks for. Greenhouse, the only major ATS with a public candidate-facing help doc on this, accepts both without stating a preference⁹.

Neither is universally "safer." The single defensible rule: if the posting names a file type, send that one exactly. If it does not, PDF preserves layout across recruiter monitors more reliably than DOCX. Save both versions so you can send either without reformatting.

5. Run the file through a free checker before you apply. Two options that will each score your resume against the specific job posting: Jobscan, which returns a percentage match rate and recommends 80% or higher¹⁰; and Resume Worded, which scores across 30+ ATS-compliance and impact checks and treats 85+ as strong¹¹.

Do not rely on Microsoft's Resume Assistant. Microsoft discontinued it in August 2022¹². Any tool that opens your resume in your browser and reads it back to you in plain text tells you what the parser is going to see.

The ATS-Safe Skeleton

Rebuild your resume in this exact order. No sidebars, no tables, no icons.

YOUR NAME (14–16pt, bold, top of page)
City, State · phone · email · linkedin.com/in/handle
   ↑ in the document body, not the page header

SUMMARY  (ALL CAPS section heading, 12pt bold)
Two lines. Target role + 2–3 signature skills + one metric.
Mirror keywords from the job posting verbatim.

EXPERIENCE
Company · City, State · Month YYYY – Month YYYY
Job Title
· Achievement bullet with a number
· Achievement bullet with a number
· Achievement bullet with a number

SKILLS
Comma-separated list. Include the spelled-out form of every acronym.

EDUCATION
Institution · Degree · Year

Save as LastName_FirstName_Resume.pdf and LastName_FirstName_Resume.docx. Send whichever the posting asks for; if silent, send the PDF.

Seven Checks Before You Send

The parser lets you through. The recruiter now has seven seconds. What they read in those seven seconds is a stack of bullets. Every bullet is either doing the work of getting you interviewed, or it is a sentence they skim past. That's Chapter 5.