The 60-second answer
Put 2 to 3 projects on a fresher resume. That is enough to show range without pushing past one page or burying your best work under filler. Each one needs a stack, a couple of bullets, an outcome, and a link. If you have more, keep the top three on the resume and let the rest live on your GitHub. Quality wins: three polished projects beat six half-finished ones.
"How many projects?" is really a question about focus. Recruiters spend seconds per resume and judge your best work, so the goal is not to list everything you have built, it is to show two or three things that prove you can build, clearly. This guide covers the number, the reasoning, what counts, and how to write each one.
The number: 2 to 3
For almost every fresher, two to three projects is the sweet spot. Two shows you can do more than one thing; three lets you show a little range (say, a full-stack app, a data project, and a small tool). Beyond three, each additional project steals space and dilutes the strong ones. Fewer than two and you look thin. So aim for two, stretch to three if all three are genuinely good.
Why not more, why not fewer
- One page: a fresher resume should be one page, and projects share it with education, skills, and experience.
- Attention: recruiters skim. Three strong projects get read; six get skimmed and none land.
- Depth: fewer projects means more room to describe each with a stack, bullets, and an outcome.
- Signal: your best two or three define you. Weak extras drag down the average.
What counts as a real project
A resume-worthy project:
- Solves a real problem, not a copied tutorial or a generic to-do app.
- Names a clear tech stack you can be questioned on.
- Shows an outcome or scale figure (users, records, time saved, accuracy).
- Links to a GitHub repo or a live demo, so it is verifiable.
Not sure which of your builds qualify? The side-projects guide walks through picking and framing them, and the GitHub profile guide covers the links.
How to describe each one
Weak
Made a food delivery app.
Stronger
Built a food-ordering web app (React + Node + MongoDB) with cart, auth, and order tracking; handled 200+ test orders with sub-200 ms API responses. GitHub link.
Name the stack, add a number, and link it. Two or three bullets per project, each opening with a verb and ending with a result. See how to quantify achievements.
A sample 3-project lineup
Here is what a strong two-to-three project section actually looks like for a CSE fresher. Notice the range, one full app, one data project, one small tool, and how each carries a stack, a number, and a link:
Store API (full-stack)
Node.js, Express, PostgreSQL, JWT
Built a REST API for a mock storefront with token auth, cart, and Stripe test payments; covered by 40+ Jest tests and documented with a Postman collection. github.com/you/store-api
Bengaluru AQI Dashboard (data)
Python, Pandas, Streamlit
Cleaned two years of public air-quality data and built an interactive dashboard; deployed on Streamlit Cloud with ~120 monthly visits. Live demo linked in the repo.
PDF Toolkit CLI (tool)
Python, Click
A 200-line command-line tool that merges, splits, and compresses PDFs; published to PyPI with 300+ downloads.
Three projects, three flavours, each explainable in an interview and verifiable in one click. That spread is exactly what "two to three" is for: enough range to look versatile, not so much that your best work gets buried.
Projects that quietly hurt you
Some entries add nothing, or actively drag down the two or three that matter. Cut these first:
- Tutorial clones: the same to-do app, weather app, or Netflix clone every batchmate submits. Recruiters have seen 500 of them.
- Projects with no README and no link, a recruiter cannot tell what it does or whether it runs.
- A long list of tiny lab assignments padded to look like a portfolio.
- Anything you cannot walk through in an interview, if you cannot explain a design choice, leave it off.
Every weak project you remove makes your strong ones stand out more. Editing down is part of the work.
What if you have none yet
If your GitHub is empty, do not pad the resume, build one genuinely useful thing this week. Automate a task you actually do, or analyse a public dataset from a source like data.gov.in, and document it with a proper README. One real project you can talk about beats three you cannot. While you build, the internship resume guide covers how to fill the rest of a one-page resume with coursework, skills, and activities, and the side-projects guide helps you pick something worth building.
Frequently asked questions
How many projects should a fresher put on a resume?+
Two to three strong projects. That is enough to show range without pushing your resume past one page or diluting your best work. Each project should have a stack, two or three bullets, an outcome, and a link. Three polished projects beat six half-finished ones every time.
Is one project enough on a fresher resume?+
One excellent project is better than three weak ones, but aim for at least two so you can show a little range. If you genuinely only have one strong project, list it well and add a smaller second one (a script, a small tool, a data analysis) rather than padding with tutorial clones.
Can I list more than three projects?+
Rarely worth it on a one-page fresher resume. Extra projects steal space and attention from your best ones. Keep your top three on the resume and let the rest live on your GitHub, which you link in the header. Recruiters judge your best work, so lead with it.
What makes a project resume-worthy?+
It solves a real problem (not a copied tutorial), names a clear tech stack, shows an outcome or scale figure, and ideally links to a GitHub repo or live demo. A to-do app everyone builds adds little; a tool you built to solve an actual annoyance, with a user count or a metric, stands out.
Where should projects go on a fresher resume?+
For a fresher with no internships, projects are the centrepiece, so place them prominently, right after education and skills. If you do have internship experience, projects come just after it. Either way, they should be easy to find, not buried at the bottom.
How do I describe a project in one line?+
Name plus stack, then bullets that each open with a verb and close with a result. For example: "Built a Django expense tracker (Python, PostgreSQL) used by 30 classmates; cut manual splitting time by ~80%." Lead with what you did, end with the outcome.
Do college or group projects count?+
Yes, if the work is real and you can explain your specific contribution. For a group project, name what you personally built ("designed the database schema and the auth flow"), not just the team outcome. A final-year major project is often the strongest thing a fresher has, so give it space. What does not count is a lab exercise everyone in your batch submitted identically.
Should I list a project that is still unfinished?+
Only if the finished part already works and demos well. A half-built app with a broken deploy link hurts you. If the core feature runs, describe what it does today (not what you plan to add), push a clean README, and link the working demo. An honest "v1" beats an aspirational README describing features that do not exist.
Where do project links go if I have no room?+
Put one clean GitHub link in your header (github.com/yourusername) and let the individual repos hold the detail. You do not need a separate link on every bullet if your pinned repos are easy to find. The header link plus well-pinned repos is enough for a recruiter to verify your best two or three.
Put your best projects on a clean resume
Free to start, no sign-up. A one-page, single-column, ATS-tested layout that keeps your top projects front and centre.