Career & Portfolio
What Recruiters Actually Check on a Developer Portfolio
Recruiters scan portfolios in minutes, not hours. Here is the real checklist they use, the failure modes that end candidacies, and what to fix first.
Let's start with how portfolio review actually works, because most advice assumes a fantasy version. A recruiter or hiring manager opens your portfolio with six other tabs open, gives it a few minutes, and forms an impression. They're not reading your code. They're not clicking every project. They're scanning for signals — and the absence of signals is itself a signal.
The 5-minute scan, in order
- First 30 seconds: does this look like a real person? A name, a face or clear identity, a one-line description of what you do. Anonymous or template-looking pages lose here.
- Next minute: the project list. They're counting and skimming titles. Two to four substantial projects beat twelve tutorial clones. They're looking for variety and depth, not volume.
- Next two minutes: one project, opened. They pick the most interesting one. Does it have a live demo? A README that explains it? Screenshots? This is the moment of truth — most portfolios fail right here.
- Final stretch: the person behind it. About page, contact info, GitHub link. Can they reach you? Does the GitHub show real activity?
The checklist that matters
- Live demos that actually load. A dead link is worse than no link — it suggests nothing here is maintained.
- READMEs that explain. What it is, how to run it, what it demonstrates. Thirty seconds of reading should be enough.
- Evidence of decisions. Commit messages, a decisions section, documented trade-offs. This separates builders from typists.
- A way to contact you. Email visible without a scavenger hunt. This is shockingly often missing.
- Consistency. The portfolio, GitHub, and resume should tell the same story about who you are.
Failure modes that end candidacies
The most common isn't a weak project — it's friction. Broken links. Demos that need five setup steps. A portfolio that only works on desktop. A contact form that goes nowhere. Every point of friction is a reason to close the tab, and there are always other tabs.
The second most common: everything looks the same. Five CRUD apps with different color schemes tell a reviewer you can follow tutorials, not that you can solve problems. One genuinely original project outweighs five interchangeable ones.
What to fix this weekend
If you have four hours, spend them in this order: (1) fix every broken link and dead demo; (2) write a proper README for your best project; (3) add a visible contact email; (4) cut your weakest two projects — curation is a skill. That's it. A small, working, contactable portfolio beats a large, broken, anonymous one every time.
Your portfolio's job isn't to show everything you've built. It's to make one busy person think: I'd like to talk to this developer.
For the construction side — actually building the thing — see How to Build a Strong Developer Portfolio. And ZEVQYN's Portfolio Builder can help you structure project pages that follow the patterns above.