Aman Gupta
Getting shortlisted for IT jobs in India is a chain — a parseable resume, exact keywords, eligibility, timing, and referrals. Here's what actually moves the needle, stage by stage.
Jun 25, 2026 · 11 min read
Read
Start from an ATS-tested template, or check how your current resume scores — both are free.
You applied to 30 roles you were qualified for. Some sent an instant "we regret to inform you" within minutes. Most sent nothing at all. It feels like a machine is throwing your CV in the bin before a human ever sees it — and you want to know why.
In most cases the ATS isn't rejecting your CV — it's burying it below better-matched resumes, and the cause is almost always one of five things: an unreadable file, a keyword mismatch with the job description, a hard knockout filter, misplaced sections, or applying to the wrong roles. The good news is that every one of these is diagnosable in about ten minutes, and fixable. This guide walks through each reason — the symptom, why it happens, and the exact fix.
➡ See exactly what the ATS reads when it gets your CV — free scan on ResumeLens.
Most ATS platforms don't hard-reject resumes — they rank them. When you apply, the system parses your CV, scores it against the job description, and slots you into a ranked list. Recruiters work that list from the top. A weak resume isn't deleted; it sits at position 180 of 250 and never gets opened. The outcome feels identical to rejection, but the cause — and the fix — is different. The myth that "ATS automatically rejects 75% of resumes" is false: the real risk is invisibility, not deletion.
There is one exception, and it explains the instant rejections: knockout filters. Many application forms ask screening questions — years of experience, location, work authorisation, notice period, expected salary, a required certification. Answer one outside the employer's set range and the system can auto-reject you in seconds, before your resume is even scored. That fast "we regret to inform you" email is almost never the ATS reading your CV and judging it — it's a single form answer tripping a filter.
What you saw | What it usually means |
|---|---|
Instant rejection email (minutes) | A knockout filter — a screening-question answer outside the employer's range |
Total silence everywhere | A parsing problem — the ATS likely can't read your file |
Silence on roles you're clearly qualified for | A keyword mismatch with the specific job description |
Recruiter views but never contacts | Misplaced contact details, or a weak/buried resume |
Symptom: near-total silence across many applications, regardless of how qualified you are.
Why it happens: the ATS converts your CV to plain text before doing anything else. If your resume is a Canva or design-tool export, an image-based or scanned PDF, or a two-column layout, the parser reads content in the wrong order, merges sections, or extracts nothing at all. Across the 1,000+ resumes ResumeLens has analysed, 70%+ of low scores came from complicated design, not missing skills — and image-based PDFs are the single most common mistake among fresher resumes.
How to confirm: run the plain-text test — copy all the text from your resume and paste it into a plain Notepad/TextEdit file. If sections are missing, jumbled, or nothing pastes, the parser sees the same broken version.
The fix: rebuild in Word or Google Docs (or Resume Builder) using a single-column, plain-text layout, and export a text-selectable PDF. This one change often resolves the silence.
Symptom: silence specifically on roles you know you're qualified for.
Why it happens: the ATS scores your CV by how closely its language matches the job description. If the JD says "stakeholder management" and you wrote "worked with teams," or it says "machine learning" and you wrote "ML," the system may not connect them — and your score drops below the threshold to be reviewed. Older parsers, still common across Indian enterprises and MNCs, are especially literal.
How to confirm: paste the JD and your CV side by side and highlight every skill, tool, and qualification in the JD that does not appear verbatim in your resume.
The fix: add the missing terms you genuinely have — in your summary and, more powerfully, inside your experience and project bullets, where keywords carry more weight. (See how to write bullets that pass ATS.)
Symptom: an instant rejection email, often within minutes.
Why it happens: a screening question — required years of experience, location, work authorisation, a mandatory certification, notice period, or expected salary — was answered outside the employer's accepted range, triggering an automatic rejection before your resume was scored.
How to confirm: re-read the application's screening questions and the JD's hard requirements. If you missed a "must-have" or answered a range question conservatively, that's likely the trigger.
The fix: only apply where you meet the genuine hard requirements, and answer range questions accurately but strategically — don't disqualify yourself by, for example, listing a salary far outside the band when a range is acceptable. This is not a resume problem and no amount of resume editing fixes it.
Symptom: recruiters seem to view your profile but never reach out, or your details come through blank.
Why it happens: many ATS platforms don't parse content in a document's header or footer — so contact details placed there can vanish. Non-standard section headings ("My Journey," "What I Bring") can also cause the parser to misfile or skip whole sections.
How to confirm: check the parsed-output view in an ATS checker — is your phone, email, and each section captured in the right field?
The fix: move all contact details into the body of the document, and use standard headings — Work Experience, Education, Skills, Certifications.
Symptom: consistently low match scores even with a clean, well-formatted resume.
Why it happens: if your experience or job titles are too far from what the JD asks for, no formatting or keyword tweak will lift the score enough — the underlying relevance isn't there. Sometimes it's a title-language gap (you're a "Software Engineer" applying to "Backend Developer" roles without the matching keywords); sometimes it's genuine over- or under-qualification.
How to confirm: check your match score against several postings. If a clean resume scores low everywhere, it's relevance, not formatting.
The fix: target roles your experience genuinely fits, and mirror the title and core terminology from the JD where it honestly applies to you.
➡ Run your CV through ResumeLens to see which of these five is happening — free.
Before | After | |
|---|---|---|
Format | Two-column Canva PDF | Single-column, text-selectable PDF |
Parsed correctly? | No — experience and skills merged | Yes — every section captured |
JD keyword match | Low — paraphrased terms | High — exact-match terms in bullets |
ATS score | ~40s | 80+ |
Result | Silence across applications | Callbacks within two weeks |
Before you reapply, run this checklist. It isolates which of the five reasons is hitting you.
Plain-text test — copy all text into a plain editor. Jumbled or missing? It's a parsing problem (reason 1).
File format — is it a text-selectable PDF from Word/Google Docs, not a Canva or image export?
JD keyword check — do the JD's key terms appear verbatim in your CV? If not, that's reason 2.
Headings — standard labels only (Work Experience, Education, Skills)?
Contact placement — details in the body, not the header/footer?
Screening questions — did you meet every hard requirement and answer ranges accurately? If an instant rejection came, it's reason 3.
Role fit — does a clean CV still score low across several postings? Then it's relevance, reason 5.
A few causes are particularly common for Indian applicants:
Image-based PDFs. The most common fresher mistake — a file that looks fine but contains no readable text, so the parser extracts nothing.
Applying through the wrong channel. Naukri's FastForward parser and a company's own Workday/Greenhouse portal read resumes differently; a CV that works on one can score lower on another. Tailor and re-check per channel.
Biodata fields breaking the parse. A photo, or contact details inside a header alongside a photo, can disrupt parsing — drop them.
Off-campus cold applications. Without a campus referral, your CV faces the ATS with no filter advantage, so exact keyword matching matters far more. (See resume format for freshers in India.)
The reason most candidates never fix the problem is that the ATS gives no feedback — just silence. An ATS checker closes that loop: it parses your CV the way a real ATS would, scores it against a specific job description, and shows you the parsed output so you can see exactly what's missing or misread, before you submit. (For what your number means, see what is a good ATS score?)
➡ Check your CV against the exact role on ResumeLens — free, instant results.
Usually for one of five reasons: the parser can't read your file (a Canva or image PDF, columns, or contact details in the header), your keywords don't match the job description, a hard screening filter eliminated you, your sections are misplaced, or your experience doesn't fit the role. The first two are the most common and the easiest to fix.
Mostly no — most ATS platforms rank resumes rather than reject them, so a weak resume gets buried low in the queue instead of deleted. The exception is knockout screening questions (required experience, location, work authorisation), which can trigger an automatic rejection before your resume is even scored.
You usually don't get told directly. Clues: total silence across many applications points to a parsing problem; an instant rejection email points to a screening filter; views without contact point to misplaced details. Run your resume through an ATS checker to see the parsed output and your match score.
An instant rejection is almost always a knockout filter — a screening-question answer (years of experience, location, work authorisation, notice period, salary) fell outside the employer's accepted range, so the system auto-rejected you before scoring your resume. Re-check the form's hard requirements.
Yes. A genuinely strong resume can still be buried if it's formatted in a way the parser can't read, or if it doesn't use the specific keywords from the job description. Strong experience and an ATS-readable resume are two different things — you need both.
Being qualified isn't the same as ranking well. If your resume paraphrases the JD's language instead of mirroring it, or if formatting prevented a clean parse, you score below the threshold to be reviewed despite being qualified. Match exact keywords and confirm the file parses cleanly.
No — modern ATS platforms read text-selectable PDFs reliably, and PDF is a safe choice. What gets rejected is an image-based or design-tool PDF (like a Canva export) where the text is baked into an image the parser can't read. Always export your PDF from Word or Google Docs.
On Naukri, two things matter most: matching the "Key Skills" tags at the bottom of each posting verbatim, and submitting a clean, parser-readable file. If your CV is an image-based PDF or paraphrases the key skills instead of using the exact terms, it scores low in Naukri's FastForward matching and you don't get shortlisted.
Use a single-column, plain-text layout with standard headings, export a text-selectable PDF, mirror the job description's exact keywords inside your experience bullets, and keep contact details in the body. Then check your score against the specific role before applying. See the complete ATS guide for the full method.
Related guides: How to Optimize Your Resume for ATS (Complete Guide) · What Is a Good ATS Score? · Resume Bullet Points That Pass ATS · Resume Format for Freshers in India · Free ATS Resume Checker
An employment gap won't get you auto-rejected by the ATS — it reads your dates, not your story. Here's how recruiters read gaps after the 2023–25 layoffs, and how to present yours honestly.
Jun 25, 2026 · 11 min read
Read
ResumeLens vs Jobscan compared honestly: where each wins, pricing, India/Naukri support, and who should pick which. A candid head-to-head, not a sales pitch.
Jun 25, 2026 · 10 min read
Read