A growing share of hiring managers now expect some form of work sample or project portfolio, even for roles that never used to ask for one. For technical roles, that expectation has a specific shape: a reviewer wants to see real code, a real deployed artifact, or a real dataset and result — not a designed showcase page. Optimizing for the wrong format wastes the exact signal a portfolio is supposed to send.
What a technical reviewer actually checks
- —Does the linked repo or demo actually load and work right now — a broken link is worse than no link
- —Is there a clear README or one-paragraph summary explaining what the project does and why, without requiring the reviewer to read the source to figure it out
- —Does the code quality match what the resume claims — commit history, structure, and tests (or their absence) are read as a signal, whether that's fair or not
- —Is your specific contribution clear on group or open-source work — reviewers assume the whole repo is yours unless you say otherwise
Structure by role
- —Software engineers — a live demo link plus a public repo, with a short architecture note (what it does, what it's built with, one interesting technical decision)
- —Data scientists / ML engineers — a notebook or write-up showing the problem, approach, and result with real numbers, not just a model accuracy score with no context
- —DevOps/SRE — infrastructure-as-code repos or a written case study of a system you designed, since 'live demo' doesn't map cleanly onto this work
- —AI engineers — a deployed RAG or agent project with a brief note on evaluation approach, which doubles as the shipped-project proof covered in the AI career pivot guide
Where the link goes and how it's described
Put the link in your resume header, next to email and LinkedIn — not buried in a "Projects" section at the bottom that a fast first pass never reaches. On the portfolio site or repo itself, lead with a one-paragraph summary a non-expert could understand before the reader has to dig into code, since the first thing most reviewers do is skim, not read line by line.
Prune it as often as you update your resume
A portfolio with an outdated framework version, a dead API key, or a project that no longer represents your current skill level actively works against you — it's read as current work by default. Three strong, working, current projects consistently outperform ten stale ones.
Frequently asked questions
Where should the portfolio link go on my resume?
In the header, next to your email and LinkedIn — not buried at the bottom. If a reviewer is going to click one link, make it easy to find in the first few seconds.
Should I include a portfolio link if I only have work I can't show publicly?
You can still link a portfolio site describing the problem, your role, and the architecture at a level that doesn't violate confidentiality, even without a public repo or live demo. A described, non-public project is still stronger than no portfolio at all.
How many projects should be on it?
Three strong, current, well-described projects beat ten stale ones. Prune regularly — a portfolio with abandoned or broken demos actively works against you.
Building a portfolio project specifically to demonstrate an AI/MLOps pivot? See the AI career pivot resume guide for what that project needs to show. Otherwise, check how your resume references your portfolio with Career Copilot's free resume checker.