Product Manager Jobs at Electronic Arts

Electronic Arts PM interview guide

The EA PM interview runs 4 to 7 rounds over 4 to 8 weeks: a recruiter screen, a hiring manager call, and then a panel loop that typically ends with a VP or department-head conversation. The one thing that defines EA's loop is the player-first lens: every question, from behavioral to product design, is evaluated against deep gaming domain knowledge and live-service product instincts.

The interview process

1. Recruiter screen (30 min). A talent acquisition phone call that checks background fit and confirms basics about the role. Candidates reported this was exploratory and friendly, focused on mapping experience to the job spec rather than testing hard skills.
2. Hiring manager interview (45 to 60 min). A 1:1 call or video interview probing past project leadership, stakeholder management, and how the candidate thinks about product. Reported to include more challenging, specific questions than the recruiter screen, with depth on prior PM work.
3. Panel loop: cross-functional 1:1s (30 min each, typically 3 to 5 sessions). Candidates meet peers on other product teams, cross-functional leads (engineering, design, marketing, analytics), and direct team members. Behavioral and situational questions dominate; be prepared to defend ideas when challenged.
4. Panel presentation: past project showcase. Reported by multiple EA PM candidates: you present a past project to the panel, followed by 30-min 1:1 debrief meetings with panel members. The panel evaluates strategic thinking, communication clarity, and how you handled trade-offs end-to-end.
5. VP or department-head 1:1 (final round). A face-to-face or video conversation with the hiring manager's VP. Per reported EA candidates, this round is explicitly about org fit and long-term career trajectory at EA, not just whether you can do the job at hand.
6. What they're really testing. Three signals dominate: (1) Gaming domain depth - do you understand live services, player engagement loops, and EA's specific franchises? (2) Data-driven product judgment - can you set KPIs, measure features post-launch, and course-correct with data? (3) Cross-functional influence - can you align engineers, designers, and business stakeholders without direct authority?

Likely PM interview questions

1. What metrics would you use to evaluate the success of a game (or a specific game feature)?Execution
2. Describe a product feature you would implement for a game and explain your rationale.Product sense
3. How would you approach a situation where a game's performance did not meet expectations?Execution