Game Developer

You make the games: the characters, the levels, and the way it feels to play. Nobody has to hire you to start either, one person can build and put out a small game now, and that is how most people get in.

Related: Software Engineer, Designer, Founder

The day in the life

jumper · the toy

// player: one square
onPress(SPACE, () => {
  player.vy = JUMP // not tuned yet
})
// no goal, no fail, no restart

a square that jumps, nothing else yet

Don't overbuild it. Make the jump feel good, that's the whole thing.

You've got a bare square that jumps, and your job is making that jump feel so good people hit restart. What one thing are you chasing?

Timing jumps over gaps: just barely clearing itJump after jump without stopping, never touching the ground

Try a day as a game developer

A short, playful taste of the real work.

Try it out
Where it’s going

Games are more popular than ever, but the companies that make them are hiring fewer people than ever. People with the very same skills get paid more building things that are not games.

Getting in

Jobs at games companies are hard to come by. You can also build your own game and sell it yourself, but most games people make alone earn very little.

Pay
New at a games company~$57KA few years at a games company~$90KMany years at a games company$112-180K

No dedicated BLS code; closest are Software Developers and Special Effects Artists & Animators (May 2024); PayScale / Glassdoor / ZipRecruiter game-dev bands (2025-26).

What you’d actually do

On a studio team you usually own one narrow slice of a big game (one system, one tool), not the whole vision, and a lot of the day is debugging and iterating. The tools help with the repetitive code and rough art, but the part that matters most is taste for what’s actually fun: the systems and game-feel judgment no tool can supply.

  • Coding & implementation50%
  • Debugging & testing20%
  • Design & systems decisions10%
  • Meetings & coordination10%
  • Tools, builds & polish10%

Half the day is writing the code for one part of the game that somebody else already decided on, and a fifth is working out why it broke.

Rough split, based on how game devs describe the work. Varies by role (programmer, artist, designer).

Making games splits into a few very different roles, even on the same team.

  • Gameplay & systemsbuilding the rules and mechanics that make a game fun to play.
  • Graphics & enginebuilding the technology that renders everything else on screen.
  • Toolsbuilding the software other developers on the team use to make the game.
  • Indiedoing most of the above yourself, on a small team with no studio behind you.

A typical early-career day

  1. 10:00Team check-in

    Quick standup: what you shipped, what you’re on, what’s blocked. Then back to your piece.

  2. 10:30Build your piece

    Work on the one system or tool you own, a small slice of a much bigger game.

  3. 1:00Debug & test

    Hunt down why something broke and make it hold up. This is a big chunk of most days.

  4. 3:00Playtest & iterate

    Play it, feel what’s off, tune it. "Is it fun yet?" is the question you keep asking.

  5. 4:30The repetitive parts, handled

    The repetitive code and rough assets get handled fast; the calls about what’s actually fun are still yours.

A rough day on a studio team. Crunch, long nights and weekends near a deadline, is the defining hazard of the job, and a real one.

The outlook

Where it’s going

Two opposite things are happening: the games market itself is large and growing again, with healthy revenue and player numbers, but the jobs went the other way. The industry just had the worst layoffs in its history (around 25,000+ in 2023-24 and still going) as studios correct from over-hiring and consolidate, with AI adding pressure on top.

Right now

It’s a tough time to land a first studio job, especially at big studios: entry roles are scarce and laid-off veterans are competing for them. But the games market is healthy, so the dream is crowded, not dead: the accessible way in is making and publishing your own games, where there’s no gatekeeper to get past.

Sources: GDC 2026 State of the Game Industry; game-industry layoff trackers (2022-26); Newzoo market-growth (2025). Dated June 2026.

Would you actually like it?

Worth a look if you love figuring out what makes a game fun and you’d build one whether or not a studio hired you.

In practice, people realize it’s their thing when…

  • they obsess over what makes a game feel good to play, not just how it looks
  • hunting down why something broke, being stuck, then suddenly having it work, feels like a puzzle rather than a slog
  • they’d happily make their own small game without waiting for anyone to hire them
  • they like owning one system deeply and getting the details exactly right

…and it probably isn’t their thing when

  • they want a steady job soon: games companies are hiring less than at any point in the industry’s history
  • they pictured making whole games: at a games company you get one narrow part of one game, plus a lot of time working out why something stopped working
  • the last weeks before a game comes out are brutal: long nights and weekends are normal, and a lot of people leave worn out

Make a Tiny Game That Actually Feels Good

Make one tiny game that actually feels good to play: pick a single thing the player does over and over, build it, then do the real work of adjusting it until that one move feels right. Knowing whether something is fun yet, and fixing it until it is, is the whole job, and the best first test of whether this is your kind of work.

3-4 hours
Try it

Explore other careers

See all →