ATS Resume Best Practices 2026: 20 Tips + What Now Backfires

What an ATS-Friendly Resume Looks Like (Annotated Example)

Below is a complete one page resume for a fictional candidate, drawn as it would appear in a Word or Google Docs file. The numbered badges match the table underneath.

Dana Whitfield, Senior Supply Chain Analyst: single column, live text, 11pt Calibri

1Dana Whitfield

2Columbus, OH | (614) 555-0147 | dana.whitfield@example.com | linkedin.com/in/danawhitfield

3Summary

Supply chain analyst with 6 years of experience in demand planning, inventory optimization, and carrier reporting for freight and retail distribution. Builds forecasts and dashboards in SQL, Excel, and Tableau. Seeking a Senior Supply Chain Analyst role.

4Skills

Technical: SQL, Tableau, Excel (pivot tables, XLOOKUP), Python, Enterprise Resource Planning (ERP)

Domain: demand planning, inventory optimization, carrier management, Sales and Operations Planning (S&OP), KPI reporting

5Work Experience

6Senior Supply Chain Analyst | Regional Logistics Company | Columbus, OH | Mar 2022 to Present

7Built weekly demand forecasts in SQL and Tableau for 40 distribution lanes, cutting forecast error from 22% to 15% over 12 months.
Shifted lane assignments using carrier on-time data, reducing expedited freight spend by $310K a year.
Led a 4 person review with warehouse and finance teams, retiring 3 duplicate weekly reports.

Supply Chain Analyst | National Retail Distributor | Columbus, OH | Jul 2019 to Feb 2022

Maintained inventory records for 6,200 SKUs in the ERP system, holding stock accuracy above 98%.
Automated the weekly carrier scorecard in Excel, saving the planning team 5 hours a week.

8Education

Bachelor of Science in Business Administration, Great Lakes State University, 2019

9Certifications

Certified Supply Chain Professional (CSCP), ASCM
Project Management Professional (PMP), Project Management Institute

Badge	Element	Best practice it shows	Tips
1	Name on the first line	Live text in the body, not an image or a header	3
2	One contact line	City and state, phone, email, and LinkedIn as plain text	3, 13, 19
3	Summary	Target role and core terms where a reader looks first	6, 8
4	Skills grouped by type	Own heading, technical and domain lines, full term with abbreviation	7, 10, 18
5	Standard heading	Work Experience, not a creative label	4, 15
6	Position line	Title, employer, city, and dates in one consistent pattern	11, 20
7	Quantified bullet	Tool, scope, and result in one sentence	12, 16
8	Education	Degree spelled out, then school and year	4
9	Certifications	Official name, abbreviation in parentheses, issuer	14
Whole page	Layout	One column, no tables, text boxes, icons, or images, standard font	1, 2, 3

Dana Whitfield, the employers, and every figure are fictional and illustrative. Replace them with your own verifiable details.

Want a downloadable version of this structure? See our ATS resume templates and the best ATS-friendly templates roundup.

Copy and Paste Format Spec, Section by Section

Use these headings and patterns as written. They are the conventional names parsers are built around, and each one keeps a section easy to find.

Section	Heading to use	Copy and paste pattern	Avoid
Header and contact	None, name as the first line	`First Last` `City, ST \| 555-555-0100 \| name@example.com \| linkedin.com/in/yourname`	Contact details in the document header, footer, or a text box; icons instead of words; a photo
Summary	Summary or Professional Summary	`Target job title with N years of experience in [core area]. [Two or three matched tools or skills]. [One quantified result].`	Objective statements, first person paragraphs, more than four lines
Skills line	Skills or Technical Skills	`Technical: Tool, Tool, Tool` `Domain: skill, skill, skill`	Skill bars, star ratings, icons, tables, sidebars
Experience entry	Work Experience or Professional Experience	`Job Title \| Employer \| City, ST \| Mon YYYY to Mon YYYY` Then bullets: `Action verb + what + tool + result`	Dates on a separate line from the employer, mixed date formats, missing employer names, titles inside a header
Education	Education	`Degree in Field, Institution, Year`	Degree abbreviations only, logos, tables
Certifications	Certifications or Licenses and Certifications	`Full Official Name (ABBR), Issuing Organization, Year`	Abbreviation alone, badge images, expired credentials without a date

Greenhouse Support lists contact details in a header, footer, or text box and incomplete job titles or company names among documented causes of a partial parse.

For a fill-in-the-blank version, see our ATS resume template or the engineer-approved template. For how to list skills in detail, see how to list skills on a resume.

Before and After: Five Common Fixes

Each pair uses fictional details. The left column breaks a parsing rule; the right column fixes it.

Before	After	Why it matters
Name and phone number inside the Word header	Name and contact line as the first lines of the body	Greenhouse lists contact details in a header, footer, or text box as a cause of partial parses
Heading: "Career Journey"	Heading: "Work Experience"	Parsers file content under conventional headings
Skills: Excel, team player, HIPAA compliance, results-oriented	Technical: Excel, SQL. Domain: HIPAA compliance, claims review	Grouped skills are easier to categorize; soft traits belong in bullets
Dates: "May 2022" in one role, "06/2023" in another	Dates: "May 2022" and "Jun 2023"	One format keeps tenure and gap calculations clean
"Improved reporting process"	"Built a weekly Tableau dashboard that replaced 3 manual spreadsheets"	Names the tool, the scope, and the outcome

How a Parser Reads Your File

A resume parser converts your file into a structured candidate record. Vendors differ in the details, but the stages below hold across the documentation we reviewed. This is a simplified model, not any one vendor's exact pipeline.

Text extraction. The parser pulls the text layer out of the file. A file with no text layer, such as a scan or an image saved as a PDF, gives it nothing to read.
Section detection. Reading from top to bottom, it uses headings to split the text into sections.
Field extraction. Within each section it identifies contact details, work history positions (employer, job title, start and end dates), education, skills, and certifications.
Record creation. The fields fill the candidate profile that recruiters search and filter. Fields that failed to parse have to be corrected by hand.

iCIMS describes parsing as extracting data from a Word or PDF document and converting it into a structured form. Greenhouse states that formatting problems may produce a partial parse that needs manual correction and verification.

What breaks extraction

Every item below appears on Greenhouse's page on unsuccessful resume parses.

Element	What goes wrong	Fix
Columns	Listed as a cause of unsuccessful parses	Single column
Tables	Complex resumes with tables are listed as a cause	Plain text lines
Headers and footers	Listed, especially with name and contact details inside them	Contact line in the body
Text boxes	Name and contact details in a text box are listed	Move text into the main body
Images and graphics	Graphics, photos, word art, and resumes uploaded as an image are listed	Live text only
Spaced letters	Spaces between the letters of a word are listed	Normal letter spacing
Unclear sections	Resumes without clear sections and with differing formats throughout are listed	Standard headings, one format

Source: Greenhouse Support, "Unsuccessful resume parse." Other systems may handle some of these better; the safe choice is to avoid all of them.

Resume Optimizer Pro's own parse follows the same idea. It is an LLM based extraction against a fixed resume schema (contact, education, work history positions, skills, certifications), designed to behave like Sovren and Textkernel style parsers without licensing their engines, and built by a former ATS software engineer. See what your file extracts with Resume Optimizer Pro. For more on the technical layer, see what makes a resume ATS compliant.

ATS in 2026: What the Documentation Shows

Three figures we confirmed on primary pages in September 2026. Everything else on this page is a rule of thumb, not a measured rate.

97.4%

of Fortune 500 companies have a detectable ATS: 487 of 500 (Jobscan, 2026 Applicant Tracking System Usage Report)

2.5 MB

the largest resume file Greenhouse Recruiting can parse (Greenhouse Support)

5

resume file types Greenhouse accepts: doc, docx, pdf, rtf, and txt (Greenhouse Support)

ATS-Friendly Resume Checklist

Twenty checks in five groups. The last column points to the tip that explains each one.

Check	Tip
File
Saved as .docx or a text based PDF, and the text can be selected and copied	5
Under 2.5 MB, with a clear name such as FirstName-LastName-Resume	5
Layout
Single column	1
No tables, text boxes, images, icons, or skill bars	3
Contact details in the body, not the header or footer	3, 13
Standard font at 10 to 12pt	2
Headings
Standard section names: Summary, Skills, Work Experience, Education, Certifications	4
Reverse chronological work history	15
Skills under their own heading, grouped by type	10, 18
Content
One date format everywhere	11
Every position shows title, employer, city, and dates	11, 13
Bullets carry a number where you can defend it	12
Certifications use official names with the abbreviation	14
Titles, dates, and employers match your LinkedIn profile, and any gap or lateral move is explained	19, 20
Keywords
Job description wording used where it is accurate	6
Full term and abbreviation both present	7
Strongest terms in the summary and first bullets	8
Each keyword backed by a bullet, with related terms alongside	16, 17
No hidden text and no stuffing	9

Short on time? Do these five first: single column with live text, standard headings, one date format, a grouped skills line, and job description wording in the summary.

File Format and File Naming

The vendor pages we fetched list both Word and PDF files as supported. The format that fails is an image, not a PDF.

Platform	What its documentation says
Greenhouse	Accepts .doc, .docx, .pdf, .rtf, and .txt; uploads up to 100 MB; cannot parse resumes larger than 2.5 MB
Workday (HiredScore documentation)	Supports DOC, DOCX, PDF, RTF, and TXT resume attachments; parsed resumes are viewable only in those formats
iCIMS	Text extraction by default covers pdf, doc, docx, rtf, and txt among others; client configurations may vary

Sources: Greenhouse Support (supported formats, unsuccessful resume parse), Workday HiredScore documentation (candidate profiles), iCIMS developer documentation (binary files).

Word or PDF? Follow the portal if it names a format. Otherwise use a .docx, or a PDF exported from Word or Google Docs.
Text based test. Open the file, select all, and paste into a plain text editor. If the text is clean and in order, a parser can read it.
File name. None of the vendor pages we reviewed says a file name affects parsing. A plain name such as Dana-Whitfield-Resume.pdf still helps recruiters who download files.

For platform specifics, see our guides to Greenhouse, Workday, iCIMS, and Lever.

Test Your File in Five Minutes

You cannot see a vendor's parser, but you can check whether your text survives extraction.

Copy everything. Select all text in the file and paste it into a plain text editor.
Read it top to bottom. Your name should come first, sections should appear in order, and no words or characters should be missing or garbled.
Find your contact details. Search the pasted text for your phone number and email. If they are absent, they sit in an image, header, or text box.
Check each position. Title, employer, and dates should read together on one line.
Check the portal. If the application form pre-fills fields from your upload, compare them with your resume and correct any errors before submitting.

A plain text paste is a rough proxy. It shows whether text survives, not how a specific vendor maps it into fields.

Which Best Practice to Prioritize by Situation

All 20 tips apply to everyone, but the order of work differs. This is editorial guidance, not vendor documentation.

Your situation	Do first	Tips
Resume built in a design tool	Rebuild as a single column with live text and standard headings	1, 3, 4, 5
Career changer	Write a summary that names the target role, and add related terms	8, 15, 17
Recent graduate	Add a grouped skills line and certifications with official names	10, 14, 18
Long career	Keep dates consistent, detail recent roles, and keep older roles short	11, 15, 20
Gap or lateral move	Use one date format and explain the gap in a line	11, 20
Applying to many similar jobs	Tailor the summary and first bullets to each job description	6, 8

Group 1: Formatting Tips

Formatting errors cause parse failures before any keyword matching runs. These five rules cover the most common ones.

Tip 1: Use a single-column layout

Parsers read top to bottom. In a two-column layout, left and right column text can merge into nonsense lines, and Greenhouse lists columned layouts among documented causes of unsuccessful parses. See our ATS resume format guide for the full list of elements to avoid.

Tip 2: Stick to standard fonts

Use Arial, Calibri, Garamond, Georgia, Times New Roman, Helvetica, Tahoma, or Verdana at 10 to 12pt for body text. Decorative and script fonts can extract as unrecognized characters, which Greenhouse also lists among import problems. Our resume font guide covers the details.

Tip 3: Avoid graphics, images, and tables

Photos, icons, and word art carry no readable text. Tables and text boxes can scramble reading order or hide content from a parser. Move that content into the main body as plain text.

Tip 4: Use standard section headings

Parsers split a resume into sections by its headings, so conventional names work best: Work Experience, Education, Skills. A label like Career Journey or Toolkit can leave content unfiled, and Greenhouse cites resumes without clear sections as a cause of partial parses.

Tip 5: Submit a .docx or a text-based PDF

Vendor documentation lists both formats as supported. What fails is an image: a scan, a screenshot, or a design export with no text layer. If the portal names a format, use that one.

Group 2: Keyword Tips

Keyword matching drives search and ranking in most ATS. These five tips cover how to match well without stuffing.

Tip 6: Mirror the language of the job description

If the job description says "cross-functional collaboration," use that phrase where it truthfully describes your work. Some systems match exact strings, and "interdepartmental teamwork" may not register. Copy wording for skills and tools, never for duties you have not done.

Tip 7: Include both spelled-out and abbreviated versions of key terms

Write "Search Engine Optimization (SEO)" once, then use either form. A search for "SEO" can miss the full phrase and the reverse. This applies to certifications (Project Management Professional, PMP), tools (Amazon Web Services, AWS), and methods (continuous integration and continuous deployment, CI/CD).

Tip 8: Place primary keywords in your summary and first bullet under each role

Recruiters scan the top of each section first, so the summary and the first bullet under each role are where a skimming reader lands. Put your most relevant terms there, in natural sentences.

Tip 9: Do not stuff keywords in white text

Text in the background color shows up the moment anyone selects all, pastes into a text editor, or converts the file. It reads as manipulation and costs you the reader's trust.

Tip 10: Use a clean skills section

A dedicated Skills heading with a comma-separated list or simple bullets gives a parser one labeled place to extract skills from. List the tools, technologies, methods, and certifications you actually use, in the job description's wording.

Group 3: Content Tips

These five tips cover content choices that affect parsing and the recruiter review that follows.

Tip 11: Use standard date formats consistently

Parsers calculate tenure and gaps from dates, and a mix of "May 2022" and "06/2023" invites errors. Pick Month YYYY or MM/YYYY and use it everywhere, including education.

Tip 12: Quantify achievements with numbers

"Reduced onboarding time by 30%" says more than "Improved onboarding process" to every reader, human or software. Use figures you can defend in an interview, and leave a number out rather than invent one.

Tip 13: Include your city and state

Many ATS let recruiters filter candidates by location, so a missing or unreadable location can hide you from searches you qualify for. Put city and state in the contact line as plain text. For remote roles, add "Open to remote."

Tip 14: List certifications with full official names

Recruiters search credentials by name. Use the issuer's official title with the abbreviation in parentheses: Certified Public Accountant (CPA), Registered Nurse (RN), AWS Certified Solutions Architect, Associate. "AWS cert" tells a search nothing.

Tip 15: Use reverse chronological order

Parsers build a work history from positions in order, and recruiters expect the newest role first. Skills-first layouts make both jobs harder. Career changers and candidates with gaps can still lead with a strong summary above a reverse chronological history. Compare layouts in 3 resume formats compared.

Group 4: 2026-Specific Tips

Many current tools use language models, not only exact string matching. Behavior varies by platform and employer setup, so treat these as sound habits, not guarantees.

Tip 16: Show keywords in context, not just in a list

"Managed a team" is weaker than "Managed a team of 8 engineers across 3 time zones to launch a product 6 weeks early." The second gives a matching model, and a reader, something to verify. Context helps wherever matching goes beyond exact strings.

Tip 17: Use related terms alongside exact ones

Semantic matching can connect "agile development" with "scrum," "sprint planning," and "iterative delivery." Use the full vocabulary of your field where it is true, not only the words in one job description. See how to make your resume ATS friendly for building that vocabulary.

Tip 18: A structured skills section helps software categorize you faster

Group skills by type: Technical Skills, Tools, Certifications, Languages. One list that mixes "Excel, team player, HIPAA compliance, results-oriented" is harder to categorize, for software and for people.

Tip 19: Keep your resume and LinkedIn profile consistent

Recruiters often open a LinkedIn profile after reading a resume. Different titles, dates, or employers invite questions. Align your headline and current role with the resume, and use the same positioning in both summaries.

Tip 20: Make your title progression easy to follow

Titles and dates show growth, lateral moves, and gaps to parsers and reviewers alike. If your path includes a lateral move or a gap, say so briefly in the summary or the role line. Unexplained gaps read as open questions.

What No Longer Works in 2026

These tactics were once common advice. They now cost you more than they gain.

Keyword Stuffing

Listing every possible keyword regardless of experience. A skill that no role bullet supports is easy for a recruiter to challenge and reads as padding. Claim only what you can substantiate.

White Text Tricks

Hiding keywords in white or tiny text. Anyone who selects all text or converts the file to plain text sees the hidden content immediately.

Over-Optimized PDF Headers

Stuffing keywords into PDF document properties (Author, Subject, Keywords). The fields a parser fills come from your visible text, so metadata adds nothing you can rely on.

Audit All 20 Tips at Once

Going through 20 tips before every application is impractical. Resume Optimizer Pro parses your resume into the fields shown above, so you can see the record a recruiter would get, and compares it with a job description to give a match score.

It then produces an optimized, ATS-friendly version of your resume, ready to submit. To compare tools that scan resumes before you apply, see our comparison of ATS resume tools.

Optimize My Resume →

Frequently Asked Questions

A resume is ATS friendly when a parser can extract it into clean fields. That means one column, real text instead of images, standard section headings such as Work Experience, Education, and Skills, a consistent date format, and contact details in the body of the file. It also uses the job description's own wording for skills and tools where that wording is accurate. Formatting gets your data read; keywords and quantified results get it noticed.

Neither is better on its own. Greenhouse and Workday's HiredScore documentation list both .docx and .pdf as supported resume file types, and iCIMS lists both among its default text extraction types, with client configurations varying. The file that fails is an image, such as a scan or a screenshot saved as a PDF. If the application portal names a format, use it. Otherwise submit a .docx or a PDF exported from Word or Google Docs, and confirm you can select and copy the text.

A template is fine if it is a single column with live text and standard headings. Avoid templates built with columns, tables, text boxes, icons, or skill bars, which are the elements parsers handle worst. Design tool exports are the usual culprits. Open the template, select all the text, and paste it into a plain text editor. If the order and content survive, the template is safe to use.

They can. Greenhouse's support documentation lists columned layouts, tables, headers and footers, and contact details placed in a header, footer, or text box as causes of partial or unsuccessful parses. Other systems may cope better, but you cannot see which system is reading your file. A single column with contact details in the body removes the risk.

We found no ATS vendor documentation that sets a page limit for parsing, so length is a reader decision rather than a parser rule. One page usually fits early career candidates. Two pages suit longer histories when every line is relevant. Keep the same single column structure and standard headings on every page, and put the most relevant material first.

Update your master resume whenever you change roles, finish a project with a measurable result, or earn a certification. Before each application, tailor the summary, skills line, and first bullets to that job description. A yearly review also catches outdated tools and inconsistent dates. Keep your LinkedIn profile aligned with every change.

Check the URL of the application portal. Workday portals typically show myworkdayjobs.com, Greenhouse shows greenhouse.io, and Lever shows jobs.lever.co. Other systems use their own address patterns. If the address does not say, follow the portal's instructions on file type and use the single column, standard heading format, which works across systems.

There is no universal passing score, and the vendor pages we reviewed publish no threshold, so any single number is a guess. A match score compares your resume with one job description, so use it to find required skills you have but have not shown. Aim for a clean parse, every required skill you genuinely have, and your strongest matching terms in the summary and first bullets.