Answer EA PM behavioral prompts
Electronic ArtsProduct Manager · HR ScreenLast updated
Prepare EA game PM behavioral answers for motivation, proud projects, recent learning, data-driven recommendations, cross-functional game development, and learning from being wrong. The solution emphasizes player impact, metrics, collaboration, and humility for a Plants versus Zombies studio interview.
For a Product Manager interview with EA's Plants vs. Zombies studio, prepare concise but compelling answers to first-round HR and written behavioral questions.
Constraints & Assumptions
- Use STAR plus a short reflection for experience-based prompts.
- Tie examples to player experience, retention, monetization health, live operations, or cross-functional game development.
- Keep the tone authentic, collaborative, and low-ego.
- Include metrics where possible, but do not fabricate exact outcomes.
Clarifying Questions to Ask
- Is the role focused on live operations, gameplay features, monetization, growth, or platform/product operations?
- Are written answers expected to be brief paragraphs or full STAR stories?
- Which game team or player segment matters most?
- Should examples come from gaming only, or are adjacent consumer-product examples acceptable?
Part 1 - Motivation And Fulfillment
What parts of your work make you happiest or most fulfilled? What do you love most about being a PM?
What This Part Should Cover
- Motivation at the intersection of player impact, problem solving, creativity, and cross-functional collaboration.
- Why game product work is meaningful to you.
Part 2 - Proud Project Or Accomplishment
What project or accomplishment are you most proud of, and why?
What This Part Should Cover
- A clear project, user/player problem, your role, cross-functional work, and measurable result.
- Why the accomplishment matters beyond shipping a feature.
Part 3 - Recent Learning
What is something you learned in the last year that positively impacted your work?
What This Part Should Cover
- A tool, concept, or mindset with clear behavior change.
- How it improved product decisions, speed, quality, or stakeholder alignment.
Part 4 - Data-Driven Recommendation
Describe a time when you used data to make a thoughtful product recommendation with measurable outcomes, and the data helped align stakeholders.
What This Part Should Cover
- Metric diagnosis, recommendation, stakeholder alignment, result, and guardrails.
Part 5 - Cross-Functional Shared Ownership
Describe a time when you collaborated with Design, Art, Engineering, Production, or other teams to achieve a successful outcome.
What This Part Should Cover
- Shared goal, decision rights, tradeoffs, communication, and outcome.
Part 6 - Realizing You Were Wrong
Describe a time when you were confident in your point of view but later realized you were wrong. What did you learn?
What This Part Should Cover
- A real mistaken assumption, disconfirming evidence, what changed, and how you now validate earlier.
Follow-up questions
- What player metric mattered most?
- How did you balance fun and monetization?
- Which team disagreed with you and why?
- What did you learn from being wrong?
- How would your approach differ for a live event versus a permanent feature?
Solution walkthrough is for members
Get the full walkthrough with reference code and complexity analysis, plus Kitty Coach at 300 messages a day. Hints, the code runner and community answers stay free.