"Your resume was rejected by the ATS" is one of the most repeated pieces of job-search advice, and one of the most misunderstood. Knowing what an applicant tracking system really does helps you fix the right problem instead of chasing myths.
What an ATS actually is
An applicant tracking system is the software a company uses to receive applications, store resumes and move candidates through hiring stages — screening, interview, offer. Popular examples include Workday, Greenhouse, Lever, Zoho Recruit and SAP SuccessFactors. Job portals also store and index your resume in a similar way.
When you apply, the system parses your resume: it extracts text and tries to fill fields such as name, contact details, education, job titles, dates and skills. Recruiters then work with that parsed data.
How screening really happens
- Knock-out questions: some applications ask about location, notice period, degree or work authorisation. Answers that don't match can remove an application automatically.
- Keyword search and filters: recruiters search the candidate pool for skills and titles ('React', 'SQL', 'Java developer') and filter by location or experience.
- Ranking or matching scores: some systems score how closely a resume matches the job description. These scores influence who a recruiter looks at first.
- Human review: a recruiter skims the shortlisted resumes, often for well under a minute each, and decides who to call.
The ATS rarely 'rejects' you on its own. More often your resume simply never shows up in the recruiter's search — because the text didn't parse, or because the words they searched for aren't on it.
Why some resumes parse badly
| Problem | What happens | Fix |
|---|---|---|
| Two or three columns | Text from columns gets mixed together or read in the wrong order | Use a single column |
| Text inside images, icons or graphics | The text isn't read at all | Keep all information as plain text |
| Contact details in the header/footer | Some parsers skip headers and footers | Put name, phone and email in the main body |
| Creative section names ('My Journey') | The parser can't map the section | Use standard headings: Experience, Projects, Education, Skills |
| Skill bars and star ratings | Shows nothing useful; the skill name may be lost | List skills as words, grouped by type |
| Unusual date formats | Experience length is calculated wrongly | Use 'Jun 2025 – Present' consistently |
Keywords: the part most people get wrong
Recruiters search for the words used in the job description. If a role asks for 'Power BI' and your resume says 'data visualisation tools', a search for Power BI won't find you.
- Use the exact name of each tool or skill you genuinely have, as the job description writes it ('JavaScript', not 'JS' alone).
- Include both the acronym and the full term once where it's common: 'Amazon Web Services (AWS)'.
- Put the most important skills in two places: the skills section and inside a project or experience bullet that shows you used them.
- Don't paste keywords you can't back up. A human reads the resume next, and the interview will test it.
Not sure if your resume is being read correctly? We review it against your target role.
See resume optimizationFile format: PDF or Word?
A text-based PDF (exported from Word or Google Docs, not scanned) is read well by most modern systems and keeps your formatting. If an employer specifically asks for .docx, send .docx. Test your PDF by selecting and copying all the text into a plain-text editor: if it comes out in the right order, a parser will usually read it too.
ATS-friendly resume checklist
- Single column, standard fonts, no tables for layout.
- Name, phone, email, city and LinkedIn in the body, at the top.
- Standard section headings.
- Skills written as the job description writes them.
- Every project or job shows tools used and a result.
- Consistent date format; no photos, graphics or skill bars.
- Saved as a text-based PDF with a clear file name, such as Firstname-Lastname-Resume.pdf.