I applied online. The process took 3 months. I interviewed at Blizzard Entertainment (Irvine, CA)
Interview
I was contacted by a recruiter about 2 months after I submitted an online application. The recruiter and I worked out a time for a phone interview the following week. I was contacted the following week by 3 SW engineers/game developers. The interview started with a pretty standard phone screen. There were some technical questions related to the job description, questions on what I did for work, and questions on why I wanted to work at Blizzard. The interviewers were straight forward, a bit quiet, but seemed to really love their job.
After the phone screen, I was given a take home assignment to complete and turn in the following the day that was quite difficult (it was similar to a project one would encounter in an upper division class CS class) despite being told it would take a few hours. I correctly implemented the project and submitted it the next day. After a few days, a technical recruiter contacted me. As others have said, the recruiter's main question and concern was over expected salary. The recruiter's tone of voice was that of a greasy, shady car salesman and after telling him a salary range typical of mid-level developers (even on the lower end), he made a passive aggressive statement that I should do research on the average salary range of the Irvine area before coming up with a final answer. This is bizarre since most Fortune 500 companies and other tech companies negotiate salary after acquiring talent due to having large resources and income to acquire employees.
I was contacted the next week and the recruiter told me they wanted to fly me down for an interview since I did good in the interview and coding project, but immediately the salary expectation was brought up as if this was another "test" I had to pass. I told him a lower range for the base salary (low relative to what other mid level SW engineers earn in the area) but this value did not seem good enough for him, and he appeared to greatly annoy him. The tone of his voice immediately became more aggressive. The recruiter tried tried to inform me the salary range was typical of what senior engineers would make (it's not for the OC area if you actually perform the research using Glassdoor and other related job websites) and tried to sell me on lowering my salary expectations since there was profit sharing, 401k matching, vacation, and tuition assistance, which are all really standard perks of most big Fortune 500 companies. I agreed to his suggestion of the lowered base salary range and thought I would negotiate later on. The recruiter said they would love to fly me down but I had a feeling that this salary quibble would play negatively against me. I was left in the dark for about 5 weeks until I finally received an email informing me I would not fly down for an interview.
The take home lesson is if you really want to work for Blizzard, pass the technical interview AND give the salary range they expect, which seems to be lower relative to the other tech companies in the area. Be weary of shady, greasy recruiters trying to chastise you for expecting an average SW engineer salary; the demand for SW engineers is very high in OC, LA, and SD (not only the Silicon Valley) and such demand should be met with good pay for engineers.
Interview questions [1]
Question 1
The technicals questions were directly related to the job description. The coding project is a bit random but from my experience and reading other reviewers, it's usually relevant to the job position or what the engineers who interview you do.
I applied through a recruiter. The process took 4 weeks. I interviewed at Blizzard Entertainment
Interview
Getting to the interview was a bit of a mess. Several of my communications with the recruiter about my goals for the interview were seemingly ignored. This meant I was shoehorned into an interview that was not the best match for my skills and goals.
The phone interviews were direct, no-nonsense affairs that seemed to work well as a first evaluation.
The on-site interview itself was efficient. There was a programming quiz in the morning, then an afternoon debrief and multiple interview sessions. The people were friendly and all were gamers. They asked good questions about all aspects of game development, and made sure I had time to ask my own questions.
They made it pretty clear that they thought a person was lucky to have the opportunity to work for Blizzard. I unfortunately got the sense repeatedly throughout the day that my individuality would not be valued or respected, but that instead I would be added as a mere cog in the machine.
Interview questions [1]
Question 1
The programming test defined a data structure incorrectly. I solved the problem as defined, but the debrief ran into a roadblock because the programmers were expecting a solution based on a different definition of that data structure. Once I realized that had happened, I tried to come up with a solution on the spot. This was a good opportunity to show my ability to think on my feet, but involved some awkward back and forth as neither set of folks realized the disconnect right away.
I applied online. The process took 2+ months. I interviewed at Blizzard Entertainment (San Francisco, CA) in May 2014
Interview
I submitted my application through the careers site, and three weeks later I got an email from a recruiter wanting to set up a phone interview. The phone interview was a week later, and was with the hiring manager and another engineer. We talked about experience, the position, my background, and what they were looking for. There were some technical questions related to the position, and two programming questions that I answered in a shared google doc.
Another week later, I heard back that they wanted to bring me for an on-site interview. From that point, it took three weeks for them to get it scheduled, with several phone calls and emails to the recruiter just to get a status update as to what was going on.
The on-site was chaotic, but all the employees were nice enough. The schedule got changed at the last minute, meaning lunch got cut short in order to accommodate people's schedules, and things became very disjointed. I understand that things change, but it's a discomforting to have the entire schedule shifted when you arrive, and then the programming piece ended up being split between two separate time slots which really messed with the flow. Some folks felt like they were just stalling to fill time, while others were rushing through, because that had other meetings to go to. In the end, I was out of there an hour earlier than the original schedule said.
After that, I never heard another word back. I called and emailed the recruiter several times over the following few weeks, but never got any response. I found this unprofessional, given that I had actually come in for an on-site. I can understand not responding to every phone interview, but if someone makes it past that stage, the least you can do is let them know the status of their application.
Interview questions [1]
Question 1
NDA - just know your algorithms, data structures, etc., as well as skills relevant to the position.