You can be perfectly qualified and still get filtered out - because of how your resume is built, not what's in it. Outright automatic rejection is rarer than the internet suggests (here's what's usually really happening), but a resume the software misreads or can't match still sinks to the bottom of the pile. Between Applicant Tracking Systems and six-second recruiter skims, small mistakes quietly kill great applications. This is a step-by-step guide to finding and fixing the 11 that do the most damage. Work through them top to bottom before your next application - each one has a quick fix.
1. Complex formatting the ATS can't read
Tables, text boxes, columns, and graphics can scramble how parsing software reads your resume, so your data comes out jumbled or missing. Fix: use a clean single-column layout with standard headings. (See exactly what goes wrong in how to make a resume that passes ATS.)
Instead of a two-column layout, where the parser reads straight across and returns Skills Python Senior Engineer SQL Acme Corp React
Write a single column, where it returns your job title, then your employer, then your skills, in that order
2. Contact info in the header or footer
Some ATS ignore headers and footers - so your phone and email vanish. Fix: put contact details in the main body, up top.
Instead of your name and email in the page header, which several systems skip entirely - the parser returns a resume with no way to contact you
Write them as the first line of the body, directly under your name
3. Submitting an image or scanned PDF
Test it in five seconds: open the file and try to select a line of text. If you can't, neither can the parser. Microsoft's guide to saving as PDF produces a text-based file; "print to PDF" from a scan does not. If you're starting from LinkedIn's save-to-PDF export, that one is text-based and safe to build from.
If the text isn't selectable, the ATS reads nothing. Fix: export a text-based PDF or use .docx.
Instead of a scanned or photographed file, where selecting the text selects nothing and the extracted content is (empty)
Write a PDF exported from the original document, where every line highlights when you drag across it
4. No keywords from the job description
If the posting says "SQL" and "stakeholder management" and your resume doesn't, you rank low when the recruiter searches and get passed over. Fix: mirror the posting's real terms for skills and tools you actually have.
Instead of Worked closely with clients on their requirements
Write Stakeholder management across 12 enterprise accounts - if that is what you did, and the posting asks for it
5. Duties instead of achievements
"Responsible for managing social media" tells a recruiter nothing. Fix: lead with results - "Grew Instagram following 3x and drove 15% of signups."
Instead of Responsible for the regional sales pipeline
Write Grew regional pipeline 30% in 12 months, from $4.1M to $5.3M
Management roles are the worst offenders here, because the duties are so familiar that it feels unnecessary to spell out the results - see the retail store manager example for the same job written both ways.
6. No numbers
Vague claims don't stick. Fix: quantify wherever you honestly can - %, $, time saved, team size, volume.
Instead of Managed a support team
Write Managed a 12-person support team, cutting first-response time from 9 hours to 40 minutes
7. Typos and inconsistent formatting
They signal carelessness and can end a strong application instantly. Fix: proofread, read it aloud, and have someone else check it.
Instead of Jan 2022 – Present on one role and 03/2019-12/2021 on the next
Write the same format on every role, so the parser builds one timeline instead of two
8. Too long (or padded)
Recruiters skim; three pages of fluff buries your best material. Fix: one page for early career, two max for experienced. Cut anything older than ~10–15 years unless it's directly relevant.
Instead of four pages covering every job since 2009, with three lines on a role you left a decade ago
Write two pages, with the oldest roles reduced to a single line each or dropped
9. A generic, one-size-fits-all resume
The same resume for every job matches none of them well. Fix: tailor the summary and top bullets to each posting - here's a step-by-step way to do it.
Instead of one summary sent to forty postings, naming no role and no company
Write a summary that names the role you are applying for in its first line
10. An unprofessional email or unexplained gaps
partyanimal99@ or a mysterious two-year gap raises flags. Fix: use firstname.lastname@, and briefly frame gaps (freelance, caregiving, upskilling) honestly.
Instead of partyanimal_99@… and an unexplained two-year gap
Write firstname.lastname@… and 2023–2024: full-time carer on its own line
11. Missing the basics recruiters scan for
No clear job titles, dates, or a target role up top makes you hard to place in six seconds. Fix: clear titles + dates, and a one-line summary naming the role you want.
Instead of a role with a company name and bullets but no job title and no dates
Write title, employer and date range on every role, in that order, every time
Nine of these eleven are checkable in seconds.
DraftCareer's free ATS checker reads your file and reports what a parser extracted: contact details, sections, dates, keyword overlap with a job you paste in. No account needed.
Run the 11-point check
Before you hit submit, tick off each fix as you confirm it on your resume:
All 11 fixed - you've removed the most common reasons a strong resume gets filtered out.
Your ticks aren't saved - it's a quick pass to run before each application.
The fastest way to stop resume auto-rejection
Most of this list is formatting and relevance - exactly what an ATS-first builder handles for you. DraftCareer's ATS-safe templates are single-column and built to be parser-safe, and on paid plans, pasting a job description helps you catch the keyword and tailoring gaps in mistakes #4 and #9. Whatever tool you use, run this 11-point list before you hit submit - it's the difference between "auto-rejected" and "interview."
