Game Designer · The architect of play — the person who decides what a game asks of its players, from Senet's ancient board to Tetris and today's three-billion-player industry.
The popular image of the job is having ideas. The actual job is everything after the idea: specifying it precisely enough that an engineer can build it, prototyping it cheaply enough that it can be killed without grief, watching strangers play it, and tuning numbers until the experience matches the intention. Ideas are the profession's cheapest commodity; finished, tested decisions are its product.
The craft's core instrument is the playtest, and its core discipline is a strange humility: the designer must treat every confused player as data rather than as a wrong opinion. Players are almost always right about how a game feels and almost always wrong about how to fix it — translating between those two facts is most of what separates seniors from juniors.
Seeing a game as interlocking loops — economy, difficulty, reward — and predicting how a change to one number ripples through all of them.
Modeling what a first-time player knows, fears and wants at every moment, which is never what the person who designed the system knows.
Making the cheapest possible version of an idea — paper, greybox, spreadsheet — fast enough to kill bad ideas before they cost a team months.
Writing and arguing clearly enough that artists, engineers and producers build the same game the designer imagined, without a meeting per sentence.
Enough scripting, engine fluency and data handling to build and tune without borrowing an engineer — the difference between proposing and testing.
Judging tone, theme and fiction so mechanics and story reinforce each other; central in some genres, delegated to narrative specialists in others.
Playing last night's build before claiming anything about it, then the team standup: what changed, what broke, what needs a design call today.
The morning block: writing specs, scripting a level in-engine, tuning an economy spreadsheet, or building a quick prototype for tomorrow's playtest.
Playing competitors and classics is genuinely part of the job; design teams dissect other studios' launches the way chefs eat at rivals' restaurants.
Watching testers play in silence, taking notes on where they hesitate, then adjusting — the loop of observe, hypothesize, tune that fills most afternoons.
Reviews with art, engineering and production: what the design costs, what gets cut, what ships. Designers spend more time trading scope than inventing features.
Nominally off. Near milestones many studios still slide into crunch — the extended overtime that scandals from 'EA Spouse' (2004) onward have made the profession's most public failing.
Craft knowledge practitioners actually pass on — not motivation.
Nintendo structures levels on the four-part scheme of classical Japanese narrative — introduce a mechanic safely, develop it, twist it against expectation, conclude with mastery. Koichi Hayashida described applying it to Super Mario 3D Land at GDC 2012, and the pattern is now taught worldwide as the cleanest way to teach through play.
When a number feels wrong, don't nudge it — double it or cut it in half. Sid Meier's tuning rule exists because small adjustments are invisible in playtests; violent changes reveal immediately whether the variable matters at all, after which fine-tuning has a direction. It saves weeks of polishing values that were never the problem.
Valve's rule during Half-Life's development: bring in outsiders weekly, say nothing, and treat every confusion as the game's fault. Ken Birdwell's 1999 account of the 'Cabal' process records whole celebrated levels being rebuilt because one silent tester got lost — the founding document of modern playtest doctrine.
World 1-1 of Super Mario Bros. teaches running, jumping and power-ups with zero text: the first Goomba approaches at walking pace in open ground, so the obvious panic jump becomes the lesson. Miyamoto and Takashi Tezuka walked through the screen's reasoning on camera in 2015 — every element is placed to make the player teach themselves.
Mark Rosewater's most-repeated lesson from three decades leading Magic: The Gathering design: an open brief produces the same safe ideas, while a hard constraint — design a set around one mechanic, one color, one cost — forces genuinely new solutions. His GDC 2016 talk 'Twenty Years, Twenty Lessons' made it the craft's best-known design principle.
Halo's combat was designed as one repeatable half-minute loop — spot enemies, plan, engage, retreat — polished until it stayed fun on the thousandth repetition, then re-dressed in new spaces and enemy mixes for a whole campaign. Bungie designer Jaime Griesemer's formulation is the standard argument for perfecting the core loop before building content on top of it.
Where design meets implementation: designers block out levels in untextured 'greybox' geometry, script encounters and expose tuning variables. Engine fluency is now assumed at hiring, the way word processing is assumed of journalists.
The profession's least glamorous, most-used instrument. Economies, XP curves, drop tables and damage formulas live in Excel or Google Sheets long before they reach the engine, and systems designers are often interviewed on spreadsheet modeling directly.
Physical prototyping survives because it is the fastest iteration loop that exists: rules can change between rounds. Card and board mockups are standard even inside video game studios for testing economies and combat math before any code is written.
Perforce or Git for the build; Confluence or an internal wiki for the living design documentation that replaced the mythical thousand-page GDD. A specification nobody can find, or that contradicts the build, functionally does not exist.
Live games instrument everything: funnels showing where players quit, heatmaps of deaths per square meter, A/B tests of tutorial variants. Reading telemetry without being ruled by it — numbers say where, playtests say why — is a distinct modern skill.
The industry's oldest interview red flag is the candidate whose portfolio is concepts rather than playable work. Every studio already has more ideas than capacity; the scarce skill is specifying, testing and cutting. Design tests exist specifically to filter for people who can execute an unglamorous brief well.
First projects die of scope: the solo MMO, the hundred-hour RPG. Jam culture exists as the antidote — the discipline of finishing something tiny is the single most transferable skill in the craft, and unfinished epics teach almost nothing. Veterans' advice is unanimous: make small finished games, then slightly bigger ones.
When playtests contradict the vision, the amateur reflex is to explain the design to the tester. Players are reliably right about how a game feels and unreliable about the fix; a designer who argues with the room's confusion instead of investigating it will polish something nobody enjoys, on schedule.
Designs buildings that must stand, meet code, please a client and cost the right amount — then carries legal responsibility if they don't.
AI-resistant 78 🎬Turns a screenplay into a finished film by deciding every shot, performance and cut, then persuades a producer, a studio and an audience the vision was worth the budget.
AI-resistant 73 ✍️The maker of book-length fiction, from Murasaki Shikibu's Heian court to the Kindle's self-publishing flood — a trade with no license, no ladder and no retirement age.
AI-resistant 62 🎻Spends years mastering an instrument or voice, then earns a living from performances, recordings and teaching in a market streaming has broadened but paid less for.
AI-resistant 60 🖌️The oldest image-making trade on record — from 45,000-year-old cave walls to the contemporary studio, still practiced one brushstroke at a time.
AI-resistant 74