How to Pass ATS: What Actually Gets Indian Job Seekers Shortlisted

If you're wondering how to pass ATS screening, here's the direct answer: get your resume parsed correctly by the system, then get it to rank high enough against a job description or recruiter search to reach a human. Applicant Tracking Systems like Workday, Oracle Taleo, and the recruiter tools built into Naukri don't reject resumes because they look boring. They convert your resume into structured data — name, phone, email, skills, education, experience — and then rank that data against a job posting or a recruiter's keyword search. If parsing breaks, you vanish from the results with no rejection email at all. If your resume never uses the words the job description uses, you rank low even when you're qualified. This guide breaks down exactly where resumes fail and what actually works for Indian campus and off-campus applications, without the recycled "75% of resumes get auto-rejected" myth that gets repeated everywhere.

What "Passing the ATS" Actually Means

Most Applicant Tracking Systems don't work like a single gate you either pass or fail. They work in three stages: parsing (turning your PDF or Word file into structured fields), matching (comparing those fields against a job description or a recruiter's search terms), and ranking (sorting every applicant against each other, not against an absolute pass mark). There is no fixed number that means "passed." A resume that ranks in the top 10% for one job description can rank in the bottom half for a nearly identical one, because the wording of the two postings is different.

This matters because it changes what you're optimising for. You're not trying to satisfy a checklist once. You're trying to make sure the system can read your resume cleanly and that your resume's language overlaps with each specific job description you apply to. For a deeper look at how "score" tools represent this, see what a good ATS score actually means.

It also helps to drop a popular but unverified claim you'll see repeated everywhere: that "75% of resumes are auto-rejected by ATS before a human sees them." That number has been traced back to marketing material rather than a published, methodologically sound study, and no major ATS vendor publishes a figure like it. What is documented, from Jobscan's own research, is that the vast majority of recruiters use some form of filtering — which is a real and useful fact on its own, without needing an inflated rejection statistic to make the point.

How the Systems Indian Recruiters Actually Use Work

Naukri's recruiter search (RESDEX) and FastForward

Naukri doesn't score your resume when you apply — recruiters search its resume database (called RESDEX) using keyword combinations: skill names, designations, years of experience, and location. Naukri's own recruiter guide describes this as keyword-based filtering across millions of profiles, which is why the exact words in your headline and skills section matter more than how creatively you describe your role. Naukri FastForward, the platform's paid resume-writing and profile-boosting service, exists specifically because Naukri itself acknowledges that "profile visibility to recruiters" depends on how your text is structured, not just what you've done.

Workday's structured fields

Workday, used by a large share of large Indian and MNC employers for campus and lateral hiring, parses your resume directly into applicant profile fields the moment you upload it during an online application. If your degree, employer name, or skill doesn't land in the right field, a recruiter filtering candidates by that field simply won't see you — even if the information is sitting right there on your resume, just formatted in a way the parser skipped.

Oracle Taleo's stricter parsing

Taleo is older than Workday and is known among recruiters and ATS vendors as one of the stricter parsers still in active use, particularly at large legacy IT services and BPO employers in India. It tends to struggle with multi-column layouts, text boxes, and tables far more than newer systems — which is a big reason "keep it simple" formatting advice, covered in detail in our ATS resume format guide, still holds up in 2026.

Why Applying Through TPO Feels Different from Off-Campus

If you're going through your college's Training and Placement Officer, a company often reviews a smaller, pre-filtered batch of resumes for that specific drive, so raw keyword matching against an ATS matters less — the company already knows who's eligible by branch, CGPA, and backlog rules before resumes even arrive. Off-campus applications are the opposite: you're one of thousands of unknown applicants hitting a public posting on Naukri, LinkedIn, or a company careers page that runs on Workday or Taleo, with no pre-filtering by a TPO in your favour. That's exactly where parsing and keyword matching decide whether a human ever opens your file, which is why the guidance in this piece matters far more for off-campus drives and referrals than for your final-semester campus placement season.

The Formatting Rules That Actually Matter

Most formatting mistakes don't get your resume "rejected" in a dramatic sense. They just cause specific fields to come through blank or garbled, which quietly drops your rank. A recruiter filtering for "3 years experience" or "B.Tech Computer Science" will never see you if that specific field parsed empty, no matter how good the actual content of your resume is.

Element	Safe for parsing	Why
Single column, standard headings	Yes	Parser reads top to bottom, left to right, mapping headings to known fields
Two/three-column layout or sidebar	Risky	Older parsers (Taleo, some Workday instances) read across columns and merge unrelated text
Tables for skills or dates	Risky	Table cells can be read out of order or skipped entirely
Standard fonts (Calibri, Arial, Times New Roman)	Yes	No embedded font substitution issues on parsing servers
Text inside images, icons, or text boxes	No	Parsers extract text streams; text inside a graphic object is often invisible to them
Contact info in header/footer	Risky	Several parsers don't scan headers and footers by default
.docx file	Yes	Most widely and reliably parsed format across Naukri, Workday, and Taleo
Scanned PDF or image-based PDF	No	No selectable text for the parser to extract at all

Keyword Matching Is a Ranking Filter, Not a Percentage Bar

According to Jobscan's State of the Job Search report, 99.7% of recruiters and employers use some form of ATS or CRM filtering, and the breakdown of what they filter by is specific: 76.4% filter by resume skills, 59.7% by education, 55.3% by job titles, 50.6% by certifications and licenses, and 44% by years of experience. That tells you exactly where to put your effort — your skills section and your stated job title need to mirror the language recruiters are actually searching for, not a creative rewording of it.

Jobscan's own platform data also found that candidates who included the exact job title from the posting on their resume were 10.6 times more likely to get an interview than those who didn't. If a Naukri or LinkedIn posting says "Business Development Executive," don't write "Sales Associate" on your resume even if the work is identical — use their words first, then explain your actual scope underneath. For a full breakdown of how to build this keyword list, see our guide to resume keywords.

Common Mistakes That Quietly Sink Fresher Resumes

• Downloading a heavily designed template from Canva or Pinterest with icons, colour blocks, and columns — these consistently cause parsing problems on Taleo and older Workday instances.
• Sending the identical resume to 50+ postings without changing a word. Off-campus drives reward small, honest tailoring per job description far more than volume.
• Using acronyms without expansion. Write "Search Engine Optimization (SEO)" once so both the acronym and the full term exist somewhere on the page.
• Outdated "Objective" statements instead of a short professional summary that repeats the target role's title and top 2-3 skills.
• Photo, personal details (marital status, religion, father's name) on the resume — irrelevant to parsing but a signal of an outdated format to recruiters reviewing it manually afterward.
• Leaving your Naukri or LinkedIn profile out of sync with your resume. Recruiters searching RESDEX or LinkedIn Recruiter are often looking at your online profile before they ever open the attached resume, so an outdated headline or skills list there can cost you a shortlist you'd otherwise have earned.
• Listing "Microsoft Office" instead of the specific tool the job needs. If a data analyst posting asks for "Excel, SQL, Power BI," a generic "MS Office" line won't match any of those three filters.

Your Online Profile Matters as Much as the Uploaded File

A large share of Indian recruitment for freshers and early-career hires doesn't start with an uploaded resume at all — it starts with a recruiter searching Naukri's or LinkedIn's database directly. Naukri's own recruiter documentation describes RESDEX as a keyword-driven search across its full user base, which means your profile headline, listed skills, and current designation function exactly like resume keywords do: if they don't match what a recruiter typed into the search bar, you don't show up, regardless of how strong your actual resume is. Keep your Naukri profile headline and skills section updated every time you update your resume, not just when you're actively job hunting.

Why This Matters More Given the Volume of Applications

The scale of fresher hiring in India is exactly why parsing and keyword matching decide who even gets seen. TCS has reportedly targeted hiring around 40,000 freshers in FY26, with Infosys targeting 20,000+ and Wipro 10,000-12,000, according to industry reporting. NASSCOM had earlier reported that India's tech industry hired close to 380,000 freshers in FY22 alone. Each of those openings draws far more applicants than positions, through both campus drives and open off-campus postings on Naukri and company career pages — which is exactly the environment where a resume that parses badly or misses obvious keywords quietly disappears from the shortlist before anyone reads it.

A Pre-Submit Checklist Before You Apply

1. Save as .docx unless the portal explicitly requests PDF.
2. Open the file in a plain text editor or copy-paste it into a blank document — if the text comes out jumbled, the parser will see it jumbled too.
3. Match your job title line to the posting's title where honestly possible.
4. Cross-check your skills section against the job description's required and preferred skills lists.
5. Remove tables, text boxes, headers, footers, and icons.
6. Keep contact details as plain text in the body, not in a header.

None of this guarantees an interview — that still depends on whether you're actually a fit for the role. But it removes the silent, invisible failures that have nothing to do with your qualifications. If you want a second read on whether your current resume clears these basics, tools like a Jobscan alternative built for Indian job portals can flag the same parsing issues before you hit submit.