How to Get Experience When Every Job Wants Experience

Nearly every entry-level posting asks for experience, and nearly every way of getting experience asks for a job first. It is a genuine deadlock, and telling students to "just network" is not an answer.

But the deadlock rests on an assumption worth examining: that experience means employment. To a hiring manager, experience is a proxy. What they actually want to know is whether you can take an ambiguous problem, make sensible decisions about it, produce something usable, and explain your reasoning to someone else. Employment is simply the most common way of proving that.

It is not the only way.

What actually counts as evidence

A hiring manager reading your application is trying to answer three questions, in this order:

1. Can this person do the work? 2. Will they be easy to work with? 3. Will they still be here in a year?

Evidence is anything that answers question one without requiring them to take your word for it. In practice that means artefacts: a document, a design, a repository, an analysis. Something they can open.

The strongest evidence has three properties. It is specific — about one real problem, not a survey of your interests. It shows reasoning, not just output, because the decisions you made are more informative than the thing you produced. And it was made under some constraint — a deadline, a brief, a stakeholder who changed their mind — because unconstrained work tells you nothing about how someone behaves when the work gets hard.

What doesn't count, and why

Certificates of completion say you watched something. Course projects where everyone built the same app say you can follow instructions. A portfolio of designs with no explanation of the problem says you can use the software.

None of these are worthless — they're just answering a question nobody asked.

Three ways to produce real evidence without a job

*Solve a problem for a real organisation.* Small charities, local businesses and student societies all have unglamorous problems and no budget. Pick one, scope it yourself, do it properly, and write up what you decided and why. You now have a stakeholder, a constraint and an outcome.

*Do the work the job would ask for, unprompted.* If you want to be a product manager, write the opportunity brief for a product you use, including what you would *not* build and why. If you want to be an analyst, find a public dataset, ask a question worth answering, and answer it. Then have someone who does that job for a living tell you where it falls short.

*Run a structured simulation.* This is why Morrio exists. A simulated internship gives you a company, a brief, a mentor who reviews your work, deliverables due weekly, and — this is the part that matters — a practitioner who reads the result and writes you an honest evaluation. You finish with artefacts and an assessment, not a certificate.

The part most people skip

Whatever you make, get it read by someone who does the job. Not a friend, not a careers advisor, not an AI that tells you it's excellent. Someone who would be your colleague, who can say "this analysis is fine but you never costed the trade-off" and mean it.

Feedback you didn't want to hear is the thing that turns a project into experience.