ATS (Applicant Tracking Systems) don't read resumes the way people do. They parse structured data - name, contact, employment history, skills, education - and then score the result against job requirements. A well-designed human-readable resume can fail an ATS parse entirely if it uses the wrong formatting conventions. Here's what to use, what to avoid, and why.
What ATS parsing actually does
When you submit a resume, the ATS runs a parser against the document. The parser tries to identify sections (experience, skills, education), extract entities (company names, job titles, dates, technologies), and map keywords against the job requirements set up by the recruiter.
The output isn't a percentage score - it's a structured record that a recruiter sees when they review your file. If the parser failed to extract your job titles, the recruiter sees a blank. If it merged your skills section with your summary, the keyword match is broken.
Most enterprise ATS platforms - Greenhouse, Lever, Workday, iCIMS - use different parsers. Some are more tolerant of complex formatting; others fail on anything beyond plain text. The safest format is the one that works on all of them.
Why ATS formatting matters more than design
Recruiter perspective
"Over 90% of Fortune 500 companies use applicant tracking systems to filter candidates before a recruiter ever sees the resume. Format failures - tables, columns, text boxes - are invisible to candidates but eliminate applications before any human reviews them."
— SHRM Talent Acquisition Research
Your resume reaches a recruiter's eyes only after passing the parse.
The ATS-safe format: what works
File format: .docx or PDF (text-based)
Both are widely supported. PDF is safer for preserving visual layout but requires that the PDF is text-based, not scanned. Never submit a scanned PDF - parsers can't read image files. .docx is the safest choice when you're uncertain.
Font: standard and readable Calibri, Arial, Garamond, or Georgia. Font size 10–12pt for body, 14–16pt for your name. No custom or decorative fonts - these sometimes fail to extract as text.
Sections with clear headers Label your sections explicitly: "Work Experience," "Skills," "Education," "Certifications." Avoid creative labels like "My Story" or "Where I've Been." The parser looks for known section names. If your experience section is labeled something unexpected, it may not be recognized.
Standard date format
Use May 2022 – Present or 05/2022 – Present. Avoid Spring 2022 or '22 – now. Parsers extract dates to calculate tenure; unusual formats cause parsing errors that make your employment history look shorter than it is.
Bullet points, not paragraphs Structured bullets parse better than prose paragraphs. Each bullet should be one accomplishment or responsibility. Start with a strong verb: "Designed," "Led," "Reduced," "Shipped," "Automated."
Skills section: a flat list List your skills as a comma-separated or line-separated list. Don't rate them with bars, stars, or percentage-fill graphics - those don't extract as text. Don't embed skills only inside job descriptions; list them explicitly in a dedicated section so the parser finds them.
Contact information: plain text, top of page Name, email, phone, LinkedIn URL, and optionally GitHub. Avoid putting contact information inside a header or footer - some parsers don't read header/footer content.
What to avoid
Tables and columns Multi-column layouts look polished in design tools but break most ATS parsers. Text from one column gets merged with another; your job titles appear next to the wrong company names. Single-column format only.
Text boxes and floating elements Text inside shapes, callout boxes, or floating elements is often invisible to parsers. This includes skills listed in a sidebar box - a common design pattern that loses all those keywords.
Graphics, icons, and photos No headshots, no skill bar graphics, no company logos. These add file size and provide nothing the parser can use.
Headers and footers Page numbers are fine if generated by the document. Content in Word-style header/footer zones may not be parsed. Keep your name and contact info in the main body of the first page.
Non-standard bullet characters Use standard round bullets (•) or dashes. Custom emoji bullets, arrows, or decorative characters sometimes fail to parse correctly and render as garbled text.
"Creative" templates from Canva or design tools These produce beautiful PDFs, but most use absolute-positioned text layers that don't extract in reading order. An ATS parser reading a Canva resume often pulls text in the wrong sequence, mixing up different sections.
Tailoring keywords: the part that actually moves your score
An ATS-safe format is the baseline. What determines whether you move forward is keyword matching - how well your resume's language matches the JD's required skills and terminology.
Match the JD's exact phrasing where accurate. If the JD says "event-driven architecture" and your resume says "message queue systems," the parser may not recognize them as equivalent. Where both are accurate descriptions of your experience, use the JD's language.
Don't keyword-stuff. Listing every technology in the JD regardless of experience doesn't work - human reviewers flag it, and modern ATS platforms score keyword context, not just presence. Include skills you can back up with evidence in your work history.
Per-job tailoring matters more than a "perfect" generic resume. A resume tailored to the specific JD's terminology consistently outperforms a generic resume in ATS scoring. This is why tailoring your resume for each job application is the highest-leverage action in an active search.
Hire.monster's AI tailoring generates a per-job resume version for each saved listing, showing which phrases from the JD were incorporated and where. This avoids the manual keyword-matching work while ensuring the output stays grounded in your actual experience.
The ATS format checklist
Before submitting:
- File format is .docx or text-based PDF
- Single-column layout, no tables or text boxes
- Standard font (Calibri, Arial, Garamond), 10–12pt body
- Sections labeled with standard headers (Work Experience, Skills, Education)
- Dates in
Month YYYYorMM/YYYYformat - Skills listed in a dedicated section as text, not graphics
- Contact info in the document body, not in a header/footer
- No graphics, photos, or icon-based skill ratings
- Keywords from the JD's required skills appear in context in your experience
ATS format vs. human-reviewed resume
The ATS version and the human-reviewed version don't have to be different documents - but they have different constraints. ATS format optimizes for parsability. Human reviewers care about:
- Measurable outcomes in bullet points ("reduced p99 latency from 4s to 180ms")
- Evidence of scope and impact ("led a team of 5 engineers")
- Clarity of career progression
A resume that's ATS-safe and also accomplishment-focused serves both audiences. The design trade-off is simplicity - clean single-column layout beats visual complexity for both parsers and recruiters who spend 7 seconds on an initial scan.
For how to present accomplishments effectively in a cover letter alongside your resume, see how to write a cover letter that doesn't read as AI-generated.
How to check if your resume parses correctly
Paste your resume text into a plain text editor. If the output is readable and the sections are in order, the parse will likely work. If text from different sections appears mixed or garbled, the original formatting has extraction problems.
Alternatively: use a tool that shows you what the parser extracted. Hire.monster's resume parser shows you the structured data pulled from your file - skills, job titles, dates, employers - so you can spot parse failures before submitting.
Key takeaways
Single-column, no tables or text boxes - this is the non-negotiable baseline
Multi-column layouts and table-based formatting break parsers reliably across Greenhouse, Lever, and Workday. If you use one rule, it's this one. A plain single-column resume with standard section headers will parse correctly on every major ATS.
Keyword matching in context beats keyword density
Including a skill once in a bullet with evidence ("designed Kafka topology handling 12M daily events") is more effective than listing the same skill five times. ATS platforms and human reviewers both discount keyword lists that aren't anchored to real work.
Tailor per job - a generic resume is a compromised resume
The ATS scores your resume against a specific JD. A resume written for "software engineering roles in general" is underoptimized for every specific role. Per-job tailoring - matching the JD's exact terminology - is the difference between 60% and 90% keyword match on the same underlying experience.
Frequently asked questions
What file format should I use for ATS?
.docx is the safest choice. PDF works if it's text-based (not a scanned image). Avoid design-tool PDFs (Canva, Adobe Illustrator) unless you've verified the text extracts correctly.
Do ATS systems rank candidates by percentage?
Most ATS platforms don't show candidates a score. They show recruiters a structured view of the parsed resume plus keyword match data. Some have AI ranking features, but the recruiter ultimately reviews and decides. Getting parsed correctly is the first hurdle; keyword match is the second.
Should I have separate resumes for each job?
Yes - at minimum, different versions tailored to different role types (backend vs. full-stack vs. infrastructure, for example). Ideally, one per application where the role is competitive. Hire.monster generates per-job versions automatically from your base resume.
Does LinkedIn's resume builder produce ATS-friendly output?
LinkedIn's resume export (PDF) is generally ATS-compatible for basic parsing. It won't be tailored to any specific JD, and it may not include all relevant keywords for a given role. Use it as a starting point, not a final submission.
Can I use a two-column resume?
For design portfolios or roles where visual presentation matters (product design, UX), a two-column format is sometimes expected. For software engineering, backend, data, and most tech roles, single-column is safer and more widely accepted by ATS systems.
Bottom line
- Single-column, no tables, no text boxes, standard fonts, standard section labels
- Skills listed as text in a dedicated section - not as graphics or sidebar boxes
- Dates in consistent format; contact info in the document body
- Match JD terminology in context, not as a keyword list
- Tailor per job - the ATS scores against this specific JD, not the category
Find jobs to tailor your resume for: hire.monster/jobs.