How to Write an ATS-Friendly Resume

Many employers use an applicant tracking system (ATS) to collect, parse, and search the resumes they receive. When a resume is hard for that software to read, parts of your experience can be missed or misplaced before a person ever sees it. This guide walks through how to build a resume that stays readable for both the software and the human reviewers who come after it.

What an ATS actually does

An ATS is software that stores submitted resumes, extracts text from them, and lets recruiters search and filter that database by keyword, job title, or other fields. Some systems also score resumes against a job description, but the scoring rules vary between vendors and are not public. What is consistent is the first step: the software has to parse your text accurately before anything else can happen.

It helps to remember that ATS is a category, not a single product. Workday, Greenhouse, Lever, iCIMS, Taleo, and SmartRecruiters all parse resumes differently. A layout that one system reads perfectly may stumble in another. The goal is not to optimise for one specific tool but to write and format your resume so that the widest range of systems can read it without guesswork.

Start from a clean, single-column layout

Parsing software extracts text in a linear order, and anything that breaks that flow risks being misread. Greenhouse, for example, lists tables, headers and footers, columned layouts, and graphics or photos among the formatting issues that can cause an unsuccessful resume parse. The University of Pennsylvania Career Services similarly notes that not all applicant tracking systems can read decorative formatting like tables, shapes, graphics, and images.

• Use a single column of text with clear section headings.
• Avoid headers and footers for important information — Greenhouse flags contact details placed in a header, footer, or text box as a common parse problem.
• Avoid text inside images, icons, or logos; the parser cannot read it.
• Use standard bullet characters rather than custom symbols.
• Keep fonts simple and avoid overlapping text boxes.

A clean layout does not have to look plain. You can still use generous spacing, a readable typeface, and a clear hierarchy. The CareerPilotAI ATS resume template is built as a single-column, text-based layout designed to parse cleanly.

Use standard, recognisable section headings

Parsers look for familiar headings to slot your content into the right fields. Headings like Work Experience, Education, Skills, and Certifications are widely recognised — the University of Pennsylvania Career Services uses sections such as Education, Work Experience, and Skills in its own resume guidance. Creative labels such as "My Journey" or "Where I Have Been" may look distinctive but often confuse parsing.

• Work Experience or Professional Experience for roles.
• Education for degrees and schools.
• Skills or Technical Skills for a skills block.
• Certifications or Licenses for credentials.
• Projects for relevant side or academic projects.

Match the language in the job description

Recruiters search resume databases using the words that appear in the job posting. If your resume uses different wording for the same skill, it may not surface in that search. Mirroring the language of the posting — without inventing skills you do not have — makes your experience easier to find.

• Mirror the exact skills and job titles used in the posting where they genuinely apply to you.
• Spell out acronyms once, e.g. "Search Engine Optimization (SEO)", then use either form.
• Place your most relevant keywords in the professional summary and a dedicated skills section near the top.
• Weave keywords into real experience bullets rather than listing them in a block the parser may ignore.

A note of caution: do not stuff keywords you cannot back up. If a keyword search surfaces your resume but an interviewer asks about a skill you listed loosely, that hurts you more than the keyword helped. To see how your current resume compares to a target posting, paste both into the CareerPilotAI Resume Keyword Checker.

A before-and-after example

Consider a data analyst applying to a role that asks for "SQL, dashboarding, and stakeholder reporting." Here is a weak version of a bullet:

Before: "Did data work and made reports for the team."

This tells the parser and the recruiter almost nothing. There is no skill keyword, no scope, and no outcome. A stronger version names the tools and the result:

After: "Built SQL queries and Tableau dashboards for the operations team, cutting a weekly reporting cycle from two days to four hours."

The after version contains the keywords from the posting (SQL, dashboards, reporting), a concrete scope (operations team), and a measurable outcome. It reads well for a human and parses cleanly for the software.

Choose the right file format and name

Export your resume as a .docx or a text-based PDF. Greenhouse, for example, accepts .doc, .docx, .pdf, .rtf, and .txt as candidate uploads, and the University of Pennsylvania Career Services recommends converting your resume to PDF before sending it. A text-based PDF is one exported from a word processor, where the text is selectable; a scanned image of a paper resume is not. Greenhouse specifically lists resumes uploaded as an image rather than a document as a cause of unsuccessful parsing. When a posting asks for a specific format, use exactly that.

• Name the file with your name and target role, e.g. jane-smith-data-analyst.pdf — Penn Career Services suggests labelling the file with your name.
• Avoid generic names like resume.pdf or final-resume-v3.docx that get lost in a crowded downloads folder.
• Keep the file size modest; Greenhouse cannot parse resumes larger than 2.5 MB.
• Keep one master document and save tailored copies per application.

An ATS-friendly resume checklist

Run your resume through this list before each application:

• Single-column layout with no tables, text boxes, or sidebars containing key information.
• Standard section headings: Work Experience, Education, Skills, Certifications.
• No critical details in the header or footer.
• No text inside images, icons, or logos.
• Keywords from the job posting appear naturally in your summary, skills, and bullets.
• Acronyms spelled out once.
• Saved as .docx or text-based PDF with a clear file name.
• Contact details (name, email, phone, location, LinkedIn) are plain text at the top.

Trade-offs and limitations

A resume optimised for parsing is not always the most visually striking document, and that is the point. A heavily designed two-column resume with icons and charts may look impressive to a human but can lose content in parsing. When you apply through an online portal, prioritise parseability; when you hand a resume directly to a recruiter at an event or by email, you have more design freedom because no parser is involved.

Also remember that no resume is guaranteed to pass every ATS. Parsing accuracy varies, and some systems struggle even with clean documents. The aim is to remove avoidable obstacles, not to chase a perfect score. You can get a quick read on common formatting issues with the CareerPilotAI Resume Formatting Checker, and a broader self-audit with the Resume Checklist tool.

Check your resume before you apply

Once your resume is clean and tailored, do a final pass. The free ATS Resume Checker gives you an instant read on how a typical parser might handle your formatting and keywords, and the Resume Keyword Checker shows how well your resume lines up with a specific job description. Both are quick ways to catch avoidable problems before you submit.

Sources and update notes

The before-and-after example and checklist in this article are educational and do not guarantee that any particular employer or applicant tracking system will parse your resume correctly or invite you to interview. Parsing behaviour varies between vendors and over time. Last updated September 1, 2026: added university and vendor sources and clarified ATS limitations.

• University of Pennsylvania Career Services — Write a Resume/CV
• Greenhouse — Supported formats for resumes and candidate uploads
• Greenhouse — Unsuccessful resume parse