How to write the projects section on a fresher resume

On a fresher resume the projects section is where the hiring decision is made, and it is also the section most consistently written badly. The common failure is describing what the project is instead of what you did and what resulted.

A project entry has four parts: what it does, what you built it with, what you specifically contributed, and one measurable outcome. Missing the fourth is what makes a project read like a tutorial you followed.

Two well-written projects beat five thin ones. If a project cannot carry a real outcome line, it is usually better left off.

Section order

Top to bottom. The order matters more than the styling, because it decides what a reader sees in the first few seconds.

Project titleDescriptive, not cute. 'Bus tracking app' beats 'TrackIt'.
Stack lineTechnologies used, comma separated, on one line.
What it doesOne sentence stating the problem it solves.
Your contributionExplicit if the project was a team effort.
OutcomeThe line most people omit. Users, accuracy, latency, records, time saved.
LinkA repository or a live URL. Clicked more often than people expect.

What has to be on the page

One measurable outcome per project.
Your specific contribution named on any team project.
A live link or repository, with a README that explains how to run it.
The stack on its own line so a keyword screen finds it and a human can skip it.

Bullets in the right shape

Bracketed values are placeholders. Substitute your own real figures, and leave a line out entirely rather than inventing a number for it.

[Project name] — [React, Node, Postgres]. [What it does in one sentence]. Built [the specific part you built]; [outcome with a number]. [link]

Weak: 'Developed an e-commerce website using MERN stack with login, cart and payment features.'

Strong: 'E-commerce storefront (MERN). Built the cart and checkout flow including Razorpay integration; handled 1,400 test transactions with a 0.4% failure rate during the college demo week.'

Mistakes that cost this profile interviews

Instead ofListing features instead of outcomes: 'has login, cart, admin panel, payment gateway'.

Do thisFeatures describe the tutorial. State what it achieved, for how many people, measured how.

Instead ofTeam projects with no indication of your contribution.

Do thisName your part explicitly. A reader assumes the vaguest reading otherwise, which is rarely flattering.

Instead ofFive projects at one line each.

Do thisKeep two or three and give them room. Depth is what is being assessed, not count.

Instead ofA GitHub link to a repository with no README and one commit.

Do thisWrite the README and commit properly, or drop the link. An empty repository is worse than none.

Free template for this format

Terminal — Gives each project a stack line and room for an outcome, with monospaced accents that suit technical projects. Hand-designed, and the PDF and Word exports are free with no watermark and no card.

Use the Terminal template Score a resume you already have

Questions

How many projects should I put on a resume?

Two or three, described in depth. Five one-line entries read as a course completion list. If a project has no outcome worth stating, leaving it off usually strengthens the page.

Can I put college assignments as projects?

Yes, provided you describe your own contribution and an outcome. Label them honestly. An assignment written well beats a personal project written badly, though having at least one self-directed project is a meaningful signal.

Should I include a GitHub link for every project?

Include it where the repository is presentable, meaning a README, a sensible commit history and code you are willing to have read. A link to an empty repository does active harm.