Blog4 min read
How to build a portfolio when you have no experience
The problem is almost never that you have nothing to show. It is that you have already ruled out everything you have.
What counts as experience?
Work you did, not work you were paid for. Coursework you took further than the assignment required, a small analysis of a public dataset, something you built because it annoyed you, a club or volunteer project with a real deadline and a real audience: all of these demonstrate the same things a job would, which is framing a problem, choosing an approach, and defending a conclusion.
The reason people discount this work is that they know how it came about, and they assume a reader will too. A reader does not. What they see is a finished thing and a description of the thinking behind it, and the thinking is the part they are actually assessing.
The exception is anything you did not really do. Following a tutorial to the end is not a project, and a reader who has seen the same tutorial will recognise it immediately. If you extended it, changed the data, or broke it and fixed it, that is the part worth writing about, and the tutorial is just where you started.
Which projects are worth including?
The ones you can talk about for ten minutes without preparing. That is the whole test, and it is more reliable than any judgement about how impressive something looks, because an interview will consist almost entirely of someone asking you to talk about it for ten minutes.
Three of those beat nine you listed. A reader's impression is set by the weakest item you included, so a strong project sitting next to two thin ones is a strong project you have chosen to discount yourself. This is uncomfortable when your list is already short, and cutting is still the right move.
How do you write about work nobody paid for?
Give the context honestly and then move on. Labelling something as a course project, a personal experiment, or volunteer work costs you nothing, and it is far better than a reader working it out for themselves, because at that point they start wondering what else was framed generously.
Then write the part that is actually interesting: what you were trying to do, what you chose, and what it cost you. "Built a dashboard in Python" describes an afternoon. "Worked out that the metric the club had been tracking all year could not answer the question they were asking, and proposed one that could" describes someone worth interviewing.
Resist inflating the scale. Nobody is fooled by a solo project described in the language of a team, and the deflation when the truth arrives is worse than the modest version would ever have been. Small and precisely described reads as confident. Vague and grand reads as neither.
When is a portfolio not worth building yet?
When you would have to pad it. A page with one real thing and three fillers is worse than a good resume on its own, because it invites a judgement you were not ready for and it makes the one real thing look like the best of a weak set. If you are not there yet, the honest answer is to go and make one more thing rather than to build the page around what you have.
It is also fair to say that for a lot of graduate schemes and large-company application processes, the screening step does not look at a personal site at all, and your effort is better spent elsewhere. A portfolio pays off where a human is choosing between candidates and wants a reason, which is smaller companies, contract work, and anything where you are applying directly rather than through a funnel.
When you are ready, the build is not the hard part. DebutPage takes the resume you already have and drafts the page from it in about two minutes, and publishing is free, so the cost of having one is your judgement about what goes on it rather than a weekend of work.
The short version: You are not short of things to show. You are short of things you have given yourself permission to describe properly.