The cruel little loop of every job search: you need experience to get hired, and you need to get hired to get experience. Here is the exit — you do not need a client to do the work. You need a project.
The trick: invent the client, do the real task
A portfolio is not proof someone paid you. It is proof you can do the thing the job needs. So pull up the job description you are chasing, find the task it leans on hardest, and build one sample that mirrors it. Hiring managers are not checking receipts — they are checking whether you can do the work in front of them on Monday.
There are four reliable ways to make a sample without a single client: spec work (do a task as if briefed), a redesign (fix something that already exists and explain why), a mock case study (a real-shaped problem with your solution), and a personal project (something you actually wanted to exist). All four are legitimate. All four show impact, not just activity.
"Skilled in data analysis and visualization. Proficient in Excel and SQL."
"I pulled 3 years of open Toronto transit data, cleaned it, and built a dashboard showing which bus routes run latest. Here is the chart, the SQL, and the one thing it surprised me with."
What a sample looks like in your field
Pick the one that matches your target role and steal the shape of it:
- Writing / marketing: rewrite a confusing product page, then a short note on what you changed and why. Or write three sample emails for a brand you admire.
- Design: redesign one screen of an app you use daily. Show the before, the after, and the problem you were solving — not just that it looks nicer.
- Data / analytics: grab an open dataset, ask one real question, answer it with a chart. Public data from Job Bank or your city's open-data portal works.
- Software: build a small, finished thing — a tip calculator, a habit tracker — and ship it somewhere clickable. Done beats clever.
- Sales / ops / admin: write the SOP, the outreach sequence, or the spreadsheet you would build in week one. Process is a portfolio too.
- Trades / hands-on: photos of a build or repair, with a line on the problem and how you solved it. A clean before-and-after is a case study.
Make it a story, not a screenshot
A sample with no context is just a thing. A sample with a three-line story is evidence. Use this for every piece, whether it is code, a chart, or a redesign:
The problem: [Company X]'s signup page asked for 9 fields and lost people.
What I did: Cut it to 3 and moved the rest to after signup.
Why it works: Fewer fields, less friction, more finished signups — here is the redesigned screen.
That is the whole game. Problem, move, result. It reads like real work because it is the shape of real work.
One honesty rule
Label spec and mock projects as exactly that. "A self-directed redesign concept" or "sample project, not affiliated with the brand" is one honest line that protects you and still shows every ounce of skill. You lose nothing by being clear it was self-initiated — initiative is the flex. Red flags are information; so is unprompted hustle. Yours points the right way.
Do not wait for permission, a brief, or a perfect idea. The first sample is allowed to be small. The point is one finished thing a stranger can click and judge — and they will judge it kindly, because most applicants send nothing at all.
Open the job description you want most, find the one task it relies on, and start a single sample that mirrors it — a redesign, a chart, a rewrite, a small build. Finish a rough version this week and write the three-line story (problem, move, result) underneath it. That is a portfolio of one. It is enough to start.
Useful: Government of Canada Job Bank for real job descriptions to mirror and free open data to build with.
Comments