What we actually look for in a junior developer's portfolio
When we review a portfolio — for a hire, a contractor, or just for feedback — a few things separate the ones that get a reply.
When we review a portfolio, for a hire, a contractor, or just because someone asked for feedback, a few patterns show up again and again in the ones that get a reply.
One real project beats five tutorials
A to-do app cloned from a course tells us you can follow instructions. A small, finished, slightly ugly project you built to solve your own problem tells us you can ship. We'll always pick the second one to talk about in an interview.
Show the mess, not just the demo
A live link is good. A live link plus two sentences on what broke and how you fixed it is better, it's the fastest way to show how you actually think, not just what you can copy.
Fewer projects, more finished
Three complete, deployed, readable projects outperform ten half-built repos every time. If something isn't finished, either finish it or leave it off, an unfinished project on a portfolio reads as a red flag, not a work-in-progress.
None of this requires more talent. It requires picking fewer things and actually finishing them, which, honestly, is most of what building anything comes down to.