A few questions I have fielded recently in conversation can be distilled down to one question.

"What are the typical roles and responsibilities people hold within the games industry?"

I think it's an important question. One that in particular, people studying games courses should be asking, and then asking themselves where they think they're going to fit in.

I am still surprised, even though it seems to happen all the time, when I talk to people in their last year of games related study that they do not yet have a feeling for the kind of role they want to take up in industry.

I am surprised because I think it is important to know what you want to do so you can focus on breaking down the steps to achieving it. It is also realistic. Most people, and I say most people, myself included, are not good at everything. If you want land work in a competitive, highly engaged workforce you need to put your best foot forward and present your strongest skills and develop them.

To that end here are some of the common roles in the industry. These roles almost always exist on a development team of any size. The only thing that changes is if there are individuals dedicated to the role. On a large team you may have multiple people in these roles, and probably highly specialised people at that. On a small team, you're just going to get people wearing many hats.

Administrative/Business

  • Studio Head. The person ultimately responsible for the studio's direction, culture and commercial outcomes. They balance creative ambition with business reality and represent the studio externally.
  • Producer. The orchestrator of the development process. They manage schedules, budgets, and cross-discipline communication. A good producer removes blockers and keeps the team focused on what matters.
  • Associate Producer. Supports the producer on day-to-day coordination, often owning specific features or milestones. A common entry point into production for people who are organised and communicative.
  • Business Development. Responsible for partnerships, platform deals, publishing agreements and other commercial relationships that keep the studio funded and the game distributed.
  • Marketing Manager. Plans and executes campaigns to build awareness and drive sales. Works closely with community and business development to position the game in a crowded market.

Art

  • Art Director. Sets and maintains the visual identity of the game. They establish the style guide, approve assets, and ensure visual consistency across all content regardless of who created it.
  • Lead Artist. Manages the art team day-to-day, assigns work, reviews output and acts as the bridge between the art director's vision and the individual artists executing it.
  • Concept Artist. Creates the initial visual explorations for characters, environments, props and UI. Their work defines the look before production begins and serves as reference for the 3D and 2D teams.
  • 3D Artist. Builds the models that populate the game world. This can range from characters and creatures to vehicles, weapons and environmental assets. They work in varying levels of fidelity depending on the project.
  • 2D Artist. Handles textures, UI elements, icons, promotional art, and any flat visual content. In 2D games they may be responsible for all visual assets including sprites and tilesets.
  • Animator. Brings characters and objects to life through motion. They create walk cycles, combat animations, facial expressions and cinematics, often working closely with gameplay programmers to ensure animations feel responsive.
  • Rigger. Builds the skeletal structures and control systems that animators use to move characters. Good rigging is invisible but makes the difference between stiff puppets and believable characters.
  • Technical Artist. The bridge between art and programming. They build shaders, optimise assets for performance, create procedural content tools and solve the pipeline problems that neither pure artists nor pure programmers can tackle alone.
  • Environment Artist. Specialises in building the game world itself. They construct levels, landscapes and interiors, often combining modular pieces into larger compositions that feel cohesive and authored.
  • VFX Artist. Creates particle effects, explosions, magic spells, weather systems and other transient visual elements. Their work provides the visceral feedback that makes gameplay feel impactful.

Design

  • Lead Designer. Owns the overall game design vision and ensures all design work is coherent. They make the difficult calls when systems conflict and mentor junior designers.
  • Systems Designer. Designs and balances the interconnected mechanics that form the game's core loops. Economy, progression, combat stats, crafting recipes - if it has numbers and rules, a systems designer is tuning it.
  • Level Designer. Crafts the spaces players move through, placing encounters, pacing challenges and guiding the player with environmental cues. They work at the intersection of art, narrative and gameplay.
  • Narrative Designer. Integrates story into gameplay systems. Unlike writers who craft prose, narrative designers determine how and when story is delivered, designing dialogue systems, branching paths and environmental storytelling.
  • UX Designer. Advocates for the player's experience at every touchpoint. They design menus, onboarding flows, control schemes and feedback systems, ensuring the game is learnable and intuitive without sacrificing depth.
  • Economy Designer. A specialisation of systems design focused on virtual economies. They model resource flows, price goods, manage inflation and ensure the game's economy remains healthy over time, particularly important in live service and multiplayer games.

Programming

  • Lead Programmer. Grizzled veterans that often have a further specialisation but they take on a mentorship role, subsystem and game software architecture, algorithmic design, coding standards, time estimate collation and often the more thorny programming tasks.
  • Gameplay Programmers. They create the rules of the game using tools and subsystems that other programmers build for them.
  • Graphics Programmers. They take the assets that the artists create and decide what to display on the screen each frame, as well as what and how to apply effects.
  • Network Programmers. They are primarily responsible for the sending and receiving of data online. Their primary skill lies on the creation of systems that can allow for latency and still work.
  • Server Programmers. Very similar to network programmers, but more about scale and how to handle and organise huge amounts of data and large amounts of users at once.
  • Tools Programmers. They build the tools used by designers and artists to create the assets for use in the game.
  • User Interface Programmers. They specialize in making the UI work. All of the meters, displays, timers, button prompts, options, overlays in the game are implemented by these people. They also frequently handle localisation.
  • Animation Programmer. Often shared or imparted upon Gameplay Programmers but frequently specialized also, they take on the building or beating of the animation system into submission.
  • Engine Programmer. Works on the core technology that everything else sits on top of. Memory management, file I/O, platform abstraction, build systems - the foundational layers that the rest of the team rarely thinks about until they break.
  • Audio Programmer. Implements the runtime audio systems - mixing, spatialization, streaming, and the interfaces that allow sound designers to hook their work into the game without programmer intervention.
  • AI Programmer. Designs and implements the decision-making systems for non-player characters. Pathfinding, behaviour trees, state machines, and the illusion of intelligence that makes a game world feel alive.
  • Physics Programmer. Implements or integrates simulation systems for rigid bodies, soft bodies, cloth, fluids and destruction. They balance physical accuracy against performance and gameplay feel.

Audio

  • Audio Director. Sets the sonic identity of the game and oversees all audio content. They make high-level decisions about music style, sound design approach, and how audio supports the player experience.
  • Sound Designer. Creates and implements the sound effects that bring the game to life. From footsteps and weapon impacts to ambient environments and UI feedback, they shape what players hear moment to moment.
  • Composer. Writes the music. They create scores that adapt to gameplay, reinforce emotional beats and establish the game's identity. Often working with dynamic music systems that require compositions to be modular and interactive.
  • Voice Director. Oversees the voice recording process, casting actors, directing performances and ensuring dialogue delivery matches the intended tone. On large projects this is a substantial coordination effort spanning many recording sessions.
  • Audio Implementer. The bridge between audio content and the game engine. They set up triggers, configure middleware tools like Wwise or FMOD, and ensure sounds play correctly in context with appropriate spatialization and mixing.

Narrative/Writing

  • Lead Writer. Responsible for the overall story, characters, tone and lore. They create the narrative framework that other writers work within and ensure consistency across all written content.
  • Writer. Creates dialogue, item descriptions, codex entries, barks, cinematics scripts and any other text content. Good game writing is concise, characterful and often operates under severe technical constraints.
  • Lore Writer. Builds and maintains the world's history, mythology, factions and internal logic. Their work provides the foundation that other content creators draw upon to keep the world feeling consistent and deep.
  • Editor. Reviews and polishes all written content for clarity, consistency, tone and correctness. They maintain style guides and catch the continuity errors that slip past writers deep in their own work.

Quality Assurance

  • QA Lead. Manages the testing team, defines test plans, prioritises bugs and communicates quality status to production. They make the call on what is shippable and what is not.
  • QA Tester. Plays the game systematically to find defects. This is far more than just playing - it requires methodical exploration, clear reproduction steps, and the discipline to test the same thing dozens of times after fixes.
  • Automation Engineer. Builds automated test suites that catch regressions without human intervention. Particularly valuable for large projects where manual testing cannot cover every permutation.
  • Compliance Tester. Ensures the game meets platform-specific requirements for certification. Each console manufacturer has extensive technical requirements that must be satisfied before a game can ship on their platform.

Community and Live Operations

  • Community Manager. The voice of the studio to players and the voice of players to the studio. They manage forums, social media, moderate discussions and relay player sentiment to the development team.
  • Live Operations. Manages the game post-launch in live service titles. They plan content cadences, monitor player metrics, run events and ensure the game remains healthy and engaging over time.
  • Customer Support. Handles player issues directly - account problems, bug reports, refund requests and toxicity moderation. The frontline of the player relationship.
  • Developer Relations. Works with platform holders, middleware vendors and external partners. They evaluate new technology, negotiate deals and ensure the studio has access to the tools and support it needs.