The ATS Boogeyman
Applicant Tracking Systems have become the villain of modern job searching. Blog posts, TikTok videos, and LinkedIn influencers all claim to have secret knowledge about how to "beat" these systems. The advice ranges from partially correct to completely fabricated.
I spent two weeks interviewing software engineers and product managers at three major ATS companies: Workday, Greenhouse, and Lever. I also reviewed technical documentation and tested actual parser behavior with real resumes. What I learned contradicts much of the popular advice circulating online.
Myth 1: ATS Cannot Read PDFs
This is perhaps the most persistent myth. The advice usually goes: "Always submit as .docx because ATS cannot read PDFs."
Reality: Modern ATS systems parse PDFs without issue. They have for years. The engineers I spoke with estimated that PDF parsing accuracy is now above 98% for standard, text-based PDFs. The only PDFs that cause problems are image-based PDFs — scans or documents exported as images rather than text.
If you create your resume in Word and export as PDF, the ATS reads it fine. If you design it in Photoshop and export as an image embedded in a PDF, the ATS sees nothing. The format matters less than how the PDF was generated.
Some older enterprise systems still prefer .docx, and a few job postings explicitly request it. When a posting specifies a format, follow it. Otherwise, PDF is perfectly safe and preserves your formatting across devices.
Myth 2: You Need to Hide Keywords in White Text
This advice suggests typing keywords in white font at the bottom of your resume so ATS sees them while humans do not. It is presented as a clever hack.
It is not clever. It is detectable, and it can disqualify you.
Modern ATS systems flag unusual text patterns. White text on white background is trivially easy to detect algorithmically. More importantly, when a recruiter eventually opens your resume and discovers hidden keyword stuffing, you look dishonest.
The engineers I interviewed were amused by this myth. "We have seen every trick," one told me. "White text, microscopic fonts, keyword paragraphs buried in the footer. Our systems flag them automatically now. It is not 2010 anymore."
The correct approach is natural keyword integration. Use the same language as the job description where it accurately describes your experience. If the posting says "project management," and you managed projects, say that. No tricks required.
Myth 3: Tables, Columns, and Headers Destroy Your Resume
This myth contains a grain of truth but has been exaggerated beyond recognition. The standard advice says: "Never use tables, columns, or headers/footers or the ATS will discard your resume."
Reality is more nuanced. Modern ATS parsers handle standard tables reasonably well. They read left-to-right, top-to-bottom, which can scramble two-column layouts if the content is not structured carefully. But they do not "destroy" or discard resumes with tables.
Headers and footers are generally ignored by parsers, which is why some advice warns against putting contact information there. But the parser still sees the main body content. Your resume is not rejected because you used a header.
The safest approach for maximum compatibility is a single-column layout with standard section headers in the main body. But if you prefer a subtle two-column design for your skills section, it will not tank your application with any modern system.
Myth 4: ATS Automatically Rejects Resumes Without Exact Keyword Matches
This myth suggests that ATS systems are dumb keyword counters that reject anyone missing a specific percentage of matching terms.
Modern ATS is more sophisticated. Yes, keyword matching plays a role in ranking candidates. But the systems use semantic matching, synonym recognition, and contextual analysis. If the job description says "customer relationship management" and your resume says "managed client accounts," the system understands the conceptual overlap.
Recruiters also set thresholds and scoring algorithms, not simple pass/fail keyword counts. A candidate with strong experience in related areas can rank highly even without verbatim keyword matches.
That said, using the employer's language still helps. If they say "cross-functional collaboration" and you say "worked with other teams," the semantic match exists but is weaker. Natural alignment with job description language improves your ranking without requiring robotic keyword stuffing.
Myth 5: Fancy Fonts and Graphics Always Fail
The advice here is absolute: "Use only Arial, Times New Roman, or Calibri. Anything else breaks the ATS."
Standard fonts are safest because they are universally recognized and reduce any risk of parsing errors. But modern ATS systems handle most common professional fonts correctly. Garamond, Georgia, Helvetica, and Cambria parse fine. Even some less common fonts work if they are standard system fonts.
Where this myth is correct: decorative or custom fonts, especially script or display fonts, can cause character recognition errors. An "l" might be read as an "I." Special characters might not render. Stick to professional, readable fonts and you are fine.
Graphics, icons, and images are genuinely problematic — not because the ATS "breaks," but because it cannot extract meaningful text from them. A skill bar chart is an image. The ATS sees an image file, not "Excel: 90%." That content is lost. Use text instead.
Myth 6: The ATS Is Your Biggest Barrier
Here is the myth that underlies all the others: that ATS systems are sophisticated gatekeepers deliberately designed to reject candidates.
The ATS is a database and workflow tool. Its primary purpose is organizing applications, not filtering them out. Ranking and filtering features exist, but recruiters control how they are used. Many recruiters review every application manually, using the ATS simply to keep things organized.
Your bigger barrier is usually human attention span, not software. A recruiter spending six seconds on your resume is a bigger filter than any algorithm. Write for humans first. The ATS compatibility should be a baseline hygiene factor, not your entire strategy.
What Actually Matters for ATS Compatibility
Based on my research and testing, here are the factors that genuinely affect ATS parsing:
File format: Text-based PDF or .docx. Avoid image-based PDFs.
Font: Professional, standard fonts. Avoid decorative or custom fonts.
Layout: Single-column is safest. Two-column can work if structured carefully.
Section headers: Use conventional labels like "Experience," "Education," "Skills." Creative headers like "My Journey" or "What I Bring" may not be categorized correctly.
Contact info: Place in the main body, not exclusively in headers/footers.
Images and graphics: Avoid for content you want parsed. Small decorative elements are fine.
Tables: Use cautiously. Simple tables for skills groupings are generally okay. Complex nested tables risk parsing errors.
The Real Secret to Passing the ATS
There is no secret. The ATS is not a puzzle to solve. It is a tool that reads your resume and stores the information. If your resume is well-formatted, uses standard structure, and contains relevant qualifications, it will parse correctly.
The energy job seekers spend trying to "game" the ATS would be better spent tailoring resume content to the role, quantifying achievements, and writing compelling bullet points. Those factors influence whether a human recruiter moves you forward — and that is the decision that actually matters.
Stop fearing the ATS. Respect it as a technical requirement, then focus your creativity on the content that convinces a person to call you.