Glassdoor users rated their interview experience at Electronic Arts as 33.3% positive with a difficulty rating score of 2 out of 5 (where 5 is the highest level of difficulty). Candidates interviewing for Localization Tester and Junior Game Tester rated their interviews as the hardest, whereas interviews for Estágio Superior and Junior Game Tester roles were rated as the easiest.
The hiring process at Electronic Arts takes an average of 21 days when considering 3 user submitted interviews across all job titles. Candidates applying for Localization Tester had the quickest hiring process (on average 21 days), whereas Localization Tester roles had the slowest hiring process (on average 21 days).
My experience with the initial recruiter screening was disappointing. The interviewer seemed disengaged, barely made eye contact, and treated the screening as a perfunctory task, wrapping it up in just 10 minutes. Despite my thorough preparation and follow-up questions, the conversation felt dismissive rather than professional.
I applied online. I interviewed at Electronic Arts (Vancouver, BC) in Aug 2024
Interview
HR screening followed by a technical interview / SQL challenge where reasoning skills and technical skills are assessed, then a fit round with stakeholders. Technical round is gradual difficulty. Stakeholder meeting is more about behavioral skillset, talking about needs, options, ...
Interview questions [1]
Question 1
Solve SQL challenges with progressive difficulty and screen sharing
I applied online. I interviewed at Electronic Arts (Xangai, Xangai)
Interview
Lasted less than an hour, around 40+ minutes.
The questions are not in order — just wrote down whatever came to mind. No live coding.
Manifestations of polymorphism
Function overloading — how the compiler resolves overloading; what overloaded functions with the same name but different parameter lists look like in the compiler
Functions with default arguments — compiler behavior
The virtual function mechanism
Understanding of C++ memory management and safety
Led to smart pointers
Thread safety related to shared_ptr
weak_ptr related questions
Types of locks
Template functions
Familiarity with template metaprogramming
Understanding of template specialization
Usage and understanding of various casts
A bunch of detailed questions on various keywords. Personally felt they went quite deep — seemed like they were gauging my level.
Project-related questions — my current research direction
Frame synchronization vs. state synchronization
Brief chat about other things
Time for my questions
The second round was scheduled three days later.
The second round focused on discussing my projects. The interviewer guided the conversation, and we explored together how to implement things better. Then one or two low-level memory-related questions. After that, it was a casual chat — including use of AI, etc.