Contacted by a recruiter a couple of weeks after applying, I set up a phone interview with an engineer.
He asked me some basic questions about my resume and we verbally went over a quick coding exercise.
I was contacted a couple days later to do a Skype interview with some engineers. We set this up for about a week later.
This interview was much harder than the first one. They sent over a PDF with three coding problems on it, and I went over the problems and solved them with the engineers by sharing a Google Doc.
A couple days later, I was told they would like to bring me in for an on-site interview. They flew me out all the way from the East Coast, and I spent the day interviewing and seeing the campus.
The first interview was pretty challenging, but not as bad as the Skype one. It didn't involve writing any actual code and was more about going over problems verbally.
The second interview was a lunch interview and actually didn't really feel like an interview at all.
The last one was with the team leader, who was the first person I spoke to. He asked me to do one relatively easy coding problem on a whiteboard and then told me they would be making me an offer at the end.
The overall experience was great. Their headquarters is amazing, and it killed me a bit to decline the offer, but after weighing all of my options, I think it was the right choice.
I'm going to apply there again in the future when I feel more ready to make a career move like this one.
Questions about data structures and algorithms.
Signed a non-disclosure agreement.
The following metrics were computed from 1 interview experience for the Blizzard Associate Software Engineer - Risk Systems role in Irvine, California.
Blizzard's interview process for their Associate Software Engineer - Risk Systems roles in Irvine, California is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Blizzard's Associate Software Engineer - Risk Systems interview process in Irvine, California.