Why your resume is not getting shortlisted (and how to fix it)

Why your resume is not getting shortlisted on Naukri, LinkedIn, campus drives or at big tech, the 10 most common causes, and a fix for each you can do today.

By the fastcv team · 26 October 2026 · 7 min read

If your resume is not getting shortlisted, the cause is usually one of a few fixable problems: the resume doesn't clearly match the job in its first few lines, the bullets describe duties instead of results, the right keywords are missing, or the file is hard for software to read. Less often, you're applying to roles that need more experience than you have. The good news: you can test for each of these in under an hour.

This guide goes through the 10 most common causes we see in engineering and fresher resumes, how to tell which one applies to you, and what to change, including what's different on Naukri, LinkedIn, campus placements and big-tech careers pages.

First, check the numbers honestly

Before rewriting anything, look at your last 20–30 applications:

  • Almost no responses at all: usually a resume problem (match, keywords, parsing) or a targeting problem (roles too senior).
  • Responses from small companies but not large ones: usually a proof problem; your bullets aren't specific enough to stand out in a big pile.
  • Shortlists but no offers: the resume works. Focus on interview preparation.

Recruiters are also busier than they were: in a Robert Half survey, 65% of U.S. hiring managers said a surge of AI-assisted applications made skills harder to verify. A resume now has to make its match obvious fast.

1. The match isn't visible in the first seconds

Recruiters skim first and read later; an eye-tracking study by Ladders found the first look averages about 7.4 seconds. If your latest title, top bullets and key skills don't line up with the job, you're filtered out before your best work is seen.

Fix: reorder so the most relevant role, project and bullets are at the top. Add a one-line headline that names the role ("Backend Engineer, Java and Spring Boot").

2. Your bullets describe duties, not results

"Responsible for developing APIs" could describe anyone. Shortlisted resumes say what changed and by how much.

Fix: rewrite your top bullets as result + number + method, the Google XYZ formula: "Cut API latency from 420 ms to 180 ms by adding Redis caching".

3. The job's keywords aren't on your resume

Recruiters search applicant systems and job portals by skill and title. If the post says "Spring Boot" and "microservices" and your resume says "Java backend work", a search can miss you.

Fix: list the must-have skills from the post and prove each one in a bullet, in the post's words where they're true. Our tailoring guide shows the method, and the free resume checker shows which required skills your resume is missing.

4. The file is hard for software to read

Two-column templates, text inside images, icons for contact details and tables can scramble the text an applicant tracking system extracts, so your skills don't match even when they're there.

Fix: use one column with standard headings, and run the copy-paste test from Is a LaTeX resume ATS-friendly?. If the pasted text comes out jumbled, change the template.

5. You're sending the same resume everywhere

A generic resume is average for every job and strong for none. Some employers make volume pointless anyway: Google allows up to three applications in 30 days.

Fix: keep a master resume and cut a tailored version for each role type (for example backend, data, frontend), then adjust the top third for each application.

6. You're applying above your level

"SDE-2, 3–5 years" won't shortlist a fresher, however good the resume.

Fix: match the required years and title roughly. For freshers, target "fresher", "graduate", "new grad", "trainee", "associate" and internship roles, and campus or off-campus drives.

7. Projects look like tutorials

"To-do app", "weather app" and "Netflix clone" with no details read as practice, not proof.

Fix: keep two or three projects with substance: what problem it solves, the stack, a number (users, load, accuracy) and a link. One deployed project with real users beats five clones.

8. It's too long, cluttered or generic

Two pages for a fresher, paragraphs instead of bullets, "hardworking and passionate team player", a photo and date of birth: each costs attention.

Fix: one page, bullets of one or two lines, no generic adjectives, no personal details beyond contact information and links. See the resume format for freshers for what to keep and cut.

9. It reads as AI-generated

Recruiters see the same AI phrasing all day: "spearheaded", "leveraged cutting-edge technologies", "results-driven professional". Generic text with no specifics now looks less trustworthy, not more.

Fix: use AI to tighten wording if you like, then put your real numbers, systems and names back in. Read what recruiters look for in 2026 for the trust signals that matter now.

10. Your profile and resume don't agree

Different titles or dates on LinkedIn, your Naukri profile and your resume make a recruiter hesitate, especially now that fabricated experience is a known problem.

Fix: align titles, dates and companies everywhere, and make sure every link on your resume works.

Naukri: why your profile isn't getting calls

On Naukri, recruiters mostly find you through search, so your profile matters as much as the attached resume:

  • Key skills and headline: use the exact skill names recruiters search for, and a specific headline ("3 years in Java, Spring Boot and microservices") rather than "Software professional".
  • Keep it fresh: Naukri's own FAQ says recruiters are more likely to view recently updated profiles, and its Profile Performance page shows which search terms found you.
  • Fill every section (current role, notice period, preferred location) so you don't drop out of filtered searches.

LinkedIn: why recruiters aren't messaging you

  • Your headline and current title should name the role you want, not just your company.
  • List your top skills in the Skills section, and use the same words in your experience descriptions.
  • Turn on Open to Work for recruiters only if you don't want it public, and add the job titles and locations you want.

Campus placements: why you're not clearing the resume round

  • Put CGPA and education first; many drives filter on cut-offs before anyone reads further.
  • Follow the format your college or company asks for, and keep it to one page.
  • Lead with your strongest project and internship, and add coding profiles if your ratings are good.

Big tech: why Google or Amazon didn't shortlist you

Big-tech roles get huge applicant pools, so the bar for specificity is higher. Amazon's recruiters say they want resumes that are well-organized, use straightforward language and highlight measurable data. Our guide to getting shortlisted at Google and Amazon covers their qualifications checklists, Leadership Principles and the service-to-product move.

A one-hour fix plan

  1. Pick one job post you really want.
  2. Check the match in the resume checker and note the missing must-haves.
  3. Rewrite your top three bullets with results and numbers.
  4. Move your most relevant work to the top; cut anything that doesn't serve this job.
  5. Run the copy-paste test on the PDF.
  6. Apply, and track responses for this version before changing more.

If you'd like to start fresh, the builder gives you a one-column Jake's Resume layout that parses cleanly, free to download as a PDF.

Frequently asked questions

Why is my resume not getting shortlisted even though I have the skills?

Usually because the skills aren't visible where recruiters look: in your latest role's first bullets, in the job post's exact words, and backed by results. A skills list alone is easy to skip, and a hard-to-parse layout can hide your skills from search.

Why am I not getting calls on Naukri?

Recruiters find you by searching Naukri's database, so check your key skills and headline use the terms they search for, fill every profile section, and update your profile regularly; Naukri says recently updated profiles are more likely to be viewed.

How many applications before I should change my resume?

If 20–30 relevant applications bring almost no responses, change the resume, starting with the match in the top third and your bullets. Track the new version separately so you know whether the change helped.

Does using a resume template from the internet hurt shortlisting?

Only if the template is hard to parse or hides your content: multiple columns, graphics, skill bars or icons. A simple one-column template with standard headings is safest.

Should freshers apply to roles asking for 1–2 years of experience?

Sometimes, if you meet most of the other requirements and have strong internships or projects. But your shortlist rate will be much higher on roles marked fresher, new grad, trainee or internship.

More guides