On this page
How many projects you need
The sweet spot is 3–5 finished projects of varying complexity. More isn't always better: 3 polished, well-explained projects make a stronger impression than 10 unfinished ones.
Which projects to include
🧩One simple oneShows basic command of syntax and logic (like a converter or calculator).
⚙️One more complex oneWorking with an API or several interconnected features shows architectural thinking.
🎨One visually polished oneEven simple logic looks more convincing with a clean interface.
💡One original ideaA project outside of any course curriculum shows initiative and genuine interest in development.
How to present your portfolio well
- Put the code on GitHub with a clear README explaining what the project does.
- Deploy a working demo that can be opened in a browser without downloading the code.
- Briefly describe which technologies were used and what problems were solved.
- Remove unfinished or broken projects from your public portfolio.
Frequently Asked Questions
Do I have to put my code on GitHub?
Strongly recommended — it's the standard way for a recruiter or technical interviewer to see your code before the interview.
Should I include course projects?
Yes, if you've finished and extended them yourself — that's a normal part of an early-career portfolio.
What's next
Build a portfolio out of real projects
The JavaScript course is built around practical assignments that become a ready-made portfolio.