Top 10 Resume Formatting Errors That Can Break ATS Parsing

Why ATS-safe formatting is intentionally boring

An applicant tracking system may extract your name, contact details, employers, dates, titles, education and skills into fields. The parser must infer reading order and meaning from the file. A layout that looks elegant as a page can become scrambled when extracted as text. The result may still reach a recruiter, but key evidence can land in the wrong field or disappear from the preview.

No format works identically in every system. The practical goal is risk reduction: use document structures that survive copying, text extraction and conversion.

1. Two-column layouts with competing reading order

A narrow skills sidebar beside a wide experience column can be read left-to-right by row rather than top-to-bottom by column. A skill may be inserted into the middle of a job bullet, while dates appear beside unrelated employers. Keep the main resume single-column. If you retain a small sidebar, ensure no critical content depends on its position and test the extracted text.

2. Tables used as the page grid

Tables are useful for data, but resumes often use invisible tables to align employers, locations and dates. Some parsers flatten cells in an unexpected order. Replace layout tables with paragraphs, tab stops or simple right-aligned text. Do not put the entire resume inside one table.

3. Contact details inside headers or footers

A document header is visually convenient, but some extraction workflows ignore headers and footers. Put your name, city, phone, email and LinkedIn URL in the body at the top of page one. Avoid a full postal address; city and state are usually enough for an Indian job search.

4. Icons without text labels

A phone glyph, envelope or LinkedIn logo may have no useful text representation. Write “Phone”, “Email” or the actual URL as text. The same rule applies to skill-rating dots and progress bars: five filled circles do not tell a parser—or a recruiter—what proficiency means.

5. Important information rendered as an image

Logos, screenshots, charts and text boxes can be skipped or read out of order. Never place your name, skills or employment history only inside an image. A portfolio link can point to visual evidence outside the resume; the resume itself should contain a plain-text description.

6. Decorative or embedded fonts

Use a common, readable font such as Arial, Calibri, Helvetica, Georgia or Times New Roman. Unusual fonts, ligatures and symbol fonts can create incorrect characters after conversion. Keep body text roughly 10.5–12 points and verify that the exported PDF remains selectable.

7. Text boxes, shapes and floating elements

Text boxes can sit outside the normal document flow. A parser may extract them first, last or not at all. Use normal paragraphs and headings. Lines and subtle background fills are fine when they are decorative and the content remains ordinary text.

8. Creative section names

“My Journey”, “What I Bring” and “Where I Learned” create unnecessary ambiguity. Use headings such as Summary, Skills, Experience, Projects, Education and Certifications. A recruiter should understand the structure without decoding your personal brand.

9. Inconsistent dates and employer structure

Use one date format throughout, such as “Jan 2022 – Mar 2025”. Put company, title, location and dates in a repeatable order. Avoid merging several internal promotions into an unreadable block; list the company once and show each title with its own dates.

10. Unsupported, scanned or corrupted files

Follow the application portal’s stated file types and size limits. DOCX and text-based PDF are commonly accepted, but the employer’s instructions control. Avoid scanned PDFs, password-protected files, Pages files and a PDF created by photographing or printing a resume. If a portal produces a poor preview, use the alternative supported format.

A five-minute parsing test before every application

1. Open the final file and confirm every word is selectable.
2. Copy the full document into a plain-text editor and inspect reading order.
3. Search the file for your email, target title and three core skills.
4. Check that company names, titles and dates remain adjacent.
5. Upload to the employer portal and review any parsed profile fields before submitting.
6. Keep a clean master DOCX and export a fresh PDF after each change.

Formatting is only the transport layer

A perfectly parsed resume can still be weak if it lacks role alignment and evidence. Once the file is stable, spend more time improving achievements, relevant skills and project scope than adjusting margins. Tailor the content truthfully for the role rather than creating a different visual design for every application.

Next, strengthen the evidence with How to Quantify Achievements on Your Resume Even If You Don't Work With Numbers, How to Use AI Tools to Tailor Your Resume for Every Job Application.

Conclusion

The safest ATS resume is readable in three places: the original document, extracted plain text and the recruiter’s preview. A single column, conventional headings and text-first content remove avoidable parsing failures while keeping attention on your experience.