Resume Mistakes That Get You Auto-Rejected by ATS

You spend two hours tailoring your resume, hit send, and hear nothing. No rejection, no interview — just silence. It is worth being precise about what happened, because the popular version is wrong: there is no robot that reads your resume and rejects it. An Applicant Tracking System (ATS) parses your file into plain text and stores it, and a recruiter then searches that stored text for the words in the posting. (Application forms do sometimes carry knockout questions — work authorisation, licences, years of experience — and those answers can rule you out automatically. Your resume itself is not what gets auto-rejected.) Here are the ten most common resume mistakes that keep candidates out of that search, and exactly what to do instead.

1. Using a Fancy Template With Tables, Text Boxes, or Columns

This is the single most widespread mistake. Resume templates from Canva, Google Slides, or design-heavy Word files often use tables and multi-column layouts to look polished. The problem is that most ATS parsers read left to right, top to bottom — like a typewriter. When your content lives inside a table cell or a floating text box, the ATS either skips it entirely or garbles the output into nonsense.

Concrete example: A marketing manager applies with a two-column Canva resume. Her skills section sits in the right column. The ATS reads the left column straight down, then the right column — producing a jumbled block of text that misattributes her job titles to the wrong employers. Her ten years of experience are now unsearchable, so nobody checks them.

Fix this by using a clean, single-column Word or Google Docs resume with standard section headings. Simple formatting is not a disadvantage — it’s a technical requirement.

2. Saving in the Wrong File Format

Most ATS platforms handle .docx and .pdf files — but not equally, and not perfectly. Some older or budget ATS tools still struggle with PDFs, especially those saved from design software rather than exported from Word. Meanwhile, .pages, .jpg, or .png files are almost universally unreadable by ATS software.

Unless a job posting explicitly requests a PDF, submit a .docx file. If you do use PDF, generate it by exporting directly from Microsoft Word or Google Docs — not from Canva or Illustrator. Those design-tool PDFs embed text as image layers that parsers cannot read.

3. Burying Keywords or Using the Wrong Ones

ATS systems score your resume against the job description by looking for specific keywords. If the posting says “stakeholder management” and your resume says “managing relationships with partners,” many systems will not make that connection — especially simpler keyword-matching tools.

Concrete example: A project manager applies for a role that lists “Agile,” “Scrum,” and “sprint planning” as requirements. His resume mentions “iterative delivery methodology.” He scores zero on those three criteria, despite having done the work for six years.

Mirror the exact language from the job description wherever it honestly reflects your experience. Read the posting carefully, note the specific nouns and phrases used, and incorporate them naturally into your bullet points and skills section.

4. Using Non-Standard Section Headings

ATS software is trained to recognise predictable section labels: Work Experience, Education, Skills, Certifications, Summary. When you get creative — “Where I’ve Made an Impact” or “My Toolkit” — the system often cannot categorise the content that follows. Your five years at a Fortune 500 company might be treated as unstructured text and ignored entirely.

Stick to conventional headings. This isn’t the place to show personality. Your cover letter and interview are. A heading like “Professional Experience” costs you nothing and ensures the ATS parses every bullet point correctly.

5. Incorrect or Missing Contact Information Formatting

ATS systems extract your name, phone number, email, and location at the parsing stage. If this information is placed in the header or footer of a Word document, many parsers will skip it — headers and footers are frequently ignored zones. The same applies to contact details embedded in graphics or icons.

Place your name, city/state (or city/country), phone number, and email address in the main body of the document, at the very top, as plain text. Include your LinkedIn URL as plain text too — not a hyperlinked icon.

6. Common Formatting Mistakes That Quietly Kill Your Score

Beyond the big structural errors, a cluster of smaller formatting choices accumulates into a low ATS parse score:

• Using images or logos: Company logos, headshots, and icons are invisible to ATS parsers. Any text inside an image — including a skills bar or a chart — is simply not read.
• Special characters and symbols: Bullets made from emojis (✔, ★, ➤) often render as garbled characters or break the parsing entirely. Use standard round or square bullets.
• Unusual fonts: Stick to widely available fonts like Arial, Calibri, Garamond, or Times New Roman. Decorative fonts may not render at all and can produce encoding errors.
• Dates in non-standard formats: “Jun ’21 – Mar ’23” confuses many parsers. Use “June 2021 – March 2023” or “06/2021 – 03/2023” instead.
• Missing job titles: Some applicants list only company names and dates without a clear job title on its own line. ATS systems look for job title fields specifically — omitting them means your experience may not be scored correctly.

7. Applying With a Generic Resume for Every Role

This is less about formatting and more about strategy. A generic resume uses generic words, and generic words are not what a recruiter types into the search box for a specific role. Our study of 3,910 real job postings found that two postings for the same job title at different companies share a median of only 25% of their named requirements (11.1% for unrelated postings) — so most of what any one posting asks for is specific to that posting.

Concrete example: A software engineer sends the same resume to a backend Python role and a DevOps position. The Python role scores her resume on Django, REST APIs, and PostgreSQL. Her DevOps application scores on Docker, CI/CD pipelines, and Kubernetes. Her generic resume partially matches both and fully passes neither.

Maintain a master resume with everything you’ve done. For each application, create a tailored version that foregrounds the skills and experience most relevant to that specific job description. It takes fifteen minutes and meaningfully increases your match rate. CareerLift’s free ATS scan can show you your exact keyword gap against a job posting, so you know precisely what to add before you apply.

8. Unexplained Employment Gaps or Vague Dates

ATS systems themselves don’t penalise gaps — but the way candidates handle gaps often creates parsing problems. Leaving date fields blank, using only years without months (“2019 – 2021”) when you actually left a role mid-year, or listing “freelance consulting” with no dates at all can confuse the chronology the ATS is trying to build.

Always include month and year for start and end dates. If you did contract, freelance, or self-employed work during a gap, list it as its own entry with a job title (e.g., “Independent Marketing Consultant”) and real dates. This keeps the timeline parseable and the content honest.

9. Letting the Application Form Contradict Your Resume

This is the mistake most people never find out they made, because it happens in the form rather than the document. Nearly every ATS asks you to confirm or correct the fields it parsed out of your resume, and many add screening questions of their own.

Two things go wrong there. First, autofill errors get accepted without being read. If parsing mangled your most recent employer or dropped an end date, the form now carries that error as fact, and it is the form — not your PDF — that populates the recruiter’s view of you. Take the extra ninety seconds and check every prefilled field, particularly job titles, employers and dates.

Second, knockout questions really are answered by software. Work authorisation, willingness to relocate, required licences, minimum years of experience, salary expectations: these are structured answers with a rule attached, and this is the one place in the process where a genuine automatic rejection exists. Answer them accurately. An answer that contradicts your resume — three years of experience in the form, five implied by your dates — is worse than either answer alone, because it reads as carelessness at best.

Concrete example: A candidate applies through a portal that asks “How many years of Python experience do you have?” and answers 2, thinking of salaried employment only, while her resume shows five years including freelance and university projects. The filter is set at 3. She is removed by the form, and her resume — which was strong — is never searched. Decide what the honest number is, then write the same number in both places.

The fix takes a minute: after submitting, reread the confirmation screen or the emailed copy of your application. If the fields there do not match your resume, the resume is not the version being screened.

10. Never Looking at Your Own Parsed Output

You can check almost everything on this list yourself in under five minutes, and hardly anyone does. Every fix above is a guess until you have seen what your file actually turns into.

The plain-text test. Open your resume, select all, copy, and paste it into a plain text editor — Notepad, TextEdit in plain mode, or any code editor. What you see is roughly what a parser sees. Then check:

• Are your name, phone number and email at the top, in that order, as readable text?
• Are your job titles, employers and dates still attached to the right roles, in the right order?
• Did anything from a two-column layout interleave into nonsense?
• Did bullet characters survive, or did they become question marks and empty boxes?
• Is anything missing entirely — typically a skills bar, an icon, or a header?

If the answer to any of those is bad, no amount of keyword work will help, because your keywords are sitting in text nobody can search. Fix the layout first, then the wording.

The search test. Take the five requirements the posting repeats most and search your plain-text version for each one. Not the concept — the exact phrase. Anything that returns nothing is either a wording gap you can fix honestly or a genuine gap you cannot, and telling those two apart is the whole job.

What Actually Happens After You Hit Submit

Almost every piece of advice about “beating the ATS” makes more sense once you know the sequence your file goes through. There are four stages, and each of the mistakes above breaks a different one.

1. Upload and parse. Your file is converted to plain text and the system tries to identify structured fields: name, email, phone, employers, job titles, dates, education, skills. This is where tables, columns, headers, footers and image-based PDFs do their damage, because the extracted text stops resembling the document you looked at.
2. Store as a candidate record. The parsed text and fields are written into the employer’s database against that requisition. From here on, nobody is reading your PDF — they are reading whatever came out of stage one.
3. Search and filter. A recruiter opens the requisition and searches the stored text, usually with terms lifted straight from the job description, sometimes with saved filters for location, work authorisation or years of experience. This is where a resume that says “iterative delivery methodology” instead of “Agile” simply does not appear in the results.
4. Human shortlist. Whatever the search returned is read by a person, quickly, in a stack. This is the stage everyone imagines is the first one.

The reason “auto-rejected” is a misleading phrase is that no stage above contains a rejection. Stage three contains an absence. Your application is still in the database, correctly stored, and simply never surfaced — which is why the silence feels so total and why nobody ever writes to explain it. It also explains why the fixes are so unglamorous: you are not persuading software, you are making sure the words a person searches for are present in text a machine could read.

One consequence contradicts a lot of advice: there is no single score to optimise. Employers are not ranking you against a threshold you could compute at home. They are running searches, and presence and wording decide whether you appear in one.

The Order to Fix Things In

If you have one resume, one evening, and a stack of applications waiting, the order matters. These fixes are not equally valuable, and doing them in the wrong sequence wastes the effort.

1. Layout first. Single column, no tables, no text boxes, contact details in the body. Nothing else you do matters if the text comes out scrambled. This is one job, done once, that benefits every future application.
2. File format second. A .docx, or a PDF exported from Word or Google Docs rather than from a design tool. Also once.
3. Headings and dates third. Standard section labels, month and year on every role. Still once.
4. Then, and only then, the wording — per application. Mirror the specific posting’s nouns wherever they honestly describe your work. This is the part that has to be redone each time, and it is why people who tailor tend to apply to fewer jobs and hear back more often.
5. Finally, the form. Check the parsed fields and answer the screening questions consistently with the resume you just uploaded.

Steps one to three are why a single afternoon of unglamorous formatting work pays off across an entire search. Step four is why a generic resume underperforms even when it is beautifully formatted: our study of 3,910 real job postings found that two postings for the same job title at different companies share a median of only 25% of their named requirements, so roughly three-quarters of what any one employer asks for is specific to that employer.

One caution about step four, because it is where honest advice and popular advice part company. Mirroring the posting means using its words for work you have actually done. It does not mean adding a certification, a licence or a system you have never touched because the posting asked for one. A missing credential is a fact about that job, not a defect in your resume — and the only thing adding it achieves is converting a lost application into a lost interview.

What to Do Before You Hit Submit

Treat every application as a two-stage process: first optimise for the ATS, then optimise for the human reader. Before submitting, run through this checklist:

1. Is the file a clean .docx or a Word-exported PDF?
2. Is the layout single-column with no tables or text boxes?
3. Does the resume use standard section headings?
4. Is the contact information in the main body, not a header?
5. Have you mirrored the key phrases from this specific job posting?
6. Are all dates in a consistent, parser-friendly format?
7. Are there any images, icons, or emoji bullets that need to be removed?

None of these fixes require design skill or hours of work. They require knowing the rules of the system you’re submitting to — and now you do. A well-optimised resume doesn’t sacrifice readability for humans; it simply removes the invisible technical barriers that were stopping you from reaching them in the first place.

Frequently Asked Questions

Does an ATS actually auto-reject resumes?

Not in the way the phrase suggests. An ATS (Applicant Tracking System) is software employers use to collect, parse, store and rank job applications. It converts your file to plain text; a recruiter then searches and filters that text for the posting’s terms. A resume that parses badly or misses those terms doesn’t come back in the search, so it goes unread — which feels identical to a rejection, but no software read it and turned you down. The one place software does decide is the application form’s knockout questions (work authorisation, licences, years of experience), which are answered separately from your resume.

Do all employers use ATS software?

Most medium and large employers do. Research consistently shows that the majority of companies with more than 50 employees use some form of ATS. Very small businesses and startups that accept emailed applications directly are less likely to use one, but it’s safer to assume ATS screening is in place unless you know otherwise.

Will a simple, plain resume look bad to human recruiters?

Not if it’s well-organised and clearly written. Recruiters spend seconds on an initial scan — they want clarity, not design. A clean single-column resume with strong content, consistent formatting, and clear section labels reads well to both ATS software and human eyes. Design only helps if it doesn’t interfere with parsing.

Is there really no software that rejects my resume?

Not from the resume itself, no. The resume is parsed, stored and searched; one that parses badly or misses the searched terms is never surfaced, which produces silence rather than a rejection. The genuine exception is the application form’s knockout questions — work authorisation, licences, minimum years of experience — which are structured answers with rules attached and can remove an application automatically. That is why answering them accurately, and consistently with your resume, matters as much as the document does.

Should I use a different resume for every application?

Keep one master resume containing everything you have done, and send a tailored version that leads with what each posting asks for. The wording changes; the facts never do. In our study of 3,910 real job postings, two adverts for the same job title at different companies shared a median of only 25% of their named requirements, so tailoring is not cosmetic — most of what each employer wants is specific to that employer.

How do I check my resume without any tools at all?

Paste it into a plain text editor. That is approximately what a parser sees. Check that your contact details, titles, employers and dates survived in the right order and that bullets did not turn into boxes. Then search that text for the five requirements the posting repeats most, using the exact phrases. Whatever returns nothing is your real gap list.

How do I know if my resume is getting lost in an ATS?

The clearest signal is applying to roles you’re well-qualified for and receiving no response at all — not even an automated rejection. You can test your resume by pasting it into a plain text editor; if the content scrambles, loses its order, or shows garbled characters, an ATS will likely have the same problem parsing it.