GDnD Wiki

GDnD Wiki

This site is for Ulster University students and staff. Enter the class access password to continue.

Game Designer Specialisations

9 min read

Summary

“Game designer” is a catch-all title that on large console and PC projects fragments into a wide spectrum of specialist roles. These specialisations emerge because projects are too large and complex for any one person to own all design decisions. Understanding which roles exist — and what temperament each demands — helps students choose a direction and helps teams structure their design departments effectively.

O’Connor is clear that these descriptions are not universal standards; studios define and bundle responsibilities differently. The list below reflects common industry practice as of 2021, focused on console/PC development (O’Connor, The Craft and Science of Game Design, see source-craft-and-science-game-design).

Key ideas

The designer’s actual job

Before cataloguing roles, O’Connor makes a foundational point: the designer’s job is not primarily to have clever ideas. “Ideas are easy, execution is the tough part.” Most developers can generate game concepts. What separates a professional designer is the ability to:

  • Collect and evaluate ideas from the whole team
  • Communicate them consistently across disciplines
  • Shepherd features through the full production cycle to a polished, functional state
  • Edit ruthlessly — culling what does not belong

Arrogance about being “the source of all good ideas” is, in O’Connor’s experience, the most common early-career mistake (O’Connor, The Craft and Science of Game Design, see source-craft-and-science-game-design).

Specialist roles

Individual contributor roles

Tech Designer Has a programming background alongside design interest. Manipulates game data, updates live-service server content, and creates gameplay content without requiring full engineering support. Acts as an interface between design and programming teams. Distinct from a gameplay programmer, who writes engine-level code rather than designing through data.

Character Designer Often artist-trained. Responsible for player characters and NPCs: concept art, animation design, backstory, voice direction, and the specific gameplay of each character. Common on heavily character-driven genres (brawlers, MOBAs, PvP titles). Specialises in making characters memorable through personality, recognisable behaviours, and visual appeal.

Interface Designer Creates the layout and functionality of the UI — colours, animations, information hierarchy, and logic flow. Requires 2D art skills and works closely with programmers to integrate assets. The core challenge is presenting all necessary information without visually competing with the game world.

Menu Designer A UI subspecialty focused on complex menu systems: matchmaking flows, progression management, consumable screens. Needs both aesthetic sensibility and strong information architecture thinking.

System Designer Designs gameplay systems and features: progression systems, crafting, combat mechanics, vehicle handling. Typically carries a feature from concept through prototyping to Alpha and Beta, working with a small dedicated art/programming pair. Must be both analytically rigorous and capable of championing their features with conviction while remaining willing to critically evaluate their own work.

AI Designer Defines the requirements and behaviours of AI opponents, allies, and background processes. Maps out the total NPC “population” and coordinates with level design on distribution. Some AI design is less about individual opponents and more about background processes that drive moment-to-moment experience and meta-loops. Increasingly common as games rely on complex or varied AI behaviours.

Bossfight Designer A specialised AI designer focused on individual boss encounters, which are effectively mini-games requiring custom environments, bespoke animations, unique effects, and multi-phase gameplay systems. Bossfights are expensive to polish and increasingly warrant dedicated expertise on larger projects.

Combat Designer Designs the complete combat system for all genres — weapons, moves, powers, spells, and how they interact. Often overlaps with AI design and level design. Requires deep expertise in balancing, mathematics, statistics, random number generation, and comparative analysis to prevent exploits and ensure no play style dominates unfairly.

Balance Designer Maintains a living knowledge of the entire game’s balance scheme when the feature set becomes too large for individual designers to self-balance. Particularly critical in MMOs and live-service games where patches and new content constantly perturb the established meta. Relies on community feedback, independent testing, and comparative analysis. Sometimes brought in near the end of production as an objective outside eye.

Economy Designer Often has formal training in economics. Creates and maintains the in-game economic system — marketplaces, resource loops, loot systems, player auction houses, and price adjustment mechanisms. Critical for free-to-play and MMO titles. Requires knowledge of how online markets behave under player pressure, as paper economies behave differently from live ones.

User Experience (UX) Designer Versed in ergonomics, visual language, and usability. May have a psychology or visual design background. Ensures a unified interaction standard across all menus and modes. A growing specialism in VR design, where physical and psychological demands make UX errors costly.

Level Designer Creates the spaces where gameplay occurs — concepting layouts, greyboxing, enemy placement, obstacle placement, reward placement, critical pathing, and visual language. May have an architecture background. Works closely with an environment artist to make spaces visually consistent. Level designers frequently outnumber system designers on large console projects, where content volume is enormous. Operates to tight, methodical deadlines.

Environment Designer Distinct from level designers: focuses on dressing existing level geometry with art assets — lighting, interior decoration, landscaping — to make the world feel authentic. Often comes from the art side. Common on open-world and large 3D projects where location-specific set-dressing supports narrative and visual signposting.

Story/Narrative Designer A professional writer specialising in interactive dialogue, NPC interaction systems, and scripted cinematics. Often involved in designing the dialogue system itself. May script and produce in-engine cutscenes. Frequently has input on environment and level design to ensure settings support the story. (See also narrative-design.)

Quest Designer Common in MMOs and open-world games with large content demands. Responsible for quest dialogue, flow, branching, scripted triggers, NPC populations, and loot/reward values. Live-game quest design requires ongoing familiarity with community behaviour and analytics.

Encounter Designer Designs individual enemy encounters — both scripted and procedural — across complex open or populated worlds. Expert in all AI behaviour types, pacing techniques, and the use of balance systems to match encounter difficulty to player ability. Creates the peaks and valleys of engagement that sustain player experience over long play sessions. (See also game-loops and interaction-loops.)

Scripting Designer Technical-leaning designer who builds game content through scripting tools — cinematics, events, quests, AI behaviour trees. Exists on a spectrum between pure designer and gameplay programmer depending on the studio. Some studios treat scripting as the core job of all designers; others treat it as a programming subspecialty.

Leadership and management roles

Production Designer Combines producer and designer responsibilities: allocates resources to features while making informed judgement calls about whether the production cost of a feature is justified by its gameplay value. An unusual hybrid that depends heavily on how a studio structures the boundary between creative and production authority.

Creative Director Sets the overall creative vision. Writes vision documents and presents to stakeholders at all levels, from junior team members to publishing management. Does not generally detail individual systems — that hands-off quality is why some lead designers prefer not to move into this role. Requires strong public communication skills, market awareness, and the ability to translate complex design ideas to non-designer audiences.

Design Director Head of the design department. Ensures design quality across all projects under the studio, supervises lead designers and lead level designers, and makes calls on scope and schedule issues. Distinct from creative director in having formal managerial responsibility for the design department — including, on larger studios, multiple simultaneous projects.

Principal Designer A senior individual contributor track for experienced designers with no interest in management. Leads documentation standards and is responsible for gameplay quality but holds no hiring, firing, or disciplinary authority. Provides a career path for senior designers who want depth rather than breadth.

Design Manager A pure management role. Interviews and hires designers for all projects, tracks individual performance, manages careers, and is responsible for department morale and effectiveness. Works with production to place the right people on the right projects. Does little or no actual design work.

In practice

For students and early-career designers, O’Connor recommends reflecting on personal temperament and skills before defaulting to “I want to be a game designer”:

  • Enjoy systems and data analysis? Look at system design, balance, or economy.
  • Strong writer? Narrative or quest design.
  • Programmer with design instincts? Tech design or scripting.
  • Interested in architecture and spaces? Level or environment design.
  • Want the broadest creative ownership? Aim for lead or creative director — but expect the journey to take years of hands-on specialised work first.

Studios vary enormously in how they label and bundle these roles. A small indie studio may have one person doing the jobs of system designer, level designer, and balance designer simultaneously. A large AAA studio may have ten quest designers on a single project. The titles are signposts, not rigid definitions.

Evidence

O’Connor grounds these descriptions in personal experience across multiple mid-to-high-end console/PC projects spanning more than two decades (from the early 1990s to the time of writing in 2021). He acknowledges explicitly that “different studios load different responsibilities on each type of designer” and that VR, mobile, and social contexts bring their own distinct demands (O’Connor, The Craft and Science of Game Design, see source-craft-and-science-game-design).

Implications

  • For students: Knowing which specialisations exist prevents the false assumption that all design work is the same. Early exposure to different design disciplines in coursework (systems, levels, narrative, balancing) helps identify natural strengths.
  • For team formation: Even on small teams, thinking in terms of specialised concerns — “who owns balance? who owns narrative?” — prevents important responsibilities from falling through the cracks.
  • For career planning: The split between individual contributor tracks (principal designer) and management tracks (design director, design manager) means there is a legitimate senior path that does not require moving into management.

Graph View

Backlinks