Making A Demo

tim-cain game-development career-advice demos job-interviews learning self-improvement

Abstract

Problem: Aspiring game developers constantly ask how to break into the industry, whether to go to school, or how to learn new skills — Tim Cain always gives the same answer.

Approach: Tim shares a personal family story as a metaphor, then draws on his decades of industry experience to explain why making demos is the single most important thing an aspiring developer can do.

Findings: Making demos teaches you what you're good and bad at, gives you concrete interview material, builds real experience with engines and languages, and produces a tangible portfolio piece. No amount of reading or thinking substitutes for actually doing.

Key insight: You have to actually use your skills to discover where your strengths are — you don't know you've reached the top of the mountain until you've climbed it. Make a demo.

Source: https://www.youtube.com/watch?v=uljC4cZh-Oc

The Universal Answer

Tim opens by acknowledging that despite having a video literally titled "How to Get a Job in the Game Industry," he still gets asked the same question constantly. His answer is always the same: make a demo. Whether someone asks about going to school, being self-taught, learning a new engine, or preparing for interviews — the answer is make a demo. The only other answer that competes is "money" (for making a good game). Those are the two biggest takeaways from his channel.

The Mountain Story

Tim shares a family anecdote as a setup. He's the youngest of five kids, and they used to debate who was their mom's favorite. Each sibling had their argument — the firstborn got the most love, the second questioned the first's choices, the third played the neglected middle child card, and Tim (kid five) claimed he was "perfection" so they stopped. But kid four delivered the zinger: "You don't know you've reached the top of the mountain until you start down the other side."

Tim admits kid four was wrong about being the favorite — but the metaphor is perfect for skill development. You have to actually do things to find your maximum, your strengths. You can't know from the outside.

Learning By Doing

Tim references his earlier videos on learning from failure. Trying many different things helped him discover what he was good and bad at, and the results weren't always obvious. He wrote the intro narration for Fallout, which made him think he was a good writer. Turns out he's good at short-form writing — lore text, funny quips — but terrible at long-form writing and character dialogue. He points to Temple of Elemental Evil as evidence of his dialogue limitations, compared to The Outer Worlds (which he didn't write) winning writing awards.

The crucial point: he couldn't have known this without actually doing it, which meant writing a lot.

School vs. Self-Taught

Tim reiterates his stance: whether you go to school or teach yourself, you should make a demo. School helps in three ways:

  • Builds a foundation of knowledge to layer skills on top of
  • Provides external evaluation — if every class grades you badly, the problem is probably you, not every teacher
  • Creates a learning environment surrounded by other motivated people

Self-teaching works too, but requires strong self-motivation and honest self-evaluation. If you think everything you make is flawless, you either have a Dunning-Kruger problem or you're a super genius (probably the former).

Why Demos Help With Interviews

Making demos turns hard interview questions into easy ones:

  • "What language do you prefer?" — You can compare languages you've actually used across different demos and explain specific tradeoffs
  • "What engines do you like?" — You can speak concretely about what each engine made easy or hard
  • "What was the most difficult feature you ever implemented?" — You can tell a real, grounded story about struggling with something like dynamic lighting in a specific engine

Tim notes that at least one interviewer will have gone through the same struggles. Hearing you talk honestly about difficulties shows experience and relatability — not weakness.

Finding Your Mountaintop

The biggest benefit of making demos is self-knowledge. You discover:

  • Things you're good at — put them in the "good at" bucket
  • Things you're bad at but can improve — work on them, then move them to the "good at" bucket
  • Things you'll never be good at — and that's okay. Put them in the "bad at" bucket and own it

Tim uses himself as an example: "You want me to write short-form lore text? I'm your guy. You want it to be funny? I'm really your guy. You want dialogue between two characters? I'm not your guy. And I know that."

The Takeaway

By making demos and actually applying your skills, you learn where your mountaintop is — what all your foundational skills build up to. On top of that self-knowledge, you have a tangible demo to show people. That combination — knowing your strengths and having proof — is what makes you perform well in interviews, be memorable, and ultimately get the job.

Make a demo.

References