Projects section for freshers (when experience is thin)
How to pick, describe, and order projects on an early-career resume when you do not have years of full-time work yet.
Why projects carry so much weight
If you don’t have years of full-time work, projects are often the proof. Recruiters use them to guess whether you can finish something, explain a tradeoff, and use the tools in the job post. Three solid projects beat eight half-finished repo links.
What counts as a project
- College mini-projects and final-year work you can actually demo or explain.
- Internships tasks you owned end to end (even small ones).
- Personal builds: apps, scripts, designs, research posters, open source PRs.
- Hackathon work, if you can say what you built in 60 seconds.
Copying a tutorial pixel-for-pixel without changing anything is weak. If you followed a guide, say what you added or fixed on top.
How many to list
Two to four is plenty for one page. Lead with the one closest to the role you’re applying for. If two projects teach the same lesson (“I used React”), keep the stronger story and drop the other.
A simple template per project
- Name + one-line purpose (what problem it solves).
- Your role if it was a team (what you owned).
- Stack or tools in plain words.
- 2-4 bullets: built X, fixed Y, measured Z if you have a real number.
- Link only if it works on a stranger’s phone (GitHub, live demo, Notion write-up).
Weak vs stronger lines
Weak: “Worked on a library management system using Java.” Stronger: “Built issue and return flows for a campus library app in Java; stored 200 sample records for the demo defence.” You don’t need fake users. Specifics beat adjectives.
More on wording in the impact bullets guide.
Where projects sit on the page
For most freshers, projects sit after education or after a short internship section. If your internship is thin and your projects are strong, projects can come first. Full layout tips: fresher resume format.
What to leave off
- Every lab exercise from first year.
- Broken links and “coming soon” demos.
- Group projects where you can’t say your part.
- Confidential company work you’re not allowed to describe. Stay high level or skip.