Here's the cruel joke at the start of every career: the job wants experience, but the only way to get experience is to get the job. You're standing outside a locked door, and the key is on the other side. Most people respond by waiting — applying anyway, getting ghosted, and slowly concluding that the system is rigged against them. It is a little rigged. But there's a side door, and it's been there the whole time.
The side door is a portfolio. Not the kind a designer or photographer carries — I mean any body of self-made evidence that you can do the work. The thing nobody tells you is that you don't need permission to start producing proof. You only think you do.
Why the experience trap isn't really about experience
When a hiring manager writes "2+ years experience required," they don't actually care about the calendar. They care about one thing: risk. Hiring an unknown person is a gamble, and "experience" is just a lazy proxy for "someone else already vetted this and they didn't blow up."
I've sat on the other side of that desk. When I read a CV, my real question is never "how many years?" It's "will this person do the thing, on time, without me babysitting them?" Years are a weak answer to that question. Shown work is a strong one.
So the goal isn't to fake experience. It's to answer the risk question directly — to hand over evidence so concrete that the recruiter's brain skips the "can they?" step entirely and jumps straight to "when can they start?"
Nobody hires a résumé. They hire a reduction in their own anxiety.
Jan Dvořák, on what hiring managers actually buy
Manufacture credible proof before anyone pays you
Credible proof has three ingredients: a real problem, a real artifact, and a real outcome. "I took a course" has none of these. "I rebuilt a local bakery's booking flow and cut their no-shows" has all three — and notice that nobody had to hire you for it to be true.
The trick is to stop waiting for assignments and start inventing them. Pick problems that are small enough to finish in a weekend and visible enough that someone could imagine paying for the result. Finished and ugly beats ambitious and abandoned, every single time.
- Redo a real company's worst page or process and document the before/after.
- Solve your own annoying problem and write up exactly how you did it.
- Volunteer the work for a nonprofit, a friend's shop, or a student club.
- Recreate a paid product feature and explain the trade-offs you'd change.
- Analyze public data nobody's bothered to look at and publish what you found.
Turn invented projects into believable receipts
A project only counts as proof if a stranger can verify it in under two minutes. That means every piece needs a short, honest writeup: what the problem was, what you decided, what you'd do differently. The thinking is the product — anyone can copy a finished file, but only you can explain why you made the calls you made.
Be specific to the point of discomfort. "Improved engagement" is noise. "Rewrote 14 product descriptions; the client's add-to-cart rate on those pages went from 3.1% to 4.4% over three weeks" is a receipt. Numbers don't have to be huge. They have to be real and yours.
And if a project flopped, say so. "I shipped this, it underperformed, here's my theory why" signals more maturity than a wall of suspiciously perfect wins. Honesty is a credibility multiplier, and almost nobody uses it.
Show your scars. A clean portfolio reads as a junior one.
What I tell every first-time applicant
Build the thing in public so the proof finds you
Here's the leverage most beginners miss: don't build in a drawer and unveil a masterpiece. Build out loud. Post the messy middle — the question you got stuck on, the fix you found, the screenshot of the thing half-working. People don't follow finished work; they follow momentum.
Working in public does two jobs at once. It creates a public trail that a recruiter can scroll, and it occasionally gets you noticed by the exact people who hire. More than one of my hires came from "I saw what you were posting" — never from a cover letter.
Record yourself walking through one project for ninety seconds. Not polished — just you, the artifact, and your reasoning. A short clip of you explaining a real decision does more than ten bullet points, because it proves the rarest thing of all: that there's a thinking human behind the work.
Package it so a busy recruiter can't miss the point
You have roughly twenty seconds before someone clicks away. So your portfolio needs to lead with the conclusion, not the journey. One line at the top — who you are and what you make — then three projects, best one first, each with a one-sentence outcome. That's it. Depth lives one click down, never on the front page.
Don't overbuild the container. A clean single page, a public repo, a Notion doc, a PDF — the wrapper is almost irrelevant. What matters is that the link works, loads fast, and shows the work without a login wall or a maze.
- Pick the three projects that best match the job you actually want.
- Write a one-sentence outcome for each, with a real number if you have one.
- Add a two-minute writeup behind each: problem, decision, result, regret.
- Put your best project first — recruiters rarely reach number three.
- Test the link on your phone, logged out, and time how long it takes to get the point.
Start ugly this weekend
The people who break the experience trap aren't more talented — they just refused to wait for permission. Pick one small, real problem, solve it badly, write down what you learned, and put it somewhere a stranger can see. Do that three times and you'll have something almost no entry-level applicant has: proof. Stop applying into the void and go manufacture your first receipt — the door's been unlocked from your side the whole time.