How recruiters actually read résumés (and what that means for ATS)

By the SpeakResume team7 min readUpdated

An applicant tracking system reads a résumé as plain text and stores it for keyword matching; the recruiter scans the same résumé visually for about six seconds. A résumé that ignores either reader is filtered out before a human ever decides.

What is an applicant tracking system?

An applicant tracking system, or ATS, is the software a company uses to store, search, and rank incoming résumés. Most large employers use one — Workday, Greenhouse, Lever, Taleo, and iCIMS are the common names — and the system sits between the candidate’s submission and the human recruiter. A résumé the ATS cannot parse cleanly is unlikely to be surfaced for review at all.

The ATS does not "score" résumés the way the internet often claims. It indexes them. A recruiter then searches the index using the keywords from the requisition — job title, required skill, degree, years of experience — and reads the candidates the search returned. Optimizing for ATS is mostly about making sure the résumé is indexable and contains the keywords a recruiter would actually search for.

What do recruiters look for in a résumé?

Recruiters look for the candidate’s most recent role, the company name, the dates, and the bullet points that match the requisition — in roughly that order, in roughly six seconds, on the first pass. They look at the top third of the first page before deciding whether the rest is worth reading. The candidate’s name, target role, and most recent job title all live in that top third for a reason.

The first read is a screening pass, not a review. The recruiter is deciding whether to spend two more minutes on the résumé, not whether to make an offer. That means the top third of the page does most of the work: a clear name, a clear summary that names the target role, and a clean experience block where the most recent job sits at the very top. Everything below the fold is for the second read.

What formatting choices break ATS parsing?

ATS parsing breaks on multi-column layouts, text inside images, decorative tables, headers and footers that hold contact information, and any "creative" résumé template built for visual rather than parsing purposes. The system reads top-to-bottom in a single stream; a two-column résumé routinely produces a transcript that interleaves a sidebar into the middle of a job entry, and the candidate’s information shows up in the wrong order.

The safest format is a single-column layout, with standard section headings — "Experience," "Education," "Skills" — and contact information in the body of the document rather than in the page header. Dates should be written out as "Jan 2022 – Present," not as graphic timelines. Skills should sit in a comma-separated list under a "Skills" heading, not in a tag cloud. Decorative elements look striking on the screen and disappear inside the ATS.

What résumé keywords actually matter?

The résumé keywords that actually matter are the exact terms from the job posting — the job title, the required skills, the named technologies, and any certifications listed as required. A keyword that does not appear in the candidate’s actual experience should not be added; an ATS keyword stuffed onto a résumé survives the index pass but fails the recruiter pass two minutes later.

A practical pattern is to read the posting twice, list the five or six terms that repeat, and confirm that each one shows up at least once in the experience block — in context, not as a list. If the posting calls the role "Senior Product Manager" and the candidate is currently a "Senior PM," writing it out in full once is worth the extra characters. The ATS rarely guesses abbreviations correctly.

How long should a résumé be for ATS?

A résumé should be one page for most candidates and two pages once the candidate has roughly ten years of relevant experience. ATS systems do not impose a length limit, but recruiters do — most will not read past page two regardless of how much is on it. A two-page résumé is justified only when the second page carries content that would otherwise be cut.

The mistake to avoid is shrinking the font to fit a two-page résumé onto one page. Body text below 10pt becomes unreadable in print, and recruiters do still print résumés. The cleaner fix is to cut the oldest roles to one or two bullets each, drop responsibilities that read as job descriptions, and lean the experience block toward outcomes with numbers. Brevity is a signal of editorial judgment.

How do you write a résumé that satisfies both ATS and recruiters?

A résumé satisfies both the ATS and the recruiter when it is single-column, uses standard section headings, includes the keywords from the posting in real context, and presents the most recent role in the top third of the page with outcome-driven bullets. The two readers do not actually conflict — they reward the same structural choices, and the visually elaborate résumés that fail one usually fail the other for the same underlying reason.

SpeakResume’s templates are all built for this pattern by default. The single-column layout, standard headings, and contact block in the document body apply to every template in the gallery, and the build flow captures the keyword-relevant detail by asking section-specific recruiter-style questions rather than letting candidates default to job-description language. The output is a PDF the ATS can read and a recruiter can scan in the same six-second pass.

Key takeaways

  • Modern ATS software parses plain text — multi-column résumés, text boxes, and decorative graphics are routinely lost.
  • Recruiters spend roughly six seconds on the first pass and look first at the top third of the page.
  • The cleanest résumés survive both readers: one column, standard section headings, and quantified bullets.