How to get into the UK games industry: a practical guide

Career guide · Updated 14 Oct 2026 · 8 min read

There is no single front door into the UK games industry, but there are a handful of well-worn routes that work. This guide sets out what they are, what studios look for at entry level, and how long breaking in tends to take.

Start with the job, not the industry

"Working in games" covers dozens of distinct careers. A studio the size of Rockstar North in Edinburgh or Playground Games in Leamington Spa employs gameplay programmers, environment artists, animators, level designers, producers, audio designers, QA testers, user researchers, data analysts, community managers, marketers, HR and finance staff. A twenty-person indie studio needs many of the same skills, just spread across fewer people.

The single most useful thing you can do early on is pick a discipline. Studios do not hire generalist "game makers" at junior level; they hire a junior programmer, a junior 3D artist or a QA tester. Your portfolio, CV and the skills you practise all follow from that choice. If you are unsure what the roles actually involve, our guide to games job titles explained breaks down what each one does day to day.

A quick way to test a discipline is to make something small in it. Spend a weekend scripting a mechanic in Unity or Unreal, modelling a prop in Blender, or writing a one-page design for a level. The work you enjoy finishing is usually a better guide than the job title that sounds most exciting.

Degree or self-taught?

Both routes produce working developers. Neither guarantees a job. What matters to a hiring manager is the quality of what you can show them, but the routes get you there in different ways.

When a degree helps

Before committing to a course, ask the admissions team which studios recent graduates now work at, what engines and tools the modules use, and how much of the final year is spent on portfolio-quality team projects. Vague answers are a warning sign.

When self-taught works

Art, animation, design, audio and QA are all disciplines where a strong portfolio regularly outweighs the lack of a degree. Free and low-cost learning is plentiful: Unreal and Unity both publish extensive official tutorials, Blender is free, and engine communities are large and helpful. The risk with self-teaching is gaps you do not know you have. Counter it by seeking feedback early from working developers, joining critique communities, and comparing your work honestly with the portfolios of people already doing the job you want.

Apprenticeships

A small number of UK studios offer apprenticeships in areas such as programming, art and QA, letting you earn while you train. They are competitive and not offered every year, so check studio careers pages directly and use the government's find an apprenticeship service.

The main routes in

Junior roles in your discipline

This is the most direct route: apply for junior programmer, junior artist or junior designer positions with a portfolio that shows you can already do a useful slice of the job. Junior roles are fewer than mid-level and senior ones at most studios, which is why the competition is stiff and why portfolio quality matters so much. Our portfolio guide covers what each discipline should show.

Graduate schemes and placements

Some larger studios and publishers run structured graduate programmes or year-long industrial placements, often with a fixed annual recruitment window. These are worth planning around if you are still studying. See our guide to graduate schemes in UK games for how they work and when to apply.

Quality assurance

QA is the entry point many developers took. It teaches you how games are built, how builds break and how a studio's teams fit together, and it puts you inside the building where internal moves happen. It is a legitimate career in its own right, not just a stepping stone. Our QA careers guide covers it in detail.

Adjacent roles

Community management, player support, localisation, marketing and IT are all real jobs inside studios. People who join in these roles and build skills on the side do sometimes move into development, though you should take such a job because you want to do it well, not purely as a back door.

Build evidence: jams, mods and small finished games

Studios want proof that you can finish things and work with other people. Three of the best ways to produce that proof cost nothing.

Whatever you make, document it. A short page per project explaining the goal, your role, what went wrong and what you would change tells a hiring manager far more than a download link on its own.

Networking without the awkwardness

Many junior hires happen because someone at the studio already knew the applicant's work. Networking in games is less about handing out business cards and more about being visible and useful in the community.

Events worth knowing

Organisations that help newcomers

Online, done well

Post your work in progress regularly in the places your discipline gathers. Ask specific questions ("does this walk cycle read as heavy enough?") rather than general ones ("how do I get a job?"). Give feedback to others. Over months, people start to recognise your name, and that recognition is what turns a cold application into a warm one.

What studios look for in a junior

Studios hiring at entry level are not expecting the finished article. They are looking for signals that you will become productive quickly and be easy to work with.

Do and don't

DoDon't
Pick a discipline and build depth in itPresent yourself as able to do "a bit of everything"
Show three to five strong, finished piecesPad your portfolio with coursework you are not proud of
Apply directly through studios' own careers pagesSend identical CVs to every vacancy you can find
Tailor each application to the studio's gamesOpen with "I have loved games since I was five"
Ask working developers for specific feedbackAsk strangers for a job in your first message

Realistic timelines

Breaking in usually takes longer than people expect, and that is normal rather than a sign you are failing. A rough shape for someone starting from scratch:

  1. Months one to six: learning fundamentals, making small exercises, finishing your first tiny projects.
  2. Months six to eighteen: building portfolio-quality work, doing jams, getting regular feedback, starting to network.
  3. The search itself: once your portfolio is genuinely ready, a junior job search commonly runs for several months, with many applications and some rejections along the way. Graduate cycles add their own timing.

Use rejections as data. If you are not getting interviews, the portfolio or CV is usually the problem. If you get interviews but no offers, look at how you are presenting and discussing your work; our guide to studio interviews can help. Keep making things while you apply: a portfolio that improves month by month is noticed when you reapply.

Where the jobs are

UK studios cluster in recognisable hubs: Guildford, Leamington Spa, Brighton, London, Cambridge, Manchester, Sheffield, Newcastle and Sunderland, Dundee and Edinburgh, Cardiff and Belfast among them. Moving to a hub widens your options, but remote and hybrid roles also exist. Our guides to UK games hubs and remote work in games cover both, and the jobs over time page shows how live vacancy numbers move across the UK.

Next steps