+ Post Job +
Online Game Project Manager
Home β€Ί Work From Home

Online Game Project Manager

πŸ“ Anywhere 🏷️ Work From Home πŸ’° $90,000 / year
Somebody has to keep a game project from quietly falling apart between milestones. That's this job. We're hiring aΒ full-time Lead Online Game Project Manager, and honestly, the title undersells it a bit β€” you'll be running point on how a game actually gets made, not just watching a calendar. This is one of the meatier online game project manager jobs going right now. If you've ever managed a title and thought "I could run this better than whoever's in charge," that instinct is basically the job description.

What you're actually signing up for

You'll sit in the middle of design, engineering, and QA, and when something between those teams starts to misfire, fixing it is your problem before it's anyone else's. Sometimes that means adjusting a sprint plan. Sometimes it means telling a stakeholder their timeline isn't realistic and backing that up with reasons they'll accept. There are a lot of people out there hunting for a game project manager vacancy near me that isn't just a glorified scheduling role. This one has real teeth.

The work, week to week

Roadmaps don't stay accurate on their own β€” you'll be updating them constantly across multiple workstreams. Standups, sprint planning,Β and retrospectives all run withinΒ Agile or a hybrid version of it,Β depending on the team. When resourcing gets tight, you decide where engineering, art, and QA hours actually go. And when risk shows up on the horizon, catching it two weeks early beats explaining a missed milestone after the fact. None of this is theoretical. People searching for game production manager hiring 2026 listings are usually looking for exactly this kind of ownership, where their calls actually move the project forward.

What gets you in the door

Games experience matters more than general PM background here. It shows up in how someone reacts when a build breaks two days before a demo β€” calm, methodical, not scrambling.
  • At least 4 years managing projects in game development or live-service software
  • Real, regular use of Jira or something comparable β€” not just a passing familiarity
  • Scrum, Kanban, or a hybrid you've actually run, not just studied
  • A decent handle on the full lifecycle, from pre-production through live-ops
  • Communication skills good enough to keep two frustrated departments talking to each other instead of past each other
  • A shipped title, or a specific story about one that slipped and what you'd do differently
Naukri Mitra tends to work with studios where production discipline matters as much as the creative side, and this posting is a good example of that balance.

Not required, but it helps

A PMP or Scrum Master certification won't hurt your chances. Neither will prior live-service experience, since ongoing content cycles behave differently than a single launch date. Budget-forecasting knowledge is useful, as is any time spent coordinating outsourced work or managing a fully remote team. Direct experience presenting milestones to a publisher is a plus, though not something we expect from every applicant.

The pay, and where this can lead

This role pays $90,000 a year. That number comes with senior-level scope attached β€” you're not managing tasks, you're shaping how the project runs. If you've done remote game project manager work before where your suggestions just got ignored, that's not what this is. People here act on what you flag. It's also not a dead-end role. PMs who handle one title well tend to get first look at bigger, multi-team programs as things scale.

What the team actually feels like

Production isn't walled off from the creative side here, which is rarer than it should be. You'll be in the room with design and engineering leads, not three steps removed getting updates secondhand. That means you're expected to actually make decisions, not just organize meetings to decide things. Crunch happens sometimes β€” we're not going to pretend it doesn't in this industry. But the aim is to plan tightly enough up front that it remains the exception, not the norm, and to be upfront about trade-offs rather than quietly grinding people down.

If this sounds like your kind of problem to solve

Send a resume, and include a short note about a project you managed under some kind of real constraint β€” money, time, headcount, whatever it was. We're more interested in how you think through pressure than in a polished summary. If you've been comparing online game project manager roles lately, this is worth putting in for.

Frequently Asked Questions

Jira. Daily. This isn't the kind of listing where "familiar with project management software" covers it β€” you need to have lived in the thing. Same goes for Scrum or Kanban. Anyone can describe a sprint cycle after reading about it once. What we're after is someone who's sat through the messy parts: an estimate that fell apart, scope creeping sideways, QA flagging something two days before a build was due. Certs are a nice line on a resume. They don't replace having actually done the job.
Start to finish, more or less β€” pre-production all the way to live-ops after launch. What the job asks of you shifts along the way. Early stage, you're mostly protecting the roadmap from getting bloated. Once the game's live, it's more reactive, responding to whatever the player base or the servers decide to throw at you that week. If you've worked a title with regular content updates rather than one clean launch date, that experience carries over nicely.
Directly, yeah. No layer of "let me check with the team and circle back." You're already in that room. Which means part of the job is making calls right there, not collecting information to decide on later.
Occasionally, not constantly β€” and anyone claiming it never happens in games probably isn't telling you the whole truth. The real question is whether it's planned for or just allowed to happen. Here the aim is tighter scheduling upfront so it stays rare, and when a trade-off does come up, it gets talked about openly instead of getting quietly absorbed by whoever's still working late.
Send the resume, sure. But add a short note too β€” one real project, run under some actual constraint. Maybe the budget got cut mid-project. Maybe the deadline moved up on you. Maybe you lost half your engineering team with no warning. Whatever it was, how you handled it tells us a lot more than another bullet-pointed summary of responsibilities.
Apply Now