Remote studios lean on your portfolio harder than on-site ones do. There is no whiteboard, no walk to the coffee machine, no chance for someone to get a feel for how you think. The portfolio has to do all of it — and most junior portfolios are built to show that you finished something rather than to show how you work.
What a junior portfolio is actually for
Not to prove you can make a game. To prove you can be handed a task and left alone with it.
That single reframe changes what belongs in it. A polished demo with no explanation proves you finished something once. A modest project with a clear breakdown of the decisions, the problems and the fixes proves you can be trusted with work.
Five projects that actually demonstrate something
- One finished, shipped small game. A jam entry counts. "Finished" is the word studios scan for, and three small complete things beat one large unfinished thing.
- One systems piece. An inventory, a save system, a state machine, an ability framework. Something with architecture you can defend.
- One performance piece. Take something slow and make it fast. Show the profiler before and after. This is the single most underused portfolio item at junior level.
- One tool. An editor extension that saved you time. Tools work signals that you think about other people’s workflow, which is exactly what remote teams need.
- One contribution to something you did not start. A mod, a plugin, a pull request. It proves you can read someone else’s code, which is what you will spend your first six months doing.
The presentation problems that sink good work
A playable build beats a video, and a video beats screenshots
Host a WebGL or downloadable build if the project allows. Reviewers have minutes, not hours, and anything that adds friction loses. A sixty-second video with the interesting part first is the fallback.
Write the README as if the reader is busy and sceptical
What it is, what you built versus what came from a template or asset pack, one hard problem and how you solved it, and what you would change now. That last line signals more maturity than anything else on the page.
Be explicit about what is yours
Nothing damages credibility faster than a reviewer recognising a store asset presented ambiguously. Using asset packs is completely normal. Being unclear about it is not.
Show the code
A public repository is standard for programming roles. Reviewers genuinely open them. Tidy the structure, remove the commented-out blocks, and write commit messages that read like a person wrote them.
What remote studios check that on-site ones might not
- Written communication. Your README and commit history are a work sample for a remote job, because remote teams run on written context.
- Whether you finish things. Unfinished work is a much bigger red flag when nobody can see you working.
- Whether you can explain your own decisions. Expect to walk someone through a project over a call — that conversation is often the whole technical interview.
Frequently asked questions
How many projects should a junior portfolio have?
Three to five, all finished, each showing something different. A long list of half-built prototypes reads worse than three complete small things.
Do game jams count?
Yes, and they are among the strongest items available to someone with no credits. They prove you scope, finish and ship under pressure — which is the actual job.
Should I include university coursework?
Only if it is genuinely good and you can separate your contribution from the brief. Coursework where everyone built the same thing demonstrates little.
Do I need a personal website?
Something with a stable URL that loads fast and works on a phone. A clean itch.io page plus a tidy GitHub beats a slow custom site.
How do I get a portfolio reviewed?
Discord communities around specific engines and disciplines are the most reliable free route. Ask for one specific thing rather than "any feedback" — you will get far better answers.
Next steps
Once your portfolio is ready, be realistic about the market you are entering — the entry-level guide is honest about how few junior remote roles exist. Check what band you are actually in with the seniority calculator, and browse live remote roles filtered by experience level.