How to Beat Applicant Tracking Systems (ATS): Resume Tips
About 75% of resumes get rejected before a human ever sees them. Here's what the bots actually look for and how to format your resume so it survives the first cut.
Last updated: May 7, 2026 · 8 min read
Quick answer: Use a single-column layout, standard section headings, no tables or graphics, and tailor your keywords to each job description. Save the .docx if the application accepts it. Most ATS rejections come from formatting, not qualifications.
What an ATS actually does
An Applicant Tracking System is the software companies use to manage job applications. Workday, Greenhouse, Lever, Taleo, iCIMS — different vendors, similar core function. When you submit a resume:
- The ATS parses your file and extracts text into structured fields (name, contact, work history, education, skills).
- It scores you against the job description, typically by keyword match.
- It surfaces high-scoring candidates to recruiters and quietly buries everyone else.
The system isn't reading your resume the way a human would. It's looking for patterns. If your formatting confuses the parser, your work history may get filed under "skills" or your name may end up in the "summary" field. Either way, your application looks broken to the recruiter who eventually sees it — if they see it at all.
The formatting rules that actually matter
1. Single column, top to bottom
ATS parsers read in normal reading order. A two-column layout — even a "creative" one with skills in a sidebar — frequently gets parsed wrong. Your name might end up at the bottom. Your skills might get jumbled into your job descriptions. Stick to a single column, full width.
2. Standard section headings
Use boring, standard headings: "Experience," "Education," "Skills," "Certifications." Not "Where I've Made Magic Happen." The ATS specifically looks for those headings to know where each section starts. Cute alternatives confuse it.
3. No tables, columns, text boxes, or graphics
These break parsers. Tables especially — your nicely-formatted skills grid usually comes out the other side as a single line of jumbled words. If your design template uses any of these, switch templates.
4. Standard fonts only
Arial, Calibri, Helvetica, Times New Roman, Georgia. 10-12pt body text, 14-16pt headings. Custom fonts can render as something completely different on the recruiter's machine, or get rejected by the parser entirely.
5. Avoid headers and footers
Putting your name and contact info in a header sounds clean, but many ATS parsers ignore headers and footers entirely. Then your contact info is invisible to the system. Put contact details in the main body of the document.
6. File format: .docx is safest
Modern ATS handles PDF fine in most cases, but legacy systems (and there are still a lot of them in enterprise) can struggle with PDFs that were exported from design tools. Word .docx is the conservative choice. If the application explicitly says PDF, follow that.
Keywords: where the actual scoring happens
The ATS isn't comparing your resume to "good resumes." It's comparing your resume to this specific job description. The system extracts key terms from the posting and looks for them on your resume.
That's why one resume rarely works for every job. The keyword set for "Senior Backend Engineer, Python, AWS" is different from "Senior Backend Engineer, Java, GCP," even though it's the same role. Take the 10-15 minutes per application to customize.
How to extract the right keywords
Read the job description and pull out:
- Hard skills and tools: programming languages, software, frameworks, methodologies.
- Certifications and qualifications: degrees, licenses, training programs.
- Job-specific terms: "agile," "stakeholder management," "P&L responsibility," whatever the posting emphasizes.
- The job title itself: if you can honestly include the title (or a near-equivalent) in your last role's bullet points, do.
Use our Resume Keyword Analyzer to compare your resume against a job description and see what keywords you're missing.
How to use them naturally
Keyword stuffing gets caught by modern ATS and looks bad to recruiters. The honest approach: incorporate keywords into the bullet points where you actually used those skills.
Bad: "Skilled in Python, Java, JavaScript, TypeScript, Go, Rust, C++, Ruby, PHP, Scala."
Better: "Built and maintained a Python/FastAPI backend serving 200k requests/day; rewrote the auth service in Go to reduce p99 latency from 800ms to 60ms."
The second version actually demonstrates the skills. It also reads like something a person wrote, which lands better with the recruiter who reads it after the bot.
The checklist before you submit
- Single-column layout, no tables, no text boxes, no graphics
- Standard headings: Experience, Education, Skills, Certifications
- Contact info in the body, not in a header
- Standard font, 10-12pt body, no fancy ligatures
- File saved as .docx (or PDF if specified)
- Keywords from the job description appearing naturally in your bullet points
- A skills section listing specific tools and technologies
- Plain-text test: paste content into Notepad/TextEdit; verify it reads correctly in order
What about AI-generated resumes?
Asking ChatGPT to write your resume is fine for a starting structure. The output usually needs heavy editing. AI-generated resumes tend to be vague ("collaborated with cross-functional teams to deliver high-impact results"), keyword-stuffed in unnatural ways, and oddly identical to thousands of other applications.
The bullet points that actually win interviews are specific. Numbers, names of systems, scope of impact. "Led migration of 200k user accounts from MongoDB to PostgreSQL with zero downtime" beats "leveraged database optimization strategies to enhance system performance" every single time.
The realistic expectation
Even a perfectly optimized ATS resume doesn't guarantee an interview. ATS optimization gets you past the first filter; the rest depends on actual fit, market conditions, and a non-trivial amount of luck. Optimizing your resume gets it onto a human's screen, which is the entire job of an ATS resume.
Frequently Asked Questions
Do all companies use ATS software?
Almost all medium and large companies do. About 75% of resumes submitted to large companies are screened by ATS before any human sees them. Small companies and startups often don't use ATS, but they typically use LinkedIn or similar platforms that have their own keyword filters.
What's the biggest mistake people make with ATS resumes?
Using a fancy template with columns, tables, or graphics. Most ATS parsers read top to bottom, left to right, and break on multi-column layouts. A "creative" resume can come out the other side looking like word salad. Stick to a single column with clear standard headings.
Should I use the same resume for every job?
No. The single best thing you can do is tailor each resume to the specific job description, mirroring the keywords used in the posting. ATS scoring rewards keyword match. Spend 10-15 minutes per application customizing instead of sending the same resume to 50 jobs.
Do graphics or logos hurt my resume?
Yes. Most ATS systems either strip them entirely (so they were wasted) or fail to parse the layout around them (so your data gets jumbled). Save the graphic design for when you're past the screen — bring a pretty PDF to the interview if you must.
How many keywords should I include?
Most ATS scoring rewards keyword density up to a point and then penalizes obvious stuffing. Aim to naturally cover the 8-15 most relevant skills, tools, and qualifications from the job description. If you can't use a term in a real sentence about your experience, leave it out.
Should I include a skills section?
Yes — it's the cleanest place for ATS keywords. List specific tools, technologies, certifications, and methodologies. Keep it scannable. Avoid soft skills here ("team player", "detail-oriented"); those belong in your bullet points where you can show evidence.
PDF or Word doc?
Word (.docx) is safer for older ATS. Modern ATS handles PDF fine, but a few legacy systems still struggle, especially with PDFs created by design tools. If the application form lists accepted formats, follow it. If not, .docx is the conservative choice.
How do I know if my resume is ATS-friendly?
Copy your resume content and paste it into a plain text editor. If the result is readable and in the right order, an ATS will parse it correctly. If columns are scrambled or sections appear out of order, your formatting is breaking things.
Test your resume
Run your resume against any job description with our free analyzer.