Applied online for the backend server position. The first phone call was a standard HR phone call with the recruiter. The second was a call with lead/senior engineers about experience and standard C++/object-oriented questions. After that, I completed a HackerRank challenge. Then, an onsite interview with a tour around their facility (extremely cool), system design, coding, lunch, and a culture fit interview. Questions were standard and not unnecessarily difficult, like at other tech companies. It pretty much served as a real indicator for them if you have the experience that they are looking for or not. I heard a couple of business days later that they would not move forward with me.
While I was very disappointed not to get the offer, I was very appreciative of the team for being super friendly, very communicative throughout the process, and being kind enough to explain things that I didn't know / help me get to the solution they were looking for, as well as providing sufficient feedback on what I could improve on in the future. Many companies don't provide any specific feedback, and you are left wondering.
They did show that they understand that interviewing is stressful for candidates and that they care to make it a great experience for them regardless of the outcome.
Easily the best interviewing experience I have ever had with any company.
I signed an NDA, but I'll say focus on distributed systems and how to design a feature. Be sure to know your multi-threading/thread synchronization tools for real scenarios, as well as standard data structures and algorithms.
The following metrics were computed from 15 interview experiences for the Blizzard Software Engineer role in Irvine, California.
Blizzard's interview process for their Software Engineer roles in Irvine, California is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having very good feelings for Blizzard's Software Engineer interview process in Irvine, California.