Games job titles are inconsistent from studio to studio, and the same word can mean quite different things at a ten-person indie and a thousand-person publisher. This guide explains the usual levels, the difference between specialist and management tracks, and what some of the more confusing titles actually involve.
The usual levels
Most UK studios use some version of the same ladder. The names vary, and not every studio uses every rung, but the shape is broadly similar across disciplines.
| Level | What the role usually involves | Broad experience guide |
|---|---|---|
| Intern, placement, apprentice | Learning on the job with close supervision, usually for a fixed period. | Student or no prior industry experience |
| Junior, graduate, entry-level | Well-defined tasks, close review, learning the pipeline. | Roughly 0 to 2 years |
| Mid-level (often no prefix) | Owns features or assets end to end with normal review. | Roughly 2 to 5 years |
| Senior | Owns complex work independently, sets standards, mentors others. | Roughly 5 or more years |
| Lead | Leads a team or discipline on a project, balancing hands-on work and people. | Usually senior experience plus leadership |
| Principal | Top-level specialist, solving the hardest problems across teams. | Extensive senior experience |
| Director, head of | Owns a discipline, department or studio-wide function. | Extensive experience including leadership |
Treat the experience column as a rough guide only. Studios assess what you can do, not how long you have been doing it. A strong developer with three years on a shipped console game may be hired as senior at one studio, while someone with eight years in a narrow role might be mid-level at another. Many listings say "X years or equivalent experience" for exactly this reason.
Junior
Junior roles are where most people start. The studio expects to train you. You will typically be given defined tasks, have your work reviewed closely and be paired with more experienced colleagues. Our graduate schemes and placements guide covers this level in detail.
Mid-level
Often the title has no prefix at all: "Gameplay Programmer", "Environment Artist", "Level Designer". At this level you are trusted to take a feature or set of assets from brief to finish, flag problems early and work with other disciplines without close supervision.
Senior
Seniors handle the hardest work on a team, make technical or creative decisions within their area and are expected to raise the quality of others' work through review and mentoring. A senior is still primarily a hands-on maker.
Lead
A lead is responsible for a team or discipline on a project: for example, the lead animator on a game. Leads plan and assign work, review output, handle line management for some or all of the team and represent the discipline in project decisions. How much hands-on work a lead does varies a lot. On a small team the lead may spend most of the week producing work; on a large one, most of it planning and supporting people.
Principal
Principal is usually a senior specialist title above senior, without the people management of a lead. Principals tackle problems that cut across teams, such as engine architecture, rendering, core gameplay systems or art pipeline, and act as a source of expertise for the studio. Not every studio uses it, and some use "staff" or "expert" in a similar way.
Director and head of
Director titles in games come in two quite different forms. Discipline directors (art director, technical director, audio director) set the vision and standards for a discipline, either on one game or across a studio. Functional directors (studio director, director of production, HR director) run parts of the business. "Head of" titles usually mean ownership of a department or function across a studio, often with budget and hiring responsibility. Whether "head of" sits above or below "director" depends entirely on the company.
Individual contributor versus management
Many studios now offer two parallel routes after senior level:
- The individual contributor (IC) track: senior, then principal or similar, perhaps then a studio-wide expert role. You progress by deepening your craft and widening your technical influence.
- The management track: lead, then manager or head of, then director. You progress by taking on responsibility for people, planning and outcomes.
The existence of an IC track matters. Historically, the only way to progress past senior in many studios was to become a lead, which took good makers away from making. If you love the craft and have little interest in line management, ask at interview whether the studio has a principal or equivalent level, and whether it pays comparably to lead roles. Our studio interviews guide lists other questions about progression.
What "associate" means
"Associate" is one of the most inconsistent words in games titles. You will see three common uses:
- As an entry level, equivalent to junior. "Associate Producer" is very often the first production role, sitting below producer.
- As a step between junior and mid-level, particularly in studios with fine-grained ladders.
- As a step below a senior title, in phrases such as "Associate Art Director" or "Associate Technical Director", meaning someone working under and alongside the director.
Read the responsibilities and requirements rather than relying on the word. If a listing asks for several years of shipped experience, it is not an entry-level role, whatever it is called.
Title inflation and deflation
Titles drift. A small studio may call someone "Head of Art" when they are the only artist, and a start-up may hand out "Lead" titles to early hires. Large studios with formal grading tend to be more conservative, so a senior at a large studio may have broader experience than a lead at a small one. The reverse also happens.
This matters in two ways. When applying, do not rule yourself out because the title is one step above yours; read what the role involves. When describing your own experience, explain scope rather than relying on your title: "led a team of four environment artists on a shipped console game" is clearer than "Lead Environment Artist" on its own. The CV guide covers how to present this.
How to read the level of a job ad
The title is only one signal. Look at these together:
- Requirements: "shipped at least one title", "experience leading a team", "deep knowledge of" all point upwards. "Passion for", "familiarity with" and "a portfolio demonstrating" point towards junior or mid-level.
- Responsibilities: verbs like "own", "define", "mentor" and "set direction" mark seniority. "Support", "assist" and "implement" usually mean earlier-career roles.
- Reporting line: if the listing says who you report to, it hints at where the role sits.
- Salary range: where one is given, it is often the clearest indicator of all. See the salaries guide.
- Interview process: senior roles often include system design discussions, portfolio deep dives or leadership scenarios rather than a basic skills test.
Glossary of commonly confusing titles
| Title | What it usually means |
|---|---|
| Technical Artist | A bridge between art and programming. Builds shaders, tools and pipelines, sets performance budgets and helps artists get their work into the engine efficiently. Often strong in scripting (commonly Python) and in an engine's material and rendering systems. |
| Technical Designer | A designer who builds and scripts gameplay directly in the engine, often with visual scripting or a scripting language. Sits between design and programming and prototypes mechanics without needing engineering support. |
| Development Director | A production leadership role, not a creative one. Responsible for delivery: schedules, budgets, team structure and risk across a project. Common in larger UK studios. |
| Producer | Makes sure the game gets made: planning, coordinating disciplines, removing blockers and communicating with stakeholders. Some producer roles also carry creative or commercial responsibility. |
| Project Manager | Overlaps with producer, but usually focused more narrowly on scheduling, tracking and process, sometimes for a specific team such as art or outsourcing. |
| Live-ops (live operations) | Runs a game after launch: events, content updates, in-game economy changes and service health. Found in production, design and data roles at studios with ongoing online games. |
| UA (user acquisition) | A marketing role that buys and optimises advertising to bring new players into a game, measured on cost and return. Common in mobile. |
| SDET | Software Development Engineer in Test. A programmer who builds automated testing systems rather than testing by hand. Bridges QA and engineering. |
| Build Engineer | Maintains the systems that turn source code and assets into playable builds: build farms, continuous integration and deployment to platforms. Sometimes part of a DevOps team. |
| Tools Programmer | Writes the editors, plugins and pipelines that other developers use every day. A good tools programmer can speed up an entire studio. |
| Gameplay Programmer | Implements the game's mechanics, controls, AI behaviour and moment-to-moment feel, working closely with designers. |
| Engine Programmer | Works on the core technology beneath the game: rendering, memory, physics, streaming, platform support. |
| Systems Designer | Designs the rules, numbers and interlocking systems of a game: progression, economy, combat balance, crafting. |
| Narrative Designer | Shapes how story is delivered through play: quests, dialogue structure, environmental storytelling. Different from a writer, though the roles often overlap. |
| QA Tester / QA Analyst | Finds, reproduces and reports bugs. "Analyst" or "Engineer" often signals more test planning or technical depth. See the QA careers guide. |
| Compliance / Certification | QA specialists who check a game against platform holders' technical requirements before release. |
| Outsource Manager | Manages relationships with external art, animation or development partners: briefs, schedules, feedback and quality. |
| Community Manager | Represents the studio to players on social channels and forums, and brings player feedback back to the team. |
Discipline names on this site
Because studios title roles so differently, we sort every listing into one of a small set of disciplines based on the title, so you can browse like-for-like. A "Technical Artist" appears under art, an "SDET" under QA, a "Development Director" under production. If a title looks mis-sorted, the full listing on the studio's own careers page is always the source of truth. The stats page shows how vacancies are split by discipline over time.
Next steps
- Browse by discipline: programming, art, design, animation, audio, QA, production.
- Starting out? See graduate and entry-level roles and read how to get into games.
- Read the career guides for programmers, designers and QA.
- Understand pay by level in the salaries guide.
- Search every live vacancy on the job board.