How to Make an ATS-Friendly Resume: Formatting Rules That Actually Matter

You have probably heard that a robot will reject your resume if you use the wrong font, a PDF, or a single table. You have probably also heard that this is a myth. Both claims contain some truth, and that is why advice about the ATS friendly resume is so confusing.

Here is the useful version. An applicant tracking system (ATS) does two things with your resume: it parses it, pulling your details into database fields, and it lets recruiters search and sort candidates. Formatting matters for the first job. Content matters for the second. A resume that fails either one is harder to find and harder to read, even if no software ever "rejects" it.

This guide separates the formatting rules that genuinely reduce risk from the ones that do not, gives you safe defaults for layout, headings, dates, fonts, and file types, and walks you through a five-minute test you can run on any template before you apply.

What an ATS-friendly resume actually means#

Almost every large employer uses an ATS. Jobscan's 2026 ATS usage report found a detectable ATS on the career sites of 97.4% of Fortune 500 companies, a share that has stayed near 98% since 2018. Smaller employers use them widely too. So the question is not whether your resume will go through one, but what the system does with it.

Job 1: Parse cleanly#

When you upload a resume, a parser extracts text and tries to sort it into fields: name, email, phone, job titles, employers, dates, education, skills. If your layout confuses the parser, your phone number might land in the "skills" field, or a whole job might vanish. A recruiter looking at your profile then sees a broken record.

Job 2: Be findable#

Recruiters search their ATS by job title, skills, tools, certifications, and location, then sort and filter the results. If your resume does not contain the words they search for, you do not show up, no matter how clean the formatting is. That is the content side of ATS-friendliness, covered in the keyword section below.

Job 3: Read well to the human who opens it#

Eventually a person reads your resume, often quickly. In a 2018 Ladders eye-tracking study, recruiters spent about 7.4 seconds on an initial resume screen, and layouts with clear sections did well while multiple columns and clutter did not, according to HR Dive. The same plain structure that helps a parser also helps a skimming human.

For a full explanation of how these systems store and rank candidates, read what an applicant tracking system is and how it works.

How resume parsing works, step by step#

Knowing what the parser does with your file makes every formatting rule in this guide make sense. Vendors use different technology, but most follow the same broad sequence.

Extraction comes first, and it is unforgiving#

If the parser cannot pull text out of an element, nothing downstream can recover it. A skills list drawn as a graphic, a summary inside a floating text box, or a contact line stored in an image simply does not exist to the system. That is why "real text in the main body" is the single most important rule.

Segmentation depends on headings#

The parser looks for familiar headings to decide where Experience ends and Education begins. When it cannot find them, it guesses, and a guess can push your degree into a job entry or your certifications into your skills. Standard headings remove the guesswork.

Normalization is where consistency pays off#

Many systems convert what they extract into standard forms, such as turning "Jan 2023" into a date value or matching "JS" to "JavaScript" in a skills list. Consistent dates and widely used terms make that conversion more reliable. Unusual abbreviations and invented titles are more likely to fall through.

What the recruiter sees afterward#

Recruiters often work from the parsed profile and a search results list, then open the original file for candidates who look promising. If parsing went wrong, your profile may show a blank title, a missing employer, or garbled skills in that list. That does not reject you automatically, but it makes you look like a weaker match next to cleaner records.

ATS myths vs. facts#

Much of the anxiety about ATS comes from claims with no traceable source. The most famous is that "75% of resumes are rejected by ATS before a human sees them." The HR Gazette, summarizing a 2025 Enhancv interview study, notes that the figure circulates without a credible source.

That study interviewed 25 U.S. recruiters. It is small and qualitative, so treat it as a window into practice rather than a national statistic. Still, the pattern is clear: systems mostly organize and help sort; people and knockout questions do most of the rejecting.

Here is how the common claims hold up.

That does not mean filters never matter. Harvard Business School research on "hidden workers" found that many systems rely on negative filters, such as ranking down candidates who have not been employed for six months, according to HBS Working Knowledge. Those filters judge your history and answers, not your font. Formatting cannot fix them, but clear dates and accurate screening answers keep you from tripping them by accident.

The ATS myths guide goes deeper on each claim, including where the myths came from.

The ATS-friendly resume layout: one column, standard order#

Layout is where parsing problems start, so get it right first. The safest structure is a single column read top to bottom, with sections in a conventional order.

Why single column#

Many parsers read a document as a linear stream of text. Jobscan describes how tables and multi-column layouts can scramble that order, producing what it calls "text-layer scrambling" where content is read in the order it was coded rather than the order it appears. In one example it describes, a design-heavy resume run through a major ATS kept the work history but dropped the skills, summary, contact details, and portfolio links.

Some modern parsers handle simple two-column layouts. The problem is that you cannot know which system an employer uses, or which version. A single column removes the gamble.

Standard section order#

For most candidates, this order parses well and reads well:

• Contact details (name, city and state, phone, email, LinkedIn or portfolio)
• Summary (two to four lines, optional but useful)
• Skills (grouped, comma- or bar-separated)
• Work Experience (reverse chronological)
• Education
• Certifications, Projects, or Volunteer Experience (as relevant)

New graduates can move Education above Experience. Career changers can move Skills or Projects higher. The resume formats guide explains when each order makes sense.

Element-by-element risk#

The table below rates common design elements by how likely they are to cause parsing problems, with a safer alternative for each.

Section headings the ATS recognizes#

Parsers rely on headings to decide where one section ends and the next begins. Creative headings make that harder. Use plain, standard names.

"Professional Experience" and "Experience" are also fine. Keep headings on their own line, in the same style throughout, and avoid placing two headings side by side.

Contact information and the resume header#

Your contact block is the most important data the parser extracts. If it fails, a recruiter may not be able to reach you, even if they like your resume.

Put contact details in the body#

Word processors have a "header" region that repeats at the top of each page. Some parsers skip it. Put your name and contact lines as the first lines of the main document instead. It looks identical on the page and removes the risk.

What to include#

• Full name on its own line, in a slightly larger size.
• City and state (a full street address is no longer expected).
• One phone number and one professional email address.
• LinkedIn URL and, if relevant, a portfolio or GitHub link, written as plain text.

Separate items with a vertical bar or spaces rather than icons. The full guide to the resume header covers formatting details, including how to handle a preferred name.

Phone and email formatting#

Write your phone number in a standard national format, such as "(555) 014-2233" or "555-014-2233," and include a country code only if you are applying across borders. Use an email address based on your name. Avoid putting your email inside a hyperlink with different display text; parsers read the visible text, so what they see should be the address itself.

Dates, job titles, and company names#

After contact details, the fields parsers work hardest to get right are titles, employers, and dates. Consistency is the rule.

Use one date format everywhere#

Pick a format and use it for every entry. Month and year is the safest choice for jobs; years alone work for education and older roles.

Write "Present" or "Current" for your current role, not a blank. Use the same dash style in every date range.

Give each job a clean title line#

Put the job title, employer, location, and dates on one or two consistent lines. For example: "Senior Data Analyst | Northwind Logistics | Denver, CO | Mar 2022 – Present." Use the title as it appeared, or a widely understood equivalent if your company's internal title is unusual ("Customer Success Manager" rather than "Client Happiness Hero").

If you held several titles at one company, list the company once and stack each title with its own dates. The guide to multiple positions at the same company shows layouts that parse well.

Fonts, bullets, and special characters#

Typography is the area with the most myths and the least real risk. Common fonts parse fine as long as they are real text.

Fonts and sizes#

Choose one readable font family, such as Calibri, Arial, Helvetica, Georgia, Garamond, or Cambria. Use 10 to 12 point for body text, 11 to 14 point for section headings, and a little larger for your name. The best resume fonts guide compares options for readability.

Bullets and symbols#

• Use standard round or square bullets, or simple hyphens.
• Avoid arrows, checkmarks, emoji, and icon fonts, which may convert to odd characters.
• Use plain bars ("|") or commas to separate inline items.
• Spell out symbols that matter, such as "and" instead of an ampersand in section headings.

Bold, italics, and caps#

Bold and italics are fine for emphasis, and all-caps headings are fine. Avoid whole paragraphs in all caps; they are harder for humans to read and offer no parsing benefit.

Skills section format that parses#

Write your skills as plain text, grouped by type, with a separator the parser can split on. Grouping helps humans scan, and plain separators help software tokenize each skill.

If you want to show proficiency, use words ("advanced," "working knowledge") rather than bars, dots, or stars. Graphical ratings carry no readable data, and most recruiters find them hard to interpret anyway.

Links and URLs#

Write links as visible text, such as "linkedin.com/in/jordanlee" or "github.com/jlee-data." A hyperlink hidden behind a word like "Portfolio" disappears when the text is extracted. Shorten long URLs by removing "https://" and "www," and make sure each one works before you send the resume.

Length and page breaks#

Two-page resumes parse fine. Page count is a human-reader decision, not an ATS limit. What matters is that each page continues the same single-column structure, that a job entry does not split awkwardly with its title on one page and all its bullets on the next, and that page numbers or repeated names in the footer do not interrupt the text. For page-count guidance by career stage, see how long a resume should be.

PDF or Word: choosing the right file type#

File type causes more worry than it deserves, but there are a few real traps. Use this decision table.

Text-based vs. image-based PDFs#

A PDF you export from Word, Google Docs, or a resume builder contains a text layer that a parser can read. A PDF made by scanning a printed page, or by exporting a design tool's artwork as an image, may contain only a picture of text. To check, open your PDF and try to highlight a single word. If you cannot, the parser probably cannot either. The Harvard College resume guide likewise reminds you to make sure formatting translates properly when converted to PDF.

File names#

Name the file so a recruiter can find it: "Firstname-Lastname-Resume.pdf" or "Firstname-Lastname-Data-Analyst.pdf." Avoid "resume_final_v7.pdf." For more on the trade-offs, read PDF or Word for your resume.

Keywords: the content half of an ATS-friendly resume#

Clean formatting gets your data into the system. Keywords get you found once it is there. If a recruiter searches for "Salesforce" and "pipeline management," your resume needs those exact words in it.

Mirror the job post's language#

Read the posting and list the job title, required skills, tools, certifications, and repeated phrases. Where they truthfully describe your work, use the employer's wording in your summary, skills section, and bullets. The resume keywords guide explains how to prioritize them, and the keyword-finding walkthrough shows the extraction step by step.

Write acronyms both ways#

Recruiters search in different ways, so include both the full term and the acronym at least once: "Search Engine Optimization (SEO)," "Certified Public Accountant (CPA)," "Electronic Health Records (EHR)."

Match the job title where it is honest#

Recruiters very often search by job title first. If the posting says "Product Marketing Manager" and your official title was "Marketing Manager, Product Launches," consider a summary line or headline that uses the target title, such as "Product marketing manager with 6 years of launch experience." Do not change the title in your work history to something you never held; use the summary and bullets to bridge the gap instead.

Put keywords in context, not in piles#

A skills section helps search, but keywords inside bullets do double duty: they get found and they prove you used the skill. "Built weekly pipeline dashboards in Salesforce for a 14-person sales team" beats a bare "Salesforce" listed in a block of 40 tools.

The free resume keyword scanner compares your resume against a job post and lists matched and missing terms, so you can see gaps before a recruiter does.

How to test whether your resume is ATS-friendly#

You do not need to guess. These five steps take about five minutes and catch nearly every structural problem.

1. Run the plain-text paste test. Open your PDF or DOCX, select all text, copy, and paste it into a plain text editor. Read top to bottom.
2. Check the order. Your name and contact details should come first, then sections in order, with each job's title, employer, and dates together.
3. Check for missing pieces. Look for anything that vanished: sidebar skills, links, contact lines, or text from a box or table.
4. Use a parser preview. Upload the resume to a parser tool or to an application with an "autofill from resume" option, and see whether each field fills correctly.
5. Fix and repeat. Change one thing at a time, export again, and rerun the test until the output is clean.

Here is what the paste test can reveal.

In the scrambled version, the sidebar skills are woven into the job entry. A parser would struggle to tell which words are a title, which are skills, and which are a date.

How to read an autofill preview#

When an application offers to fill fields from your resume, treat the result as a free parse report. Check the work history entries first: does each one have the right title, employer, and start and end dates? Then check education, and finally the contact fields. If two jobs merged into one, or a date landed in the wrong entry, the cause is almost always layout, not content.

Fix the field by hand before you submit, because the corrected version is what the recruiter will see. Then fix the underlying layout in your template so the next application parses cleanly without manual repairs.

What to fix first when the test fails#

If the paste test or preview shows problems, fix them in this order. Each step solves the most common cause of the symptom.

For a quicker check, the free ATS resume checker flags sections, dates, and contact details that do not parse, and the resume parser shows your resume field by field the way an ATS stores it. If something does break, the guide to resume parsing errors lists the usual causes and fixes.

When a designed resume is fine#

ATS-friendly does not mean ugly. It means the structure is simple. You can still use a clean accent color, good spacing, a well-chosen font, and clear hierarchy. What you avoid are layout tricks that hide text from a parser.

Some situations call for a more designed version, as long as you keep a parse-safe one for portals.

If you work in a visual field, the creative resume guide covers when design helps. For choosing a template that balances both needs, see how to choose a resume template.

Keeping two versions in sync#

If you keep both a designed and an ATS-friendly version, update content in one place first, usually the ATS version, then copy changes into the designed one. Dates, titles, and numbers should match exactly across both, because a recruiter may see the parsed profile and the designed PDF side by side. A quick diff of the two text exports before each application catches drift.

ATS-friendly rules for special situations#

The core rules apply to everyone, but a few situations need small adjustments.

• New graduates: Put Education above Work Experience and add a Projects section with standard formatting. Treat each project like a job entry, with a title line and bullets.
• Consultants and contractors: List the agency or your own business as the employer, then name major clients inside the bullets. This keeps the employer field clean and still makes client names searchable.
• Career changers: Keep chronological order so dates parse, but lead with a summary and skills section that use the new field's vocabulary.
• Federal applicants: USAJOBS resumes follow their own rules on length and required details, so do not assume a private-sector ATS template fits. The federal resume guide covers what changes.
• International applications: Some countries expect a photo or personal details that U.S. resumes omit. Follow local norms, but keep the structure single-column and text-based either way.

Portal quirks#

Large platforms such as Workday, Greenhouse, Lever, and iCIMS each handle uploads a little differently, and some ask you to retype details after parsing. Always review the autofilled fields before you submit. The guide to applying through Workday, Greenhouse, and other portals walks through the common screens.

Common ATS formatting mistakes and quick fixes#

Most problems come from a handful of habits. Fix these and your resume will parse cleanly on almost any system.

Other mistakes worth catching:

• Skills listed only in a sidebar or table, so they never reach the parsed record.
• Job titles placed under the dates instead of on the title line, so titles and employers swap.
• A summary written inside a text box, which some parsers skip entirely.
• Hyperlinks attached to words like "Portfolio" with no visible URL, which disappear in plain text.
• Two different resumes uploaded to the same employer with different dates or titles.

Remember that formatting is only part of the picture. Many systems also show recruiters a match score; the guide to ATS resume scores explains what those numbers mean and how much to trust them.

Next steps: your ATS-friendly resume checklist#

Run through this list once for your master template, then focus your energy on tailoring content for each job.

• Single-column layout with no text boxes or tables for core content.
• Standard section headings: Summary, Skills, Work Experience, Education.
• Name and contact details in the body, not the document header.
• One consistent date format, with "Present" for your current role.
• Job title, employer, location, and dates on a clean title line.
• A common font at 10 to 12 point, with plain bullets.
• Text-based PDF or DOCX, matching any instruction in the posting.
• Keywords from the job post in your summary, skills, and bullets.
• Plain-text paste test passed, with nothing missing or out of order.

Once your template passes, stop worrying about the robot. Spend the time you save on what actually moves recruiters: relevant experience, specific results, and the job post's language used honestly. Whether you build in a word processor or a resume builder such as Resume Maker, any clean document that passes the paste test will do the job.