Resume Formatting Rules That Apply to Every ATS

Every applicant tracking system parses resumes differently. Workday, Greenhouse, Taleo, Lever, iCIMS -- they all have their own quirks, strengths, and blind spots. We'll cover platform-specific advice in separate guides. But before you worry about any of that, there's a set of formatting rules that work everywhere.

These are the universal basics. Get them right, and your resume will parse correctly on every major ATS. Get them wrong, and it won't matter how well-written your content is -- the system will either misread it or miss it entirely.

Use standard section headings

ATS parsers look for specific section headings to categorize your information. When they find "Work Experience," they know the bullet points that follow are your job history. When they find "Education," they know to look for degrees and institutions.

Creative headings like "Where I've Made an Impact" or "My Professional Journey" might look good to a human, but they confuse parsers. The system doesn't know that "Where I've Made an Impact" means "Work Experience," so your entire job history might end up miscategorized or ignored.

Stick to these headings:

• Work Experience (or Professional Experience)
• Education
• Skills (or Technical Skills, Core Competencies)
• Certifications (or Licenses & Certifications)
• Summary (or Professional Summary)
• Projects (if applicable)
• Volunteer Experience (if applicable)

No tables, columns, or text boxes

This is probably the single most important formatting rule. Tables and multi-column layouts break parsing on nearly every ATS platform. The parser reads left-to-right, top-to-bottom, but tables and columns create a different reading order. The result is scrambled text -- your job title might merge with a date from a different section, or your skills list might split into fragments scattered throughout the parsed output.

Text boxes are even worse. Some parsers ignore text box content entirely, meaning anything inside one simply disappears. If you've put your contact information or skills in a text box, the recruiter's system might show a resume with no name, no email, and no skills listed.

Use a single-column layout with clear line breaks between sections. It's not as visually striking, but it parses perfectly everywhere.

Choose standard, readable fonts

ATS parsing isn't usually affected by font choice -- the system reads the underlying text data, not the visual rendering. But there are two good reasons to stick with standard fonts anyway.

First, some older parsers do rely on font metadata, and non-standard fonts can occasionally cause character encoding issues where special characters turn into garbled symbols. Second, if your resume does reach a human (which is the goal), readability matters. Decorative or overly stylized fonts make scanning harder.

Safe choices:

• Calibri (the most commonly recommended by recruiters)
• Arial
• Helvetica
• Times New Roman
• Georgia
• Garamond

Use 10-12pt for body text and 13-16pt for section headings. Don't go below 10pt -- it's hard to read on screen, and some parsers struggle with very small text.

Reverse chronological order

List your work experience with your most recent position first, then work backward. This is the format every ATS expects, and it's the format recruiters prefer. When a system parses your resume, it typically assigns "current" or "most recent" status to the first position it encounters under Work Experience.

Functional resumes (which group experience by skill rather than by job) are harder for ATS systems to parse and are viewed with suspicion by many recruiters. If you're changing careers or have gaps, a combination format -- skills summary at the top, followed by chronological work history -- gives you the best of both worlds without confusing the parser.

Submit .docx or clean PDF

The .docx format is the safest choice for ATS compatibility. Every major platform can parse Word documents reliably. PDF parsing has improved significantly in recent years, and most modern systems handle clean PDFs well -- but "clean" is the key word. A PDF created by saving a Word document as PDF is clean. A PDF created by scanning a printed page, exporting from a design tool like Canva, or flattening a complex layout often isn't.

If a job posting specifies a format, always follow their instructions. If it doesn't specify, .docx is the safer bet. If you strongly prefer PDF, make sure it's text-based (you should be able to select and copy text from it) rather than image-based.

Avoid: .pages, .odt, .rtf, image files (.png, .jpg), or any format that requires specialized software to open.

Keep content out of headers and footers

Many resume templates put your name, email, phone number, or LinkedIn URL in the document header or footer. This looks clean visually, but most ATS parsers skip headers and footers entirely. They read the document body, and anything outside it is invisible to them.

If your name is in the header and the parser ignores it, your application might show up in the recruiter's system as an unnamed candidate with no contact information. That application is going nowhere.

Put everything in the main body of the document. Your name, phone, email, and LinkedIn should be in the first few lines of the document body -- not in the header area.

No graphics, icons, or images

Skill-level bars, star ratings, headshot photos, decorative icons, and infographic-style layouts are all invisible to ATS parsers. The system can't read an image, so it ignores it. If your skills section is a visual bar chart showing "Python: 4/5 stars," the parser sees nothing. Your Python skill doesn't exist as far as the system is concerned.

This applies to logos too. Don't put company logos next to your work experience -- they add nothing for the parser and can sometimes disrupt the text flow around them.

Spell out abbreviations (at least once)

Different job postings use different abbreviations for the same thing. One says "SQL," another says "Structured Query Language." One says "PMP," another says "Project Management Professional." If you only use one form and the posting uses the other, the keyword match fails.

The solution: Include both forms at least once. In your skills section: "Project Management Professional (PMP)." In a bullet point: "Managed databases using SQL (Structured Query Language)." This covers both versions without looking awkward or forced.

Use standard date formats

ATS parsers need to read your employment dates to calculate tenure and identify your most recent role. Non-standard date formats can cause parsing errors.

Use one of these formats consistently:

• January 2022 - Present
• Jan 2022 - Present
• 01/2022 - Present

Don't use just years ("2022 - 2024") unless you want the parser to assume January-to-January. Avoid overly specific dates ("January 15, 2022") -- month and year is the standard. And always use "Present" or "Current" for your current role, not a future date.

Name your file professionally

This isn't a parsing issue -- it's a human one. Recruiters download dozens of resumes at a time. A file named "resume_final_v3_REAL_FINAL.docx" or "document1.pdf" doesn't help anyone.

Use this format: FirstName-LastName-Resume.docx (e.g., "Sarah-Chen-Resume.docx"). It's immediately identifiable, sorts well alphabetically, and looks professional. If you're submitting for a specific role, you can add it: "Sarah-Chen-Resume-Product-Manager.docx."

The bottom line

These ten rules work across every major ATS platform. They're not about gaming the system -- they're about making sure the system can read your resume accurately in the first place. The best content in the world doesn't help if it's trapped in a format the parser can't understand.

Once you have these basics in place, you can start thinking about platform-specific optimization. We cover Workday, Greenhouse, Taleo, Lever, and iCIMS in separate guides. But start here -- these universal rules are the foundation everything else is built on.