A fresher CV has one section that carries it, and it is not the one with your tenth-standard percentage. It is projects. Here is what a recruiter actually does with that section, why most entries there fail, and how to fix yours in an afternoon.
What actually happens to your CV
Somebody spends between six and twenty seconds on the first pass. They are not reading. They are scanning for something to ask you about in the interview.
That means your project section has one job: give them a reason to ask a question. Not to prove you are good. Just to be interesting enough to open.
This changes what a good entry looks like. "Built an e-commerce website using HTML, CSS, JavaScript" gives them nothing to ask. They have seen four hundred of those today.
The four things that make a project worth listing
1. Somebody other than you used it
Even three people. Especially if you can say what broke when they did. "Twelve classmates used it for a semester; two of them found a bug where…" is a story. A tutorial you followed is not.
2. There is a number in it
Not an invented one. Real numbers: how many files it processes, how long it takes, how many records it holds, how many people used it. Numbers signal that the thing ran.
3. You made a decision you can defend
"I used a text file instead of a database because there were only ever going to be about 200 rows and I did not want a dependency." That sentence tells an interviewer more about you than your CGPA does. It shows you thought, rather than followed.
4. Someone can look at it
A GitHub link, or a live URL. A project nobody can see is a claim. With a link, it is evidence — and the difference costs you ten minutes.
How to write the entry
Three lines. No more.
Attendance Tracker — Python, SQLite github.com/you/attendance
Command-line tool that reads a class schedule and computes how many
classes can be missed while staying above 75%. Used by 12 classmates
across one semester. Chose SQLite over flat files after the file
version corrupted when two people ran it at once.Line one: name, tech, link. Line two: what it does, in plain words. Line three: something real — usage, a number, or a decision.
Compare that with what most CVs carry:
Attendance Management System
Technologies used: Python, SQLite, Tkinter
A system to manage student attendance records efficiently.The second version could describe anything. It could describe nothing. It has no link, no number, and the word "efficiently" is doing work it cannot support.
What to cut
- Tutorial clones. The to-do app, the calculator, the portfolio built by following a YouTube series step by step. Everyone has them. Listing them signals you have nothing else.
- "Technologies used" as a list of nine things. Three is confident, nine reads as padding.
- Group projects where you cannot say what you did. You will be asked, and "we all worked on everything" is a bad answer.
- Unfinished projects described as finished. Interviewers open the repo.
How many projects
Two good ones beat six weak ones. Six entries make a recruiter assume they are all shallow, and they are usually right.
If you have exactly one, that is fine in first or second year — as long as it is real and you can talk about it for ten minutes.
If you have nothing yet
You are in the normal position for a first-year, and it is fixable faster than you think.
Pick something small you would actually use. Build the ugliest working version this weekend. Put it on GitHub with a README. Give it to three friends and note what confused them. Fix two of those things.
That is a complete CV entry, and it took a weekend and a bit. It will be better than most of what your batch lists, because most of your batch will list tutorials.
The shortcut that is not a shortcut
Hackathons and competitions do the same job with a deadline attached — which, if you have been meaning to build something since June, is the actual missing ingredient.
They also give you the two things a solo weekend project does not: someone else looked at your work and scored it, and there is a certificate with a verification code that makes the entry checkable. "Shortlisted in round two of a national hackathon" is a line a recruiter can verify, and verified lines are rare on a fresher CV.
It is not magic. You still have to build the thing. But the deadline is what turns "I keep meaning to" into a repository with commits in it.