The hardest part of a fresher resume is that it has to argue for you without any employment history to argue with. Most freshers respond by padding — listing every course, every workshop certificate, every technology they have ever opened. That makes it worse, because it buries the two or three things that would actually get you a call.
Your resume has one job: survive a scan that lasts a few seconds, and give the reader one reason to open your project. Everything below serves that.
One page. Not a suggestion.
If you have no full-time experience, a second page is almost always padding, and it signals that you cannot tell important from unimportant. Everything fits on one page if you cut the things that are not evidence.
Order that works for a fresher: name and contact, then a short skills line, then projects, then education, then whatever is left — internships if you have them, positions of responsibility, achievements. Projects go above education, because projects are the only part a technical interviewer will actually ask about.
The projects section is your entire resume
Two or three projects, described properly, beat six listed by name. For each, the reader needs to know what it does, what you built it with, and what happened as a result.
The format that works is one line of context and then two or three bullets. Each bullet should say what you did and what changed because of it. And at least one bullet per project needs a number in it — a latency, a count, a percentage, a time saved. Numbers are what separate a resume that reads like a claim from one that reads like evidence.
Weak: 'Made a web app for college fest registration using React and Node.'
Strong: 'Built a fest registration portal (React, Node, Postgres) used by 1,200+ students across 3 days. Moved registration from a shared spreadsheet to a queued API, cutting duplicate entries from ~40 per day to under 5. Added caching that took the schedule page from 4s to 1.2s under peak load.'
Same project. The second one gets an interview, because every clause is checkable and the interviewer already has three questions to ask you.
How to find numbers when you think you have none
Most freshers say their projects have no metrics. They almost always do, and you just have not counted them. Users or testers. Rows or records processed. Time before versus time after. Errors or crashes before versus after. Number of screens, endpoints, or test cases. Size of the dataset. Hours saved per week for whoever used it.
Even 'used by my 60-person class for two weeks' is a real number and beats 'user-friendly interface'. If a number genuinely does not exist, describe a decision and its consequence instead — what you chose, and what it prevented.
The skills line, and how to stop it hurting you
List what you can be interviewed on. Every technology on that line is an invitation to be questioned about it, and getting caught out on something you listed is far more damaging than not listing it.
Group them plainly — languages, frameworks, databases, tools — and drop the self-assessed proficiency bars. Nobody believes a five-star rating you gave yourself, and it wastes space that a project bullet could use.
Cut: MS Office, Windows, 'internet', and any course-completion certificate that has no project attached to it.
The ATS reality, without the myths
Larger Indian employers do filter resumes by keyword before a human sees them. The practical implications are boring: use a single-column layout, use normal section headings like Projects and Education, save as PDF unless told otherwise, and use the same words the job description uses. If the posting says 'REST APIs' and your resume says 'web services', match their phrasing.
What is not true: that you need a special template, that graphics are automatically fatal, or that white-text keyword stuffing works. It does not, and being caught doing it ends the application.
Common mistakes that cost interviews
A photo, date of birth, marital status, or full home address — none of it is expected on an Indian tech resume and it takes space from your projects. An objective line that says you are seeking a challenging role in a reputed organisation; it says nothing and every reader has seen it a thousand times. Listing ten projects at one line each. A GitHub link that leads to an empty profile, which is worse than no link. And typos in the technology names — 'MySql', 'Javascript', 'NodeJs' inconsistently spelled reads as carelessness in a job that punishes carelessness.
One more: do not send the same resume to a service company and a product company without changing the top third. The projects can stay; which ones you lead with should not.
A quick self-check before you send it
Read only the first third of your resume and ask whether a stranger could say what you are good at. Then check that at least one bullet per project has a number. Then read it aloud — anything you stumble over is a sentence you cannot defend in an interview either.
Then get it in front of something that will actually mark it against a role rather than agree with you. placd's resume tools and a free AI mock interview that will ask you about the projects you just listed are at placd.in — the fastest way to find out whether your resume survives contact is to be questioned on it.