Explore

Studio & indie

Game Developer

The most competitive job in software, for less money than software.

Typical pay

$65k-$130k

How you get in

Portfolio of shipped games; CS degree common

Outlook

Volatile; the industry cycles hard

Game developers build the code behind games. Passion for the medium means an oversupply of applicants, which pushes pay below equivalent software roles and makes crunch and layoffs endemic to the industry.

A day in the life

  1. 9:30aStand-up, then triage bugs from QA
  2. 10:00aImplement a gameplay feature in engine
  3. 12:30pLunch
  4. 1:30pProfile and optimize a frame rate problem
  5. 3:30pPlaytest build review with designers
  6. 5:30pFix what the playtest broke

How to get in

Ship games and build a portfolio

Duration

1-3 years

Cost

$0-$2,000

Credential

None — shipped games are the credential

  1. Learn C++ or C# and one engine deeply
  2. Finish and ship small games — finishing matters far more than scope
  3. Enter game jams to build a body of completed work
  4. Apply with a portfolio of things people can actually play

Computer science degree

Duration

4 years

Cost

$40,000-$200,000

Credential

BS in computer science

  1. Complete a CS degree — stronger fallback than a games-specific degree
  2. Build games outside coursework
  3. Intern at a studio, which is the main pipeline into full-time roles
  4. Keeps general software open if the industry cycles down

QA or tools into development

Duration

1-3 years

Cost

$0

Credential

None — internal track record

  1. Get hired in game QA, which is the most accessible studio role
  2. Learn the codebase and write automation and tools
  3. Move into an engineering or tools programmer role internally
  4. A well-worn path, though QA pay is low while you wait

What people love

  • · You build the thing you love
  • · Deeply technical and creative at once
  • · Indie and solo development is genuinely viable
  • · Skills transfer to simulation, film and general software

What wears people down

  • · Pay is below equivalent software engineering roles
  • · Crunch and post-launch layoffs are structural
  • · Extremely competitive to enter
  • · Studio closures happen regardless of your performance

From people doing it

Add yours