EU remote
Game Producer
About this role
Main challenge War Planet Online is a real-time MMO strategy game developed by Gameloft where players step into the role of military commanders, building bases, managing modern armies, and competing for global dominance on a seamless, shared map of Earth set in the near future. As Game Producer you organise, coordinate and monitor the development of the game or of one of its major features. The main challenge is holding three things together at the same time: adherence to deadlines, expected quality level the game and the technical and licensing requirements that come from outside the studio.
You do that by keeping the production process clear for the team and by making sure information reaches everyone who needs it, on time. You work alongside and report to the Lead Producer. What does it mean on a daily basis Support the Lead Producer on the organisational and technical sides of the development cycle, including build submissions. Act as Scrum Master: run sprint planning, daily stand-ups, reviews, retrospectives and other team meetings.
Break the game or feature roadmap down into releases and sprints. Work in JIRA every day: create stories, maintain boards and track task progress. Follow the team's workload and re-prioritise tasks when plans or capacity change. Keep project documentation accurate, up to date and easy to find. Track the game's key performance indicators and propose actions to improve them. Check that what the team delivers meets internal and external requirements, including those from headquarters, the licensor and the porting teams.
Work with the estimates provided by the Leads and their teams, continuously maintain and adjust the plan as estimates evolve, and proactively flag any discrepancies between the plan and actual timelines to the Lead Producer, Game Manager, and the team. Play War Planet Online and comparable 4X titles, follow what happens in the market, and share what you learn with the team. Give stakeholders structured updates before they have to ask for them.
Support a working atmosphere where people collaborate, raise problems early and help each other. What success would look like Sprints and releases land on the agreed dates, at the expected quality level, without last-minute surprises. Builds pass submission, compliance and licensor checks without repeated rework. The team knows what it is working on and why, and blockers are raised early enough to be solved. JIRA and the project documentation show the real state of the project, so anyone can see where things stand.