How to Build a Portfolio When You Have No Work Experience

The advice to "build a portfolio" is given far more often than it is explained. For someone with no employment history it raises an obvious question: a portfolio of what?

Quantity is the wrong target

The instinct is to show everything — every course project, every hackathon, every certificate. This works against you. A reader spends about two minutes on a portfolio, and twelve items means twelve seconds each, which is not long enough for any of them to land.

Three pieces, each with its reasoning attached, beats twelve pieces with none.

What a piece needs to contain

Not just the artefact. The artefact is the least interesting part, because AI can now produce a plausible version of almost any artefact in minutes, and every reader knows it.

What cannot be faked as easily is the account of how you got there:

- The brief. What was the actual problem, in one paragraph, including the constraint. - What you tried that did not work. The single most persuasive thing you can include, and the one almost nobody includes. - The decision you were least sure about, and what you chose in the end. - What you would do differently. Evidence that you can evaluate your own work, which is most of what being managed well requires.

A mediocre artefact with this attached is more convincing than an excellent artefact without it.

Where the work comes from when nobody is assigning it

Four sources, roughly in order of how much they prove:

*Real problems for real people.* A local business, a student society, a family friend's spreadsheet that takes them four hours a week. Unglamorous and worth more than anything invented, because someone else's need supplied the constraint.

*Teardowns of things that exist.* Take a product you use and write the analysis you would write if you worked there. Cheap to start, and it demonstrates judgement directly.

*Work simulations.* A structured brief with deadlines and feedback, which supplies the constraint you cannot easily manufacture alone. This is what Morrio's internships and capability challenges are — you finish with artefacts and an assessment rather than a certificate.

*Course projects, reframed.* Not useless, but only if you can say what you would have done differently given the brief the assignment did not give you.

What to leave out

Certificates of completion. Group projects where your contribution is indistinguishable. Anything where the reader cannot tell which decisions were yours. Tutorial projects that thousands of people have built — a hiring manager has seen that same weather app many times.

The part people get wrong last

Portfolios are usually organised by artefact type, which is how the maker thinks. Organise by problem instead, which is how the reader thinks. "How I decided what to cut from a launch" is a better heading than "Product Documents", because the first one tells a reader whether to keep reading.