Freshers

9 Resume Mistakes Freshers Make (and How to Fix Each One)

No work experience is not the problem. These nine habits are — and every one of them is fixable in an afternoon.

8 min readPublished 19 July 2026

A fresher resume is judged on potential and evidence of ability, not tenure. The most common mistakes are not about lacking experience — they are about burying the evidence that does exist.

1. An objective that says nothing

Weak

Seeking a challenging position in a reputed organisation where I can utilise my skills and grow with the company.

Strong

Final-year Computer Science student (CGPA 8.7) with internship experience in React and Node.js. Looking for a full-stack developer role where I can build user-facing products.

The first version could belong to anyone. The second states a field, a level, evidence, and a target role in one sentence.

2. Listing coursework instead of projects

Every CS graduate took Data Structures. Nobody is impressed by the syllabus. What differentiates you is what you built with it — so give projects their own section, with what it does, what you used, and a measurable outcome.

Weak

Course project on machine learning.

Strong

Crop-yield predictor — trained a gradient-boosting model on 12 years of ICAR rainfall and yield data (Python, scikit-learn); 87% accuracy, deployed as a Streamlit app used by 40+ students.

3. Rating your own skills out of five

Star ratings and percentage bars ("Python ████░ 80%") are subjective, unverifiable, and invisible to an ATS, which reads the bar as nothing at all. Group skills by category as plain text instead, and let projects demonstrate depth.

4. Writing duties instead of achievements

Weak

Responsible for managing the college technical fest.

Strong

Coordinated a 3-day technical fest for 1,200 attendees; raised ₹2.4 lakh in sponsorship and led a 15-member volunteer team.

5. Going past one page

With under three years of experience, one page is the expectation. A two-page fresher resume signals padding. Cut school details if you have a degree, cut unrelated hobbies, and cut anything you would not want to be asked about.

6. An unprofessional email address

cool_rahul_007@example.com undermines everything above it. Use firstname.lastname@ some mainstream provider. It takes two minutes and it is the cheapest credibility you will ever buy.

7. Including personal details that invite bias

Photo, date of birth, marital status, father's name, full residential address — none of these are expected on a modern Indian resume for a corporate role, and all of them take up space that projects should occupy. City and state is enough.

8. One resume for every application

You do not need to rewrite from scratch, but the summary and the skills order should change per role. If the JD leads with SQL and data modelling, those belong above your React work — even if React is what you enjoy more.

9. Typos, and inconsistent formatting

  • Read it backwards, sentence by sentence — it breaks the habit of reading what you meant to write.
  • Check that every bullet in a section ends the same way (all with full stops, or none).
  • Check date formats are identical everywhere.
  • Have one other person read it. They will catch what you cannot see any more.

The order that works for freshers

  1. Contact details
  2. Short summary (2–3 lines)
  3. Education — while you are a fresher, this outranks experience
  4. Projects — usually your strongest evidence
  5. Internships / work experience
  6. Skills, grouped by category
  7. Certifications, positions of responsibility, achievements