Most people get their first games job through a placement, an internship, an apprenticeship or a carefully targeted junior application rather than a formal graduate scheme. This guide explains how each route works in the UK, when to apply, and what makes an entry-level candidate stand out.
Why "graduate scheme" means something different in games
In banking, accountancy or the civil service, a graduate scheme is a structured programme: a single intake each year, rotations through departments, a cohort of peers and an application window that opens and closes on fixed dates. Very few UK game studios work like that. Most studios are small or mid-sized, hire against specific projects, and recruit when a team needs someone rather than on an annual cycle.
That has two consequences. First, the entry-level market is spread across several different kinds of opportunity, and you need to look for all of them. Second, timing is less predictable than in other industries. A studio may open three junior programmer roles in March because a project has just been greenlit, then hire nobody new for a year. The candidates who do well are the ones who are ready with a portfolio or CV when those roles appear, not the ones waiting for a scheme to open.
Larger publishers and platform holders with UK offices are the main exception. Some run formal graduate intakes, often in programming, QA or business functions, and these do tend to follow a yearly pattern. They are competitive and worth applying for, but they are a small slice of the total.
The main entry routes
Year-in-industry placements
Many UK degrees offer an optional sandwich year between the second and final years, spent working full time at an employer. In games, placements are most common in programming, QA, production support and occasionally art and design. A placement is usually paid, lasts around twelve months, and is assessed by your university as part of your degree.
The value of a placement is hard to overstate. You return to your final year having shipped work, used a professional pipeline and built references, and a good number of placement students are offered a job on graduation. If your course offers the option, take it seriously from the start of your second year.
Summer internships
Summer internships typically run for eight to twelve weeks between academic years. They are less common in games than in tech generally, and are more likely to appear at larger studios. Under UK law, an intern who is doing real work for the company is usually a "worker" and entitled to at least the National Minimum Wage. The gov.uk guidance on employment rights for interns sets out the rules. Be cautious about any unpaid "internship" that involves producing work for a commercial product.
Graduate programmes
Where formal graduate programmes exist, they are usually at publishers, large multi-site studios or platform holders. Expect an online application, often a technical test or portfolio review, one or more interviews and sometimes an assessment day. Rotations across teams are more common in business, data and production programmes than in craft disciplines like art or animation.
Apprenticeships
Apprenticeships combine paid work with structured training, and you do not need a degree to start one. In England they are organised by level:
- Level 2 (intermediate) and Level 3 (advanced): equivalent to GCSE and A level respectively. In games these sometimes appear in QA, IT support or junior digital roles.
- Levels 4 and 5 (higher): equivalent to the first years of a degree. Software development and data apprenticeships at this level are increasingly used by studios.
- Levels 6 and 7 (degree): equivalent to a bachelor's or master's degree, with the qualification paid for through the employer.
Scotland runs Modern Apprenticeships and Graduate Apprenticeships, and Wales and Northern Ireland have their own schemes. Official listings are on gov.uk for England, with equivalent services run by the devolved governments. Games apprenticeships are still relatively uncommon, so if a studio near you offers one, it is worth applying early.
Junior and entry-level roles
For most people this is the real route in. A role titled "Junior Programmer", "Junior Artist", "Associate Designer" or "QA Tester" is, in practice, the graduate job. These are advertised year-round and do not care whether you graduated last month or three years ago. Our guide to games job titles explains how studios use "junior", "associate" and "graduate" differently, and the QA careers guide covers testing as a starting point.
When to apply
Because studios recruit against projects, there is no single deadline to aim for. There are still patterns worth knowing:
- Placements: roles starting in the summer or September are often advertised from the previous autumn through to spring. Start looking at the beginning of your second year, and talk to your university placement team early.
- Summer internships: generally advertised in winter and early spring. Larger companies may close applications well before Easter.
- Formal graduate programmes: where they exist, these tend to open in early autumn for the following year's start. Check company careers pages from September of your final year.
- Junior roles: any time. Studios often hire more after a funding round, a publishing deal or a project moving into full production, which you cannot predict. Checking listings regularly matters more than any calendar.
A practical approach for final-year students is to apply for any junior roles that fit from around January onwards, while keeping your portfolio current. Most junior roles want someone who can start within a month or two, so applying in October for a role that starts in August rarely works unless the listing says so.
How to find opportunities
Entry-level roles are scattered, so use several channels at once:
- Live listings. We pull vacancies directly from UK studios' own careers pages every day. The graduate and entry-level page collects roles whose titles mark them as junior, graduate, intern, placement or apprentice.
- Studio careers pages. Our directory of UK studios lists every studio we track. Bookmark the careers pages of the ones you would most like to join, including those not hiring right now.
- Your university. Placement offices often hold relationships with local studios that never advertise publicly.
- Events and game jams. Industry events, student showcases and jams are where studio staff meet new talent. Jams also produce portfolio pieces with a deadline, which is excellent practice.
Courses, competitions and initiatives worth knowing
University courses
The UK has a large number of games-related degrees, and quality varies. Courses with strong industry ties tend to share some traits: staff who have worked in studios, team projects that mimic production, guest talks from developers, and a track record of placements. Abertay University in Dundee is the best-known example, with a long history of games education and close links to the city's studios. Many other universities across England, Scotland, Wales and Northern Ireland run respected programmes; ask any course you are considering where its recent graduates now work.
Ukie
Ukie is the trade body for the UK games and interactive entertainment industry. It publishes careers information, runs student-focused activity, and operates Digital Schoolhouse, a programme that brings computing and games into schools. Its resources are a reliable starting point for understanding how the industry is structured.
Grads in Games and Search for a Star
Grads in Games is a long-running initiative aimed at students and recent graduates. Its Search for a Star competition sets challenges in disciplines such as programming and art, judged with input from studios. Entering is worthwhile even if you do not place: the challenges are designed around what studios test for, and the finished work can go straight into your portfolio.
Into Games
Into Games is a not-for-profit focused on widening access to games careers, particularly for people from under-represented backgrounds. It runs programmes, workshops and resources for people at the start of their careers, including those not on a games degree.
How to stand out as an entry-level candidate
Studios hiring juniors are not expecting a finished professional. They are looking for evidence that you can learn quickly, work in a team and finish things. The candidates who stand out tend to show the following:
- Finished, focused work. Three polished pieces beat ten half-finished ones. A small game that is complete and playable says more than an ambitious prototype that crashes. Our portfolio guide goes into detail.
- Relevance to the studio. If a studio makes mobile puzzle games, a portfolio of photoreal environments is less persuasive than stylised, readable art. Tailor what you lead with.
- Evidence of teamwork. Group projects and jams count. Say clearly what you did, which tools you used and what you would do differently.
- Industry-standard tools. Familiarity with the engines, art packages and version control that studios use (for example Unity or Unreal, and Git or Perforce) shortens your onboarding.
- A short, specific application. A one-page CV and a few sentences on why this studio and this role. Our CV and cover letter guide has templates and examples.
A useful test: could a lead at the studio look at your application for two minutes and know what you would be good at on their team? If not, cut and refocus until they could.
Discipline-specific notes
- Programming: show C++ or C# code, ideally in a public repository with readable commits. Gameplay systems, tools and small engines all work. See the programming careers guide.
- Art and animation: show process as well as finals: wireframes, texture breakdowns, blocking passes.
- Design: show playable levels or systems, with short write-ups explaining the intent and what playtesting changed. The design careers guide covers this.
- QA: clear, well-structured bug reports from games you have tested are a strong addition to a CV.
What to expect once you start
The first months in a junior role are mostly about learning the studio's pipeline: how work is assigned, how it gets reviewed, how builds are made and how bugs are tracked. Expect to work on small, well-defined tasks at first, to have your work reviewed closely, and to be paired with a more experienced colleague. That is normal and a sign of a well-run team, not a lack of trust.
A few things are worth checking before you accept an offer:
- Is the role permanent, fixed-term or tied to a single project?
- Who will you report to, and how often will you meet them?
- How does the studio handle overtime, and is it paid or given back as time off?
- Is there a probation period, and what does passing it involve?
- What does progression from junior to mid-level look like here?
Our guide to interviewing at a game studio includes more questions to ask, and the salaries guide explains how to read the pay ranges studios advertise.
Next steps
- Browse current graduate, junior and entry-level roles.
- Look by discipline: programming, art, design, QA.
- Read how to get into the games industry for the wider picture.
- Find studios near your university in the guide to UK games hubs or the full studio directory.
- See every vacancy on the job board.