How many projects a beginner's portfolio needs

The short answer

Two or three. More isn't needed; fewer is thin.

The reason is mundane: whoever reviews your CV spends a few minutes on it. They'll open the first link, maybe the second. They will never reach the tenth.

Why quantity doesn't work

Ten average projects convey scatter, not diligence. The reader sees someone who started a lot and apparently finished little.

Three finished projects with working links say the opposite: this person carries things through. For a beginner that's the most valuable trait, because not finishing is the standard failure.

Choosing the three

The first is your strongest. The one closest to the job you want. That's the one they'll open.

The second is about something else. It shows range: if the first is about interfaces, make the second about data or automation.

The third is a team project. Even a small one. It answers the question that otherwise goes unanswered: can you work with people.

That set answers three things at once: do you build, are you versatile, can you collaborate.

What to do with the rest

Don't delete them, don't display them. Pin the ones that matter and simply leave the rest off your CV.

Coursework repetitions are best hidden entirely: they add nothing and blur the impression.

When quantity does matter

One case: contributions to open projects. There, more merged changes is better — it shows consistency and the ability to work to someone else's rules. Those count differently from your own projects.

What matters more than number

Depth of the story. An interview will spend twenty minutes on a single project: why that storage, how you solved this, what you'd change now.

Someone with one project they can discuss in detail beats someone with ten they describe in the same vague terms.

So it's better to invest properly in one — finish it, deploy it, document it, build part of it with someone and get your contribution confirmed — than to spread yourself across five.