ATS & Optimization · Format

Resume Format Guide:
Which Format Passes ATS and Gets Read

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.

By Rolerise Editorial16 min read
75%

of resumes are rejected by ATS before a human reads them

98%

of Fortune 500 companies use ATS to screen resumes

7.4 sec

average time a recruiter spends on first pass once a resume reaches them

~40%

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.

The Three Resume Formats — What Each One Actually Is

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.

Reverse-Chronological

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.

  • ATS compatibility: Excellent. This is the structure ATS was built to parse.
  • Recruiter reception: Most familiar — no cognitive load, easy to scan.
  • Best for: Consistent career progression in one field; candidates applying to the same type of role they currently hold; anyone with 3+ years of relevant experience.
  • Avoid when: Your most recent role is least relevant to the target job; you have significant gaps; you are making a major career change.

Functional (Skills-Based)

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.

  • ATS compatibility: Poor. Skills without job-context are mis-categorized or ignored. Work history without dates creates parsing errors.
  • Recruiter reception: Negative in most cases — widely associated with hiding gaps, inflating credentials, or lacking genuine experience.
  • Best for: Almost no situation. The problems outweigh any benefit.
  • Avoid when: Always — use the hybrid format instead if you want skills-first framing.
Why functional resumes fail

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.

Hybrid (Combination)

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.

  • ATS compatibility: Good — preserves the standard chronological structure ATS expects, while adding keyword-rich skills section at top.
  • Recruiter reception: Positive — familiar structure, skills immediately visible without hunting.
  • Best for: Career changers; candidates with highly relevant skills that aren't obvious from job titles; anyone re-entering the workforce; senior candidates with broad skill sets.
  • Avoid when: Your work history is the strongest signal — in that case, chronological is cleaner.
Three resume formats — quick comparison
FormatATS ScoreRecruiter ReceptionUse WhenAvoid When
Reverse-ChronologicalExcellentMost positive — familiar, easy to scanConsistent career in one field; applying to same-level roleCareer changing; recent role is least relevant; major gaps
FunctionalPoorNegative — 54% of recruiters flag itAlmost neverAll standard job applications
HybridGoodPositive — familiar structure with prominent skillsCareer change; skills need to be visible before work historyWhen work history alone tells the story clearly

ATS Format Rules: What Causes Parsing Failures

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).

❌ Format elements that break ATS

  • Two-column or three-column layouts

    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.

  • Text inside tables used for layout

    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.

  • Contact information in the document header

    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.

  • Text inside text boxes or shapes

    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.

  • Icons for contact information

    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.

  • Skill progress bars, rating dots, or visual skill indicators

    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.

  • Scanned PDFs or image-based PDFs

    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.

  • Non-standard section headings

    "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.

✓ Format elements that pass ATS reliably

  • Single-column layout — all content flows top to bottom in one column
  • Contact info in document body — not in the header/footer zone
  • Standard section headings — Experience, Education, Skills, Summary, Certifications
  • Plain text bullet points — standard • or – characters, not custom symbols or images
  • Standard fonts — Calibri, Arial, Helvetica, Georgia, Times New Roman, Garamond
  • Font size 10–12pt body — no smaller; ATS may skip very small text
  • Bold and italic sparingly — for emphasis only, not for entire sections
  • .docx file type — universally compatible; PDF only if exported as text-based PDF from Word/Google Docs
  • Simple horizontal dividers — a plain line between sections is fine; decorative borders are not
  • Margins 0.5–1 inch — no narrower; some parsers truncate content outside standard margins
ATS platform parsing behaviour — format recommendations by platform
ATS PlatformUsed ByFormat SensitivityRecommended FormatHow to Identify
WorkdayFortune 500, large enterprisesHigh — tables and columns break parsing.docx, strict single column, no tablesURL contains "wd3.myworkday.com" or "wd1.myworkday.com"
Taleo (Oracle)Large corporations, governmentVery High — oldest parser, strictest.docx, single column, plain text onlyURL contains "taleo.net"
iCIMSEnterprise, healthcare, manufacturingHigh — headers/footers ignored.docx, no tables, contact in bodyURL contains "icims.com"
GreenhouseTech startups, mid-marketMedium — handles PDF wellPDF or .docxURL contains "greenhouse.io"
LeverTech-forward companiesMedium — more format-tolerantPDF preferredURL contains "lever.co"
SmartRecruitersGlobal mid-marketLow — modern AI parserPDF or .docxURL contains "smartrecruiters.com"
AshbyHigh-growth tech startupsLow — human-first review culturePDF preferredURL contains "ashbyhq.com"
BambooHRSMBs, 50–500 employeesLow — basic parserAny standard formatURL 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.

PDF vs .docx — Which File Type to Submit

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.

PDF vs .docx — ATS compatibility comparison
.docxPDF (text-based, exported from Word)PDF (image-based, scanned or from design tool)
ATS compatibility (general)Best — universally supportedGood — supported by modern ATSFail — zero extractable text
Workday / Taleo / iCIMSBestAcceptable but riskierFail
Greenhouse / Lever / AshbyBestBest — these platforms prefer PDFFail
Preserves formatting for human readerVaries — depends on recipient's Word versionYes — consistent across all viewersYes — 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
How to check if your PDF is text-based

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.

One additional rule: file naming

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.

Visual Format Rules: What Recruiters Need to See in 7 Seconds

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.

Length

Resume length by experience level
Experience LevelRecommended LengthReasoning
Student / Entry level (0–2 years)1 pageLimited experience; one page forces prioritization; recruiter expects brevity
Early career (2–5 years)1 pageEnough experience to fill one page well; two pages suggests padding
Mid career (5–15 years)2 pagesSufficient substantive history to justify two pages; most recruiters expect it
Senior / Executive (15+ years)2 pages maxRoles older than 15 years rarely contribute to hiring decisions; remove or condense
Academic / Research / CV contextUnlimitedCVs 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.

Font and sizing

Font recommendations for resume formatting
ElementRecommendedSizeAvoid
Body text (bullets, descriptions)Calibri, Arial, Helvetica, Garamond, Georgia10–11ptComic Sans, Papyrus, display fonts; anything below 10pt
NameSame family as body, bold16–20ptDecorative fonts; fonts not used elsewhere in the document
Section headingsSame family, bold or all-caps11–13ptColored headings in non-standard colors; icon-decorated headings
Contact infoSame family as body10–11ptIcon-only contact items; QR codes (most ATS cannot extract linked data from them)

White space and margins

  • Margins: 0.5–1 inch on all sides. Never below 0.5 inch — some ATS and printers truncate content near the edge.
  • Line spacing: 1.0–1.15 within sections; add 6–8pt space between sections. This creates visual breathing room without inflating length.
  • Bullet spacing: 2–4pt space after each bullet. Bullets that run together are the most common cause of recruiter fatigue on dense resumes.
  • Section dividers: A simple horizontal line between major sections is sufficient and ATS-safe. Decorative dividers, gradient lines, or icon-decorated separators are not.

Color

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.

Section Order: What Goes Where and Why

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.

Reverse-Chronological — section order

  1. Contact Information — name, phone, email, LinkedIn, city/country
  2. Professional Summary — 3–4 sentences, role + skills + outcome
  3. Work Experience — most recent first, 3–5 bullets per role
  4. Education — degree, institution; no GPA unless under 3 years post-grad
  5. Skills — grouped by type: languages, tools, methodologies
  6. Certifications — if relevant to role; full name, not acronym only
  7. Projects — only if directly relevant and not covered in experience

Hybrid — section order

  1. Contact Information
  2. Professional Summary — leads with target function, not origin field
  3. Skills — moved up; grouped by target field priority
  4. Relevant Projects — if direct experience is thin
  5. Work Experience — full reverse-chronological, not minimized
  6. Education
  7. Certifications

Special cases: when to move Education up

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.

Format Before and After: Same Content, Two Different Outcomes

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.

❌ Before — Designed template, fails ATS

⚠ 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

✓ After — Single-column, passes ATS

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.

Complete Format Checklist

Run this before every application. Every "no" is a rejection risk that has nothing to do with your qualifications.

Layout and structure

  • Single-column layout — no sidebars, no two-column design
  • No text boxes or shapes containing text
  • No tables used for layout purposes
  • Contact information in the document body — not in the header or footer zone
  • All section headings are standard: Experience, Education, Skills, Summary, Certifications
  • Margins between 0.5 and 1 inch on all sides

File and font

  • Saved as .docx — or as text-based PDF (verify: can you highlight text in the PDF?)
  • File named: FirstName_LastName_Resume.pdf or .docx
  • Font is standard: Calibri, Arial, Helvetica, Georgia, or Garamond
  • Body font size 10–11pt; name 16–20pt; section headings 11–13pt
  • No icons for contact information — plain text only
  • No skill bars, progress indicators, or visual skill ratings

Length and visual hierarchy

  • Length is appropriate: 1 page (0–5 years) or 2 pages (5+ years)
  • White space between sections — document does not feel dense or cramped
  • Bullets are consistent: all use the same bullet character
  • No bullet uses more than 2–3 lines — if longer, it is two bullets
  • Dates are consistent: either "Jan YYYY" everywhere or "YYYY" everywhere — not mixed

Section order

  • Contact → Summary → Experience → Education → Skills (chronological) OR
  • Contact → Summary → Skills → Projects → Experience → Education (hybrid)
  • Education does not appear before Experience unless entry-level or degree is the primary qualifier
  • Most recent role is listed first in Experience

Content format (ATS keyword placement)

  • Primary keywords from the job posting appear in the Summary
  • Skills section uses exact tool names — "Salesforce" not "CRM software"
  • Certifications spelled out in full — "AWS Certified Solutions Architect" not "AWS cert"
  • Degree field stated clearly — "Bachelor of Science in Computer Science" not "BS, CS"

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.

Frequently Asked Questions