Stephen Brenish
If you want to become a game producer, the degree question comes up early, and it is expensive to get wrong. A four-year program can cost tens or even hundreds of thousands of dollars. A self-taught path costs very little in money but a lot in discipline.
The useful question is not “degree or no degree.” It is “what do studios actually hire producers on, and which path gets me that evidence fastest?”
What studios actually hire on
Producers come from everywhere: QA, design, engineering, software project management, film and TV production, business, and game programs. Studios hire mainly on evidence that you can do the job:
- You have shipped something, even something small, and can explain your role in it.
- You can describe your process specifically: how you planned, what slipped, why, and what you changed.
- You can talk to engineers, artists and designers credibly about their work.
- You think clearly in writing, because so much of production is written communication.
A degree can help you get the first interview, particularly at large employers that screen on credentials. It rarely gets you the job on its own. What separates candidates in the room is evidence of production thinking.
What degree programs do well, and badly
Structured programs are good at forcing you to finish things, putting you on teams with deadlines, and building a network of peers and instructors. Many dedicated game programs also give you real team projects, which is valuable experience.
Where programs often underdeliver: agile and Scrum as actually practiced in studios rather than the textbook version, milestone documentation that publishers accept, managing up to executives and down to a team at the same time, and current tools. Fill those gaps deliberately, whichever path you choose.
A structured self-taught path
What I *actually* do as a Product Manager (in 2023) · Chloe Shih on YouTube
The self-taught producers who succeed share one pattern: they ship something, document it, and talk honestly about what went wrong. A realistic structure looks like this.
Months 1 to 6: foundations. Read The Art of Game Design by Jesse Schell for how designers think, and The Game Production Handbook by Heather Maxwell Chandler for the craft of production. Take a structured fundamentals course, such as Google’s Project Management Certificate. Join a small mod or hobby project in a production role.
Months 7 to 14: produce real projects. Produce a team through several game jams. Track every sprint in a real tool, and write a short postmortem after each one. You will learn more from three jams with honest postmortems than from a year of tutorials.
Months 15 to 24: ship and build a portfolio. Help a small team ship something to itch.io or Steam, owning the schedule, risks and release. Turn your trackers, milestone documents and postmortems into a producer portfolio.
Illustration: a self-taught candidate with one shipped game, a documented sprint history and a public postmortem applies to a dozen small and mid-size studios. A few respond, one or two interview, and perhaps one makes an offer. That is a normal hit rate for a first production role, and the documentation is what gets those interviews.
The trap on the self-taught path
There is a hard line between preparation and avoidance. Some people spend years “learning production” from videos and never produce anything. If you are a year in and have not shipped or documented a project, you are on the wrong side of that line.
The middle options
Community college programs and certificates can be good value: structure and peer accountability at a fraction of the cost of a four-year degree, often with credits that transfer later. Short professional courses can fill specific gaps. Compare total cost, the instructors’ industry experience, and graduates’ actual outcomes before you enroll anywhere.
How to decide
- Choose a degree if you want a structured environment, value the network, are targeting employers that screen on credentials, or want to explore several disciplines before choosing production.
- Choose the self-taught path if you are already working (especially in QA, design or project management), can hold yourself to deadlines, and are willing to produce real projects in public.
- Either way, ship something, document it, and be able to explain what you would do differently.
For what the job pays once you get there, see game producer salary ranges by studio size and role, and for the interview itself, game producer interview questions.
Photo: Vlad Bagacian via Pexels
