Process
It was kind of a long process. Months ago, I applied for the position, only to my surprise, I got an email about a phone interview. It was set up about two weeks later, followed by an in-person interview.
I had a great group of interviewers, very personable, not too hard at all. For this position, as long as you know what you're talking about and computers are second nature to you, it's easy as pie for the technical questions. The rest of the questions are team-oriented, and about the process of QA and bug finding. If you have never fixed anything in your life or worked out a problem backward to see where the fault lies, this will be hard for you. If not, good luck.
Questions
Two programs that are linked together are not performing the way they should. How do you find the bug that is causing the communication issue?
Was this helpful?
Interview Statistics
The following metrics were computed from 2 interview experiences for the Blizzard QA Analyst I role.
Success Rate
Blizzard's interview process for their QA Analyst I roles is incredibly easy as the vast majority of engineers get an offer after going through it.
Experience Rating
Candidates reported having very good feelings for Blizzard's QA Analyst I interview process.
Blizzard Work Experiences
- 5.0Love working in hereWeb Developer • Current EmployeeJanuary 29, 2020Pros: Well, at least our team has a good manager. Okay salary.Cons: Can't think of anything right now.
- 5.0Great Intern Support, Few EventsSoftware Engineer (Internship) • Current EmployeeIrvine, California, United StatesAugust 22, 2021Pros: Provided great support to interns, even though it was a virtual internship.Cons: I wanted to see more intern-specific events while understanding that it is hard to frequently hold an event virtually.
- 3.0Great when I started, going downhill painfullySoftware Engineer • Former EmployeeIrvine, California, United StatesOctober 12, 2013Pros: Some very smart and great people to work with. Games are great and the employees do care about the product.Cons: Growth in some critical departments (QA) was too fast for the inexperienced management team to handle. Their response was to hire more inexperienced and out-of-industry people, which made the problem worse.
