Resume Writing6 min readMay 3, 2026By Temburu Akhil

How to List Projects on a Resume (With Examples for Developers)

For students, freshers, and developers, the Projects section is often the most powerful part of the resume. But most people write it wrong — listing tools used without showing impact. Here is how to make your projects stand out.

Why Projects Matter

Projects demonstrate practical ability in a way that grades and certifications cannot. A functioning deployed application or a well-structured GitHub repository tells a recruiter far more than a certificate from an online course. For freshers, projects are often the deciding factor between getting shortlisted and being rejected.

Which Projects to Include

Prioritize projects that are: (1) relevant to the role you are applying for, (2) deployed or publicly accessible, and (3) involve the technologies listed in the job description. Do not include tutorial projects (like a to-do app) unless you added significant custom functionality.

  • Personal projects built to solve a real problem
  • Final year or semester projects with measurable results
  • Open source contributions (even small ones)
  • Hackathon projects (include your placement if you won)

How to Format Each Project Entry

Each project entry should have: (1) Project name — in bold, possibly with a link. (2) Tech stack — listed below the name in italics. (3) 2-3 bullet points describing what you built, key features, and measurable outcomes.

Writing Strong Project Bullet Points

Weak: "Built a web app using React and Node.js." Strong: "Developed a real-time collaboration tool serving 200+ concurrent users, using WebSocket and Redis pub/sub for sub-50ms message delivery." The strong version answers: what was built, what tech was used, and what was the scale or impact.

Where to Put the Projects Section

For freshers and early-career developers (0-3 years): put Projects right after Education, before Work Experience. For experienced engineers: put Projects after Work Experience. If your projects are stronger than your work history, lead with them regardless of seniority.

Linking to Your Work

Always include a GitHub link or live demo URL for your project. Before submitting any application, check that your GitHub repositories are public, have a clear README, and the code is reasonably clean. A recruiter clicking a broken link or an empty repo is worse than not linking at all.

TA

Temburu Akhil

Author & Developer

Temburu Akhil is a software engineer and the creator of Build Resume. He builds career-tech tools and writes data-driven guides to help job seekers optimize their resumes, pass Applicant Tracking Systems (ATS), and land their dream roles.

Ready to build your resume?

Use Build Resume — free, ATS-optimized, and takes less than 15 minutes.