Topic: Resume & LinkedIn

Resume mistakes that get freshers rejected (including by ATS)

Updated · 5 min read · Resume & LinkedIn

Most fresher resumes are rejected for fixable reasons: a layout that applicant tracking software (ATS) can't read, skills that don't match the job description, vague project descriptions, listing skills you can't defend in an interview, and careless errors. An ATS is software many companies use to store and filter applications; if it can't read your resume or doesn't find the job's key terms, a recruiter may never see it. Fix the mistakes below and your resume becomes both machine-readable and convincing to the person who reads it next.

How applications are usually screened

For many fresher roles, your resume goes through two filters:

  1. Software filter. The ATS extracts text from your file and may rank or filter candidates by keywords, eligibility (degree, year, location) and knockout questions in the application form.
  2. Human skim. A recruiter scans the top results quickly, looking for the role's must-have skills and something concrete that proves them.

Each mistake below fails one or both filters.

1. Fancy templates that the software can't read

Two-column layouts, tables, text boxes, headers and footers, icons for phone and email, and skill bars look nice but often scramble when software extracts the text. Your skills might land in the middle of your address, or disappear.

Fix: use a single-column layout, standard section headings ("Skills", "Projects", "Education"), and real text for contact details. Save as a text-based PDF (not a scanned image) unless Word is requested.

2. Skills that don't match the job description

If the job asks for "REST APIs, Spring Boot, MySQL" and your resume says "web development, backend, databases", both the software and the recruiter may miss the match.

Fix: read the job description, note the exact terms for skills you genuinely have, and use those terms in your skills line and project bullets. Don't copy skills you don't have; you'll be asked about them.

3. Keyword stuffing

The opposite mistake: pasting long lists of technologies, or white-text keywords, to fool the software. Recruiters notice instantly, and interviewers ask about every item.

Fix: list only what you can answer basic questions on. A short, honest skills section with proof in your projects beats a long one.

4. Vague project descriptions

"Developed a website using HTML, CSS and JavaScript" tells the reader almost nothing. Neither does "Worked on a machine learning project".

Fix: say what the project does, who it's for, what you personally built and what you learned or achieved. Our guide on how to write projects on a resume shows the formula with examples.

5. A generic objective at the top

"To work in a challenging environment where I can utilise my skills for the growth of the organisation" appears on thousands of resumes and uses your most valuable space.

Fix: replace it with a two-line summary: your target role plus your strongest proof. For example, "2026 IT graduate targeting QA automation roles; built a Selenium and TestNG suite of 40 automated tests for a college e-commerce project."

6. Too long, or padded with irrelevant details

Two or three pages, a photo, date of birth, father's name, religion, a "Declaration" paragraph, hobbies taking half a page. None of these help an IT recruiter decide, and some are personal details you don't need to share.

Fix: one page. Skills and projects first, education brief, achievements only if relevant. Drop the declaration and personal details.

7. Claiming skills you can't explain

Listing "Machine learning, AWS, Docker, Kubernetes, React, Angular" after a single tutorial each is risky. Interviewers often pick the most impressive item on your resume and ask you to explain it.

Fix: for every skill listed, be ready to explain a basic concept and where you used it. Move "familiar with" items to a separate, honest line or remove them.

8. Spelling, grammar and formatting errors

Typos in "Javascript", inconsistent date formats, random bold text, three different fonts. For a role that values attention to detail, these suggest the opposite.

Fix: read the resume aloud, use a spell checker, check every date and heading is consistent, and ask a friend to proofread.

9. Unprofessional contact details

An email like "rockstar_rahul99" or a missing phone country code can hurt you before anyone reads further.

Fix: use a simple firstname.lastname style email, a reachable phone number, and links to your LinkedIn and GitHub that actually work.

A GitHub link that leads to empty repositories, or a portfolio that doesn't load, undermines everything else.

Fix: pin your best two or three repositories, add short READMEs, and click every link in your resume before sending.

11. Sending the same resume everywhere

A resume tuned for "software developer" sent to a QA automation role reads as a mismatch.

Fix: keep a master resume and spend ten minutes tailoring the summary, skills order and project order for each role. The fresher resume format guide includes a layout that makes this easy.

A quick self-check before you apply

CheckYes / No
Single column, standard headings, text-based PDF
Fits on one page
Skills match the job description's terms (honestly)
Every project says what it does, what I built, what I learned
I can explain every skill listed
No typos, consistent dates and fonts
Professional email, working links
Tailored summary for this role

Frequently asked questions

Can an ATS read PDF resumes?

Most modern systems read text-based PDFs well. Problems usually come from complex layouts or scanned images, not from the PDF format itself. If an employer asks for Word, send Word.

Should I use online "ATS score" checkers?

They can catch formatting problems, but don't chase a score by stuffing keywords. A clear resume that honestly matches the job matters more.

Does a resume photo hurt?

For most IT roles in India it adds nothing and takes space. Leave it out unless an employer specifically asks for one.

How often should I update my resume?

Whenever you finish a project, internship, certification or achievement. Keeping it current means you can apply quickly when a good opening appears.