Myth: every ATS rejects two-column resumes
Unsupported as a universal claim.
Columns can create a bad extraction order, especially in PDFs. A parse failure is possible. Automatic rejection solely because a page has two columns is a much stronger claim, and vendor behavior varies. Test the exported text or use one column to reduce risk.
Myth: ATS software cannot read PDFs
False as a blanket statement.
Workday lists PDF among supported resume types, and many commercial parsers accept it. Image-only PDFs and PDFs with poor character mappings can fail. The internal text matters more than the extension.
Myth: you need an 80 percent ATS score
No common standard supports that threshold.
Checker percentages come from product-specific rules. Employer systems may use different match features, labels, or no resume match score at all.
Myth: missing one keyword causes automatic rejection
Possible in a configured rule, but not a universal resume-parser behavior.
A required-license question can trigger rejection in a configured workflow. Keyword search and skills matching are separate features. The exact setup belongs to the employer.
Myth: white-text keyword stuffing works
It can put hidden words into extracted text. That makes it a liability, not a sound strategy.
Hidden text can produce misleading data and becomes obvious when a recruiter views extracted content. It does not prove a skill or meet a qualification.
Myth: graphics always cause rejection
The risk depends on what the graphic replaces and how the surrounding text is stored.
A decorative line is unlikely to matter. An image containing your entire work history is a serious extraction problem. An icon-only phone or email label adds no useful text.
Myth: all ATS products use the same algorithm
False.
Workday, Greenhouse, Lever, iCIMS, and Taleo expose different features and configuration models. Some use third-party parsing or matching services. Customer settings add more variation.
Myth: a resume must always fit on one page
This is a recruiter and context question, not a parser limit.
A second page does not inherently break text extraction. Length should reflect relevant experience and the norms of the role. Keep each page easy to scan and remove material that does not help the application.
Sources used on this page
- Concept: Candidate Skills MatchWorkday Documentation
Documents an optional skills-match feature, its supported files, and its Strong to Low labels.
- Auto-rejectGreenhouse Support
Shows that configured application-question responses can trigger automatic rejection.
- Unsuccessful resume parseGreenhouse Support
Documents parse failures, a 2.5 MB parsing limit, and layout-related errors.
- Getting Started: Career Section overviewOracle Help Center
States that Taleo Enterprise resume parsing is delivered through a third-party partner service.
- PDF format familyLibrary of Congress
Notes that scanned-image PDFs do not necessarily support text indexing.