Fewer, better pieces, picked for the job you want, with a short story on each. A hiring manager spends a minute or two on a first look, so the first piece has to carry it.
How many pieces should a student portfolio have?
Six to ten. Three great pieces beat ten okay ones. If you find yourself explaining why a piece is weaker, cut it.
What should each piece say?
A few lines: what the problem was, what you did yourself, and what happened. If it was a team project, say which part was yours. People who hire can tell, and they appreciate being told.
What do hiring managers look at first?
The first piece, the way you describe your own work, and whether the site works. A broken link or a portfolio that will not load on a phone ends a lot of first looks.
Should I show process or only finished work?
Both, for at least one piece. Sketches, early versions, and the idea you threw out show how you think. One deep case study and several finished pieces is a good mix.
What about developers and technical students?
Same rules. Two or three projects with a clear README, a live link or a short video, and a line about what you would do next. A pile of tutorial repos counts as homework, not a portfolio.
I do free portfolio reviews for students. See student portfolio reviews.
Answered by Jared Lukes, Minneapolis. Twenty-five years in brand, UX, and technology, currently holding fractional AI and technology seats at three companies. About Jared.