The ATS Resume Checklist Recruiters Actually Use (2026)
Priya Sharma · Career Coach & Ex-Recruiter
I spent seven years screening resumes on Naukri. I've looked at well over 10,000 applications — and the same mistakes kept killing good candidates in the first 30 seconds. This is the checklist I wish every applicant had.
Let's be honest about something: most "ATS guides" online are written by people who have never actually sat inside an ATS reviewing candidate files. They'll tell you to "use keywords" and "avoid creative formatting" and leave it at that. That advice isn't wrong, but it's not complete.
I spent seven years recruiting for IT services, product companies, and banking clients on Naukri. Before that, I was on the inside — reviewing parse reports, checking why candidates with good profiles weren't surfacing in searches, escalating broken resumes to our sourcing team. The things that trip up resumes are more specific than most guides admit.
Here is the actual checklist I use. Twenty checks across four categories. Run your resume against every single one before you apply.
The One Test Most People Skip
Before anything else, do the paste test. Open your resume. Select all text. Copy it. Open Notepad (or any plain text editor). Paste it.
What you see in Notepad is approximately what an ATS will extract from your resume. If your Skills column merged with your Experience column, if bullet points disappeared, if sections are out of order — the ATS experienced the same problem. This test takes 90 seconds and immediately tells you whether your layout is ATS-safe.
A two-column resume almost always fails this test. The parser reads left to right across the entire line — so it reads your skills from the left column alongside your job title from the right column, producing garbage. I rejected candidates for roles they were qualified for simply because the system couldn't parse their experience correctly and they fell below the match threshold.
What Most ATS Guides Get Wrong
The advice to "save as PDF" is not universally correct. PDF is safer than DOCX for modern ATS platforms like Greenhouse, Lever, and the latest version of Workday — because a properly exported PDF preserves text structure reliably. But Naukri's own parser, and older enterprise systems like Taleo 9 and iCIMS (heavily used in Indian IT services and BFSI sectors), parse DOCX more reliably than PDF — especially if the PDF was exported from Canva or a graphic design tool.
My recommendation: keep both versions. For Indian job portals and IT services companies, upload DOCX. For product company career pages (Flipkart, Razorpay, Zepto, and global companies with modern ATS), upload PDF.
Also: never use the Word document header/footer feature for your contact information. This is extremely common in templates downloaded from the internet. Those header regions are completely skipped by ATS parsers. The system will parse your resume and find no name, no email, no phone — and either reject the file or park it with missing data. Your contact information must be in the main body of the document.
The Photo Question (India-Specific)
Indian resumes traditionally include a passport-sized photograph. If you are applying to Indian IT services companies (TCS, Infosys, Wipro, Accenture India) for operational roles, a photo is culturally expected and rarely causes ATS issues since many of these companies still use semi-manual screening processes.
However: if you are applying to any global company, any FAANG or FAANG-adjacent company with Indian offices, or any company using Greenhouse, Lever, or Workday — remove the photo. These companies run bias-avoidance compliance programs. Resumes with photos are sometimes automatically flagged or routed differently. The photo adds no parsing value (ATS cannot read it) and creates compliance risk on the hiring team's end.
The Keyword Matching Reality
Here is something I learned from watching ATS match scores: many systems do not synonymise. If the job description says "Machine Learning," and your resume says "ML," you may not get credit for the match. If the JD says "React.js" and your resume says "ReactJS," some parsers treat those as different strings.
Use the exact terminology from the job description. Copy the job description into a text file. Go through it and identify every skill, tool, certification, and methodology mentioned. Now check your resume. Do all of them appear, using the same words? If not, add them — as long as you actually have those skills.
One more thing: the summary section is prime keyword real estate that most people waste on phrases like "dynamic professional with a passion for excellence." That sentence adds zero to your ATS match score. Instead, use your summary to establish your role, your core technical stack, and your experience level — three to five specific keywords in two to three sentences.
The 20-Point ATS Checklist
File & Format
Single-column layout — no text boxes, tables, or multi-column sections
Why: Parsers read left-to-right. Columns scramble the content.
File format matches the portal (DOCX for Naukri/Shine, PDF for product company career pages)
Why: Different ATS systems handle formats differently.
Contact info in the document body — NOT in a Word header/footer region
Why: ATS skips header/footer zones entirely.
File named: FirstName_LastName_Role_Resume.pdf
Why: Some ATS systems use filenames to pre-populate fields.
Passed the paste test (copy → Notepad → still readable)
Why: If Notepad loses structure, ATS will too.
Section Structure
Section headers use standard names: Experience, Education, Skills, Summary
Why: Custom headers like 'Where I've Worked' confuse parsers.
Skills section placed in the top half of the resume
Why: ATS weights content higher the earlier it appears.
Work experience dates use a consistent format throughout (e.g., Jan 2022 – Mar 2024)
Why: ATS calculates years of experience from dates. Inconsistency creates errors.
No photo, no graphics, no logos
Why: ATS cannot read images. Logos are treated as blank space.
Bullets use standard characters (– or •) not decorative Unicode arrows
Why: Special Unicode bullets sometimes render as '?' in parsers.
Keywords & Match Rate
Every core requirement from the JD appears at least once in your resume
Why: Match rate is the primary ATS filter at most companies.
Keywords match the JD's exact terminology (don't write 'ML' if the JD says 'Machine Learning')
Why: Many ATS systems don't synonymise — they match strings.
Summary/objective section contains 3–5 core role keywords
Why: The summary is prime real estate. Most people waste it on filler.
No keyword stuffing or hidden white text
Why: Modern ATS systems flag keyword manipulation as spam.
Technical skills listed individually, not buried in paragraphs
Why: 'Experience with Python, SQL, and Tableau' parses better as a skills list.
Content Quality
Every bullet starts with a strong action verb (not 'Responsible for' or 'Helped')
Why: ATS compliance scores include action-verb density.
At least 60% of bullets include a measurable outcome
Why: Quantified impact is a primary signal of seniority for ATS scoring.
LinkedIn profile URL matches the role/title on your resume
Why: Some ATS systems cross-reference. Discrepancies create flags.
Resume is 1 page (fresher/0–3 yrs) or 2 pages max (senior roles)
Why: Multi-page resumes get lower ATS compliance scores on most Indian systems.
No personal information: DOB, marital status, father's name, Aadhaar
Why: Global companies reject these for bias-avoidance compliance. Adds no value.
India-Specific ATS Notes for 2026
Naukri.com Resume Database
Naukri's internal search algorithm weights the "Headline" field very heavily — this is the short role title you set on your profile. Make sure it matches your resume's job title exactly. Inconsistencies between your Naukri headline and resume title are one of the most common reasons recruiters find a candidate in search but pass on them when they open the profile.
Naukri also has a "Resume Score" displayed to recruiters (not you). This score factors in completeness, recency, keyword density, and action verb usage. Resumes that score below 70 are surfaced less often in search results, regardless of how relevant the candidate is.
Indian IT Services vs. Product Companies
TCS, Infosys, Wipro, and HCL use a mix of internal ATS tools (iRecruiters, Keka, SAP SuccessFactors) and manual shortlisting for lateral hiring. For these companies, keyword match on specific technology stack matters, but so does "total experience" calculation — which the ATS derives from your date ranges. A single date that is formatted differently can cause the system to miscalculate your years of experience by a year or more, pushing you below the minimum filter.
Product-led companies in India (Razorpay, CRED, Zepto, MeeshoTech, PhonePe) have largely adopted modern SaaS ATS platforms. They behave more like global standards — Greenhouse, Lever, or Workday. Single-column PDF resumes with clean formatting work best here.
After the Checklist: Verify With a Score
Running this checklist manually takes time and a trained eye. The fastest way to validate that your resume is ATS-ready is to run it through an ATS simulator with the actual job description you're applying for.
ScoreMyResume does exactly this — it parses your resume the way an ATS would, scores keyword match against your JD, checks ATS compliance rules, and shows you specifically which sections need work. It's the same type of analysis I used to do manually, automated in 30 seconds.
Run Your Resume Through the ATS Check
Upload your resume + paste the job description. Get your ATS score, keyword gaps, and compliance issues in 30 seconds — free.
Score My Resume Free →