You spent hours on a beautifully designed resume. Two columns, custom icons, a sleek color scheme, and a progress bar for each skill. It looks fantastic on screen. Then you submit it to 50 job applications and hear nothing back.
The problem isn’t your qualifications. The problem is that applicant tracking systems can’t read your resume. The design elements that make your resume look polished to a human make it completely unintelligible to the software that screens it first.
About 75% of resumes are rejected by ATS before a human ever sees them, according to a frequently cited Harvard Business School study on workforce management. Many of those rejections happen not because the candidate is unqualified, but because the ATS couldn’t extract the information it needed from the document’s formatting.
Here’s exactly what breaks ATS parsing and what to do instead.
What ATS Actually Sees When It Reads Your Resume
Before getting into specific mistakes, it helps to understand how ATS parsing works. An ATS doesn’t “look” at your resume the way you do. It doesn’t see columns, colors, or visual hierarchy. It reads the underlying text layer of your document and tries to categorize that text into fields: name, contact info, work experience, education, skills.
Think of it like copying all the text from your resume and pasting it into a plain text editor. If the result is readable and logically ordered, the ATS will parse it correctly. If the result is a jumbled mess of overlapping text fragments, the ATS will either misfile your information or reject the document entirely.
Here’s a real example of what goes wrong. A two-column resume might display like this to you:
What you see: Left column shows skills and education. Right column shows work experience with dates neatly aligned.
What ATS sees: “Python JavaScript Bachelor ACME Corp 2019 of Science Manager 2022 University Sales increased of Michigan revenue…” The ATS reads left to right, top to bottom, and merges both columns into one stream of text. Your carefully organized sections become word salad.
Two-Column Layouts: The Most Common Killer
Two-column layouts are the single most common reason ATS systems misparse resumes. They’re popular because they look clean and make efficient use of space. But ATS parsing engines read documents in a linear, top-to-bottom flow. When they hit a two-column layout, one of three things happens:
- The system reads across both columns, merging unrelated content
- The system reads one column and ignores the other entirely
- The system throws a parsing error and the resume gets flagged for manual review (which often means it’s skipped)
Some modern ATS platforms handle columns better than others. Workday has improved its parsing in recent years. But Taleo, iCIMS, and many older systems still struggle. You have no way of knowing which ATS a company uses before you apply. Using a single-column layout eliminates the risk entirely.
The fix: Use a single-column layout where each section stacks vertically. You can still create visual separation with section headers, horizontal rules, and strategic use of bold text. A single-column resume doesn’t have to look boring.
Tables: Invisible Walls That Block Content
Tables create a similar problem to columns, but worse. Many ATS systems skip table content entirely because they can’t reliably determine which cell maps to which field.
Candidates commonly use tables for:
- Aligning dates with job titles
- Creating side-by-side skill lists
- Organizing education entries
In every case, there’s a simpler alternative that ATS systems handle correctly. Use tab stops for date alignment. Use bulleted lists for skills. Use standard text entries for education.
A specific gotcha: Some resume templates in Microsoft Word use invisible tables (tables with no visible borders) to control layout. The document looks like a normal single-column resume, but behind the scenes, the content sits inside table cells. To check, click anywhere in your Word document and look for the Table Tools tab in the ribbon. If it appears, your resume has hidden tables.
To remove them: select all content (Ctrl+A), then go to Insert > Table > Convert Table to Text. Choose “Separate with paragraph marks.” Then reformat the spacing.
Text Boxes: The Content That Disappears
Text boxes are floating objects in Word and PDF documents. ATS systems frequently ignore them entirely because they exist on a different layer than the main document text.
This is a particularly sneaky problem. You’ll see the text box content when you open the file. A human reviewer will see it too. But the ATS parser reads only the main text layer, so anything inside a text box simply doesn’t exist as far as the software is concerned.
Common places candidates put text boxes:
- Contact information headers
- Professional summary sidebars
- Key skills callout boxes
- Quote or testimonial highlights
If your contact information is in a text box, the ATS can’t extract your phone number or email. Your resume goes into a pile with no way to reach you. That’s an application that’s dead on arrival.
The fix: Type all content directly into the document body. If you need a section to stand out visually, use bold text, a slightly larger font size, or a horizontal line. Never use floating text boxes.
Headers and Footers: Where Information Goes to Die
This one catches a lot of people off guard. It feels natural to put your name and contact info in the document header, just like you would on a business letter. But most ATS systems do not parse content from headers and footers.
The header/footer area in Word and PDF documents is technically separate from the document body. ATS parsers typically focus on the body text and ignore header/footer content. If your name, phone number, and email are in the header, the ATS creates a candidate profile with no contact information.
Some candidates also put page numbers in the footer, which is fine (ATS ignores it, but no harm done). The issue is when critical information lives there.
The fix: Put your name and all contact information at the very top of the document body. You can center it, bold it and format it to look like a header visually. Just make sure it’s typed into the main text area, not the actual header field.
Icons and Graphics: Pretty but Unreadable
Little icons next to your phone number, email and LinkedIn URL. Graphical section dividers. A headshot in the corner. These elements are purely visual. ATS systems cannot interpret them.
But the problem goes beyond ATS ignoring the graphics themselves. Sometimes graphical elements cause the parser to skip surrounding text. An icon placed inline with your phone number can cause the ATS to mangle the number. A graphical divider between sections can cause the parser to merge the sections above and below it.
There’s also a related issue with special characters and Unicode symbols. Some candidates use Unicode bullets (like stars or arrows) instead of standard bullet points. Older ATS parsers can choke on non-standard Unicode characters, replacing them with question marks or garbled text.
The fix: Use standard bullet points (round dots). Use text labels instead of icons (“Email:” instead of an envelope icon). Skip the headshot entirely. In fact, in the US, including a photo on your resume can create bias concerns for employers, so it’s best practice to leave it off regardless of ATS.
Skill Bars, Star Ratings and Progress Charts
Those graphical skill indicators (a bar showing Python at 80%, Excel at 90%) are completely invisible to ATS. The software sees nothing. No skill name, no proficiency level. Just empty space.
This means your entire skills section can effectively disappear from your parsed resume. The ATS creates a candidate profile that lists zero skills, and you get filtered out of every search a recruiter runs.
Even if the ATS manages to pick up the skill names (because they’re rendered as text next to the graphic), it can’t interpret the visual indicator. So the proficiency information is lost regardless.
The fix: List skills as plain text. Group them by category if you want organization. If you need to indicate proficiency, use words: “Proficient,” “Advanced,” or “Working knowledge.” For a deeper look at whether skill ratings help or hurt your resume, check out our guide on skill levels on resumes.
Fancy Fonts and Custom Typography
Not all fonts are created equal when it comes to ATS parsing. The system needs to be able to read each character in your document. Decorative fonts, script fonts and some modern sans-serif fonts can cause character recognition issues.
Fonts that are safe for ATS parsing:
- Arial
- Calibri
- Times New Roman
- Garamond
- Cambria
- Georgia
- Helvetica
Fonts that cause problems:
- Script or handwriting fonts (Pacifico, Dancing Script)
- Decorative display fonts (Impact, Lobster)
- Condensed or ultra-thin fonts that blur at small sizes
- Custom or embedded fonts that may not be installed on the parsing server
There’s another font-related issue that’s less obvious. If you use a font that the ATS server doesn’t have installed, the document may render with a fallback font that has different character widths. This can cause text to overlap or shift, breaking the parsing further.
The fix: Stick with Arial, Calibri, or Times New Roman. These three fonts are installed on virtually every system, parse cleanly and are readable at standard resume sizes (10-12pt).
File Format: PDF vs. DOCX vs. Everything Else
The file format you submit affects how well the ATS can parse your resume. Here’s the breakdown:
DOCX (Microsoft Word): The safest choice for ATS compatibility. Word documents preserve the text layer cleanly, and every major ATS can parse .docx files. If the job application doesn’t specify a format, submit .docx.
PDF: Generally safe, but with caveats. PDFs come in two types. Text-based PDFs (created by exporting from Word or Google Docs) are usually parsable. Image-based PDFs (created by scanning a printed document or using certain design tools) are not. The ATS sees a picture, not text.
How to check: open your PDF and try to select the text with your cursor. If you can highlight individual words, it’s text-based and likely parsable. If clicking and dragging selects the entire page as one block, it’s an image-based PDF and the ATS can’t read it.
Google Docs export: When you download a Google Doc as PDF, it creates a text-based PDF that parses well. When you download as .docx, formatting sometimes shifts. Test both and verify the output looks correct.
Formats to avoid: .pages (Apple), .odt (OpenDocument), .rtf (Rich Text Format). While some ATS systems can handle these, compatibility is inconsistent. Don’t take the chance.
One more thing about filenames: Name your file “FirstName-LastName-Resume.docx” or similar. Some ATS systems display the filename to recruiters, and “Resume_Final_v3_UPDATED(1).docx” doesn’t make a good first impression.
Color: Use It Sparingly, If at All
Color doesn’t break ATS parsing on its own. The ATS doesn’t see color. It reads text regardless of whether that text is black, blue, or green. So technically, colored text won’t cause parsing errors.
The issue is practical. If a recruiter prints your resume in black and white (which many still do), light-colored text can become illegible. A dark blue heading is fine. A light gray subheading disappears on a black-and-white printout.
Safe use of color:
- Dark blue or dark gray for section headings
- Black for all body text
- A single accent color (navy, dark teal, dark maroon) for your name or section dividers
Avoid:
- Light colors for any text
- Colored backgrounds behind text blocks
- Gradients or color transitions
How to Test Whether Your Resume Parses Correctly
Don’t guess. Test your resume before submitting it. Here are three methods:
Method 1: The copy-paste test. Open your resume and select all text (Ctrl+A). Paste it into a plain text editor like Notepad or TextEdit (in plain text mode). Read through the result. Is every section in order? Is all the text present? Are there any garbled characters or merged lines? This simulates what basic ATS parsing produces.
Method 2: Submit to a job board. Create a profile on LinkedIn, a major job board, or a company career site. Upload your resume and check the auto-populated fields. If the system correctly fills in your name, current job title, employer and education, your resume parses well. If it gets any of these wrong, you have a formatting issue.
Method 3: Parse it yourself. Several free resume parsing tools exist online. Upload your document and review the extracted data. Look for missing sections, misordered content, or fields that didn’t populate.
If your resume fails any of these tests, the issue is almost always one of the design problems listed in this article. Fix the formatting first, then retest.
Safe Design Choices That Still Look Professional
ATS-friendly doesn’t mean ugly. You can create a clean, professional resume that passes every parser without looking like a plain text file from 1997.
Use bold and caps for section headers. “WORK EXPERIENCE” or “Work Experience” creates visual hierarchy that both humans and ATS systems understand.
Use horizontal lines sparingly. A thin line between sections adds visual structure without confusing the parser. Most ATS systems handle simple horizontal rules just fine.
Use consistent date formatting. Pick one format (“Jan 2020 – Mar 2022” or “01/2020 – 03/2022”) and use it throughout. Mixing formats can confuse the date-parsing logic in some ATS systems.
Use standard bullet points. Round dots. That’s it. Not arrows, not checkmarks, not custom Unicode characters.
Use strategic white space. Margins of 0.5 to 1 inch. Line spacing of 1.0 to 1.15. Space between sections. White space makes your resume scannable for humans without affecting ATS parsing.
For a full breakdown of ATS-compatible templates that nail this balance, see our guide on ATS-friendly resume formats and templates.
The Real Cost of Design-First Resume Thinking
Here’s the uncomfortable truth. A visually stunning resume that ATS can’t parse is functionally worse than a plain text document that parses perfectly. The beautiful resume never reaches a human. The plain one does.
That doesn’t mean you should submit a text file. It means design should serve readability, not replace it. The best resumes are ones where you don’t notice the design at all. They look clean, organized and professional. They guide the eye naturally from one section to the next. And they do it with basic formatting tools that every ATS on the market can handle.
Many of the most common resume mistakes fall into the category of design choices that feel intuitive but hurt your chances. For more on that broader topic, take a look at our roundup of common resume mistakes to avoid.
If you’re starting from scratch and want to skip the formatting guesswork, 1Template builds all its resume templates with ATS compatibility as a baseline requirement. Every template is tested against major parsing engines before it’s published, so you can focus on your content instead of debugging invisible formatting issues.
Stop designing your resume for Instagram. Start designing it for the software that decides whether anyone ever reads it.
