Many developers list every project they have ever built on their resume. A Telegram bot. A web scraper. A color palette generator. A half-finished CLI tool. Even a college weekend "game" never shipped.
This looks like range and initiative. It looks like noise.
The developers getting interviews are not the ones with the most side projects listed. They list the right ones, strategically.
The "I Build Things" Badge Nobody Cares About
Hiring managers in 2026 do not care if you build things. They assume it. You are applying for a software engineering role. Building things is the baseline.
When they see your side projects section, they are asking:
- Whether this person builds things with purpose
- Whether they ship something people use
- Whether their choices show judgment
When you list 12 side projects, most incomplete, most "learning exercises," you demonstrate starting a lot and finishing little. Hiring managers read between the lines.
Three Types of Projects Hurting You
Type 1: The "I was learning X" project
Projects:
- Todo App, built to learn React
- Blog, built to learn Next.js
- CRUD API, built to learn Express
If your project description starts with "built to learn," cut it. This is your learning path. It is not a product. It is not impact. Nobody is impressed by a Todo app built to learn React. They look for what you built with React.
Type 2: The half-shipped project
You listed it. It has a GitHub link. The last commit was 14 months ago. There is no README. No live demo.
Hiring managers click links. When they land on a dead project with 3 commits and a folder named old_backup_DO_NOT_DELETE, it becomes a negative data point.
Type 3: The unfocused everything
A game engine, a recipe app, a crypto tracker, a weather CLI, and an ML model for classifying dog breeds. All on one resume.
Curiosity without direction looks like lack of focus to someone with 8 seconds to scan your resume. You want to look like someone who doubles down, not someone who drifts.
The 1-3 Rule
List 1 to 3 projects maximum. Make each one earn its place.
For each project, it should answer at least one of these:
- Does it have real users? (Even 50 users matters)
- It solved a real problem you had
- It uses tech directly relevant to the target job
- It has been written about, starred, or featured somewhere
If you are unable to say yes to at least one, consider cutting it.
The Template
Project Name, one-line description
Tech: stack
- The problem it solved
- Scale or usage: "500+ active users" or "handles 10K reqs/day"
- What makes it interesting technically
Links: live demo | GitHub
Before: "Taskr, a task management app built with React and Firebase"
After: "Taskr, real-time task manager used by 3 remote teams (12 users). Tech: React, Firebase, Tailwind. Built to solve async communication chaos in freelance work. Added live presence indicators, reducing 'is this done?' Slack messages by ~60%."
The second version has a story. It has numbers. It shows judgment.
Less But Sharper
Developers hesitate to cut projects because it "makes the resume shorter."
Wrong mental model.
A resume is not a portfolio gallery. It is a business case. You are making an argument: "Here is why you should talk to me." Every line not strengthening the argument weakens it.
Cut your projects list to 3 today. Rewrite each one with the template above. Make every line earn its place on your resume. For a quick gut-check, try running your resume through an ATS checker like https://sira.now.
Top comments (0)