Zynga Interview Questions & Reviews

Interview Details – I had a initial phone interview asking about my qualifications. Afterward, an in-person interview was scheduled on the Zynga campus. The interview took I believe 4 hours from 10am-2pm. They provided lunch in between. Each interview was about half an hour, and someone with your same position talked to you off the record during lunch. Some interviews were more like a conversation, while others asks a lot of situational questions.

Interview Details – Phone interview ,Asked about my background, then shared a screen to write a program. Calculate the angle between a minute and hour hands in a clock.

Interview Details – Applied through a business school career site posting. Recruiter contacted me and we were able to set up a call. I happened to be in SF the week of the call, so when that went well Zynga very quickly scheduled me to come and interview at HQ two days later. The company got back to me two weeks later to say no.

The interview questions were largely geared toward consulting case questions, which is symptomatic of why Zynga is where it is.

Interview Details – Started off with an on campus interview at my university - 1 coding question and asked about projects. Was called for another phone interview which had to be rescheduled thrice as the interviewer did not show up each time. So when it finally happened, asked another coding question on a shared editor and some basic HR questions. Got the results in a few days and was flown to an onsite interview at SF. Everything was quite smooth from there, had 4 interviews - 2 with technical developers,1 with a manager and 1 with HR. Questions asked were quite standard - data structures, link-lists, hash tables, language specific and differences.

Interview Details – For the initial screening call, you'll want to emphasize your interest in gaming and show some familiarity with Zynga games (I'd pick a mobile game and a web game like Farmville 2). Notably, they typically ask if you have any ideas for new features and how you would implement them, and they look to see that you have a basic understanding of which engagement metrics to look at when evaluating the success of games (DAU, MAU, retention etc.).

Negotiation Details – It was an internship, standard package

Interview Details – Mostly by phone and some face to face interviews

Negotiation Details – not great, the recruiter I worked with was not very experienced

Interview Details – Started off with a campus 1 on 1 interview. They then asked me to come on site to meet with engineers on the team. There were 4 interviews, with tests ranging from simple bit manipulation to big-O analysis. Overall average difficulty.

Interview Details – I had one phone interview followed by a fly-out interview with about seven people that lasted all day. The phone interview consisted of a series of questions about CS fundamentals -- but no programming questions -- followed by a brain teaser and a few behavioral questions.

The in-person interview was obviously more rigorous, but being confident in the fundamentals and studying Programming Interviews Exposed was more than enough to prepare. Three of the interviews consisted of programming questions; one had a design/architecture focus; one centered on explaining CS concepts; and the others were largely behavioral.

Negotiation Details – The offer I received was better than I was expecting, so I didn't negotiate. When I mentioned that I was considering an offer from another company, though, I was asked if there was anything they could do that would convince me to go with them.

Interview Details – Asked me some simple behavioral questions (why do you want to work for Zynga etc). He also asked some very simple technical questions such as differences between C and Java, differences between a linked list and an array.