What actually makes a developer portfolio stand out?
Posted by Big_Baby_9257@reddit | learnprogramming | View on Reddit | 4 comments
I’ve been looking at a lot of junior dev portfolios recently and noticed most of them struggle with the same things:
- unclear project descriptions
- too much focus on tech, not outcomes
- messy structure
What do you think actually makes a portfolio stand out when applying for jobs?
Would love to hear from people who’ve hired or been hired recently.
TwingoSigma@reddit
Whenever I invite programmers for a second interview which is where we want to have a look at some code someone wrote in the past, I tell them they can also show some older code they would not write the same way today.
There are way more information underlying if someone is talking about his faults from the past and the thought processes since then, than looking at some project he specifically built for job interviews.
bootyhole_licker69@reddit
clear problem solved, tiny writeups, real users if possible, no tutorial clones
Dry-Hamster-5358@reddit
Honestly, the biggest thing is clarity
If I can understand what you built, why you built it, and what impact it had in 30 seconds, that already puts you ahead
Good portfolios show thinking, not just code
like what tradeoffs you made, what problems you faced, how you improved things
Also, fewer but deeper projects > many shallow ones, one solid project you can explain well is way better than five random ones
Small things matter too a clean README, a live demo, and not broken links
Most people don’t stand out because they look the same, so even a bit of personality or clear storytelling helps a lot
azian0713@reddit
Clear thought processes for efficiency and scalability, purposeful architecture, edge case testing, clear documentation, examples, test cases, readable code instead of one liners, functionality, complexity, and if it seems they are solving problems on a higher level or addressing singular small problems as they come.