Reading ATS-Filtered Candidate Resumes

Why ATS Output Looks Nothing Like the Resume a Candidate Submitted

Most small business owners open an ATS-parsed resume and assume they’re seeing what the candidate sent. They’re not—and that gap costs real hiring decisions. Understanding exactly what happened between submission and your screen is the foundation of reading these documents well.

When a candidate uploads a resume, the ATS parses it: it reads the raw file, strips out most formatting, and maps text into structured fields—name, contact info, work history, education, skills. What you see in your dashboard is a reconstruction, not the original. The quality of that reconstruction depends on how cleanly the resume was written, which file format was used, and how sophisticated the ATS parser is. All three vary enormously.

The practical consequence is that a strong candidate with an unusually formatted resume may look thin on your screen, while a mediocre candidate who wrote a plain, keyword-dense document may look polished. Reading ATS output well means accounting for both of these distortions.

What the ATS Actually Does to a Resume

Before you can interpret filtered output, you need a working mental model of the transformation process. ATS systems generally do five things to every resume they receive:

Strip visual formatting. Columns, tables, text boxes, headers, footers, and graphics usually don’t parse. Any information a candidate placed in a sidebar or multi-column layout may be scrambled or dropped entirely.
Segment text into categories. The parser assigns blocks of text to fields like “Job Title,” “Employer,” “Dates,” and “Responsibilities.” When the parser is wrong about which block goes where, data ends up in the wrong field—or nowhere.
Extract and score keywords. Depending on your system’s configuration, the ATS compares the parsed text against the job description you entered and generates a match score or rank. This score reflects keyword overlap, not competence.
Normalize dates and job titles. The system tries to standardize inconsistent formats. A candidate who wrote “Jan ’19 – Mar ’21” may end up with different dates in the system than what they intended, especially across international date formats.
Discard what it can’t place. Certifications listed in an unusual section, volunteer work formatted as a table, or skills embedded inside a paragraph may simply disappear from structured fields while still existing in a raw text view.

Knowing these five transformations tells you where to look for distortion when something seems off about a candidate’s record.

The Match Score Is a Starting Point, Not a Verdict

Most ATS platforms show you some kind of ranking—a percentage match, a star rating, or a numeric score. Hiring managers under time pressure often sort by this number and review only the top tier. That is a defensible triage strategy, but it requires understanding what the score actually measures.

ATS match scores are primarily a measure of keyword overlap between the resume and the job description you wrote. A candidate scores high by using the same words you used. This rewards candidates who tailor their resume to each posting and penalizes those who write in their own natural language. It also penalizes candidates whose genuine expertise is described differently than your terminology.

A concrete example: you post for a “Customer Success Manager” and require “churn reduction” experience. A candidate who spent three years doing exactly that work at a company that called it “retention management” and “subscriber lifecycle optimization” may score poorly. The work is identical. The vocabulary is different. The score reflects vocabulary.

The correction is simple: treat the score as a first filter, not a final filter. Candidates scoring in the middle range deserve a second look, particularly for roles where real-world terminology varies by industry, region, or company size. Reserve hard cutoffs for minimum-qualification screens—credentials, required licenses, geographic constraints—where the criteria are binary and the words are unlikely to vary.

How to Read a Parsed Resume Correctly

When you open a candidate’s ATS profile, you are typically looking at two layers of information: the structured fields the system populated, and the raw parsed text sitting below or behind them. Get in the habit of checking both.

Check the structured fields for parsing errors first

Before you evaluate content, scan for obvious parsing mistakes. Common ones include:

Job titles appearing in the employer field and vice versa
Employment dates that are off by months or years
Skills listed under education or contact info
A candidate’s name appearing as a job title
Large chunks of text collapsed into a single field

If you see any of these, you cannot evaluate the candidate from the structured view alone. Pull the original resume file—most ATS platforms store it—and read that directly. Disqualifying a candidate because the parser scrambled their record is a process failure, not a hiring decision.

Read the raw text for substance, not the formatted profile for first impressions

The formatted ATS profile is designed for speed. It shows you what the system considers most relevant. But relevance in ATS terms means keyword frequency, not depth of experience. The raw parsed text—often accessible as a plain-text view or a stored PDF—shows you what the candidate actually wrote.

When reading for substance, look for:

Specificity in descriptions. “Managed a team” is weak. “Managed a six-person support team handling 300 tickets per week” is specific. Specificity indicates real experience rather than resume padding.
Evidence of progression. Titles that advance, scope that grows, responsibilities that compound over time. ATS profiles often flatten this into a list; the raw text shows the arc.
Results language. Candidates with genuine accomplishments tend to describe outcomes. Candidates inflating their experience tend to describe activities. Neither is a perfect rule, but the pattern holds often enough to be useful.
Internal consistency. Does the skill set match the described work? If someone lists advanced SQL but their entire work history is in retail management with no data-adjacent responsibilities, that warrants a question—not a disqualification, but a question.

Account for the resume formats your ATS struggles with

Some resume styles parse better than others. Single-column, chronologically organized resumes in standard Word or PDF format parse reliably on most platforms. The following formats frequently cause problems:

Multi-column layouts (common in design-oriented professions)
Resumes built in Google Slides or Canva rather than Word or a dedicated resume tool
Heavy graphic design with icons, progress bars, and infographics replacing text
Resumes submitted as images rather than text-layer PDFs
Documents with extensive headers and footers used for contact information

Candidates in creative fields—design, marketing, communications—are more likely to use visually formatted resumes. This creates a systemic bias: the people most qualified for roles requiring visual judgment are the ones most likely to have resumes your ATS cannot read. The practical fix is to look at original files for any candidate in a visually-oriented role before making a decision based on the parsed profile.

Using Skills Sections Without Over-Relying on Them

Most ATS platforms extract a skills list from each resume and display it prominently. Treat this section with calibrated skepticism. Skills lists are the easiest part of a resume to inflate—a candidate can list any tool or technology they have touched once, and the ATS will count it. The listed skill and the depth of that skill are two entirely different things.

Rather than using the skills list as a qualification check, use it as a prompt list for your screening call. If a candidate lists project management software you use, ask them to describe how they’ve used it. If they list a certification, ask them when they completed it and how recently they’ve applied it. The skills list tells you what to ask about; the conversation tells you whether the claim holds up.

Pay more attention to skills that appear in the body of work experience descriptions than to those listed in a standalone skills section. When a candidate writes “reduced fulfillment errors by standardizing our inventory tracking in [specific software],” that’s evidence of the skill embedded in context. That carries more weight than the same tool appearing in a bulleted list at the bottom of the page.

Building a Simple Review Workflow

For most small businesses reviewing twenty to sixty applicants per role, a two-pass workflow keeps the process honest without consuming excessive time:

Pass one: Use the ATS score to sort, but set your review cutoff lower than instinct suggests—typically including the middle tier. Flag candidates with obvious parsing anomalies for manual file review.
Pass two: For candidates you’re considering advancing, pull the original resume file and read it directly. Confirm the structured fields are accurate. Look for the substance markers described above.

This adds roughly two to three minutes per candidate in the consideration pool. For a twenty-applicant shortlist, that’s under an hour—time well spent to avoid filtering out capable people on the basis of a parser’s limitations rather than the candidate’s actual qualifications.

The Practical Takeaway

An ATS is a processing tool, not a judgment tool. It moves resumes through a system quickly and consistently, which is genuinely useful. What it cannot do is evaluate whether someone will be good at the job. That judgment still belongs to you—and it requires reading past the score, checking for parsing errors, pulling original files when something looks wrong, and treating skills lists as questions rather than answers. The hiring managers who understand that distinction consistently find better candidates than those who outsource the judgment to the algorithm.