How to List Projects on a Resume
Projects matter most for freshers and career changers without much work history, but they're worth including for experienced candidates too when they demonstrate skills outside the day job.
Where the section goes
For freshers, projects typically sit above or right after education, ranked as highly as work experience. For experienced candidates, a smaller projects section usually goes after work experience, used to show additional or emerging skills.
How many to include
Two to four strong, well-described projects beat six thin ones. Quality and relevance to the target role matter far more than volume — cut anything that doesn't clearly demonstrate a relevant skill.
The structure for each project
Project name, the tech stack or tools used, and 1-2 bullet points describing what it does and any measurable outcome or scale. "Expense Tracker App — React Native, Firebase. Built a mobile expense tracker with category-based budgeting, used by 20+ beta testers" covers all three in two lines.
Link to it if possible
A GitHub repo link or live demo link next to the project name adds credibility a description alone can't. Make sure the linked repo actually reflects the project described — a broken or empty link undermines the whole entry.
Pick projects that match the target role
A project using React and Node.js is more relevant to a web development application than a machine learning notebook, even if the ML project is more technically impressive. Match project selection to what the specific job actually needs.