Me postulé a través de una recomendación de un empleado. El proceso tomó 2 semanas. Acudí a una entrevista en Zynga (San Francisco, CA) en jun 2012
Entrevista
1st Interview: Phone interview. Asked the usual introduction stuff, why zynga. what interested me about the position,etc.etc. Then I was questioned on my past experience with working big data and asked to give examples of what types of analysis I conducted. Then i was asked what skills in excel I had developed to clean data sets.
2nd Interview: Panel Interview. I interviewed with 4 different members of the CRM department. I was thought this would be more of the meat and potatoes section of the interview, but they threw me a curveball and asked to list the "motto's" of Zynga( Be your own CEO, Move at Zynga Speed), let's say i didn't expect them to ask to that degree. Then I was asked, in great detail, about my past experiences analyzing data and to give examples of when my analysis had helped to make clear decisions. I was quizzed on some statistical concepts. All four interviewers followed the same type of format. They all said the same thing, that I am more than qualified for the position with my work and educational background, but I was not offered the position.
Preguntas de entrevista [1]
Pregunta 1
Please list Zynga's Mottos and give an example of how you represented that in your past work experience.
Me postulé a través de una recomendación de un empleado. Acudí a una entrevista en Zynga
Entrevista
Started with an initial phone screen by a Central Analyst. This took about 20 minutes. He asked questions like:
-Why Zynga?
-Give me an example of when you used data analysis to make a decision
Then followed up with a on-site interview with 4 1:1 interviews. Each interview went along the same lines:
-Why zynga?
-Give me an example of when you used data analysis to make a decision.
-Pick one of Zynga's mottos and tell me when you clearly exemplified this in previous work.
-What are your excel skills?
-How would you try to make a compelling argument to the development team to put in the work necessary to fix a bug that only affects a small percentage of our users?
