Taro Logo

Software Engineer Interview Experience - Irvine, California

August 18, 2017
Negative ExperienceNo Offer

Process

The process took a little over a month.

I applied online by reference and briefly spoke to a recruiter over the phone. She asked me general questions, including about my expected salary.

A week went by, and then I was asked to do a phone interview. The phone interview consisted of many behavioral questions mixed with general technical questions, mostly discussing C# vs. C++, WPF, MVVM, and UI. There were no riddles or anything like that.

I then received a test via email, asking me to create a tool and send back the code. Less than 24 hours after submitting it, I was invited for an onsite interview, which is a marked improvement over my last interviews with Blizzard, which took over a month to hear back from.

I visited onsite from 10 AM to 5 PM. There were groups of interviews with people from the team from all areas: artists, designers, producers, and the team I was applying for. They all asked nearly identical questions but were very nice people. It was an enjoyable experience, but the technical questions were a bit of a mess. At one point, there was even a debate and disagreement among the interviewers, who referred to Google for the answer. It wasn't particularly impressive and kind of threw me off. I was also asked some rather low-level binary questions that were much different from the test and what was on the phone interview, which I hadn't expected. They felt like they came out of nowhere. I believe those are why I was rejected; I didn't respond quickly to them. They were kind of irrelevant to the role, though, so it was disappointing and put a damper on things. But that was early on, so we still interviewed with everyone else.

I was told I would hear back the next day or after the weekend on Monday. A week went by without word, and I had to email twice over several days before getting a response at the end of the day on a Friday. I was rejected with no feedback. I'm not sure it was worth all that time and effort, and the recruiter was slow to respond. They didn't even call to give news or acknowledge the emails.

Questions

What is MVVM, and why would you use it versus alternatives?

Have you used Winforms? Why is it dated?

Was this helpful?

Interview Statistics

The following metrics were computed from 15 interview experiences for the Blizzard Software Engineer role in Irvine, California.

Success Rate

47%
Pass Rate

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.

Experience Rating

Positive67%
Neutral13%
Negative20%

Candidates reported having very good feelings for Blizzard's Software Engineer interview process in Irvine, California.

Blizzard Work Experiences