Interview

Interviewing elsewhere... got any tips for EA-specific questions?

0x52c1…6a4f

·35d ago·2 comments

So, yeah, the title says it all. I've started quietly brushing off the resume and hitting up some recruiters. Been at EA for about 5 years now, working on the backend services side. I'm decent at interviewing, but I feel like EA has its own quirks. Are there any common 'behavioral' questions they tend to ask that are super EA-centric? Like, questions about 'collaboration' that really mean 'deal with this toxic producer'? Or anything about navigating 'complex projects' that's code for 'this project is a dumpster fire and you need to put it out'? I want to be prepared, but also don't want to sound like I'm just reciting the company values handbook. Any advice from folks who have successfully jumped ship from here, or even those who've interviewed *into* EA and noticed this?

Join the discussion — anonymously

Sign in to comment, reply, and vote. Your username and email are never shown publicly — posts and votes only display an anonymous handle.

Comments (2)

0x2e8f…59bc

·35d ago

Hey, good luck with the interviews! For EA-specific questions, I'd lean into how you've handled ambiguity and cross-functional dependencies. They often talk about 'player focus' – be ready to give examples of how you've prioritized features or bug fixes based on potential player impact, even if it meant tough decisions or saying 'no' to internal stakeholders. Also, be prepared to discuss how you've adapted to changes in project scope or technology mid-development. Highlight your resilience and ability to course-correct effectively.

0x7f73…4468

·35d ago

Honestly, just treat it like any other tech interview. 'Collaboration' and 'complex projects' are buzzwords everywhere. Focus on concrete examples from your backend services work. How did you ensure scalability? What challenges did you face with microservices or database migrations? If they throw out EA jargon, just reframe it in standard engineering terms. They want to know you can build robust systems, not just navigate internal politics. Don't overthink the 'EA-centric' angle too much.