Your resume can be rejected before a single human reads it — not because you're underqualified, but because of how the document is structured. Here is exactly what to change.
of resumes are rejected by ATS before a human reads them
of Fortune 500 companies use ATS to screen resumes
average time a recruiter spends on first pass once a resume reaches them
of ATS rejections are caused by formatting issues alone — not missing qualifications
Most candidates spend hours perfecting the content of their resume. They agonize over bullets, quantify achievements, and tailor language to the role. Then they put all of it inside a beautifully designed two-column template — and the ATS receives a garbled mess it cannot read.
Resume format is not a cosmetic decision. It is an infrastructure decision. The wrong structure means your content never gets evaluated at all. This guide covers everything you need to know: the three main formats and when to use each, the specific formatting rules that determine ATS compatibility, file type, length, and the visual elements that consistently cause parsing failures.
There are three resume formats in common use. Most guides describe them as interchangeable options. They are not — each has specific strengths, weaknesses, and ATS compatibility characteristics that make it right or wrong for a given situation.
Structure: Contact info → Summary → Work Experience (newest first) → Education → Skills
The default and most widely used format. Work history is the primary section, listed in reverse date order. Skills and education appear below experience. The recruiter reads your career story from most recent to oldest.
Structure: Contact info → Summary → Skills / Competencies (grouped) → Work History (minimal, dates only) → Education
Groups skills and competencies at the top, relegating work history to a brief list with minimal detail. The intention is to emphasize what you can do over where you have worked.
54% of recruiters view a functional resume negatively on sight. ATS systems parse skills with higher confidence when they appear within work experience bullets — context-free skills lists score lower and are sometimes discarded entirely. The format that was designed to help career changers and gap-havers is the one most likely to get them rejected before a human reads a single line.
Structure: Contact info → Summary → Skills Section → Work Experience (reverse-chronological, full detail) → Education
Combines the best of both formats: a prominent skills section at the top for ATS keyword density and recruiter visibility, followed by a full reverse-chronological work history with detailed bullets. The work history is not minimized.
| Format | ATS Score | Recruiter Reception | Use When | Avoid When |
|---|---|---|---|---|
| Reverse-Chronological | Excellent | Most positive — familiar, easy to scan | Consistent career in one field; applying to same-level role | Career changing; recent role is least relevant; major gaps |
| Functional | Poor | Negative — 54% of recruiters flag it | Almost never | All standard job applications |
| Hybrid | Good | Positive — familiar structure with prominent skills | Career change; skills need to be visible before work history | When work history alone tells the story clearly |
ATS systems do not "read" your resume — they extract structured data from a document. Any design element that disrupts text extraction causes a failure. The extracted data is then matched against the job posting. If key information is lost in extraction, it cannot be matched — no matter how well-written your content is.
The following elements cause parsing failures across all major ATS platforms including Workday, Greenhouse, Lever, iCIMS, and Taleo. Some cause partial failures (specific sections lost); others cause complete failures (blank candidate profile).
The most common and most damaging issue. ATS reads documents linearly — left to right, top to bottom. In a two-column layout, the right column is either read out of sequence (interleaved with left-column content, creating nonsense) or ignored entirely. A resume that looks clean and organized to a human can appear as scrambled text in ATS.
Many templates use invisible tables to create column alignment. ATS text extraction does not respect table cell boundaries — content merges in unpredictable ways. Your contact info can appear next to your job title; your bullet points can merge into a single unbroken string.
Microsoft Word and Google Docs headers are separate content zones. Most ATS parsers treat them as metadata, not body text. Your name, phone, and email — the most critical contact fields — may not be extracted at all if they are placed in the document header rather than the body.
Any text placed inside a Word text box, shape, or drawing object is invisible to most ATS parsers. Candidates who put their name in a decorative header box, or their skills in a sidebar text box, create invisible content.
Phone icons, email icons, LinkedIn logos — these are images. ATS cannot read images. Your contact information must be plain text. An icon next to a phone number is not parsed as a phone number label.
These communicate skill level visually — which is meaningless to ATS. Worse, the surrounding layout usually involves tables or columns that cause parsing failures. "Python ●●●●○" does not tell ATS you know Python. "Python" in a plain text skills list does.
A PDF created by scanning a printed page, or by saving a design tool output as an image, contains zero extractable text. ATS sees a blank document. This is increasingly common with Canva, Adobe Illustrator, or Figma-based resume designs.
"Where I've Made an Impact" will not be recognized as a work experience section by most ATS. Section headings must be standard variants of: Experience / Work Experience, Education, Skills, Summary / Professional Summary, Certifications, Projects.
| ATS Platform | Used By | Format Sensitivity | Recommended Format | How to Identify |
|---|---|---|---|---|
| Workday | Fortune 500, large enterprises | High — tables and columns break parsing | .docx, strict single column, no tables | URL contains "wd3.myworkday.com" or "wd1.myworkday.com" |
| Taleo (Oracle) | Large corporations, government | Very High — oldest parser, strictest | .docx, single column, plain text only | URL contains "taleo.net" |
| iCIMS | Enterprise, healthcare, manufacturing | High — headers/footers ignored | .docx, no tables, contact in body | URL contains "icims.com" |
| Greenhouse | Tech startups, mid-market | Medium — handles PDF well | PDF or .docx | URL contains "greenhouse.io" |
| Lever | Tech-forward companies | Medium — more format-tolerant | PDF preferred | URL contains "lever.co" |
| SmartRecruiters | Global mid-market | Low — modern AI parser | PDF or .docx | URL contains "smartrecruiters.com" |
| Ashby | High-growth tech startups | Low — human-first review culture | PDF preferred | URL contains "ashbyhq.com" |
| BambooHR | SMBs, 50–500 employees | Low — basic parser | Any standard format | URL contains "bamboohr.com" |
Knowing which ATS you're facing changes what to optimize. If you're applying to enterprise companies using Workday or Taleo, keyword matching becomes even more critical — their parsers apply stricter exact-match logic. Full breakdown: ATS Resume Optimization: The Complete Checklist.
This question has a nuanced answer that most guides oversimplify. The right file type depends on which ATS platform the employer uses — and the safe default has changed in the past few years.
| .docx | PDF (text-based, exported from Word) | PDF (image-based, scanned or from design tool) | |
|---|---|---|---|
| ATS compatibility (general) | Best — universally supported | Good — supported by modern ATS | Fail — zero extractable text |
| Workday / Taleo / iCIMS | Best | Acceptable but riskier | Fail |
| Greenhouse / Lever / Ashby | Best | Best — these platforms prefer PDF | Fail |
| Preserves formatting for human reader | Varies — depends on recipient's Word version | Yes — consistent across all viewers | Yes — but irrelevant if ATS fails |
| Default recommendation | ✅ Safe default when format not specified | ✅ Use when posting specifies PDF, or for Greenhouse/Lever | ❌ Never use for job applications |
Open your PDF in any viewer (Adobe Reader, Preview, or browser). Try to click and highlight a word with your cursor. If the text highlights — it is text-based and ATS-compatible. If nothing highlights, or the entire page is selected as one block — it is image-based and will produce a blank ATS profile. This test takes 10 seconds and eliminates the most catastrophic possible format error.
Name your file FirstName_LastName_Resume.pdf or FirstName_LastName_Resume.docx. Not resume_v3_FINAL.pdf, not My Resume.docx, not CV.pdf. Recruiters save and sort files — your name in the filename is a functional necessity, not a formality. It also signals the level of attention to detail you bring to the role.
Once your resume passes ATS, a human has 7.4 seconds on first pass. Format is not just an ATS problem — it is a visual hierarchy problem. A recruiter who finds the page dense, hard to scan, or visually disorganized will move on before they have read a single substantive line.
| Experience Level | Recommended Length | Reasoning |
|---|---|---|
| Student / Entry level (0–2 years) | 1 page | Limited experience; one page forces prioritization; recruiter expects brevity |
| Early career (2–5 years) | 1 page | Enough experience to fill one page well; two pages suggests padding |
| Mid career (5–15 years) | 2 pages | Sufficient substantive history to justify two pages; most recruiters expect it |
| Senior / Executive (15+ years) | 2 pages max | Roles older than 15 years rarely contribute to hiring decisions; remove or condense |
| Academic / Research / CV context | Unlimited | CVs follow different conventions — publications, grants, and presentations all belong |
The most common mistake: candidates over 10 years of experience try to fit everything on one page by reducing font size, eliminating white space, and cramming bullets. This produces a dense, unreadable document that performs worse than a clean two-page version. When in doubt, choose white space over compression.
| Element | Recommended | Size | Avoid |
|---|---|---|---|
| Body text (bullets, descriptions) | Calibri, Arial, Helvetica, Garamond, Georgia | 10–11pt | Comic Sans, Papyrus, display fonts; anything below 10pt |
| Name | Same family as body, bold | 16–20pt | Decorative fonts; fonts not used elsewhere in the document |
| Section headings | Same family, bold or all-caps | 11–13pt | Colored headings in non-standard colors; icon-decorated headings |
| Contact info | Same family as body | 10–11pt | Icon-only contact items; QR codes (most ATS cannot extract linked data from them) |
Color is not inherently an ATS problem — most parsers extract text regardless of color. The problem is how color is typically used: in column headers, in sidebar backgrounds, in skill bars. These structural choices cause ATS issues independent of the color itself.
If you use color at all, limit it to: your name (optional), section heading text, or a single subtle accent line. Never use color to differentiate sections of a two-column layout — that layout itself is the problem.
The order of sections is not arbitrary — it reflects both ATS expectations and the visual hierarchy a recruiter needs to scan your document in 7 seconds. ATS parsers have configured field expectations based on standard section order. Placing Education before Experience on a mid-career resume, for example, causes ATS to mis-categorize date ranges and seniority signals.
Education should appear before Work Experience only in two cases: you are a student or recent graduate with under 2 years of work experience, or the role explicitly requires a specific degree and your degree is your strongest qualifying signal (e.g., applying for a role requiring a PhD when you have a PhD but limited work history in the field).
Where your skills appear in the section order also affects how ATS weights them. Keywords in the summary and in the top bullets of your most recent role carry more match weight than identical keywords buried in the skills section at the bottom. The mechanics of this: How to Tailor Your Resume to a Job Description.
The following example shows the same candidate — same experience, same skills, same role — with two different formats. One gets parsed correctly and passes ATS. The other produces a partially corrupted profile and is filtered before a human reads it.
⚠ Name in document header — may not be extracted
[Two-column layout: left sidebar with skills/contact, right column with experience]
⚠ Left sidebar: skills, contact info — in a text box, not body text
⚠ Right column: experience bullets — ATS reads columns sequentially, merging them
Left sidebar content (in text box):
📧 [email protected]
📞 +1 555 000 1234
Skills: Python ●●●●○ SQL ●●●○○ Tableau ●●●●●
Right column experience:
Data Analyst — Fintech Corp
Built dashboards reducing reporting time by 60%
⚠ ATS output: garbled text merging both columns; email parsed as part of skills; skill bars produce zero keyword value; "Python" may not be recognized
Alex Chen
[email protected] · +1 555 000 1234 · linkedin.com/in/alexchen · New York, NY
SUMMARY
Data analyst with 5 years in financial services, specializing in reporting automation and business intelligence. Proficient in Python, SQL, and Tableau. Track record of reducing manual reporting overhead and improving data pipeline reliability.
SKILLS
Languages: Python, SQL, R
Visualization: Tableau, Power BI
Databases: PostgreSQL, Snowflake, BigQuery
Tools: dbt, Airflow, Git
EXPERIENCE
Data Analyst — Fintech Corp (B2B payments platform, Series C)
— Built automated Tableau reporting suite replacing 8 manual Excel processes; reduced analyst reporting overhead by 60% (~15 hours/week)
— Designed SQL data models in dbt supporting finance and ops team reporting; 99.8% uptime over 18 months
✓ ATS output: name, contact, all skills, all keywords, all bullets extracted correctly. Match score against data analyst posting: 74%
The content is essentially the same. The difference in ATS outcome is entirely structural. The designed version may win a design award; the clean version wins interviews.
Run this before every application. Every "no" is a rejection risk that has nothing to do with your qualifications.
Format alone does not win interviews — it gets your resume read. Once the format is clean, the content needs to convert. The most common reason qualified candidates fail at the content stage: Is Your Resume Too Generic? 8 Signs and How to Fix Them.