Here is the number nobody publishing "entry level remote game jobs" listicles will give you: of the 32 remote roles live on this board right now, exactly 2 are entry level or junior. One entry, one junior. Seventeen are mid-level and eleven are senior. That ratio is the actual difficulty of the thing you are trying to do — and knowing it changes the strategy completely.
Why entry-level remote game jobs are rare
It is not gatekeeping. Remote work removes the two things juniors depend on most: overhearing how decisions get made, and being able to turn around and ask. A studio that hires a junior remotely is committing to structured mentorship over video calls, which is expensive. Most studios only do it for disciplines where the work is easy to review asynchronously.
The disciplines that do open up first
- QA and testing — the most common genuine entry point into games, remote or otherwise.
- Community and social — studios hire here on evidence of doing it, not on a degree.
- Player support — real work-from-home roles, though almost always tied to a language and a timezone.
- Data and analytics — junior analyst roles exist because SQL work reviews cleanly over a pull request.
- Production assistance — coordinator roles at studios large enough to have layers.
The disciplines that rarely do
Gameplay programming, engine work, systems design and technical art almost never open at entry level remotely. When those roles say "junior" they usually mean two to three years of shipped work. Applying anyway is not harmful, but it should not be your main plan.
What actually counts as experience
Shipped beats studied
A finished, published game jam entry outranks a half-finished ambitious project every time, and it outranks coursework by a wide margin. "Shipped" is the word studios are scanning for. Three small finished things beat one large unfinished thing.
Contributions to other people’s projects
Bug reports with reproduction steps, a Unity or Godot tool that someone else uses, a mod with installs, a localisation pass on an indie title — all of this is verifiable, and verifiability is the whole problem a junior has to solve.
Adjacent professional experience
Support work anywhere transfers to player support. Any analytics job transfers to game analytics. Moderating a large Discord transfers to community. You may not be entry-level in the way you think you are.
How to apply when you have no shipped title
Apply to the studio, not the aggregator
Job aggregators are useful for finding out that a role exists. Apply on the studio’s own careers page whenever you can — the application actually reaches a human there, and aggregator "remote" tags are frequently wrong.
Send evidence, not adjectives
"Passionate about games" appears in every application in the pile. A two-line note saying which of their systems you took apart, and one link to something you made, does not. Keep it short enough to read on a phone.
Apply early, not perfectly
Remote entry-level listings attract hundreds of applications in the first 72 hours and many studios stop reading after the first fifty. A good application on day one beats an excellent one on day nine. This is why the job board and the weekly alert exist.
Expect a test, and do it well
Entry-level games hiring is unusually test-driven — a QA bug hunt, a support ticket exercise, a short SQL task. This is good news: it is the one part of the process where having no track record does not count against you.
Internships and contracts are the side door
One of the roles currently on this board is an internship and five are contract positions. Juniors dismiss contract work because it is not permanent, which is backwards: a three-month remote contract is the fastest legitimate way to turn "no shipped title" into "shipped title", and studios convert contractors far more often than they hire strangers.
Avoiding the scams that target beginners
Entry-level searchers get targeted hardest. The rules are simple and absolute: a real studio never asks you to pay for training, equipment or a "certification"; never sends a cheque to buy your own laptop; never conducts the whole hiring process on Telegram; and never asks for bank details before a signed offer. If you are looking at tester work specifically, read what is real and what is a scam in games tester jobs from home before applying anywhere.
Frequently asked questions
Can I get a remote game job with no experience at all?
Realistically, not with literally nothing. But the bar is lower than a degree — a finished jam game, a documented mod, or a portfolio of bug reports is enough to be taken seriously for QA, community and support roles.
Do I need a games degree?
No. It helps with a first interview and stops mattering entirely after your first shipped title. Studios hiring remotely weight portfolio and written communication far above credentials, because they cannot assess you across a desk.
How many applications should I expect to send?
Being honest about the ratio above: if two of thirty-two live roles are junior-friendly at any moment, a realistic search runs for months, not weeks. Set up alerts, apply within a day of a role appearing, and keep shipping small things in the meantime — the portfolio work is what shortens the search.
Is remote worse for a first games job?
For learning speed, on-site or hybrid is genuinely better if it is available to you. If it is not, choose the remote studio with the most structure — written documentation, a named mentor, regular one-to-ones — over the one with the best-known name.
Where to start
Filter the live board by experience level to see what is open at entry and junior right now, and read how to get a remote job in the games industry for the longer version of the application strategy.