Most resume advice focuses on content — the bullets, the summary, the keyword work. But a non-trivial share of resumes are rejected before content matters. The parser fails to extract the contact info, the date format confuses the years-of-experience filter, the file is named in a way that overwrites another candidate's resume in the recruiter's downloads. The candidate gets a silent rejection, and the resume itself was fine.

This post is about that layer — the small mechanical mistakes that disqualify a resume early. None of them require new experience or a rewrite. All of them can be fixed in under fifteen minutes if you know to look.

Where a resume actually drops

Most candidates assume rejection happens when a recruiter reads the document and decides "not a fit." That's one stage of several. The full drop pipeline looks roughly like this:

The numbers vary by industry, role, and applicant volume, but the shape is consistent: most of the loss happens before a human is involved. If your resume drops at one of the early stages, no amount of bullet polish saves it. The fix is mechanical.

File naming

The single most-overlooked detail. A recruiter downloads dozens of resumes per posting. If yours is named Resume.pdf or My_Resume_Final_v3.pdf, it lands in their downloads folder alongside thirty other files named Resume.pdf and gets renamed by the OS as Resume (3).pdf. They lose track of which is yours.

The convention that works: firstlast-jobtitle.pdf, all lowercase, hyphens not underscores, no version numbers. A recruiter scrolling through their downloads sees janedoe-marketing-manager.pdf and can find it in three seconds.

This sounds petty. It is. It also takes five seconds to fix and removes one source of silent loss.

Contact info that doesn't parse

Many ATS parsers strip out headers and footers entirely — they're treated as page chrome rather than content. If your phone number, email, or LinkedIn URL lives only in the page header, it can vanish from the parsed record. The recruiter sees a name with no way to contact you. The application is technically incomplete.

The fix: put contact info in the body of the document, on its own lines, in plain text. A small designed header at the top is fine; the actual values should appear below it in selectable text. Test by opening your PDF and copy-pasting the contact block into a plain text file. If anything is missing, the parser is likely missing it too.

Date formats that confuse the years-of-experience filter

ATS systems often calculate "years of experience" by parsing the date ranges in your work history. They look for a recognizable pattern — Mar 2020 – Present, 01/2020 – 03/2024, 2020 – 2024 — and add up the spans.

What breaks this:

• Mixed formats. Mar 2020 – Present for one role and Spring 2022 – Now for another forces the parser to guess. It often guesses wrong, attributing zero years to the latter.
• Seasonal labels. "Spring," "Summer," "Last year" don't parse. They land as zero-duration roles.
• Missing end dates. A role with a start date and no end date may be read as one day of experience.
• Reverse chronological order broken. If the parser expects most-recent-first and you've placed an older role at the top, it may compute negative experience.

The fix: same format on every row. Pick one — Mar 2020 – Present is the most parser-friendly — and apply it everywhere.

Format choices that read as "decoration" to the parser

We covered this in detail in the parser piece, but the short version applies here: tables, two-column layouts, headers/footers, image-only PDFs, and graphical skill bars are all treated as either ignored or scrambled by most parsers. Your bullet points become a wall of jumbled phrases. Your skills become "Image."

You don't need a "minimalist" resume to clear this. You need a single column, real text, and conventional section labels. Most modern resume templates handle this correctly; the trouble starts when candidates use design-tool exports (Canva, Figma) that flatten to image-only PDFs without realizing it.

The five-second test: open your resume PDF and try to copy text from it. If you can copy the body content into a plain text editor and it looks roughly right, the parser can probably read it. If you copy and get garbled spacing or nothing at all, you have a parser problem.

The other small ones that add up

A few that don't fit a category but deserve a sweep before you submit:

• Email typos. A typo in your own email is harder to catch than you'd think. If a recruiter tries to reply and the address bounces, you're done. Read it out loud.
• Stale URLs. A LinkedIn URL pointing to an old account, a portfolio link that 404s, a GitHub link that requires a login. Every link should resolve in a private browser window.
• The wrong company name in the body. This happens when you tailor a resume and miss a place where you mentioned the previous target. "Excited to bring my skills to Acme Corp" in a Globex application gets dropped to the bottom of the pile.
• The wrong job title in the file name. Same problem. The recruiter notices.
• An old summary that contradicts the rest. A summary that says "five years of experience" when your work history shows seven, or vice versa. Recruiters don't read it as a humble or a brag — they read it as carelessness.

A pre-submit checklist

Before you click submit, run this list:

1. File name follows firstlast-jobtitle.pdf (or your equivalent personal convention).
2. Contact info is selectable in the body, not just in a designed header.
3. Date format is identical on every row.
4. Two-second copy-paste test: body text copies cleanly into a plain editor.
5. All URLs in the document resolve in a private browser window.
6. The company name and the job title in the file name match the application you're submitting.
7. Email address read out loud, character by character.

It takes about three minutes once you've done it twice. A real chunk of preventable rejections vanish.

What this isn't

This isn't an argument that mechanical polish wins job offers. Strong content still does most of the work. The point of the list above is that polish is the ground floor — without it, content never gets read. With it, you're on the same starting line as the candidate whose resume is otherwise comparable.

Spending three minutes on the mechanics is a higher-leverage move than another forty-five minutes of bullet rewriting. Do the mechanics first.