How to Get a Job in the Game Industry

tim-cain career-advice game-industry hiring game-development

Abstract

Problem: How does someone break into the game industry — the most common question Tim Cain has been asked throughout his career?

Approach: Tim shares his own origin story of entering the industry at age 16, then draws on decades of experience reviewing resumes and hiring to give practical advice.

Findings: The single most effective thing an applicant can do is make a game. Not just have ideas, not just show a portfolio of isolated assets — but ship something playable that demonstrates the ability to realize an idea. Candidates who include a playable demo move to the front of the hiring queue regardless of their discipline.

Key insight: Ideas are worthless without execution. Making a game — even a small one using existing engines and asset stores — proves you can edit, scope, and ship, which is what hiring managers actually care about.

Source: https://www.youtube.com/watch?v=W8hesnidqqE

1. Tim's Origin Story

Tim traces his love of games back to 1976 when his family got a Pong unit, followed by the Atari 2600 which "ignited his brain." At age 13, he mailed hand-drawn game designs to Atari with a letter saying "let's make games." Atari wrote back a kind response suggesting he go to college, study computer science, and call them — plus a $5 coupon he never used because keeping it felt cooler than buying a game. His mother saved all of it, and he later framed the whole package.

1.1. The First Job at 16

When his high school got Atari 800 computers, Tim became obsessed — staying so late in the computer lab that he got in trouble for coming home after dark. At 15, his mom helped him get his own Atari 800, and he dove into BASIC, then assembly language, learning the machine's extended graphics modes and sound capabilities.

A friend two years older got a job at a game company that needed an art tool with resolution and color capabilities beyond what PCs or Apple IIs could offer. The friend knew Tim could do it on an Atari 800. Tim interviewed, demonstrated the extended graphics modes, and was offered the job — but he was only 15. Virginia labor laws prohibited hiring teenagers under 16 for that type of work. They told him to call on his birthday. Two months later, the day he turned 16, his mom drove him to the DMV, he got his license, drove her home, then drove to the company for his first day. He's been in the game industry ever since.

2. The Actual Advice: Make a Game

Tim's answer to "how do I get a job in the game industry" is blunt: make a game.

He anticipates the objections — "I'm an artist, I can't code" or "I'm a writer, I can't build a game" — and dismisses them. Between Unity, Unreal, Godot, GameSalad, and countless other engines, there's no excuse. You can buy a template game from an asset store and drop your own art or writing into it. You can learn scripting. It's not that hard.

2.1. Why This Works

When reviewing resumes, Tim says there's rarely one obvious standout. You get several qualified candidates who are good in different ways. But the ones who include a playable game — whether it's a link to a web page, a download, or (in the old days) a floppy disk — move to the head of the queue.

This works because a finished game demonstrates:

  • Editorial judgment — knowing what makes a good game idea vs. a bad one
  • Scoping ability — understanding that two ideas might not belong in the same game
  • Follow-through — the willingness to go beyond ideas to execution
  • Contextual skill — showing your assets (art, writing, code) working together in a real product

2.2. Ideas Are a Dime a Dozen

Tim is emphatic: he doesn't care about your ideas. Everyone in the industry has ideas. He has books full of them — enough to make a new game every year for the rest of his life. What matters is the ability to realize ideas. That's the skill that's actually scarce and valuable.

2.3. It Doesn't Even Have to Be Finished

Tim shares that he once hired a programmer not because their demo game was polished, but because he got to see the source code and it was excellent. The person is still in the industry today. The game itself was unfinished — but the quality of execution was clear.

3. The Competitive Reality

Tim closes with a reality check: other candidates are doing this. If you're competing for a job and someone else included a playable demo and you didn't, you're at a disadvantage. You can hope to get lucky and be so far ahead of other candidates that it doesn't matter — but if you don't want to rely on luck, put in the extra work, make a game, and show off your skills in context.

4. References