Real, anonymous reports from people who interviewed for Software Engineer at Activision Blizzard, newest first and distilled into what to expect across the loop.
After a recruiter screening, I moved into a technical coding interview where the focus was straightforward problem solving rather than a deep dive into theory. I remember it feeling like a gate to make sure I could think clearly under time pressure, and then the process widened out into multiple virtual conversations.
My process started with a recruiter screening, then I went straight into a technical round that felt relatively manageable compared to the usual bar—more like a fundamentals check with quick follow-ups. I was asked a basic coding question (easier than a typical LeetCode easy), and then the interviewer kept the momentum going with rapid questions about the technologies I’d listed—things like databases, Python and C++, plus microservices and how I’d think about debugging.
The interview process typically begins with a recruiter screening that focuses on the candidate's background, motivations, and fit for the role, often described as a straightforward and supportive interaction.
Candidates can expect a technical coding interview that emphasizes problem-solving skills and fundamental programming concepts, often involving straightforward coding challenges rather than complex algorithms.
Following the coding round, candidates typically engage in discussions focused on system design and debugging, assessing both technical reasoning and collaboration skills in a team environment.
The interview process includes behavioral questions that explore candidates' past experiences, teamwork, and cultural fit, with a focus on real-world scenarios rather than theoretical knowledge.
Candidates have reported varying experiences with communication and feedback throughout the process, with some appreciating clear instructions while others felt a lack of transparency and follow-up.
While many candidates found the interview process engaging and well-structured, some reported negative experiences related to scheduling issues or lack of closure, impacting their overall impression of the company.