Four candidates describe Blizzard software engineering interviews: recruiter and hiring manager conversations, a timed online or HackerRank assessment, and for one senior candidate a four-interview loop with system design.
$138K
Avg. Base Comp
$155K
Avg. Total Comp
3-6 rounds
Typical Rounds
Not reported
Process Length
Candidates who interviewed for Blizzard engineering-related roles describe a process that starts conversationally and gets technical quickly. Recruiter calls covered background and interest in Blizzard. One gameplay engineer candidate was also asked about their experience with Blizzard games such as Overwatch, so know the portfolio and have a personal answer ready.
The most repeated technical theme is hashmaps and concurrent data structures. A gameplay engineer candidate was asked how a hashmap works and how to recreate it from scratch. A senior candidate was asked what could substitute for a HashMap and how to build a concurrent version. Expect to explain internals and trade-offs, not just name APIs.
Assessments differ by role. The gameplay candidate reported a 2-hour HackerRank test. An internship candidate reported a 45-minute online assessment built around a calculator that handled parentheses, powers and floating-point numbers, and said feedback was slow.
The senior candidate's final loop had four interviews: system design for a shared event-ingestion and data-processing pipeline, a homework coding assignment, and two behavioral or leadership rounds. That candidate was told to treat interviewers as colleagues and think aloud, and was interrupted often with suggestions. Practice talking through a solution while taking input. An SDET candidate faced mostly behavioral and design-philosophy questions, including how game testing differs from other testing. All four reported no offer, so use these reports as preparation signals rather than a fixed format.
Synthesized from 4 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Blizzard Entertainment process.
I applied to Blizzard back in early 2024 and got contacted by a recruiter a few months later. The process started with a HireVue screening, which was pretty standard—just me on camera answering questions. Then I had a one-on-one with the recruiter, which felt more like a conversation than an interrogation. After that, they sent me an online assessment to complete.
The OA itself was brutal. I got a calculator problem that required handling addition, subtraction, multiplication, division, parentheses, power operations, and floating-point numbers. It sounds simple on the surface, but the implementation was genuinely complex—you had to think about operator precedence, nested parentheses, and precision with doubles. They gave me 45 minutes to solve it, which felt tight for an internship-level position. I managed to get some test cases passing, but not all of them. The real kicker was the timeline: I'd applied months earlier, done the screening and recruiter call, and then had to wait even longer for the hiring manager and engineering teams to review my OA. By the time they actually looked at my submission, the positions had already been filled by other candidates.
Prep tip from this candidate
If you interview at Blizzard, expect the OA to be significantly harder than typical internship-level problems—think modified LeetCode hard questions with tight time constraints. Practice implementing parsers and expression evaluators with operator precedence and floating-point edge cases, and be prepared for a slow feedback loop between rounds.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Blizzard Entertainment
Design a scalable event data pipeline for real-time, multi-application ingestion and processing.
| Question | |
|---|---|
| Video Game Respawn Model | |
| 2nd Highest Salary | |
| Integer to Roman | |
| P-value to a Layman | |
| Google Maps Improvement | |
| Nearest Common Ancestor | |
| Groups of Anagrams | |
| Hurdles In Data Projects | |
| Tower of Hanoi | |
| Valid Anagram | |
| Find Duplicate Numbers in a List | |
| Spam Classifier | |
| Customer Success vs. Free Trial | |
| Rider Discount | |
| Track Your Most Valuable Gamers | |
| Matrix Rotation | |
| KNN From Scratch | |
| Subscription Retention | |
| Concurrent LLM Serving | |
| Worker Distribution Dilemma | |
| Implementing the Fibonacci Sequence in Three Different Methods | |
| User Event Data Pipeline | |
| Moving Window | |
| Confidence Interval Explanation | |
| Loan Model | |
| Cloud-Agnostic Deployments | |
| Deciding Between Solutions | |
| Drink Production Allocation | |
| International e-Commerce Warehouse |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an initial recruiter conversation about their background and motivation. One gameplay engineer candidate was asked about Overwatch and other Blizzard games, and an SDET candidate was asked about game development experience. Tone was described as friendly. An internship candidate also reported a HireVue screening before the recruiter call.
Two candidates describe a hiring manager call that went into technical depth without live coding. Questions reported include how a hashmap works and how to rebuild it, and what to use instead of a HashMap and how to make a concurrent version. Candidates may also be asked about current projects and trade-off thinking.
Candidates report timed or take-home coding work. One reported a 2-hour HackerRank test, another a 45-minute online assessment with an expression-evaluator calculator problem, and a senior candidate described a homework coding assignment. Format likely varies by role and level, so confirm details with your recruiter.
A senior candidate reports four back-to-back interviews: system design for a shared event-ingestion pipeline, a collaborative coding session, and two behavioral or leadership rounds. An SDET candidate reported three one-hour interviews with two to three interviewers each, focused on conflict with managers, automation design and game testing. Not every role reported a loop like this.
