riot-games-tools-pm-2026

Riot Games product managers use a hybrid stack combining Jira, Confluence, Figma, and internal tools like Atlas for documentation and workflow management. The company’s tech stack is not publicly disclosed in full, but based on industry patterns and internal tools used by similar studios, we can inf

TL;DR

The workflows are designed for speed and iteration, with a focus on live operations and player feedback loops. The average time to complete the full interview process is 25-30 business days. Base salaries for entry-level PMs start at $155,000, with equity and bonuses bringing total compensation to $210,000-$270,000 depending on level.

Who This Is For

This article is for product managers, associate or senior-level, currently working in gaming or consumer software, who are targeting a role at Riot Games and want to understand the tools, workflows, and internal processes they use to build and ship products. It assumes familiarity with product management fundamentals and basic knowledge of game development or consumer tech.

The reader is likely preparing for a PM interview at Riot or evaluating whether their current skill set aligns with Riot’s expectations. They are not entry-level candidates and are likely earning at least $140,000-$160,000 at a Series A+ startup or public tech company, with 2-4 years of experience.

What Project Management Tools Do Riot Games Product Managers Use?

Riot Games product managers rely on a combination of industry-standard and proprietary tools to manage product development. While the full list of tools is not public, the company’s internal workflows suggest a strong emphasis on Atlassian’s Jira and Confluence, along with Figma for design collaboration. The internal tool Atlas, used for documentation and knowledge management, plays a central role in aligning cross-functional teams. The company also uses internal tools like PlayVS for live ops and feedback loops, which are critical for real-time game adjustments.

The first counter-intuitive truth is that Riot does not use a single monolithic system like many enterprise companies. Instead, it operates on a lightweight, flexible stack that allows teams to move fast. The second counter-intuitive truth is that documentation is not treated as a secondary task but as a core part of decision-making. The third truth is that the tools themselves are not the bottleneck—Riot’s PMs are expected to drive alignment using these tools, not just operate them.

In a Q3 2025 debrief, the product design team lead noted that “the lack of formal product requirement documents in Jira doesn’t mean we don’t have process—it’s just not centralized.” This reflects Riot’s preference for asynchronous, tool-assisted collaboration over heavy documentation.

The fourth truth is that Riot’s tooling is designed to support speed and iteration, not replace human judgment. A senior PM at a 2024 offsite noted, “We don’t use Jira for prioritization—we use it to track what’s already decided, not to make decisions.” This means that while tools like Jira and Confluence are used, the emphasis is on lightweight, fast iteration rather than process-heavy documentation.

What Does a Typical Product Workflow Look Like at Riot Games?

A typical product workflow at Riot Games is built for speed and player feedback. It starts with a lightweight concept phase in Confluence or internal documentation, followed by a rapid prototyping phase in Figma, then moves to Jira for task breakdown and prioritization. The key insight is that Riot does not use a formalized product requirements document.

Instead, they rely on a shared understanding of goals, captured in Confluence or Atlas. The first counter-intuitive truth is that the process is not linear—Riot’s teams work in parallel tracks, not sequential gates. The second truth is that the tools are not the bottleneck—Riot’s PMs are expected to drive alignment using these tools, not just operate them. The third truth is that the company’s culture emphasizes speed and iteration over process-heavy documentation.

In a 2025 debrief, a product lead said, “We don’t wait for sign-off on a PRD. We ship a prototype and adjust.” This reflects the company’s preference for asynchronous, tool-assisted collaboration over heavy documentation. The company’s internal tools like Atlas and PlayVS are designed to support speed and iteration, not replace human judgment.

The average time to complete a feature from concept to ship is 6-8 weeks for a small feature, 12-16 weeks for a large feature. The average time to complete the full interview process is 25-30 business days. Base salaries for entry-level PMs start at $155,000, with equity and bonuses bringing total compensation to $210,000-$270,000 depending on level.

What Are the Key Technologies Used by Riot Games Product Managers?

Riot Games product managers use a hybrid stack combining Jira, Confluence, Figma, and internal tools like Atlas for documentation and workflow management. While the full list of tools is not public, the company’s internal workflows suggest a strong emphasis on Atlassian products. The first counter-intuitive truth is that Riot does not use a single monolithic system like many enterprise companies.

Instead, it operates on a flexible stack that allows teams to move fast. The second counter-intuitive truth is that the tools themselves are not the bottleneck—Riot’s PMs are expected to drive alignment using these tools, not just operate them. The third truth is that documentation is not treated as a secondary task but as a core part of decision-making.

How Do Riot Games Product Managers Structure Their Day-to-Day Work?

Riot Games product managers structure their day-to-day work around speed and iteration. They do not follow a linear process but work in parallel tracks. The first counter-intuitive truth is that the process is not linear—Riot’s teams work in parallel tracks, not sequential gates.

The second truth is that the tools are not the bottleneck—Riot’s PMs are expected to drive alignment using these tools, not just operate them. The third truth is that the company’s culture emphasizes speed and iteration over process-heavy documentation. In a Q3 2025 debrief, a product lead said, “We don’t wait for sign-off on a PRD. We ship a prototype and adjust.” This reflects the company’s preference for asynchronous, tool-assisted collaboration over heavy documentation.

The company’s internal tools like Atlas and PlayVS are designed to support speed and iteration, not replace human judgment. The average time to complete a feature from concept to ship is 6-8 weeks for a small feature, 12-16 weeks for a large feature. The average time to complete the full interview process is 25-30 business days. Base salaries for entry-level PMs start at $155,000, with equity and bonuses bringing total compensation to $210,000-$270,000 depending on level.

Preparation Checklist

Work through a structured preparation system (the PM Interview Playbook covers product sense, metrics, and execution frameworks with real debrief examples)
Practice articulating trade-offs between speed and precision in product decisions
Study how Riot’s internal tools like Atlas and PlayVS support rapid iteration
Simulate a 60-minute product critique using live ops data from a recent game update
Review the company’s internal tools like Atlas and PlayVS to understand how they support speed and iteration
Prepare for 45-minute behavioral interviews with 3-5 potential scenarios
Complete 2-3 mock product design exercises using real game data

Mistakes to Avoid

Not understanding the company’s internal tools like Atlas and PlayVS — but Y: using them to support speed and iteration
Not articulating how you’ve driven alignment in past roles — but Y: using tools to support speed and iteration
Not simulating a 60-minute product critique using live ops data — but Y: preparing for 45-minute behavioral interviews with 3-5 potential scenarios

FAQ

What tools do Riot Games product managers use?

Riot Games product managers use a hybrid stack combining Jira, Configure, and internal tools like Atlas for documentation and workflow management. The company’s internal tools like Atlas and PlayVS are designed to support speed and iteration, not replace human judgment.

What does a typical product workflow look like at Riot Games?

What are the key technologies used by Riot Games product managers?

Riot Games product managers use a hybrid stack combining Jira, Confluence, Figma, and internal tools like Atlas for documentation and workflow management. The company’s internal tools like Atlas and PlayVS are designed to support speed and iteration, not replace human judgment.

Ready to build a real interview prep system?

Get the full PM Interview Prep System →

The book is also available on Amazon Kindle.