Most resumes are not rejected because the candidate is unqualified. They are rejected because the recruiter could not quickly see why the candidate fits, or because something on the page created doubt. A first screen often takes less than a minute, so small problems carry a lot of weight.
Here are the mistakes recruiters mention most often, and what to do instead.
1. Sending the same resume everywhere
A resume written for "any IT job" fits no job particularly well. If the role is for a data analyst and your first section talks about Android development, the recruiter has to work to find the relevant parts, and they usually will not.
Fix: keep a master resume with everything, then make a focused copy for each type of role. Reorder projects and skills so the most relevant ones come first, and use the same terms the job description uses when they truthfully describe your experience.
2. Duties instead of results
"Responsible for testing the application" describes a job title, not what you achieved. Every tester was responsible for testing.
Fix: write bullets that start with an action and end with an outcome. "Automated 180 regression test cases with Selenium, cutting release testing from three days to one" tells the reader what you did and why it mattered. Not every bullet needs a number, but aim for most of them to show a result.
3. Designs that software cannot read
Creative templates with columns, icons, tables, text inside images and skill bars look appealing in a template gallery. Applicant tracking systems, which many companies use to sort applications, often read them as jumbled text or miss sections entirely.
Fix: use a clean single-column layout with standard headings. Save as PDF unless asked otherwise. To test it, open the PDF, select all the text and paste it into a plain text editor. If the result is in the wrong order or missing pieces, an ATS will struggle too.
4. Listing skills you cannot defend
Interviewers frequently pick a skill from your resume and ask about it directly. If you listed Docker because you followed one tutorial, a single follow-up question can undo an otherwise strong interview, because it makes the interviewer doubt everything else on the page.
Fix: list only skills you have used in a project or job and can explain. If you are learning something, you can say so honestly in an interview instead.
5. A generic objective statement
"To work in a challenging environment where I can enhance my skills and contribute to the growth of the organisation" is the most common opening line in Indian resumes. It takes space and says nothing.
Fix: either delete it or replace it with a specific two-line summary naming the role you want, your core skills and one concrete achievement.
6. Spelling and grammar errors
Typos signal carelessness, and for roles that involve writing, documentation or client communication they can be an automatic rejection. Common culprits are technology names: "Javascript", "Mysql", "Github" and "React.Js" instead of JavaScript, MySQL, GitHub and React.
Fix: run a spell check, read the resume aloud slowly, and ask someone else to proofread it. Check that technology names use their official spelling and capitalisation.
7. Too long, or padded to look long
Freshers sometimes stretch to two pages with school achievements, hobbies and a declaration. Experienced candidates sometimes list every task from a ten-year career. Both bury the strongest material.
Fix: one page for freshers and candidates with under five years of experience, two pages at most for senior candidates. Older roles can be summarised in a single line each.
8. Unexplained gaps and vague dates
Recruiters notice gaps of several months. A gap by itself is rarely a problem; preparing for exams, family responsibilities, health and upskilling are all common reasons. What raises questions is a gap that looks hidden, such as listing only years ("2023 - 2024") to blur the timeline.
Fix: use month and year for every role. For a long gap, add a single honest line: "Career break, 2024: completed AWS certification and built two cloud projects."
9. Personal details that do not belong
Photos, date of birth, religion, marital status, father's name, passport number and full home address are still common on Indian resumes, but private-sector employers do not need them to shortlist you. Some of these details also expose you to identity misuse if your resume is shared widely on job boards.
Fix: keep only your name, phone number, email, city and professional links. Provide anything else later, when an employer formally asks for it during onboarding.
10. Exaggerating or copying
Claiming a promotion you did not get, inflating your salary, or copying project descriptions from a friend or the internet is risky. Background verification is standard at most mid-size and large companies, and interviewers are skilled at spotting answers that do not match the resume. An offer withdrawn after a failed verification is far worse than a modest but honest resume.
Fix: describe your real work as clearly and specifically as you can. Honest, specific details are more convincing than impressive-sounding vague ones.
11. A careless file and email
A file named resume(2)final.docx sent from an address like cooldude1999 with an empty message body creates a poor first impression before the resume is even opened.
Fix: name the file with your name and the word "Resume", send it as a PDF, use a professional email address, and write a short, polite message with the role name in the subject line.
A quick self-review
Before you apply, hold your resume next to the job description and ask:
- Within ten seconds, can someone see which role I am suited for?
- Does my strongest, most relevant work appear in the top half of the page?
- Does every bullet show what I did and what happened as a result?
- Could I comfortably answer a question on every line?
If you are writing your first resume, start with our section-by-section fresher resume guide.