You spent days on your resume. You sent it to around 50 roles through Naukri, LinkedIn and company career pages. Weeks later, you have a few auto-generated rejection emails and a lot of silence.
It is tempting to believe a "robot" read your resume and threw it away. The reality is more specific, and more useful to understand. An Applicant Tracking System (ATS) is mostly a database and a search tool for recruiters. It rarely "reads and rejects" a resume on its own. What it does is decide how your resume is stored, whether a recruiter's search finds it, and where it appears in the list. If any of those steps goes wrong, a human may simply never open your file.
This guide explains each step in plain terms, shows what goes wrong for Indian freshers, and gives you fixes you can apply today.
What an ATS actually is
When a company such as a large IT services firm or a growing startup posts a role, it can receive hundreds or thousands of applications. Recruiters cannot open each PDF by hand. So companies use software such as Workday, Taleo, SuccessFactors, Greenhouse, Lever, Zoho Recruit or Darwinbox (common in Indian companies) to collect applications in one place.
Most ATS tools do four jobs:
- Collect every application against a job opening.
- Parse each resume, which means pulling the text out and splitting it into fields like name, phone, email, education, skills and experience.
- Let recruiters search and filter that database using keywords and criteria.
- Track each candidate through stages such as Applied, Screened, Interview, Offer.
Let us look at the steps that affect you the most.
Step 1: Parsing - turning your file into data
Parsing is where most hidden damage happens. The ATS does not "see" your resume the way you do. It extracts text in reading order and tries to guess which text belongs to which field.
Before and after: a parsing example
Here is a fresher resume built in a fancy two-column template with a skills table and contact details in the page header.
What you see: a neat page with your name at the top, a left sidebar listing skills, and a right column with projects.
What a parser may extract:
Name: (blank)
Email: (blank)
Skills: Java Python React Library Management System Built a desktop
Education: B.E. Computer 2026 SQL Git Engineering Pune University 8.1
Experience: (blank)
The contact details were inside the header, which some parsers skip. The two columns were read line by line across the page, so skills got mixed into the project and education text. A recruiter who searches for "React" may still find you, but your profile looks broken, and a search filtered by degree or graduation year may miss you.
The same content in a simple one-column layout:
Name: Priya Kulkarni
Email: priya.kulkarni@gmail.com | Phone: +91 98xxxxxx10
Education: B.E. Computer Engineering, Savitribai Phule Pune University, 2026, CGPA 8.1
Skills: Java, Python, React, SQL, Git
Projects: Library Management System - Built a desktop app in Java and MySQL...
Same person, same skills. The second version is simply readable.
File and layout problems that commonly break parsing
- Scanned PDFs or resumes saved as images. If you can't select the text with your cursor, the ATS can't read it either. Always export from Word or Google Docs as a text-based PDF.
- Tables and text boxes. Content inside them is often skipped or read out of order.
- Two or three columns. Text can get merged across columns, as in the example above.
- Headers and footers. Many parsers ignore them, so never put your name, phone or email only there.
- Icons instead of words. A phone icon next to a number is fine, but a skill shown only as a logo or a star rating cannot be read. "React - 4/5 stars" becomes "React" at best.
- Unusual fonts or heavy graphics. Stick to Arial, Calibri, or similar standard fonts.
Some ATS tools handle these formats better than others, and you rarely know which one a company uses. A plain one-column layout is the safe choice everywhere.
Step 2: Knockout questions - the main source of auto-rejection
When people say "the ATS rejected me automatically", it is usually because of screening (knockout) questions, not resume keywords. These are the questions you answer in the application form, for example:
- What is your notice period? (Some roles only accept immediate joiners or up to 30 days.)
- Do you have a minimum of 60% or 6.5 CGPA throughout 10th, 12th and graduation?
- Do you have any active backlogs?
- Are you willing to relocate to Chennai / work from office in Hyderabad?
- What is your year of graduation? (Many fresher drives are open only to specific batches.)
- Do you need visa sponsorship?
Recruiters can set the system to reject or move aside candidates whose answers don't meet a fixed rule. That rejection can arrive within minutes, which is why it feels automatic.
What to do: read the eligibility criteria before applying, answer every screening question honestly, and don't waste applications on roles where you clearly fail a hard rule like the batch year or CGPA cutoff. Lying here is risky, because marks, backlogs and graduation year are checked against your documents at the offer or background-verification stage.
Step 3: Recruiter search and ranking
Once your resume is parsed and you pass the screening questions, you sit in a pool with other applicants. Now the recruiter works with that pool:
- Keyword search. A recruiter hiring a Java developer may search for "Java AND Spring Boot AND SQL". If those words are not in your parsed text, your profile does not appear in the results, even if you know the tools.
- Filters. Location, graduation year, degree, experience range and expected CTC are common filters.
- Ranking or match scores. Many newer systems compare your resume with the job description and show a match percentage. Recruiters often start from the top of that list. A low score does not delete you, but if 800 people applied, the recruiter may never scroll down to you.
This is why "the resume was set aside" is more accurate than "the resume was rejected". Nobody pressed a reject button. Your profile just did not surface.
How to make your resume ATS-friendly
Use standard section headings
Parsers look for familiar section names to split your resume into fields. Use headings such as:
- Education
- Technical Skills (or Skills, or Core Competencies)
- Projects
- Internships / Work Experience
- Certifications
- Achievements
Avoid creative headings like "My Journey" or "Where I've Been", because the parser may not know what to do with them. "Core Competencies" is a widely recognised heading and works fine.
Mirror the job description's wording
Read the job post and list the skills it mentions. If you genuinely have them, use the same words. If the post says "RESTful APIs", write "RESTful APIs" rather than only "web services". For abbreviations, include both forms once, for example "Search Engine Optimization (SEO)" or "Continuous Integration / Continuous Deployment (CI/CD)".
Put skills both in your skills list and inside project bullets. A keyword used in context ("Built REST APIs in Spring Boot for a college event portal") is more convincing to the recruiter who reads it later.
Write bullets with action verbs and results
Start each bullet with a verb (Built, Designed, Automated, Reduced, Led) and add a measurable outcome where you honestly have one.
- Weak: "Responsible for college fest website."
- Better: "Built the college fest registration site in React and Firebase; handled around 1,200 registrations over three days."
Keep the file simple
- One column, standard fonts, 10-12 pt text.
- No photo, tables, text boxes, or skill bars.
- Name and contact details in the main body, at the top.
- Save as a text-based PDF unless the portal asks for .docx.
- File name like
Priya_Kulkarni_Resume.pdf.
Check before you apply. Paste your resume text and the job description into JobYaar's free ATS Resume Checker. It gives an approximate match score, lists missing keywords, and checks for standard section headings, action verbs and measurable results. It runs in your browser, and the score is a guide rather than a copy of any employer's system, so still follow the formatting rules above.
Common myths about ATS
"You need a 100% match score." No. Scores are a guide for recruiters, not a pass mark. Aim for a resume that clearly covers the role's main skills.
"White-text keyword tricks fool the system." Hidden text often appears in the parsed output, and a recruiter who sees a block of random keywords will lose trust quickly. Avoid it.
"Small companies don't use ATS." Many do, through job portals and low-cost tools. Even when a person reads your resume directly, the same clean format helps them too.
"Once rejected, always rejected." Your profile often stays in the database. Recruiters search it again for future openings, which is another reason to keep it parsing correctly.
Quick checklist
- Text in the PDF is selectable.
- One column, no tables, text boxes or images.
- Contact details are in the body, not the header.
- Standard section headings.
- Job-description keywords you genuinely have are included, in context.
- Screening questions answered honestly; eligibility (batch, CGPA, backlogs, location) checked first.
Getting past an ATS is not about tricking software. It is about making sure your real skills are readable and searchable, so a recruiter actually gets to see them.