7 Formatting Details That Scramble Your Resume in Workday, Greenhouse & Lever (2026 ATS Checklist)

You spend hours polishing your resume. You tweak every bullet point, check every comma, and make sure it looks perfect. Then you hit "submit" on a job application. Your document vanishes into a black box called an Applicant Tracking System (ATS).

A week later, you hear nothing. Maybe you weren't a fit. Or maybe, your beautifully formatted resume turned into digital gibberish the second the ATS tried to read it.

This happens every single day. Workday, Greenhouse, and Lever are three of the most common gatekeepers. They're not evil. They're just software trying to parse complex, human-designed documents. When they encounter certain formatting choices, they get confused. The result? Your "5 years of Python experience" gets filed under "Hobbies" or disappears entirely. The recruiter only sees a broken, half-empty profile.

I've seen resumes where the entire work history was parsed into the name field. I've seen skills lists turn into one long, unreadable word. It's frustrating, and it kills your chances before a human ever gets involved.

The good news? You can prevent it. By understanding how these systems "see" your resume, you can format it for compatibility, not just for beauty. This isn't about gaming the system. It's about clear communication.

Let's get into the seven specific formatting details that most often scramble your data, and exactly what to do instead. Consider this your 2026 validation guide.

Key Takeaways

• Headers and footers are resume kryptonite for ATS parsers. Any text placed in these areas is likely to be deleted or misplaced, including your contact information.
• Fancy visual dividers (lines, icons, text boxes) create parsing chaos. The ATS reads them as garbled text or section breaks, corrupting your content.
• Overly complex tables and columns often collapse, dumping text into a single, unreadable column and destroying your careful layout.
• Uncommon or stylized fonts force the ATS to make a guess, which usually ends with your text being misread or replaced with a generic font, breaking spacing.
• Saving your resume as a .docx is the safest bet for maximum compatibility across Workday, Greenhouse, and Lever. Avoid .pages and complex .pdfs.
• Using color for critical information is a major risk. If the ATS strips color (and it often does), your key headings or labels vanish.
• Special characters in section headers (like ">>" or "~*") confuse the parser's logic, making it harder to correctly identify your "Work Experience" or "Skills" sections.

1. The Header & Footer Black Hole

This is the number one mistake I see. To make a resume look sleek, people put their name, phone number, and email in a nice header. Sometimes they put "Page 1 of 2" in the footer.

Here's what happens in Workday, Greenhouse, and Lever: The parsing software is designed to read the main body of the document. Text in the header and footer is often ignored completely or, worse, pulled into the first line of the parsed text in a weird way.

The Result: The ATS profile is created without your phone number or email. The system might put your name in the "Address" field. You become unreachable. I once reviewed a parsed resume where "John Smith - (123) 456-7890" was parsed as the candidate's previous job title. The actual work history started three fields down.

The Fix:

• Keep all critical text in the main document body. Your name, phone, email, and LinkedIn URL should be the first plain text in the file.
• Never use headers/footers for contact info. Use them only for non-essential elements you're okay with losing, like a document title or page number.
• Simple left alignment is your friend. A clean, left-aligned block at the very top is the most universally parseable format.

Bad Example (What the ATS Sees): [Header: Jane Doe | (555) 123-4567 | jane@email.com] [Main Body Starts Here] "Senior Marketing Manager..." (The ATS might start parsing at "Senior Marketing Manager" and create a profile for someone named "Senior Marketing Manager" with no contact details.)

Good Example: Jane Doe (555) 123-4567 | jane@email.com | linkedin.com/in/janedoe

--- (then the rest of the resume) ---

2. Decorative Lines, Text Boxes & Icons

We get it. A thin gray line under your name looks professional. A small icon next to your phone number is sleek. A text box to highlight a career summary seems like a good idea.

To an ATS, these are alien objects. The parser is looking for words and standard formatting cues (like bold text or bullet points). When it hits a line drawn with a shape tool, it might insert a string of gibberish characters (like "===========") or simply break the reading flow. Text boxes are notoriously bad. The ATS often reads the text inside the box out of sequence, or misses it altogether.

The Result: Your resume gets filled with random characters. Sections get merged. That important summary in the text box? Gone.

The Fix:

• Use standard keyboard characters for simple dividers. If you must have a line, use hyphens (---) or underscores (___). Even these should be used sparingly.
• Avoid shapes, text boxes, and icons entirely. Do not use them for contact info, section headers, or skill ratings.
• Use bold, italics, and capitalization for emphasis. These are simple, well-understood formatting commands that ATS parsers can handle.

3. Multi-Column Layouts & Complex Tables

A two-column layout is great for saving space. One column for dates, one for job details. A table to neatly organize your skills into categories.

Parsers read documents linearly, from top to bottom, left to right. When they encounter a column or a table, they have to decide how to "flatten" it. Often, they read straight across the first row, then the second row, merging columns into a single, nonsensical text block.

The Result: "2020-2023 | Project Manager | Tech Corp" might become "2020-2023Project ManagerTech Corp" all in one field. Your beautiful skills table turns into "PythonSQLAgileJavaScrumAWS" as one "skill."

The Fix:

• Use a single-column format for the core resume content. This is the safest choice.
• If you use a table, make it extremely simple. A two-column table for skills (e.g., "Technical: Python, SQL" | "Soft: Leadership, Communication") might survive, but test it.
• Consider using tabs or simple indents instead of columns for date alignment. Or, just place dates on the same line as the job title, to the right.

Bad Example (In a Table):

Good Example (Linear): Senior Developer, Innovate Co, 2021-Present

4. Fancy & Uncommon Fonts

You want your resume to stand out. So you choose a beautiful, sleek font you found online. The ATS sees a puzzle.

Parsers have a built-in list of standard fonts they recognize easily (Arial, Calibri, Times New Roman, Georgia, Helvetica). When you use an uncommon font, the system does one of two things: 1) It tries to map it to a similar standard font, which can mess up spacing and character recognition, or 2) It fails to read it properly, substituting placeholder characters.

The Result: Your carefully kerned text gets jumbled. Characters like "&" or "@" might turn into a "?" or a blank space. Line breaks happen in weird places because the ATS's version of the font has different spacing.

The Fix:

• Stick to the ATS-safe font classics. Use Arial, Calibri, Times New Roman, or Georgia.
• Use font size and weight (bold) for hierarchy, not a unique font family.
• Never use custom or downloaded fonts. They will not translate.

5. The Wrong File Format (.pages, .pdf, .docx)

This is a huge point of confusion. What's the "best" file to upload?

• .docx (Microsoft Word): This is the gold standard for ATS compatibility. It's the native format the parsers are most optimized to read. The text and structure data are clearly defined in the file.
• .pdf: This is a gamble. A "true" or "searchable" PDF (where you can highlight text) is usually okay. However, if your PDF is just an image (like a scanned document) or was created from a complex design tool, the ATS cannot read it at all. Some older ATS systems also parse .pdfs less accurately than .docx.
• .pages (Apple Pages): Just don't. Many ATS platforms cannot even process this file type. If they can, the parsing is often disastrous.

The Result: Uploading a .pages file might get you an error. Uploading an image-based PDF creates a blank profile. Uploading a complex PDF might lead to the formatting errors we've already discussed.

The Fix:

• Always save and submit a .docx file as your primary resume. This is your workhorse file for applications.
• You can have a beautifully formatted .pdf for emailing directly to humans (like a hiring manager or a networking contact), but for the ATS portal, use the .docx.
• If you must use a PDF, ensure it's created from a Word document and is text-searchable. Open it and try to highlight a sentence. If you can, it's likely okay.

6. Relying on Color for Meaning

You use red text for your job titles. Or you have a nice blue sidebar for your contact info. It looks great in color.

ATS parsers frequently strip out color information to normalize the text. They are looking at the raw text data, not the visual presentation.

The Result: If your section headings are only distinguishable because they are green, they become plain text when color is removed. That sidebar? If the text is only set apart by a colored background, it now flows into the main body with no separation.

The Fix:

• Do not use color as the only way to convey information. A heading must be bolded, larger, or have a distinct format, not just a different color.
• If you use color, treat it as a decorative enhancement. Ensure the document is perfectly readable and logically structured in black and white. Print it on a black-and-white printer to test.
• Avoid colored text boxes or background shading for critical content.

7. Special Characters in Section Headers

You write ">> WORK HISTORY <<" or "~ SKILLS & EXPERTISE ~" to make your sections pop.

The parser is looking for standard labels to map data to the right fields: "Experience," "Work History," "Employment," "Skills," "Education." When you add extra characters, you obscure the signal.

The Result: The system might still correctly identify "WORK HISTORY" but it might also get confused and treat the whole line as a plain text paragraph. It's an unnecessary risk.

The Fix:

• Use simple, standard words for your section headers. Experience. Skills. Education. Projects. Certifications.
• You can bold them and use all caps for visual effect, but keep the words themselves clean.
• Avoid arrows, asterisks, tildes, or other decorative symbols in headers.

Bad Example: "### *** Professional Experience ***" Good Example: "PROFESSIONAL EXPERIENCE" (in bold, size 14pt)

How to Test Your Own Resume (A Practical Method)

You don't need to buy expensive software. Here's a free, effective way to see what an ATS sees:

1. Copy-Paste Test: Open your resume in Microsoft Word or Google Docs. Select all the text (Ctrl+A) and copy it (Ctrl+C). Open a new, plain text editor like Notepad (Windows) or TextEdit (Mac, in "Plain Text" mode). Paste (Ctrl+V) the text.
2. Analyze the Carnage: What you see in Notepad is a rough approximation of what many parsers extract. Look for:
   • Is your contact info at the top?
   • Are section headers clear?
   • Did all the text from headers/footers, text boxes, or columns disappear or get jumbled?
   • Are there weird symbols or long strings of characters where lines used to be?

If your resume looks logical and clean in Notepad, you're on the right track. If it's a mess, you've found your formatting problems.

The Simple, ATS-Friendly Resume Template

Based on all of the above, here's the blueprint for an ATS-optimized resume:

• File Format: .docx
• Font: Arial or Calibri, 10-12pt for body.
• Structure: Single column. No tables for main content.
• Headings: Bold, standard titles (EXPERIENCE, SKILLS, EDUCATION).
• Contact Info: Plain text at the very top of the document body.
• Bullet Points: Use the standard "bullet point" character (•), not arrows or checkmarks.
• Margins: 1 inch all around is safe.
• No: Headers, footers, text boxes, icons, images, or columns.

It won't win a graphic design award, but it will get your information into the recruiter's search results accurately. That's the only goal of the ATS stage.

Final Thoughts

Crafting a resume is a balance between human appeal and machine readability. Before you submit to any major platform like Workday, Greenhouse, or Lever, run through this checklist. Strip away the fancy formatting. Embrace clarity.

Think of it this way: you're preparing a document for two audiences. First, a simple robot that needs clean data. Second, a busy human who needs to quickly see why you're great. Your formatting choices should serve both masters. Start by making the robot happy, and you'll get the chance to impress the human.

The tools you use matter. Using a builder like Career Dog can help because it's designed with these ATS constraints in mind, creating clean, compatible documents from the start without you having to remember every technical rule. But the principles are what's key: simplicity, standard formatting, and logical structure.

Your skills and experience are the main event. Don't let a formatting quirk be the reason they never make it to the stage. Test your resume, simplify it, and submit with confidence.