You decide how the game actually works. Not what it looks like and not the code underneath, but the rules, the systems, and the moment-to-moment experience: what the player can do, what happens when they do it, what the cost is, what the reward is, and how all of that adds up to something that is genuinely fun rather than merely functional. You invent a jump and then decide exactly how high, how floaty, how forgiving — and those tiny numbers are the difference between a game that feels great and one that feels wrong. The primary pull is Creation, but it is creation under the hardest possible test, because the thing you are making does not exist until someone plays it and it works on them.
The core discipline is the loop: imagine a system, build a rough version, watch real people play it, notice where they get bored or confused or frustrated, and change it. You will do this more times than you can count. Designers live partly in engines and partly in spreadsheets, because so much of design is balancing — tuning the numbers behind weapons, economies, difficulty curves, and progression so the experience stays fair and compelling all the way through. The job rewards people who can hold a whole system in their head and feel, almost physically, where it is sagging.
This is the corner of the field most often confused with "playing games for a living." It is closer to the opposite. You play the same broken, unfinished slice of your own game hundreds of times, hunting for the specific reason it is not yet good, which is a very different relationship to play than the one that drew most people in.
Kitsune can talk through anything on this page — whether it might suit you, what to do next, questions this page doesn't answer. Everything here is yours to read either way.
Most of your ideas will not survive contact with a playtest, and the skill is not having ideas but killing your own. New designers fall in love with a clever system and defend it; experienced ones treat every idea as a hypothesis to be tested and discarded without grief if the players do not respond. The emotional discipline of letting good-on-paper ideas die is harder than the creative work itself, and it is what separates designers who improve from those who stall.
"Fun" cannot be specified in advance, which makes this an uncomfortable job for anyone who wants certainty. You cannot prove a design will work before building it; you can only build it and find out. The job is a long act of faith punctuated by evidence, and people who need to know the answer before they start tend to struggle here.
There is no single gate. Common routes include games-design degrees, computer-science or art degrees, and entirely self-taught paths backed by a portfolio of small, finished games. The single most persuasive thing a new designer can show is completed work — even tiny games made in a free engine — because finishing demonstrates the one trait the industry most needs and most rarely sees. Many designers also enter sideways, from QA testing, community roles, or programming and art, having shown design instincts on the job. Comfort in an engine such as Unity or Unreal is effectively assumed.
Junior execution tasks assisted while the core 'finding the fun' craft is robustly human; fewer roles to learn that craft on the job.
Senior/lead design strong; entry rung narrows, demands a portfolio of finished games.
People drawn to Game Designerare often drawn to these — in the order they're closest. The ones marked sit in a different field entirely.