Your resume disappears into a void after you click “submit.” No rejection email, no follow-up, nothing. Just silence. You’re qualified for the role, maybe even overqualified, but you can’t seem to get past the first gate.
Welcome to the world of Applicant Tracking Systems (ATS), where perfectly good candidates get filtered out before any human sees their application. The frustrating part? Most ATS rejections happen for technical reasons that have nothing to do with your actual qualifications.
Your resume might be poorly formatted for machine reading. Or it could be missing keywords that the ATS is programmed to find. Sometimes the system literally can’t parse what you wrote, so it treats empty fields as disqualifications. These are all fixable problems once you understand what’s going wrong.
Let me walk you through the most common reasons ATS software rejects qualified candidates, and more importantly, how to fix each one.
Understanding How ATS Actually Works
Before troubleshooting rejections, it’s helpful to understand what these systems do.
ATS software doesn’t “read” your resume the way a human would. It parses the document, attempting to identify and categorize information into database fields: name, contact info, work experience, education, skills, and so on. Then it searches those fields for criteria set by the recruiter.
When the parsing fails or the search comes up empty, your application gets deprioritized or outright rejected. The system isn’t making sophisticated judgments about your qualifications. It’s running pattern matching and keyword searches on the data it managed to extract.
This creates two main failure modes: the ATS can’t properly parse your resume (technical failure), or it parsed successfully but didn’t find what it was searching for (content failure). Let’s tackle the technical failures first.
Common ATS Systems Used by Employers
Not all ATS platforms are created equal. Each has its own parsing quirks, and knowing which system you’re up against can help you optimize accordingly. Here are the five most widely used platforms.
Workday is used by a huge portion of Fortune 500 companies. It handles PDFs reasonably well but tends to struggle with two-column layouts and tables. If you’re applying to large enterprises, assume Workday is involved.
Greenhouse is popular with tech companies and startups. It generally parses modern document formats reliably, but still prefers clean, single-column resumes. One notable quirk: it pays close attention to skills section formatting.
Lever is also common in the startup and mid-size company space. It imports resumes fairly cleanly but relies heavily on keyword matching. If your language doesn’t mirror the job description, Lever will score you lower even if your experience is a strong fit.
iCIMS is widespread across healthcare, retail, and large enterprises. It has a reputation for strict parsing, meaning unusual formatting causes more problems here than on most other platforms. iCIMS also tends to weight job title matching more heavily than other systems.
Taleo (owned by Oracle) is one of the oldest ATS platforms and is still widely used by large corporations and government contractors. It has notoriously strict formatting requirements. PDFs that aren’t text-based, non-standard fonts, and complex layouts all cause problems in Taleo. If the company is a large, established corporation, there’s a good chance Taleo is involved.
The practical takeaway: you often won’t know which system a company uses. Optimizing for the strictest requirements (clean formatting, standard fonts, single-column layout, mirrored keywords) means your resume works across all of them.
Formatting That Breaks ATS Parsers
Complex Layouts and Multiple Columns
Humans love creative resume layouts with columns, text boxes, and creative spacing. ATS parsers hate them.
When you format your resume in two columns with work experience on the left and education on the right, the ATS often reads left to right, top to bottom. This means it might interpret your content as: job title, degree, job description, coursework, dates, dates. Now your work experience is jumbled with your education, and the parser can’t make sense of either.
The fix: Stick to single-column layouts with clear section headers. Boring? Yes. Effective? Also yes. Save the creative layouts for industries where you’re submitting directly to humans.
Here is what this looks like in practice:
Before > Two-column layout with job titles and companies in the left column, descriptions on the right, dates floating between columns
After > Single-column layout: Job Title, Company Name, dates on one line, followed by bullet point descriptions below
Tables and Text Boxes
Tables seem like a clean way to organize information. The ATS sees them as data structures it needs to understand, and it usually fails.
When you put your work experience in a table with columns for dates, company, and description, the ATS might extract only some cells, miss others entirely, or scramble the order. Text boxes are even worse because some parsers skip them completely, treating the content as irrelevant decorative elements.
The fix: Use simple text formatting with standard punctuation and spacing. If you need to show dates, use tabs or spaces rather than table structures. Everything important should be plain text in the document flow.
Images, Graphics, and Visual Elements
That clean icon next to each section header? The ATS ignores it at best, gets confused by it at worst. Photos, logos, decorative graphics, all of these create parsing problems.
Some ATS attempt to run optical character recognition (OCR) on images, which introduces errors. Others skip images entirely. If you’ve embedded important text in an image (please don’t), that information is effectively invisible.
The fix: Remove all images, icons, graphics, and visual embellishments. Use text-based formatting like bold headers and bullet points. If you must include a logo or photo (some industries expect it), ensure no critical information is embedded in the image.
Headers, Footers, and Margins
Putting your name and contact information in the document header seems logical. You want it on every page if printed, right? The problem: many ATS parsers skip headers and footers entirely, which means your contact information might not get extracted.
The fix: Put your name and contact information at the top of the document body, not in headers or footers. One page is ideal anyway, but if you need multiple pages, your contact info should be in the main content area of the first page.
File Format Issues
Using the Wrong File Type
You submit your beautifully designed PDF, and the ATS chokes on it. Or you send a .docx file, and the system converts it incorrectly, mangling your formatting.
PDF handling varies widely across ATS platforms. Some parse PDFs perfectly. Others struggle with text extraction, especially if the PDF was created from an image or has unusual font embedding. Older ATS may not handle PDFs at all.
Word documents (.doc and .docx) generally parse better, but version compatibility issues occasionally cause problems. Some systems prefer .doc over .docx for legacy reasons.
The fix: When possible, submit Word documents (.docx) for maximum compatibility. If you must use PDF, create it directly from a word processor (not by scanning) and use standard fonts. When the job posting specifies a format, follow that exactly.
Font Problems
That distinctive font that makes your resume stand out? It might not exist on the ATS server. When the parser encounters a font it doesn’t have, text extraction can fail or produce garbled output.
Decorative fonts, script fonts, and uncommon typefaces create the most problems. Even if the text extracts correctly, unusual fonts sometimes cause character recognition errors.
The fix: Use standard fonts that exist on every system: Arial, Calibri, Times New Roman, Georgia, Helvetica. These fonts are designed for readability and compatibility. Font size should be 10-12 points for body text, 14-16 for your name.
Keyword and Content Problems
Missing Job-Specific Keywords
The job description lists “project management” seventeen times. Your resume says “project coordination” and “managed initiatives.” The ATS searches for “project management” as an exact phrase. Result: zero matches.
This is the most common content-based rejection. The ATS is programmed to find specific terms that appear in the job description, and if those exact terms aren’t on your resume, you score poorly in the matching algorithm.
The fix: Mirror the language in the job description. If they say “project management,” you say “project management,” not synonyms that mean the same thing to humans. This isn’t keyword stuffing. It’s speaking the same language. Compare your resume against the job posting and ensure important terms appear where relevant to your experience.
Before > Coordinated cross-functional initiatives and oversaw delivery timelines across multiple teams
After > Led project management across cross-functional teams, ensuring on-time delivery for 12+ concurrent initiatives
Skills Section Doesn’t Match the Search
Many ATS searches focus heavily on the skills section. When the system searches for “Python, SQL, AWS,” it’s often looking specifically in fields it identified as “skills.”
If you mention these technologies scattered throughout your experience section but don’t have a dedicated skills section, the ATS might miss them. Or if your skills section is titled something unusual like “Technical Competencies,” the parser might not recognize it as the skills field.
The fix: Include a clearly labeled “Skills” section with relevant keywords. Use standard section titles: “Skills,” “Technical Skills,” or “Core Competencies.” List specific technologies, methodologies, and tools that match the job description.
Job Titles Don’t Align
You were a “Customer Success Specialist II” but the job description wants “Account Manager” experience. To a human, these roles might be equivalent. To an ATS searching for “Account Manager” as a title, your experience doesn’t match.
Some ATS search job titles specifically, and mismatches lead to lower scores or rejection. This is tricky because you shouldn’t lie about your title, but you need the ATS to recognize relevant experience.
The fix: If your actual title was unusual or company-specific, you can clarify in parentheses: “Customer Success Specialist II (Account Management).” This preserves accuracy while making the connection clear to both ATS and humans. Alternatively, ensure your bullet points use terminology from the job description, even if your title doesn’t match exactly.
Experience Dates in Wrong Format
You list your experience as “Jan 2020 - Present” and the ATS is configured to parse dates as “MM/YYYY.” Now the parser can’t identify your employment dates, which triggers automatic rejection if date ranges are required fields.
Different ATS handle date parsing differently. Some are flexible, others are strict. When dates fail to parse, your experience might show gaps where none exist, or the system might flag you as not meeting minimum experience requirements.
The fix: Use consistent, standard date formats throughout: “January 2020 - Present” or “01/2020 - Present.” Avoid abbreviations that could be ambiguous. Test your resume through ATS scanners to verify dates parse correctly.
Section Naming and Organization
Non-Standard Section Headers
Your resume has sections titled “My Journey,” “What I’ve Built,” and “Where I Learned Stuff.” Creative? Sure. Parseable? Not so much.
ATS parsers look for standard section names to categorize information. When they see “Professional Experience,” “Work History,” or “Employment,” they know this is the work experience section. When they see “My Journey,” they might treat it as miscellaneous text or skip it entirely.
The fix: Use conventional section headers that ATS software recognizes:
- Work Experience (not “My Journey” or “What I’ve Done”)
- Education (not “Academic Background” or “Where I Studied”)
- Skills (not “What I Know” or “Competencies & Expertise”)
- Certifications (not “Credentials” or “Additional Training”)
You can still write compelling content within these sections. The headers just need to be machine-readable.
Section Order Problems
Education appears before experience, then skills, then certifications, then more experience. The ATS parser makes assumptions about section order and gets confused when the structure is non-standard.
Most parsers expect: header information (name, contact), professional summary or objective, work experience, education, skills, and certifications. Deviating from this order occasionally causes parsing errors where information gets misclassified.
The fix: Follow conventional resume structure. For experienced professionals: contact info, summary, work experience, education, skills. For recent graduates or career changers: contact info, summary, education, relevant experience, skills. Keep it predictable.
Acronyms and Abbreviations
Using Only Acronyms or Only Full Terms
The job description mentions “SEO” six times. Your resume says “Search Engine Optimization” every time. The ATS searches for “SEO” as a keyword. No match.
Or the opposite happens: the job description says “Search Engine Optimization,” you say “SEO,” and the search comes up empty. Different companies and recruiters have different conventions, and ATS searches are often literal.
The fix: Use both the acronym and the spelled-out term on first mention: “Search Engine Optimization (SEO).” Then you can use the abbreviated form throughout the rest of your resume. This ensures you match both search styles.
Industry-Specific Jargon Without Context
You worked with “SAP S/4HANA” and assume anyone hiring for this role knows what that means. The recruiter configuring the ATS search isn’t technical and searches for “SAP” and “ERP software” instead. Your specific skill doesn’t match their general search.
The fix: Include both specific and general terms where relevant. “SAP S/4HANA (ERP software)” or “Enterprise Resource Planning (ERP) systems including SAP.” This helps you match both specific and broad searches.
The Contact Information Trap
Email Addresses the System Can’t Parse
Your email is formatted oddly in the resume, or you’ve written it as “name at domain dot com” to avoid spam scrapers. The ATS tries to extract your email address and fails. Now there’s no way to contact you, so the system automatically rejects the application.
The fix: Write your email address in standard format: name@domain.com. No spaces, no spelled-out words, no tricks. Make it impossible to miss, usually right below your name at the top of the resume.
Phone Numbers in Unusual Formats
You write your phone number as “one-two-three-456-7890” or “(123) four five six-7890” trying to avoid robocalls. The ATS can’t parse it as a valid phone number.
The fix: Use a standard format: (123) 456-7890 or 123-456-7890. Include your phone number even if you prefer email contact. Missing or unparseable phone numbers often trigger automatic rejection.
Missing or Buried LinkedIn URL
Many ATS specifically extract LinkedIn URLs for recruiter research. If your LinkedIn isn’t on your resume or is buried in a footer the parser skips, that’s a missed opportunity. Some systems prioritize candidates with LinkedIn profiles.
The fix: Include your LinkedIn URL in your contact information section at the top: linkedin.com/in/yourname. Keep it simple and standard. Make sure your LinkedIn profile is updated and matches your resume content.
Special Characters and Formatting Marks
Fancy Bullets and Symbols
Those elegant bullet points (►, ■, ✓) look polished but sometimes cause character encoding problems. The ATS might render them as random characters, question marks, or simply fail to parse lines that contain them.
The fix: Use standard bullet points: - or even just hyphens. Keep special characters to an absolute minimum. If the character isn’t on a standard keyboard, think twice before including it.
Unusual Punctuation and Symbols
Using “@” to mean “at” in job titles or descriptions, or symbols like “&” instead of “and” can occasionally cause parsing issues, especially in older ATS platforms.
The fix: Spell things out. Use “and” instead of “&”, write “at” instead of “@”. Yes, this feels overly cautious, but ATS compatibility requires caution.
How to Test If Your Resume Passes ATS
Fixing problems is only half the battle. You need to verify the fixes actually worked. Here are three ways to do that before you submit another application.
The copy-paste test is free and revealing. Copy all text from your resume and paste it into a plain text editor (Notepad on Windows, TextEdit on Mac). Does the information appear in the right order? Are sections clearly separated? Can you identify your job titles and dates without confusion? If the plain text version is a mess, ATS parsers will struggle too. This is the fastest sanity check you can run.
ATS scanning tools go deeper. Tools like ResumeRefiner analyze your resume against a specific job description, show you which keywords you’re missing, flag formatting problems that might cause parsing errors, and give you a match score. The key advantage here is that you see the gap between what the ATS is looking for and what your resume currently delivers, before you submit. That’s a much better position than applying and guessing why you didn’t hear back.
The multiple format test helps if you’re unsure whether to submit a PDF or a Word document. Create both versions and test both through a scanning tool. Some ATS give you a preview of what they parsed. If the option is available, check it. Seeing the parsed output directly tells you whether your formatting survived the extraction process.
One more thing: re-run this test every time you update your resume or target a new job. A resume that passed ATS for a marketing manager role might score poorly for a growth manager role, even if the experience is identical. The keyword sets are different.
Quick ATS Checklist
Before submitting any application, run through this list. It covers the most common rejection triggers and takes about five minutes.
Formatting - Single-column layout, no tables or text boxes - Standard fonts only (Arial, Calibri, Times New Roman) - No images, icons, or decorative graphics - Contact information in the document body, not headers/footers - File saved as .docx (unless PDF is specifically requested)
Section headers - “Work Experience” or “Professional Experience” (not creative alternatives) - “Education” (straightforward) - “Skills” or “Technical Skills” - “Certifications” if applicable
Content - Job-specific keywords from the posting appear in your resume - Acronyms written out on first use with abbreviation in parentheses - Skills section clearly labeled and populated with relevant terms - Job titles clarified with parenthetical if your actual title is unusual - Dates in consistent format throughout (Month YYYY or MM/YYYY)
Contact information - Email in standard format (name@domain.com) - Phone number in standard format - LinkedIn URL included at the top
Final check - Copy-paste test completed (plain text reads logically) - Resume scanned against the specific job description - No fancy bullet symbols or unusual special characters
If you can check every box on this list, you’ve eliminated the most common technical reasons for ATS rejection. What remains is a content question: does your experience actually match what they’re looking for?
When ATS Rejection Might Not Be the Problem
Sometimes you fix all the technical issues and still hear nothing. This might not be ATS rejection at all.
Your resume might be getting through the ATS just fine, but you’re not competitive with other candidates who made it through the same filter. The ATS isn’t rejecting you. Human reviewers are, or they’re prioritizing others first.
Or the job posting has been filled, but the company hasn’t closed the listing. Or they’re collecting resumes for future openings. Or the role doesn’t really exist yet and they’re testing the market.
The point: ATS optimization is necessary but not sufficient. It gets you through the initial filter, but you still need compelling content, relevant experience, and sometimes luck with timing. Fix the technical barriers first, then focus on the content that makes you stand out among the applications that do get through.
The Bigger Picture
ATS rejection feels impersonal because it is. These systems process thousands of applications looking for specific patterns and keywords. They’re not evaluating your potential or fit beyond those narrow criteria.
The good news: once you understand what triggers rejection, you can fix most problems. Use standard formatting, mirror job description language, include relevant keywords, and test your resume through scanning tools.
The better news: humans still make final hiring decisions. Getting past the ATS is just step one. The resume that makes it through needs to be compelling enough to convince someone to interview you. So yes, optimize for ATS, but don’t optimize so hard that humans find your resume boring or keyword-stuffed.
Balance technical compatibility with genuine communication about your value. The goal isn’t to trick the ATS. It’s to ensure the system correctly understands what you’re qualified to do. Once it does, your actual qualifications can speak for themselves.
Related Resources
If you want to see exactly how your resume scores against a job description before you submit, ResumeRefiner analyzes your resume against any job posting, flags keyword gaps and formatting problems, and helps you make targeted improvements. No guessing, no silence after clicking submit.