I applied online. The process took 3 weeks. I interviewed at Zynga (San Francisco, CA) in May 2015
Interview
I applied online. A phone screen was scheduled a week later. It's technical in natural, but nothing too difficult. Clearing that, I was scheduled for the on-site interviews. There were 6 rounds of 45 min one-on-one interviews. They were more technical and challenged than the phone interviews, but nothing at the Google level. 2 of them were on system design. Other 4 focused more on algorithm. They would also ask about your experience and projects. Try to give them some challenging and interesting stories. There were also 3 extra informational interviews which are mainly to meet the manage/director/lead. I think it's a very nice gesture for them to meet and talk to candidates.
Interview questions [1]
Question 1
* String traversal.
* Word search in matrix.
* Give one challenging project story.
The process took 2 weeks. I interviewed at Zynga (San Francisco, CA) in Mar 2016
Interview
- Initial HR phone screen.
- Phone screen with engineering team of various levels.
- Fly-out for all day discussion with other Senior-level engineers about process, projects, and decisions.
- Discussions with manager about team structure and potential role.
Interview questions [1]
Question 1
Discuss experiences listed on resume at a high level then get into low-level details, as would be expected for the role.
I applied through an employee referral. The process took 4 weeks. I interviewed at Zynga (San Francisco, CA) in Feb 2016
Interview
On the basis of an employee referral, I sent in my resume for the position that focused on Javascript with some HTML/CSS. The initial phone screen was part behavioral and part technical, with some coding done over Collabedit (not as nice as some I've seen). There was real-world binary tree question.
Then there was a a 4-part on-site interview. Three were one on one, and one had two people. I was interviewed by the engineering manager for the position, a more senior engineering manager, a senior executive (former engineer), and a panel of a potential colleague and a more senior engineering manager.
I had a chance to step out, use the restroom and grab snacks/a drink, but four+ hours is a long time to be stuck in a room proving yourself. Still, it probably wasn't as bad as I had feared.
I felt like all of the problems were actually quite reasonable and made sense for working with the particular game. This was not just bizarre algorithms for the sake of being obscure. I felt like I was clueless about a lot of things, but I was able to push on, thinking out loud so they knew where I was trying to go.
After it was all said and done it took a little over a week to hear back from them.
Interview questions [3]
Question 1
What considerations would you have if we wanted to add a certain kind of feature to this game with over a million daily players?
Looking at a small portion of the game, how would you go about validating a play?
If you won the powerball lottery today, what would you do tomorrow? (I think I was supposed to say: I'd still make games, because I love it! I was more pragmatic, but hopefully still positive.)