How to Show Your Portfolio to Employers

Make it one click away

A portfolio that lives on your laptop is not a portfolio. The work has to be somewhere a stranger can reach in one click, without an account, without a download, and without asking you for anything.

You have a few sensible options and none of them cost money. A shared document with view access for anyone holding the link is the lowest friction and perfectly respectable. A simple one page site works if you already know how to make one. A code hosting site with a clear read me file is right if your project involves code. A PDF attached to an application works too, though it cannot be updated once sent.

Whatever you choose, test it properly: open the link in a private browser window, logged out of everything, on a phone. A link that asks for permission or fails on mobile is worse than no link, because it wastes the reader's goodwill at exactly the wrong moment.

Referencing it on a CV

Do not create a portfolio section that lists five things. One line in the right place is stronger than a wall of links, and readers are scanning.

Put a single link near the top, next to your contact details, and give it a name that says what it is rather than the word portfolio. Then, if the project relates to a role you held, add one line inside that role describing it in plain terms. If it does not relate to any role, a two line projects section near the top is fine.

The line itself should be a fact, not a boast.

The real test is explaining it

Here is the thing that catches people out. The project is not the evidence. Your ability to talk about the project under questioning is the evidence, and the two come apart the moment you did not really build the thing.

Interviewers will not ask you to recite features. They will ask why. Why that approach and not another. What happened when it went wrong. What you would change. Someone who genuinely made the decisions answers those easily and even enjoys it. Someone who pasted a finished thing into a folder starts hedging within two questions.

So rehearse. Not a script, which sounds rehearsed in the bad way, but the shape of the answers.

Here is a write up of a project I built. Interview me about it as a sceptical hiring manager would.
Ask one question at a time. Start easy, then get harder. Push on:

why I chose this approach over an obvious alternative
what happened when it produced a wrong result
what is still manual and why
what I would do differently with more time
After each answer, tell me in one line whether it was specific enough to be convincing, and what was missing.
[paste your write up]

Do that once and you will find the two questions you cannot answer well. Those are the ones you will be asked.

Talking about it without overclaiming

There is a comfortable middle between undercutting yourself and inflating. Aim for it deliberately, because both edges cost you.

Undercutting sounds like it was just a small thing, nothing really. It invites the reader to agree with you. Inflating sounds like I built an AI platform that transformed the process. It invites one specific question that ends the conversation.

The middle sounds like: I had a problem that took two hours a week, I built something that gets it to twenty minutes, one part still needs a human because it made this specific mistake, and here is what I would fix next.

Where else to put it

Mention the project in your covering message in one sentence with the link, rather than describing the whole thing. If you post about your work publicly, post the write up, not a screenshot with a celebratory caption. And when someone in a conversation asks what you have been doing, having one concrete answer ready is worth more than a long list of courses.

Turn this project write up into three versions, all plain and factual:

One sentence for a covering message, including where the link would go
Twenty five words for a CV line
A spoken walkthrough of about ninety seconds, structured as problem, what I built, what went wrong, what I would change
Use only facts from the write up. No adjectives about me. Do not claim any result the write up does not state.
[paste your write up]

Then say the ninety second version out loud, once, to an actual person or an empty room. Reading it silently does not count, and you will hear the sentence you cannot defend the moment you say it.

Here is how I plan to describe my project out loud. Flag every phrase that claims more than the facts support, and every phrase that undersells what I actually did. Give me a plainer replacement for each.
Then tell me the single question an interviewer is most likely to ask after hearing this.
[paste your walkthrough]

Nothing here guarantees an interview. What it does is make sure that when you get one, the strongest thing about you is in the room with you.