Ryan Cole
Every aspiring game producer I’ve met has the same question, and almost none of them phrase it right. They ask “what should I put in my portfolio?” when the real question is “what does a hiring producer actually need to see before they’ll trust me with a team and a budget?” Those are very different questions, and answering the second one changes everything about how you build your portfolio.
I’ve sat on both sides of this. I’ve submitted production portfolios cold to studios I desperately wanted to work at, and I’ve been the person skimming fifty applications trying to find someone who actually understands what producing is. The portfolios that stopped me were never the flashiest ones. They were the ones where I could see, in five minutes, that the person understood the job.
What Producers Actually Do (and Why Your Portfolio Probably Misses It)
Most aspiring producers come from design or programming backgrounds, and it shows. Their portfolios are full of game screenshots, design docs, and features they shipped. That’s not nothing, but it answers the wrong question.
Producing is about getting a team to ship something together, on time, without destroying each other. It’s communication, prioritization, risk management, and a hundred small decisions that never make it into patch notes. When a hiring manager looks at your portfolio, they’re trying to figure out: has this person actually done that?
So a portfolio with only finished games and GDDs is missing the most important evidence. Show me a sprint board. Show me a post-mortem you wrote. Show me the Slack message you sent when the scope was blowing out and the team needed to cut a feature. Documentation of process beats polished screenshots almost every time.
The concrete stuff that actually works: milestone tracking spreadsheets (anonymized if needed), risk registers, project retrospectives, team communication artifacts, production schedules. If you’ve been using Jira, Confluence, Notion, or Codecks to manage even a student project, export something meaningful from it and put it in front of people.
The Student Project Problem (and How to Work Around It)
Here’s where I’ll push back on what everyone tells you: most people in this industry will say that student projects “don’t count.” I think that’s wrong, and it’s gatekeeping dressed up as standards. What doesn’t count is a student project presented without context. A student project where you show exactly what you were responsible for, what broke, how you adapted, and what shipped? That counts.
I’ve hired people with zero commercial credits specifically because their student portfolio showed good judgment under pressure. One person’s portfolio included a one-page “project health report” they’d written midway through a jam game gone sideways. Scope had doubled, two team members had dropped out, and the document laid out a clean triage plan. We hired her. That document cost her maybe two hours to write and probably got her the job.
Here’s the reframe: stop thinking about projects as credentials and start thinking about them as case studies. For every project you include, write a 300-500 word breakdown covering what your actual role was, what the biggest production challenge was, how you handled it, and what you’d do differently. That’s it. That structure will serve you better than any fancy portfolio site.
What to Actually Include (Specific, Not Generic)
Let’s get concrete. Here’s what a strong entry-level producer portfolio typically needs, in rough priority order:
At least two or three project case studies with the structure above. Mix the types if you can: one game jam (speed, constraint), one longer student project (sustained management), and ideally one commercial or contract project even if it’s small.
A production artifact for each project. This is the thing most people skip. Even something simple, like a one-page feature prioritization matrix you made in Google Sheets, or a build checklist you maintained, proves you were actually doing production work and not just “helping.”
A short professional statement. Not an objective statement from 2003, but a paragraph about how you think about production. What’s your philosophy on scope? How do you handle team conflict? Hiring managers read these carefully, and a generic one hurts you.
Evidence of communication. This one’s weird to explain but easy to show. A screenshot of a team standup summary you sent. A one-pager you wrote to explain a scope cut to stakeholders. Anything that shows you can translate between technical reality and project expectations.
One thing I’d cut: elaborate interactive portfolio websites unless you’re genuinely good at web design. I’ve seen people spend three weeks building a custom portfolio site when they should have been working on the actual content. A clean PDF or a well-organized Notion page (Notion’s free tier handles this fine) does the job. The format isn’t the portfolio.
The Networking Layer You Can’t Skip
Sources
- Pew Nguyen
- helping. A
Your portfolio doesn’t get evaluated in a vacuum. It lands in someone’s inbox, or it gets pulled up because someone you met at a conference remembered your name and searched for you. The production track is smaller than people think, and most mid-level and senior roles in studios don’t get posted publicly at all.
Start showing up where producers talk. The Game Developers Conference is obvious, but it’s also expensive. The hallway conversations at smaller regional events like Midwest GameFest or local IGDA chapter meetups are often more accessible and more useful. Discord communities matter too, specifically ones organized around game dev: the Game Dev League server is active, and the Indie Game Developers server has a production-specific channel worth lurking in.
What I’d actually recommend doing right now: find three producers working at studios you respect, look at their LinkedIn or personal sites, and do the work of reading what they’ve written or said publicly. Then, if you have a genuine reason to reach out (not “can you review my portfolio please”), do it. A specific question about a project they shipped is a reasonable cold message. “Can you mentor me?” to a stranger is not.
The producers who get hired are the ones who make it easy for a hiring manager to say yes. That means a portfolio that’s specific, honest about process, and shows evidence of the actual job. Build that, and the rest follows.
Photo: Pew Nguyen via Pexels
