15 Resume Mistakes Indian Freshers Make: We Found These in 500+ Resumes

We Read 500+ Fresher Resumes Last Month. It Was Painful.#

Not exaggerating. We sat down with 500+ resumes from Indian freshers: B.Tech students from VIT, SRM, Amity, KIIT, DTU, IP University. MBA grads from tier-2 B-schools. BCA and MCA folks from Pune and Bangalore. We scored them, parsed them through three different ATS systems, and took detailed notes.

The pattern was brutal. The same 15 mistakes appeared again and again. Not minor formatting hiccups. These were fundamental errors that get resumes instantly rejected.

Here is the thing that frustrated us the most: many of these students had solid skills. Decent projects. Relevant internships. But their resumes were actively sabotaging them. A resume from a VIT CSE student with 3 solid full-stack projects scored 29/100 on ATS because of how it was formatted. Twenty-nine.

According to Jobscan, over 98% of Fortune 500 companies use ATS. In India, every major recruiter (TCS, Infosys, Wipro, HCL) runs one. Your resume hits a robot before any human. And robots are not forgiving.

These are the 15 mistakes we found most frequently, with before/after examples so you can fix them today.

Mistake #1: Using a Canva Template with Columns, Icons, and Graphics#

This was the single most common problem. Out of 500 resumes, roughly 340 used Canva or similar graphic-design templates.

They looked beautiful. Two columns, skill bars with percentages, little icons next to section headings, a colourful sidebar. The students clearly spent hours making them look polished.

ATS cannot read any of it.

We ran 20 Canva-designed resumes through Taleo, Workday, and iCIMS. 18 out of 20 had critical parsing failures. Names were misread. Skills ended up under Education. Entire sections vanished.

Before: A gorgeous two-column Canva template with a dark sidebar, skill percentage bars, and icons. Visually stunning, but ATS reads it as random text fragments scattered across the page.

After: A clean single-column format in Google Docs or Word. Standard headings. No graphics. Plain but perfectly parseable. ATS score jumped from 31 to 78 for the same content.

We wrote an entire guide on this: ATS Resume Format Guide. The short version: ditch Canva for your job applications. Use it for your portfolio site, not your resume.

Mistake #2: The "Career Objective" Nobody Reads#

"To obtain a challenging position in a reputed organization where I can use my skills and contribute to the company's growth while enhancing my professional development."

Sound familiar? We found this exact sentence (or a slight variation) on 200+ resumes. Copy-pasted from the same template, clearly.

No recruiter reads career objectives. They are filler. Worse, they waste the most valuable real estate on your resume: the top 3 lines, which is the first thing both ATS and recruiters scan.

Before: "Objective: To secure a challenging position in a dynamic organization that offers professional growth while being resourceful and innovative."

After: "B.Tech Computer Science graduate (VIT, 8.2 CGPA) with experience in Python, React.js, and PostgreSQL. Built 3 full-stack applications including a real-time chat platform handling 500+ concurrent users. NPTEL certified in Data Structures and Algorithms."

The second version packs keywords, specifics, and credibility into the same space. The first says absolutely nothing.

Mistake #3: Listing Skills Without Any Proof#

"Skills: Leadership, Communication, Problem Solving, Team Player, Quick Learner, Adaptable"

We saw this on nearly every single resume. A big block of soft skills with zero evidence. Here is what recruiters actually think when they see this: nothing. They skip it entirely.

Worse, ATS doesn't score you for soft skill buzzwords. It looks for technical keywords matching the job description: specific programming languages, tools, frameworks, certifications.

Before: "Skills: Hard-working, Quick Learner, Team Player, Leadership, Communication, Creative Thinking"

After: "Technical Skills: Python, Java, React.js, Node.js, MySQL, Git, AWS (EC2, S3), Docker | Tools: VS Code, Postman, Jira, Figma | Certifications: AWS Cloud Practitioner, NPTEL Data Structures (Gold)"

Soft skills should be demonstrated through your project descriptions and experience bullets, not listed in a sad block at the bottom. (For more on how to structure your skills section, check our resume for freshers guide.)

Mistake #4: Writing "Responsible For" Instead of "Achieved/Built/Delivered"#

This might be the difference between a call and silence. We compared resumes that got interview calls versus those that didn't. The ones that got calls used action verbs and numbers. The rejected ones used passive language.

Before: "Responsible for developing a weather application as part of the final year project."

After: "Developed a real-time weather forecasting application using React.js and OpenWeatherMap API, displaying current conditions and 5-day forecasts for 200,000+ cities. Reduced API response time by 40% through client-side caching."

Same project. Completely different impact. The first sounds like you were assigned homework. The second sounds like you shipped a real product.

Action verbs that work: Built, Developed, Designed, Implemented, Optimized, Automated, Reduced, Increased, Led, Deployed.

Mistake #5: The Photo on Resume Debate#

This one is specifically Indian.

In India, a lot of resume templates include a passport-sized photo in the top-right corner. Career cells at many colleges still recommend it. Here is our take after reviewing hundreds of resumes and talking to recruiters at Naukri, LinkedIn India, and multiple service companies:

Don't include a photo on your resume.

Three reasons:

1. ATS cannot parse images. If your photo takes up space, that's less parseable text.
2. It opens the door to unconscious bias (appearance, gender, age, religion markers).
3. No major international or Indian tech company requires or expects it.

The exception? If a job posting specifically asks for a photo (some government jobs and some traditional manufacturing companies do), then include it. Otherwise, skip it.

One SRM student we worked with had a 2-inch photo taking up the entire right side of his header. When he removed it and reorganized his contact info, his ATS parse rate went from 55% to 91%. The photo wasn't being "read". It was just blank space to the ATS, pushing his actual content into weird positions.

Mistake #6: Including Father's Name, Date of Birth, and Marital Status#

Still happening in 2026. We found "Father's Name: Shri XYZ" on about 120 of the 500 resumes we reviewed.

Unless you are applying to a government PSU job that explicitly requires it, remove all of this:

• Father's name
• Date of birth
• Age
• Marital status
• Gender
• Nationality (it is obvious from your address)
• "I hereby declare that the above information is true..."

This is outdated practice from the 1990s. Modern tech companies, startups, and even most service companies do not need personal demographic information at the resume stage. It also wastes space that could be used for skills and projects.

Before: "Personal Details: Father's Name: Shri Ramesh Kumar | DOB: 15/03/2002 | Marital Status: Single | Gender: Male | Nationality: Indian | Languages: Hindi, English"

After: That entire section is deleted. The space is now used for an additional project description with tech stack and metrics.

Mistake #7: One Generic Resume for Every Application#

We asked 50 freshers a direct question: "Do you customize your resume for each job?" Forty-three said no. They had one resume and sent it everywhere: Naukri, LinkedIn, Internshala, company career pages. Same file, different "Apply" button.

This is why your ATS score is low. ATS matches your resume against the specific job description. If the JD says "React.js, Node.js, MongoDB" and your resume leads with "Java, C++, Data Structures" (even if you know React), the ATS gives you a low match score.

You don't need to rewrite your entire resume for every application. But you do need to:

1. Read the JD carefully
2. Mirror the exact keywords and phrases from the JD
3. Reorder your skills to match what the JD prioritizes
4. Tweak your summary to reflect the specific role

A student from DTU told us she was getting zero responses from 100+ applications. She started customizing her resume for each role (same content, just reordered and keyword-matched) and got 7 calls in two weeks.

Mistake #8: Typos, Grammatical Errors, and Inconsistent Formatting#

You would be shocked. "Programing" instead of "Programming." "Deveoped" instead of "Developed." "Refrences available upon request." Three errors in one line.

Out of 500 resumes, 187 had at least one obvious typo. That's 37%. And these were resumes from engineering students at reputable colleges.

Formatting inconsistency was even worse:

• Some bullets used "•", others used "-", others used ">"
• Date formats mixed: "Jan 2025" next to "2024-06" next to "June, 2024"
• Font sizes varied randomly across sections
• Some sections were bold, others weren't
• Random indentation

These might seem minor. They are not. A CareerBuilder survey found that 58% of recruiters will reject a resume for typos alone. In India, where hundreds of applications pour in for every opening, a typo is the easiest excuse to move to the next candidate.

Fix: Run your resume through Grammarly, then have a friend read it, then read it yourself one more time. Check that every date, bullet style, and font size is consistent.

Mistake #9: Using a College Email (or Worse, a Joke Email)#

We saw email addresses like [email protected], [email protected], and multiple variations of [email protected]. Real examples from real resumes.

Also common: using your college email like [email protected]. College emails expire after you graduate. If a recruiter tries to email you 3 months later, it bounces. You've lost the opportunity and you'll never know.

Use: [email protected] or [email protected]. If taken, add a number or middle initial. Keep it professional.

Mistake #10: Listing Every Course from Your Degree#

We found a resume that listed 42 subjects under Education. Forty-two. Including "Environmental Studies" and "Professional Ethics" for a software developer role.

Nobody cares about your entire course list. Recruiters spend 6 seconds scanning a resume (according to Ladders Inc eye-tracking study). You want those 6 seconds spent on your skills and projects, not on "Discrete Mathematics, Operating Systems, Computer Networks, Database Management Systems, Theory of Computation..."

Before: "Relevant Courses: Data Structures, Algorithms, DBMS, OS, CN, Compiler Design, TOC, Software Engineering, AI, ML, Cloud Computing, Cyber Security, Web Development, Mobile Computing, Big Data Analytics, IoT"

After: Remove the coursework section entirely. If a specific course is relevant to the job, mention it within a project description: "Built using concepts from Advanced DBMS coursework, implementing B+ tree indexing and query optimization."

Mistake #11: The 3-Page Resume (For a Fresher)#

Your resume should be one page. One. Not two, not three. One.

We received resumes that were 3-4 pages long from students with zero work experience. How? By including everything: coursework lists, a paragraph-long career objective, a personal details section, references, a "Hobbies" section listing "Listening to music, Watching movies, Playing cricket."

A recruiter at a Bangalore startup told us directly: "If a fresher sends me a 3-page resume, I assume they can't prioritize information. That's a red flag for any role."

One page. Always. No exceptions for freshers.

Cut the coursework list, personal details section, hobbies (unless genuinely relevant), references section, and the declaration. If your content still overflows, reduce font size to 10-10.5pt, reduce margins to 0.5 inches, and be more concise in your bullet points.

Mistake #12: Not Including a GitHub or Portfolio Link#

For tech roles (and that's most of what Indian freshers apply for), not having a GitHub link on your resume is a missed opportunity. We asked 15 recruiters at tech companies whether they click GitHub links on resumes. Eleven said yes, especially for freshers.

Your GitHub profile is proof. Resumes claim things. GitHub shows them. A student who says "Proficient in React.js" but has zero React repos looks less credible than one who links to 3 deployed projects.

Before: No links except LinkedIn (which was also not updated).

After: LinkedIn profile URL (customized) + GitHub profile URL + one deployed project URL. All hyperlinked in the resume PDF.

If you are not sure how to set up your GitHub properly, we wrote a full guide: GitHub Profile for Freshers.

Mistake #13: Underselling Projects with Vague Descriptions#

"Built a to-do app" tells the recruiter nothing. What tech did you use? How does it work? What problem does it solve? How many features does it have?

This was one of the most heartbreaking mistakes we found. Students had genuinely impressive projects but described them in one lazy line.

Before: "E-commerce website. Made a basic online shopping site for academic project"

After: "Developed a full-stack e-commerce platform using React.js, Node.js, Express, and MongoDB, featuring user authentication (JWT), product search with filters, cart management, and Razorpay payment integration. Deployed on AWS EC2 with 99.9% uptime over 3 months. GitHub: [link]"

Before: "Weather app. Used API to show weather"

After: "Built a responsive weather forecasting application using React.js and OpenWeatherMap API, displaying real-time conditions, 5-day forecasts, and location-based auto-detection for 200,000+ cities. Implemented client-side caching reducing API calls by 60%."

The difference? Specific tech stack, scale numbers, and measurable outcomes. Even if the "200,000+ cities" is just what the API offers, so frame it that way. It is accurate and impressive.

Mistake #14: Putting "References Available Upon Request"#

Nobody asks for references at the resume stage in India. Definitely not for fresher roles. This line wastes a full line of space and makes your resume look like it was built from a template downloaded in 2008.

Just delete it. Use that line for literally anything else: another skill, another project link, a certification.

Mistake #15: Wrong or Missing File Name#

This is subtle but we noticed it across dozens of submissions. Resume file names like:

• Document1.pdf
• Resume Final FINAL (2).pdf
• resume_updated_new_latest.docx
• Untitled document.pdf

When a recruiter downloads 200 resumes, they see the file names in a folder. "Document1.pdf" tells them nothing and looks careless.

Correct format: Rahul_Kumar_Resume_2026.pdf or Priya_Sharma_SDE_Resume.pdf

Simple. Professional. Identifiable.

The Fix: Run Your Resume Through an ATS Before Applying#

The core problem behind all 15 mistakes is the same: students don't test their resumes against ATS before submitting them. They optimize for how a resume looks on screen, not how software parses it.

According to NASSCOM, Indian IT services received over 7.5 million applications in 2025. With volumes like that, ATS filtering isn't optional. It's the first gate. If your resume doesn't parse correctly, nothing else matters. Not your skills, not your projects, not your CGPA.

Quick Checklist: Fix These Before Your Next Application#

Here's a rapid-fire list. Go through your resume right now and check each one:

• Single-column layout (no Canva templates for applications)
• No career objective. Use a professional summary with keywords
• Technical skills listed with specific tools, languages, and frameworks
• Every bullet point starts with an action verb
• No photo on resume (unless specifically asked)
• No father's name, DOB, marital status, or declaration
• Resume customized for each job description
• Zero typos, checked with Grammarly + human proofreader
• Professional email address ([email protected])
• No irrelevant coursework lists
• One page maximum
• GitHub and LinkedIn links included and hyperlinked
• Projects described with tech stack + numbers + outcomes
• No "References available upon request"
• File named properly: YourName_Resume_2026.pdf

If you are building your fresher resume from scratch, our resume for freshers with no experience guide walks you through every section. And if you want to understand exactly how ATS works and what format to use, read the ATS resume format guide.

Sources & Further Reading#

• Jobscan: 98% of Fortune 500 Use ATS
• CareerBuilder: Resume Mistakes Survey
• TheLadders: Eye-Tracking Study on Recruiter Behavior
• India Skills Report 2025: Wheebox
• NASSCOM: Indian IT Industry Data
• Naukri.com: Resume Tips
• LinkedIn India: Resume Best Practices
• GeeksforGeeks: Resume Building for Freshers
• Harvard Business Review: ATS and Hiring
• AmbitionBox: Salary and Company Reviews