How do you write a resume that gets past applicant tracking systems? You format it simply, match your language to the job description’s keywords, and avoid design elements that confuse the software parsing your document. An applicant tracking system, or ATS, is software that employers use to collect, sort, and filter job applications before a human ever reads them. Understanding how these systems read a resume — and what makes them misread one — is the key to making sure yours reaches a hiring manager at all.
What an Applicant Tracking System Actually Does
An ATS is a piece of recruiting software that stores every resume submitted for a job posting in a searchable database. Recruiters use it to filter large volumes of applicants down to a manageable shortlist. It does this in a few ways:
- Parsing: the system extracts text from your resume file and sorts it into fields such as name, contact information, work history, education, and skills.
- Keyword matching: the system compares the words in your resume against the words in the job posting, or against keywords a recruiter has manually entered.
- Ranking: based on keyword matches and sometimes other criteria, the system assigns your application a score or rank relative to other candidates.
The critical point is that the ATS does not “understand” your resume the way a person would. It reads text, and it reads it best when that text is organized in predictable, standard ways. If the software cannot correctly extract your job titles, dates, or skills because of formatting problems, a qualified candidate can be filtered out before a recruiter ever sees the application — not because of a lack of qualifications, but because of a parsing failure.
Formatting Dos and Don’ts
Do Use a Simple, Linear Layout
Structure your resume in a single column that reads from top to bottom: contact information, then a summary, then work experience, then education, then skills. This mirrors how parsing software is built to scan a document, and it also reads cleanly for a human reviewer later.
Don’t Use Tables, Text Boxes, or Columns
Multi-column layouts, tables, and text boxes are common in visually designed resume templates, but many ATS platforms parse them incorrectly. The software may read across columns instead of down them, scrambling your work history into nonsense, or it may skip text placed inside a text box entirely. If a template looks impressive in a design program, be suspicious of how it will perform once converted to plain text.
Do Use Standard Section Headings
Label your sections with conventional names: “Work Experience,” “Education,” “Skills,” “Certifications.” An ATS is often programmed to look for these specific terms to know where to file information. A creative heading like “Where I’ve Made an Impact” instead of “Work Experience” may not be recognized, meaning the system fails to associate your job history with the correct field.
Don’t Rely on Headers, Footers, or Images
Some parsing systems skip the header and footer sections of a document entirely, which means contact information placed there — a common design choice — may never be read. Avoid putting your name, phone number, or email inside a header or footer. Similarly, avoid logos, icons, and graphics used to represent skills or contact details, such as a small phone icon next to your number; the system reads text, not images, so information conveyed only visually is invisible to it.
Do Choose a Compatible File Format
Save your resume as a .docx or a standard PDF unless the job posting specifies otherwise. Word documents are generally parsed reliably. Most modern ATS platforms also handle PDFs well, but PDFs created by exporting a heavily designed file, or PDFs that are actually scanned images of a resume rather than text, can fail to parse at all. If you use a PDF, confirm the text within it is selectable — if you can highlight and copy the words with your cursor, the text is real and parsable, not an image.
Don’t Use Unusual Fonts or Special Characters
Stick to standard fonts such as Arial, Calibri, or Times New Roman. Decorative fonts can render as garbled characters when converted to plain text. Likewise, avoid using symbols in place of bullet points, or special characters like em dashes or bullet glyphs that some older parsing systems misread as strange characters or line breaks.
Keyword Strategy
Mirror the Job Description’s Language
The most effective way to beat applicant tracking systems on keyword matching is to closely read the job posting and reuse its specific terms. If the posting asks for “project management” experience, use that exact phrase rather than a synonym like “managing projects.” If it lists a specific tool, such as “Salesforce” or “Python,” and you have that experience, name it explicitly rather than describing it generically. ATS keyword matching is often literal, so close paraphrasing can cause a real match to be missed.
Include Both Spelled-Out Terms and Acronyms
Job postings and resumes often use industry terms inconsistently — some write “Search Engine Optimization,” others write “SEO.” Because you cannot know which version the system or recruiter has searched for, include both the first time you use the term: “Search Engine Optimization (SEO).” After that, either version is fine.
Build a Skills Section
A dedicated skills section, listed clearly near the top or bottom of the resume, gives you a direct place to include relevant keywords without forcing them awkwardly into sentences about your job duties. List specific software, certifications, methodologies, and technical abilities that appear in the job description and that you genuinely possess.
Don’t Keyword-Stuff
Adding a long list of every keyword you can find, including ones unrelated to your real experience, does not help. Some systems flag unusually dense or repetitive keyword use, and a human recruiter reviewing your resume after it passes the initial screen will notice terms that don’t connect to any actual experience described elsewhere. The goal is accurate, natural matching — not volume.
Tailor Each Application
A single generic resume sent to every job posting will match fewer keywords, on average, than a resume adjusted for each specific role. This does not mean rewriting the document from scratch each time. It means reviewing the job posting, identifying its key terms and requirements, and adjusting your summary, skills section, and bullet points to reflect the language used, provided it accurately reflects your background.
Writing for the Human Reader Too
An ATS is a filter, not the final decision-maker. If your resume passes the automated screening, a person will eventually read it. This means formatting for software compatibility should not come at the expense of clarity and impact. Use concrete accomplishments, quantify results where you can, and keep bullet points concise. A resume that is simple enough for an ATS to parse correctly is also, generally, one that is easy and quick for a busy recruiter to read.
Conclusion
Writing a resume that gets past applicant tracking systems comes down to two combined habits: formatting the document in a simple, standard way that software can parse accurately, and using language that closely matches the specific job posting so the system recognizes your qualifications as relevant. Neither habit requires sacrificing a clear, well-written resume — in fact, the practices that satisfy an ATS are largely the same ones that make a resume easier for a human reader to follow once it reaches their desk.