“Game designer” is the vaguest job title in the industry, which is exactly why Liz England wrote this field guide in 2014. The same title covers wildly different work depending on studio size, genre, platform, and whether a studio even has a design department.

Her map runs in four bands:

  • Generalists — Designer, Junior/Associate, Senior, Lead, Creative Director. The larger the studio, the more specialized the titles get, and the Creative Director is the closest thing to “the idea guy” — the keeper of the vision, working like a film director.
  • Levels and missions — Level Designer owns architecture and moment-to-moment play inside a space; Multiplayer Level Designer handles the same job against competitive and co-op constraints; World Builder works in open worlds and MMOs where one area has to serve many purposes; Mission Designer handcrafts gameplay in space that already exists; Quest Designer covers the smaller secondary story content.
  • Systems — Systems Designer owns global rules across the whole game (combat is a system, throwing grenades is a mechanic); Combat Designer owns enemies, weapons, bosses, ammo, difficulty; Economy Designer owns the sources and sinks of in-game currency; plus Multiplayer, Puzzle, and Narrative designers, the last concerned with how the player interacts with story rather than the prose itself.
  • Crossover and not-designers — Monetization Designer (design plus business), Technical Designer (the engineering/design bridge), UI Designer, Writer, and Design Support, a low-level role that does the grunt implementation so seniors can keep thinking. Meanwhile Graphic Designer, UX Researcher, Sound Designer, Software Designer, and Game Architect all carry “design” in the name and sit outside the design team entirely.

The taxonomy is useful; the framing questions are the real payload. A level designer asks whether the player gets there by elevator or ladder. A systems designer asks how many pieces of intel exist and how they are spread across the whole game. A puzzle designer asks what new mechanic this puzzle is teaching. Those questions define a role far better than any title does.

For a solo or AI-assisted developer, the piece doubles as a coverage checklist, because you are every one of these people. The failure mode is doing the fun roles (systems, combat) and skipping the unglamorous ones (economy balance, UI, narrative plumbing). England’s own aside — one project where she was level designer, mission designer, and systems designer on the same chunk of gameplay — is the normal case at small scale, not an exception.