Every career guide tells students to "build a portfolio." Few explain what that actually means. A portfolio is not a gallery of everything you have ever made — it is a curated argument that you can do the work someone wants to hire you for.
The 3-project rule
Three strong projects beat twelve tutorial clones. Aim for:
- One project that solves a real problem (even a small one, like a study planner for your own routine).
- One project that shows technical depth (something with a backend, an API, or real data).
- One project that shows polish (good design, clear README, deployed and usable).
Presentation matters as much as code
For each project, write a short case note: what problem it solves, what you built, what you learned. Include a live link and screenshots. Recruiters spend under a minute per project — make that minute count.
What to skip
- Tutorial projects copied line by line, presented as your own ideas.
- A "skills" section listing twenty technologies you touched once.
- Fancy animations that break on mobile. Keep it fast and readable.
Where to host it
A simple personal site is enough. GitHub Pages, Vercel, and Netlify all host static sites for free. Link it from your LinkedIn, your CV, and your freelance profiles.
The maintenance habit
Add to your portfolio as you learn, and remove or refresh old work once a year. A portfolio is a living document, not a one-time assignment. Start with one project this month — done is better than perfect.
