ATS Survival Guide

If you've worked in recruitment for more than a week, you've experienced the frustrating mystery of ATS parsing failures. A beautifully formatted resume goes in, and a jumbled mess of data comes out. Employment dates land in the skills section. Job titles appear where company names should be. Entire paragraphs of qualifications simply vanish, never to be seen again.

This isn't random. It isn't bad luck. And it isn't something you have to accept as an inevitable cost of doing business.

The science behind ATS parsing is well-documented but poorly understood. These systems were designed in an era when resumes were simple text documents—single column, standard fonts, predictable structure. The creative revolution in resume design has left them struggling to adapt, and billions of dollars of recruitment technology hasn't fundamentally changed the parsing engines at their core.

Understanding why these systems fail is the first step toward ensuring your candidates never experience rejection at the digital gatekeeper.

The Fundamental Problem: Parsing vs. Reading

When you look at a resume, your brain performs an incredible feat of pattern recognition. You instantly understand that the large text at the top is a name, that dates on the right side of a line correspond to the position listed on the left, that a section titled "Education" contains academic history even if it's formatted differently from every other resume you've seen.

Applicant Tracking Systems don't read. They parse. They apply rigid rules to extract specific data from specific locations within a document. When a resume doesn't conform to these expectations—and creative resumes rarely do—the parsing fails.

The Table Tragedy

Consider the most common resume layout choice that breaks parsing: tables. Designers love tables. They create clean columns, precise alignment, and professional-looking layouts. To the human eye, a two-column table with dates on the left and job details on the right is perfectly clear.

To an ATS, that table is chaos. Most parsers read text left-to-right, top-to-bottom, regardless of visual layout. Your carefully structured table becomes a word salad: "2020 Senior Marketing Manager 2022 Acme Corporation Led team of 12..."

The dates, titles, companies, and descriptions all merge into an incomprehensible stream. The parser tries to apply rules—"dates usually come before or after job titles"—but the data doesn't match expectations, so it gets discarded or misassigned.

The PDF Puzzle

Modern PDFs are complex digital constructs. They contain multiple layers: text layers, image layers, form fields, embedded fonts, accessibility tags, and more. A PDF that looks identical to another might have completely different internal structure.

Some PDFs store text as actual text—characters that can be selected, copied, and parsed. Others store text as shapes, essentially drawing each letter rather than encoding it. Still others store text as images, with no parseable content at all beyond the visual representation.

When a candidate exports their resume from Canva, Adobe InDesign, or certain Mac applications, the resulting PDF often contains text-as-shapes rather than text-as-text. The file looks perfect on screen. It prints beautifully. And it contains zero parseable content for an ATS.

The Font Fiasco

Fonts embed into PDFs in different ways. Some embed completely, allowing any system to render them correctly. Others embed partially, including only the characters used in the document. Still others reference system fonts without embedding anything.

When an ATS encounters a font it can't render, different things happen. Some systems substitute fonts, potentially changing character mapping and creating gibberish. Others fail silently, extracting text correctly but displaying it wrongly. The worst simply crash or return empty results.

Custom fonts, decorative fonts, and fonts with unusual character sets are particularly problematic. A resume featuring "Zapfino" or "Brush Script MT" might render as squares, question marks, or simply blank space.

The ATS Landscape: Every System is Different

Not all Applicant Tracking Systems fail in the same ways. Understanding the specific quirks of the systems your clients use dramatically improves your success rate.

Bullhorn: The Agency Standard

Bullhorn dominates the staffing industry, and for good reason—it's purpose-built for high-volume agency recruiting. But its parser is notoriously strict about formatting. Tables are essentially forbidden. Multi-column layouts fail consistently. Header and footer content often gets ignored entirely.

Bullhorn works best with single-column, clearly-sectioned resumes using standard fonts. If your candidates include creative elements, those elements will be stripped at best and will scramble the entire document at worst.

Greenhouse: The Startup Favorite

Greenhouse has gained massive market share among technology companies and startups. Its parser prioritizes structured data extraction over visual fidelity. It looks for specific patterns—name at top, contact information in identifiable formats, section headers that match expected terminology.

Creative section titles break Greenhouse parsing. "My Journey" instead of "Work Experience" means that section might not parse at all. "What I Bring" instead of "Skills" creates similar problems. Greenhouse rewards conventionality.

Workday: The Enterprise Behemoth

Workday applications are infamous among job seekers for good reason. The system's parsing is aggressive and unforgiving. Resumes that work everywhere else often fail in Workday applications.

The secret to Workday success is extreme simplicity. Plain text formatting, standard section headers, no graphics, no tables, no columns. Essentially, the resume format from 1995 is what Workday handles best in 2026.

iCIMS: The Enterprise Alternative

iCIMS serves many large enterprises and handles high volumes. Its parser is reasonably robust but struggles with the same fundamentals: tables, columns, and non-standard fonts.

Unique to iCIMS are occasional failures with very long resumes. Documents exceeding certain page counts or character limits may truncate silently, losing critical experience from senior candidates.

Modern Systems: Lever, Ashby, SmartRecruiters

Newer ATS platforms have made significant investments in parsing technology. Lever, Ashby, and SmartRecruiters handle creative formats better than their predecessors. But "better" doesn't mean "perfect."

These systems still struggle with text-as-image PDFs, unusual fonts, and highly complex layouts. They're more forgiving of minor formatting variations but will still fail on documents that push design boundaries.

The Solution: Intelligent Reformatting

The answer isn't to reject all creative resumes—many excellent candidates invest in professional resume design. The answer is intelligent reformatting that preserves content while optimizing structure.

This is exactly what Distill provides. Our processing engine analyzes incoming documents at the structural level, understanding what content exists regardless of how it's formatted. We then reconstruct that content into a clean, ATS-optimized format that parses correctly across all major systems.

Preserving What Matters

Good reformatting isn't about stripping design elements—it's about preserving information integrity. Dates stay with their corresponding positions. Skills remain categorized appropriately. Contact information appears where systems expect to find it.

We maintain the logical structure of the original document while eliminating the formatting elements that cause parsing failures. The result is a resume that conveys the same qualifications in a format every ATS can process.

Specific System Optimization

Different clients use different systems. A resume optimized for Bullhorn might differ slightly from one optimized for Greenhouse. Distill allows you to specify target systems, applying optimizations specific to each platform's quirks.

For high-volume submissions to a single client, this targeted optimization dramatically improves success rates. For general submissions, our universal format works across all major systems.

Beyond Parsing: The Human Element

ATS optimization isn't just about getting past the digital gatekeeper. It's about presenting candidates professionally at every stage of the process.

When a hiring manager opens a resume from their ATS, what do they see? If the parsing failed, they see a mess—disorganized data that makes the candidate look careless. Even if the original resume was beautiful, the parsed result in the ATS is what the hiring manager evaluates.

Clean parsing means clean presentation. It means your candidates look as qualified as they actually are. It means hiring managers can quickly evaluate and compare, leading to more interviews and more placements.

Putting Knowledge Into Practice

Throughout this guide section, you'll find specific articles for individual ATS platforms. Each article explains the parsing behavior of that specific system, common failure modes, and exact solutions.

Whether you're troubleshooting a specific upload failure or optimizing your workflow for a major client's preferred system, these guides provide the technical foundation for success.

Start with the guides for your most common target systems. Implement the recommendations for your candidate preparation workflow. And when you need instant conversion, Distill's reformatting engine handles the technical complexity in seconds.

Your candidates deserve to be seen. Don't let outdated parsing technology hide their qualifications.