What is ATS? Why 75% of Resumes Get Rejected Before a Human Reads Them

An Applicant Tracking System (ATS) is software that companies use to collect, store, and filter job applications before a recruiter ever opens a single resume. When you apply on Naukri, LinkedIn, or a company careers portal, your resume almost certainly passes through an ATS first. Think of it as an automated gatekeeper that decides which applications are worth a human's time.

Companies adopted ATS because hiring at scale is genuinely impossible to manage manually. A mid-sized Indian IT company receiving 5,000 applications for 50 open roles cannot have recruiters read every submission. The ATS shortlists the top candidates by matching resume content against the job's requirements, passing only the highest-scoring profiles to the recruiter's queue.

The ATS does not read your resume the way a human does — it parses it. It scans for recognisable section labels like 'Experience', 'Education', and 'Skills', then extracts the text within each section and indexes it. Keywords from your resume are compared against keywords in the job description, and a relevance score is calculated.

Most modern ATS platforms go beyond exact keyword matching. They also look at context — whether a skill appears in a relevant section, how recently it was used, and whether quantified results accompany it. However, the matching still relies heavily on your resume being cleanly parsed, which means anything that disrupts text extraction — tables, columns, graphics — directly hurts your score.

India has one of the world's most competitive job markets by volume. A single software engineer opening at an MNC like Infosys or Cognizant can attract thousands of applications within 48 hours of posting. Recruiters managing 20–30 open positions simultaneously simply cannot manually review every resume — so ATS shortlisting decides the fate of the majority of candidates.

Research consistently shows that around 75% of resumes are filtered out by ATS before reaching a recruiter. In India, this number is likely higher given the sheer application volume. Many rejections have nothing to do with the candidate's actual qualifications — they happen because the resume was not structured in a way the ATS could parse and score correctly.

Tables and multi-column layouts are one of the biggest culprits. When an ATS tries to parse a two-column resume, it often reads both columns horizontally — mixing job titles with dates from the wrong column and creating garbled, unscorable output. Decorative headers and footers with contact information can be completely ignored because some parsers skip those zones.

Creative fonts, icons, and embedded graphics cause similar problems. An ATS does not render your resume visually — it extracts raw text. A skill displayed as an icon with a label next to it may be read as a random symbol rather than a skill name. Fancy resume templates downloaded from Canva or Pinterest are frequently ATS nightmares dressed up as attractive design.

Using non-standard section headings is another common mistake. Labelling your work history 'My Journey' or your skills section 'What I Bring to the Table' confuses the parser. The ATS expects 'Work Experience', 'Skills', 'Education' — deviating from these conventions means your content may not be correctly categorised and scored.

Start with a single-column layout using a clean, standard font like Calibri or Arial at 10–12pt. Use clearly labelled section headings that match what ATS systems expect. Submit as a PDF unless the job posting explicitly asks for DOCX — a well-structured PDF preserves formatting while remaining parseable.

Mirror the language used in the job description. If the JD says 'RESTful APIs', use that exact phrase rather than 'REST services' or 'API development'. Read the requirements section carefully and ensure the skills and tools listed there appear somewhere in your resume — in context, not as a dumped list at the bottom.

Finally, quantify your impact wherever possible. ATS systems give higher relevance scores to resumes that include numbers, percentages, and outcomes alongside skills. 'Reduced API response time by 40%' ranks higher than 'worked on API optimisation' because it signals real-world application of the skill, not just familiarity with the term.