Video Game Producer Role: What Producers Actually Do

Producer is the least understood job in game development, partly because no two studios define it the same way. It’s also one of the few roles where the work is invisible when done well and extremely visible when it isn’t. Here’s where the title came from, what the job involves now, what it pays, and who tends to be good at it.

Where the Title Came From

The producer title arrived in games from an unexpected direction: the music business.

The earliest widely documented use of “producer” in games is credited to Trip Hawkins, who established the position when he founded Electronic Arts in 1982. Describing the role in an interview the following year, Hawkins said producers manage the relationship with the artist. They find the talent, work out product deals, get contracts signed, manage them, and bring them to conclusion. They do most of what a product manager does, minus marketing and packaging decisions. His summary is still the best short description anyone has produced: “they’re a little like book editors, a little bit like film producers, and a lot like product managers.”

The music connection was deliberate. Hawkins’ thinking was shaped by his relationship with Jerry Moss, co-founder of A&M Records, and the idea was that producers would manage artists and repertoire the way the record industry did. He brought in record producers from A&M to help train EA’s first producers, which remains one of the stranger and more revealing facts about how game development got organised.

By late 1983 EA had five producers, and the composition tells you what the role was understood to be at the time: a product marketer, two people from Hawkins’ former employer Apple who were described as good at working with engineering people, one former IBM salesman and executive recruiter, and a product marketer from Automated Simulations. Not a project manager among them. Sierra On-Line’s 1982 game Time Zone may have been the first to credit a “Producer” and “Executive Producer” at all.

What the Job Actually Is

Strip away the studio-specific variation and a producer does two things. The first is the one people picture. The second is the one that decides whether they’re any good.

The project half

Designing a realistic schedule and then defending it. Tracking budget. Breaking work into deliverable chunks, commonly two to four week sprints with defined goals, and accepting that those goals will shift. Managing dependencies between disciplines so that the animator isn’t waiting on a rig that’s waiting on a model. Reporting upward to leadership or a publisher.

The recurring test is scope. When something slips, and it always does, the producer works out what can move, what can be cut, and what has to hold. That’s less about spreadsheets than about judgment: knowing which feature is load-bearing for the experience and which one the team is attached to for reasons that won’t survive contact with a deadline.

The people half

A producer cannot study a schedule all day. The job is to keep the machine running, which mostly means being the person anyone can go to with a question about the project and get a real answer.

That involves noticing that two disciplines have different assumptions about what “done” means before it becomes a two-week rework. It means surfacing a problem someone is embarrassed to raise. It means protecting focus, which often means saying no on behalf of a team that finds it hard to. The best producers we place are the ones people go to first rather than the ones people report to.

How much of this sits with the producer varies enormously. At some studios an art lead carries much of the planning and scheduling for their discipline. At others the producer owns it end to end. This is the single biggest reason the title means so little on its own, and why reading the responsibilities matters more than reading the name.

The Production Ladder

Production has clearer progression than most game development disciplines, though the titles vary by studio.

What Video Game Producers Earn

Production accounts for roughly a tenth of game development professionals, making it one of the larger disciplines after engineering, art, and design. Figures below are median annual gross salaries from our own Gamedev Salary Pulse, a predominantly European survey.

One pattern worth knowing if you’re negotiating: production salaries compress at the top relative to engineering. A senior engineer in North America out-earns a senior producer by a considerable margin, while the gap is much narrower in Central and Eastern Europe. Executive producer roles are where production compensation catches up, because the job stops being delivery and starts being business decisions.

About Crunch

The producer’s relationship with crunch deserves an honest treatment rather than a defensive one.

When a team works extended hours for extended periods to hit a date without cutting features, that is usually a planning or scoping failure. Someone committed to a scope the schedule couldn’t carry, or failed to raise a risk early enough for it to be addressed cheaply. Producers own a meaningful share of that.

The honest complication is that producers frequently don’t hold the authority the responsibility implies. A studio’s leadership, or a publisher’s milestone, can impose a date that no amount of good production practice will accommodate. A producer can flag the risk, model the options, and still be overruled. They then manage the consequences of a decision they argued against, which is one of the genuinely hard parts of the job and something worth asking about in an interview.

What separates good producers here is not preventing every crunch, which isn’t always within their power. It’s raising problems early enough to be solved, being honest upward about what a scope will actually cost, and refusing to let optimism substitute for a plan. If you’re interviewing for a production role, how a studio answers questions about crunch tells you a lot about whether the job is set up to succeed.

Is Production the Right Fit for You?

The honest version: it suits people who get satisfaction from other people’s work going well.

Producers rarely make the thing. They make it possible for the thing to be made, which means the recognition is indirect and frequently invisible. If you need your own fingerprints on the output, production will frustrate you. If you find genuine reward in a team hitting its stride because you removed three obstacles nobody else noticed, it’s one of the most satisfying jobs in the industry.

The traits we see consistently in strong producers: comfort with ambiguity, because plans are always partly wrong. Directness without abrasiveness, since the job involves delivering unwelcome information regularly. Enough technical and creative literacy to understand what disciplines are telling them, without needing to do the work themselves. And a tolerance for being the person who says no.

Routes in Video Game Producer Career

QA is the most common internal path, because testers develop a detailed understanding of the product and the studio’s workflow before moving across. Production coordination and assistant roles are the direct entry point. Discipline leads sometimes move into production when they discover they prefer enabling the team to doing the craft themselves.

Project management from outside games transfers better than most external routes, though it needs adjusting: game development is more iterative and less predictable than most software work, and producers who arrive expecting a plan to survive contact with production tend to struggle initially. Experience running anything creative under deadline pressure, whether film, events, or agency work, is more relevant than it sounds.

For a wider view of how production sits alongside other departments, see our guide to every role that makes a game happen.

---

Common Questions

What does a video game producer do?

Makes sure the game gets made. That means the schedule, budget, scope, and dependencies on one side, and communication, unblocking, and people management on the other. Producers rarely build the game themselves; they create the conditions in which other people can. The balance between those two halves varies considerably by studio, which is why the job description matters more than the title.

Who was the first video game producer?

It’s genuinely disputed. The commonly repeated account credits Trip Hawkins with establishing the position when he founded Electronic Arts in 1982, with the title popularised by EA from there. Brad Fregger became Activision’s first producer in 1983 and is often described as the first person to hold the title. Fregger has himself argued publicly that Activision created the role in 1981, before EA. Encyclopaedia editors note he isn’t a neutral source on his own career, so treat it as contested rather than settled.

What’s the difference between a producer and a project manager?

Considerable overlap, with two differences that matter. Game development is more iterative and less predictable than most software projects, so producers plan for change rather than against it. And the role carries a creative dimension that pure project management doesn’t: producers routinely make judgment calls about what serves the game, not just what fits the schedule. Project managers from outside games transfer well, but usually need to adjust to how much of the plan is provisional.

How much do video game producers earn?

According to our Gamedev Salary Pulse, senior production roles have median annual gross salaries of around €54,000 in Central and Eastern Europe, €57,170 in Western Europe, €62,300 in the Nordics, and €82,490 in North America. Production compensation compresses at the top compared with engineering, and executive producer roles are where it catches up, because the job shifts from delivery to business decisions.

How do I become a game producer?

The most common internal route is QA, because testers learn the product and the studio’s workflow in detail before moving across. Production coordinator and assistant roles are the direct entry point. Discipline leads sometimes move into production when they find they prefer enabling a team to doing the craft. From outside games, project management transfers reasonably well, as does experience running anything creative under deadline pressure, such as film, events, or agency work.

Are producers responsible for crunch?

Partly, and honestly so. Crunch to hit a date without cutting features usually reflects a planning or scoping failure, and producers own a share of that. The complication is that producers often lack the authority their responsibility implies: leadership or a publisher can impose a date that no production practice can accommodate, and the producer manages the consequences of a decision they argued against. Good producers raise problems early enough to be solved and are honest upward about what a scope will actually cost.

What should I ask in a producer interview?

The most useful question is who decides what gets cut. Production titles are unusually unreliable, and two roles with identical titles at different studios can mean a scheduling and reporting function or genuine authority over scope and budget. That one question locates the role accurately, and studios tend to respect being asked it.

What kinds of producer roles exist?

Beyond the standard ladder of coordinator, associate producer, producer, senior producer, and executive producer, studios also hire technical producers for engineering-heavy work where schedules depend on understanding technical risk, and live ops producers for the post-launch lifecycle: content cadence, seasonal events, patch schedules, and reacting to live player data. The live ops variant barely existed as a standalone title a decade ago.