Why an 89 ATS Score Still Gets No Interview Calls

"ATS score 89, still why am I not getting interview calls?" is the title of a thread on r/developersIndia, and the question comes up again and again in Indian job-seeker forums. Another post describes getting the score to 89 and receiving zero online assessments from off-campus applications. These threads are not evidence of how any company hires. They show a common and reasonable confusion: if a tool says the resume is 89% good, why does nothing happen?

The short answer is that the score and the shortlist answer different questions. This article explains the gap, and what you can do about each part of it.

What the score actually measures

A resume checker, including Guul's, reads your file and applies its own rules. Typical checks are:

• whether the text can be extracted at all (not a scanned image, not text inside graphics);
• whether headings such as Education, Experience, Projects and Skills are recognisable;
• whether your name, email, phone number and dates come out in the right places;
• whether your bullet points communicate specific experience and achievements;
• whether the words in a job description you pasted also appear in your resume.

Every tool weighs these differently, so the same resume can score 89 in one checker and 62 in another. Neither number is used by the company you applied to. No employer we know of publishes that it rejects candidates below a checker score, and a recruiter using Workday, Taleo or Naukri's recruiter tools does not see the number your checker showed you.

Guul's score combines parsing, structure and content quality. Adding a job description also includes job matching and changes the category weights. The scoring methodology explains the current checks and weights. Read that breakdown rather than treating the overall number as a readability result or a prediction of interview chances.

Fixing scrambled dates helps software read the file; strengthening a vague bullet helps a person understand your experience. Both can matter. Prioritise the specific problems behind the score instead of chasing a target number without knowing what improved.

For India, Guul's previews simulate how Workday-family and Taleo-family systems are likely to read your file. They are simulations, not tests inside an employer's account. Guul does not simulate Naukri, Zoho Recruit, Darwinbox or Keka, so it cannot tell you how those systems will display your resume.

What the score cannot see

Most of what decides a shortlist is not in the file's structure. A checker cannot know:

• How many people applied. An off-campus fresher role can attract thousands of applications. Jaganathan Gopalakrishnan, identified in the source biography as Head, Branding, TCS Talent Acquisition, has written that evaluators may be asked to pick 50 résumés from 5,000 and spend "eight to ten seconds per résumé" in early rounds (TCS careers blog). At that ratio, a readable resume is the minimum, not the edge.
• Hard filters in the application form. Many portals ask for your graduation year, degree, location, notice period or percentage in separate fields. If the role is for a 2025 batch and you are 2023, a perfect resume does not help. Read the eligibility lines in the posting before you apply.
• The employer's final judgement of your fit. A DevOps resume sent to a data analyst opening can score well on structure while matching the role poorly. Job-match feedback can highlight gaps in the evidence you provide, but it cannot know every employer requirement or how a recruiter will weigh your experience.
• Referrals and timing. Some roles are filled from referrals or earlier applicants before your application is read. That is not something a resume can fix.

None of this means your resume is fine. It means the score was never the right measure of whether it is working.

Signs the resume is the problem

Look at your results honestly across at least 20 to 30 applications to roles you genuinely match. If you get no assessments, no recruiter calls and no replies at all, the resume is a likely cause. Check these, in order:

1. The top third of the first page. A recruiter should see your target role, your strongest proof for it and your degree or current job within a few seconds. If the top is a long career objective ("seeking a challenging position in a reputed organisation…"), replace it with two lines naming the role and your best evidence. In the same TCS article, Gopalakrishnan cautions that experienced reviewers can spot generic copied wording. Describe your own experience instead.
2. Projects that say what you did. "Worked on an e-commerce website using React" tells the reader nothing about you. "Built the cart and checkout pages in React for a 4-person college project; wrote the API tests that caught a price-rounding bug" does. Only include numbers you can explain in an interview.
3. Skills you can defend. A list of 25 technologies invites questions you may not be able to answer. Keep the ones you have used in a project or job, and show where.
4. One resume for every role. If you apply to backend, testing and data roles with the same file, each version reads as a weak match. Keep a short, focused version per role family.
5. Details the form will ask anyway. For many Indian applications you do not need current CTC, expected CTC or a notice period on the resume itself; the portal usually asks. See our guide to CTC and notice period on a resume.

Make the first screen easy for a person

After a system stores your resume, a person reads it, often quickly. Design for that reader:

• Use one column for the main content. Two-column layouts can look good but sometimes come out in the wrong order when extracted.
• Put employer or college, title and dates on the same line or block, in the same format every time (for example "Jun 2024 – Present").
• Write the degree the way the posting does: "B.Tech, Computer Science and Engineering, 2025". Add CGPA with its scale, for example "CGPA 8.1/10". Our guide on 10th and 12th marks and CGPA covers when to include which.
• Keep freshers to one page where you can, and experienced candidates to two. A third page is acceptable in some Indian applications, but every extra page lowers the chance your best line is read.
• Save as PDF unless the employer asks for Word, and open the PDF once to check that the text is selectable.

For fresher-specific structure, read Fresher resume ATS notes for India. If you are applying to both Indian and overseas employers, the India vs US resume format checklist explains which personal details to drop for each.

Use the checker for what it is good at

A checker is worth running for specific, fixable problems:

• the extracted text is missing your phone number or email;
• a date range is read as one date, or two jobs merge into one;
• a section heading is not recognised, so your projects land under "Other";
• a bullet lists a responsibility without explaining your contribution;
• a job description names a skill you really have but described differently ("Postgres" in your resume, "PostgreSQL" in the posting).

Use Guul's resume checker to review the findings across readability, structure, content and job matching when a posting is supplied. Make changes that improve the resume while keeping every claim accurate. The score does not promise a shortlist.

A realistic weekly routine

If you are applying off campus, a routine beats a higher score:

1. Pick five to ten openings a week that you match on degree, batch year and core skills.
2. For each, reorder your projects or bullets so the most relevant one is first. Do not invent skills to match.
3. Apply through the company's own careers page where possible, and keep a simple sheet of where and when you applied.
4. After three or four weeks, compare the responses. If one version of your resume gets replies and another does not, that is better evidence than any checker score.

If you still get no replies after a month of well-matched applications, ask a senior, a placement cell volunteer or a mentor in your target role to read the first page for ten seconds and tell you what they remember. That test is closer to what happens in a real shortlist than any number.