What you'll learn

  1. Quick answer
  2. The objective statement nobody reads
  3. Projects described as feature lists
  4. Skill bars and inflated lists
  5. Formatting that automated screening cannot read
  6. Length, and what to cut
  7. FAQ

Quick Answer

Keep it to one page, lead with projects rather than an objective, describe what you built and what it achieved rather than listing technologies, and use a single-column layout that automated screening can read. Every line should be checkable.

The objective statement nobody reads

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

Every fresher resume opens with a version of this. It says nothing specific, applies equally to any candidate and any company, and consumes the most valuable space on the page — the part read first.

Replace it with either nothing, or two lines of substance: what you do and what you are looking for. "Final year CSE student. Backend work in Python and Java; built a booking system handling concurrent reservations. Looking for a 2027 new-grad backend role."

That version is specific, checkable, and tells a recruiter within seconds whether to keep reading — which is the only job the top of a resume has.

Projects described as feature lists

This is the biggest missed opportunity, because projects are the strongest thing a fresher has.

Weak: "E-Commerce Website — Built using React, Node.js, MongoDB. Has login, cart, and payment features."

Every reader already assumed those features. Nothing here separates you from the other two hundred applicants with an e-commerce project.

Stronger: "E-Commerce Store (React, Node, MongoDB) — Prevented overselling under concurrent checkouts by reserving stock inside the payment transaction. Live demo · GitHub."

Same project. The second version demonstrates that you met a real problem and made a decision, gives the interviewer an obvious question to ask, and includes a link that proves it exists. Two or three projects at this depth beat six listed by feature.

Skill bars and inflated lists

Two related mistakes. The first is percentage bars or star ratings — "Python 80%" is unverifiable and invites the question of what the other 20% is. Nobody has a shared scale for this. List skills as plain grouped text.

The second is listing everything you have ever touched. A skills section with twenty-five entries including four languages, six frameworks, three databases and Photoshop reads as inflation, and it dilutes the things you are actually good at.

Group them honestly, for instance: Languages — Python, Java, SQL. Frameworks — Django, React. Tools — Git, Docker, Postman. If a skill is on your resume, assume you will be asked about it. Anything you cannot discuss for two minutes should not be there.

Formatting that automated screening cannot read

Many companies run resumes through automated screening before a human sees them. Some formatting choices survive that badly:

  • Two-column layouts — text can be read in the wrong order, scrambling your content.
  • Text inside images or icons — invisible to a parser.
  • Headers and footers holding contact details — frequently skipped entirely.
  • Unusual section names — "My Journey" instead of "Experience" may not be recognised.
  • Sending a .docx or an image — send a PDF unless asked otherwise, and name it Firstname-Lastname-Resume.pdf rather than resume-final-v3.pdf.

A plain single-column layout with standard headings is not boring; it is legible to both a parser and a tired human. Save the design effort for your portfolio site.

Length, and what to cut

One page. As a fresher there is no reason for two, and a second page signals padding rather than experience.

What to cut without hesitation: school marks once you are in final year, your photo, date of birth, marital status, father's name, full postal address, references available on request, and hobbies unless genuinely relevant. Much of this is convention in some Indian resume templates and adds nothing for a technical role — while consuming space that projects need.

What earns its place: education with CGPA if it is strong, two or three projects with links, skills, internships, and any genuine achievements such as contests, publications or open-source contributions.

Then check every claim is checkable. See explaining your project in an interview — everything on the page is fair game, and being unable to defend a line you wrote is worse than never having written it.

Frequently Asked Questions

Should a fresher resume be one page or two? One. Without professional experience, two pages means padding, and it makes the strong content harder to find. Cut rather than shrink the font.
Do I need a different resume for each application? Not a full rewrite, but reordering projects and skills to match the role's emphasis takes minutes and noticeably improves relevance. Keep one master version and adjust it.
Should I include my CGPA? Include it if it is strong or if the companies you are targeting filter on it, which many do for campus roles. If it is weak, leave it off and let projects carry the resume.
Are certifications worth listing? A few relevant ones, yes. A long list of introductory course certificates adds little, because interviewers ask what you built rather than what you completed. One certificate plus one project using that skill is far stronger.
How do I show experience if I have none? Projects are your experience. Describe them the way you would describe work: what the problem was, what you built, what the outcome was. Internships, freelance work, college fest technical roles and open-source contributions all count.