Resume Rejected by ATS? 15 Fixes That Work (and What Really Happened)
Most ATS rejections come from knockout questions, parsing errors or missing keywords. Find which one hit you and apply 15 fixes in order.
An ATS rarely rejects a resume by itself. Most "ATS rejections" come from one of four places: a screening question you answered outside the recruiter's rules, a parser that misread your layout so you never show up in searches, keywords that don't match the job, or a recruiter who read it and passed. Fix the layout, use the job's exact terms where they are true, and answer screening questions carefully.
Below is how to tell which of the four happened to you, then 15 fixes in the order that usually helps most. Before you change anything, run your current file through the free ATS resume checker. It scores the file without sign-up, and a free account flags the exact lines that cost you, so you fix the real problem first.
Where does the rejection actually happen?
The idea of a robot that reads every resume and bins most of them is mostly a myth. Greenhouse, a major ATS vendor, says on its candidate blog that applications in its system "are reviewed by real people, one by one, in the order received". It also explains that recruiters can set auto-reject or auto-advance rules, and those rules are tied to answers to specific application questions, such as whether you are legally allowed to work in the country. Its support documentation gives another example: automatically rejecting applicants who answer "no" to a question about holding a required licence.
So the useful question is which stage stopped you.
| Where it stopped | Typical sign | What to fix |
|---|---|---|
| Screening (knockout) question | Rejection email within minutes or hours of applying | Read the eligibility rules and answer every question honestly and precisely (fixes 13–14) |
| Parsing | The form's autofill put your details in the wrong fields, or the email field came out empty | Layout and file (fixes 1–6) |
| Search and matching | No response for weeks, even for roles you fit | Keywords and skills section (fixes 7–10) |
| Human review | Rejection after a few days or weeks | Bullets, summary and fit (fixes 11–12, 15) |
Fixes 1–6: make sure the software can read your resume
If the parser can't read you, nothing else matters. Greenhouse's support page on unsuccessful parses lists the usual causes: files over 2.5MB, graphics, photos or word art, image files, tables, headers and footers, contact details in a header, footer or text box, columned layouts, inconsistent section formatting, letters with spaces between them, and abbreviated job titles.
1. Switch to a single-column layout
Two-column templates with a coloured sidebar are the most common cause of scrambled parsing. Move everything into one column that reads top to bottom.
2. Put contact details in the body
Your name, phone, email and city should be normal text under your name, not in the page header, footer, a text box or icons only.
3. Remove tables, text boxes and graphics
Skill bars, star ratings, logos and tables used for layout either disappear or come out in the wrong order. Write skills as plain text.
4. Send a text-based PDF or DOCX under 2.5MB
If you can't select the text in your PDF with a mouse, the parser can't read it either. Rebuild scanned or image-based files from Word or Google Docs.
5. Use standard section headings
"Experience", "Education", "Skills", "Projects" and "Certifications" are what parsers look for. "My Journey" and "Toolbox" aren't.
6. Spell out job titles and normalise letter spacing
Write "Senior Software Engineer", not "Sr. SWE". Remove decorative S P A C E D letters from your name and headings.
Our ATS-friendly resume format for India has a complete template with these rules applied.
Fixes 7–10: match how recruiters search
Recruiters find candidates by searching. On Naukri, the support documentation describes searches by "all the words", "any of the words" or an "exact phrase", plus filters such as experience. If the job says "Power BI" and your resume says "BI dashboards", you may not appear.
7. Use the job description's exact terms where they are true
Mirror the wording of tools, skills and qualifications the post asks for, but only for things you have actually done. "PostgreSQL" and "Postgres" may be treated differently; use the version the job uses.
8. Add a clear Skills section
Group skills by type (languages, frameworks, tools, cloud, databases) in a section of their own. Skills buried inside paragraphs are harder to find.
9. Tailor the summary to each role
Two or three lines that name the target role and your two most relevant strengths. A generic objective ("seeking a challenging position") wastes the most-read lines on the page.
10. Don't stuff keywords
Greenhouse says plainly that you don't have to stuff your application with keywords to show up in its recruiters' searches. Repeating a keyword ten times or pasting the job description in white text only makes the resume worse for the human who reads it next.
Fixes 11–12: give the recruiter a reason to say yes
11. Rewrite duties as results
"Responsible for testing" tells a recruiter nothing. "Wrote 150 unit tests for the payments module, raising coverage from 45% to 80%" does. Start with a verb, say what you did and end with a result you can explain in an interview.
12. Remove template leftovers and inconsistencies
Search your file for "Company Name", "Lorem ipsum" and "XYZ". Greenhouse lists placeholder data like "First Last" or "Company 1" as a cause of failed parses, and recruiters notice it instantly. Check that every role uses the same date format and that your dates match your application form.
Fixes 13–15: the application itself
13. Read the eligibility criteria before applying
Campus and fresher drives often set rules such as minimum marks, graduation year or permitted backlogs. Experienced roles may require a location, a notice period or work authorisation. If you don't meet a hard requirement, a knockout rule will reject you no matter how good the resume is.
14. Answer screening questions precisely
Notice period, current location, willingness to relocate, expected CTC and years of experience are common questions. Give honest, exact answers in the format asked. "2.5" when the form expects years and months, or a rough guess at experience, can trip a rule you can't see.
15. Re-check, then apply early and follow up
Run the edited resume through an ATS checker again and compare the score with your first run. Apply in the first few days after a post goes up; Greenhouse, for one, says applications are reviewed in the order received. Then message the recruiter or a team member on LinkedIn with one line about why you fit.
A 20-minute fix-it routine
| Minutes | Do this |
|---|---|
| 0–3 | Run your current resume through the checker and note the score |
| 3–8 | Fix layout: one column, contact details in the body, no tables or graphics |
| 8–13 | Paste the job description into the checker and add missing terms you can honestly claim |
| 13–18 | Rewrite your three weakest bullets as action plus result |
| 18–20 | Export as PDF, run the Notepad test (copy all text, paste, check order), re-check the score |
For what the numbers mean, see what a good ATS score is, and for portal-specific keyword advice, read our Naukri resume tips. When you're ready, check your resume free; the score takes seconds and needs no sign-up.
