ATS Parsing Is a Minefield: 7 Technical Formatting Details That Scramble Your Resume in Workday, Greenhouse & Lever

You spend hours on your resume. You tailor every bullet, quantify every achievement, and polish it until it shines. You hit submit, confident you're a perfect match.

Then, nothing. Radio silence.

The problem isn't your experience. It's the robot that read your file first. Applicant Tracking Systems (ATS) like Workday, Greenhouse, and Lever parse your resume into structured data for recruiters. If the parse fails, your entire application can vanish into a black hole. The recruiter might see a jumbled mess of text, or worse, a blank profile.

From what I've seen, about 90% of "ghosting" after an application can be traced back to a parsing error. The ATS didn't understand your document. It's maddening because the mistakes are often invisible to you. Your PDF looks flawless in Preview or Word.

But the parser sees a different story.

I've talked to recruiters who use these systems every day. They'll admit that a badly parsed resume rarely gets a second look. They don't have time to manually reconstruct your career from scrambled text.

So let's fix that. This isn't about keyword stuffing. This is about the technical, structural foundation of your document. The boring stuff that actually matters most. Here are the seven formatting details that will absolutely scramble your resume in the major ATS platforms in 2026, and exactly how to avoid them.

Key Takeaways

• Headers and Footers are poison. Text placed in these areas is often completely ignored or misread by parsers. Move everything into the main body.
• Tables and Text Boxes are a trap. They might look neat, but most parsers cannot read the text inside them correctly, leading to blank sections in your parsed profile.
• Your choice of file type is critical. A .docx file is almost always the safest bet for maximum compatibility. PDFs can work, but only if they are created and saved correctly.
• Fancy icons and symbols become garbage. The parser tries to read them as text characters, creating nonsense strings that corrupt your contact info and skills.
• Overly complex layouts confuse the reading order. Two-column designs and sidebars often get read out of sequence, making your career timeline nonsensical.
• Uncommon fonts don't travel well. If the system can't map your font, it substitutes one, potentially breaking your careful formatting and spacing.
• Special characters in file names can break the upload. The ATS may reject the file before it even tries to parse the content.

1. The Header & Footer Black Hole

This is the number one mistake I see. People love to put their name, phone number, and email in a fancy header. Or they'll put "Page 1 of 2" in the footer.

Big mistake.

ATS parsers, especially in Workday, are notoriously bad at reading content in the header and footer sections of a document. The software is designed to parse the main body text. Content in the header/footer zones is frequently stripped out entirely or placed in a random, illogical field.

What the Recruiter Might See:

• A parsed profile with no name or contact information.
• Your city and state listed as your job title.
• Your phone number shoved into the "Summary" field.

The Fix: Move every single piece of critical information into the main body of the document. Your name, phone, email, city, state, and LinkedIn URL should be the first plain text the parser encounters. Just type them at the top. Simple left alignment is fine. No fancy text boxes or tables to contain them (see point #2).

On Career Dog, when you build a resume, the contact section is automatically placed in the safe, main body area of the template. You don't have to think about it.

2. The Table and Text Box Trap

You want your resume to look organized. So you use a table to create a clean two-column layout for your skills. Or you put your company name and dates in a neat little text box.

Stop. Please.

Tables and text boxes are visual formatting tools, not semantic structures. To a parser, a table is a complex grid object. Many older parsing engines simply skip over them, extracting zero text. Newer ones might try, but they often pull the text out of order (reading left to right, row by row, instead of in the visual flow you intended).

What the Recruiter Might See:

• A "Skills" section that is completely blank in your ATS profile.
• Your job dates merged with your company name in one unreadable string.
• A chaotic jumble of words where your clean layout used to be.

The Fix: Use tabs, spaces, and simple line breaks for alignment. For a skills section, consider a simple list with bullet points. Instead of a table for your work history, use a plain linear format:

Senior Data Analyst | ABC Corporation | Jan 2022 – Present

That vertical bar (|) is a simple text character every parser can understand. It's clear and failsafe.

3. The .PDF Paradox

PDFs are great. They lock your formatting so it looks the same on any screen. That's also their biggest weakness for ATS parsing.

There are two kinds of PDFs: "true" or "searchable" PDFs (which contain selectable, parsable text layers) and "image" PDFs (which are essentially pictures of your text). If you scan your resume or save it as an image-based PDF, the ATS cannot read a single word. It's a blank document to them.

Even a text-based PDF can have issues. Some parsers handle .docx files more natively. Greenhouse, for instance, has historically had slightly better luck with .docx files for complex parsing.

What the Recruiter Might See:

• The dreaded "Parsing Failed" flag on your application.
• A blank candidate profile with an attachment they have to manually open.
• Incomplete or incorrect field mapping.

The Fix: When in doubt, submit a .docx (Microsoft Word) file. It is the universal donor of resume file types. If you must use a PDF:

1. Create it from a Word processor or a dedicated resume tool (like career.dog, which exports proper text-based PDFs).
2. Never create it by scanning a printed page.
3. After saving, open the PDF and try to highlight a line of text with your cursor. If you can't, it's an image and will fail.

4. Iconography & Symbol Sabotage

It's a trendy look: a tiny envelope icon next to your email, a phone icon, a LinkedIn logo. It looks clean and modern to the human eye.

To the parser, it's alien code.

Parsers read text. When they encounter a symbol or icon from a custom font (like FontAwesome or Wingdings), they try to interpret it as a text character. This usually results in a random letter, number, or garbled Unicode character appearing in the middle of your contact info.

What the Recruiter Might See:

• Email: "[q] john.doe@gmail.com"
• Phone: "(555) 123-4567 [b]"
• Skills: "Python [x] SQL [x] Tableau [x]" where the [x] is a garbled mess.

The Fix: Use words. Just type "Email:" or "Phone:". For lists, use bullet points that are standard keyboard characters (like a hyphen "-" or an asterisk "*"). Strip out all visual flair that isn't standard text. Clarity beats cuteness every time in an ATS.

5. Column Calamity (The Reading Order Problem)

Magazine-style resumes with a left sidebar for contact/skills and a right main column for experience are popular in creative fields. They are also a parsing nightmare.

Parsers read documents in a logical order, which is often not the visual order. Most default to a "left-to-right, top-to-bottom" reading of the underlying code. A two-column layout can get read straight across the page, splicing your "Python" skill with the first word of your job title from the other column.

Workday's parser is particularly sensitive to this. It can completely lose the chronology of your experience.

What the Recruiter Might See:

• A work history that appears out of order.
• Skills merged with job descriptions.
• A confusing, incoherent candidate profile that takes too much effort to decipher.

The Fix: Stick to a single-column format for the core content of your resume. This gives the parser one clear, logical path to follow from top to bottom: Contact > Summary > Experience > Education > Skills. It's boring. It's effective. Save the creative layout for a portfolio website or a PDF you bring to an interview.

6. Font Follies

You download a beautiful, rare font to make your resume stand out. It looks gorgeous on your MacBook.

But the ATS server runs on Linux. And it doesn't have your special font installed.

When this happens, the system substitutes a default font (like Arial or Times New Roman). This substitution can wreck your careful spacing. Text can overflow, line breaks can appear in weird places, and your whole document can reflow, potentially pushing critical information onto a second page that the parser might ignore.

The Fix: Use standard, system-safe fonts. The gold standards are:

• Sans-serif: Arial, Calibri, Helvetica, Verdana
• Serif: Times New Roman, Georgia, Garamond

These fonts are ubiquitous across all operating systems. The parser will see exactly what you see. On Career Dog, all templates use these ATS-safe fonts by default, so you get a professional look without the compatibility risk.

7. The File Name Fiasco

This error happens before the parse even begins. You save your resume as "John Doe - Resume (2026) vFINAL.pdf".

Those parentheses and spaces can cause upload errors in some older ATS systems. While most modern systems handle them, why risk it? Some systems may also misinterpret the dash or parentheses as part of a command.

The Fix: Use a simple, clean naming convention. Use underscores or hyphens, but avoid symbols.

• Good: John_Doe_Resume.pdf or John-Doe-Resume.docx
• Risky: Doe, John (Data Analyst) Resume v2.1 FINAL.pdf

Your ATS Parse Survival Checklist

Before you hit submit on your next application, run through this list:

1. Open your resume in a plain text editor (like Notepad or TextEdit). Does all your critical text appear? If not, it's hidden in headers, footers, or tables.
2. Remove all tables and text boxes. Replace them with tabs, spaces, and line breaks.
3. Save a copy as a .docx. Use this as your primary application file.
4. Delete all icons, symbols, and custom bullets. Use standard keyboard characters.
5. Convert to a single-column layout. Ensure the reading order is obvious.
6. Change your font to Arial or Times New Roman. Just for a sanity check. Does it still look okay?
7. Rename your file to Firstname_Lastname_Resume.docx.

What to Do Next

The goal isn't to outsmart the ATS. It's to make your resume effortlessly readable for the machine, so a human gets to see it looking perfect.

Start with a clean, ATS-friendly template. This removes 80% of the guesswork. At Career Dog, the templates are built from the ground up to avoid these exact pitfalls: no headers/footers for content, no tables, safe fonts, and a logical single-column flow. You can focus on your achievements, not on debugging your margins.

Then, for your most important applications, do the text editor test. It's the quickest way to see what the parser sees.

Finally, remember that a parse-friendly resume is also a clean, scannable resume for a tired recruiter. By fixing these technical details, you're not just pleasing a robot. You're creating a clearer, more professional document for everyone in the hiring process. That's how you move from the black hole to the interview list.