J'ai postulé via la recommandation d'un employé. Le processus a pris plus d'une semaine. J'ai passé un entretien chez Google (Mountain View, CA) en mars 2010
Entretien
I was interviewing for an Engineering Manager position but what be came quite clear early on was that Google thinks that a manager is a technical lead. The interview was very challenging as I was prepared to discuss items like resource allocation, mentoring, schedule estimating, and other things that managers tend to do. The questions I was asked were purely technical and even included a coding exercise. While I read a great deal of code in my job, I do not write much. Needless to say, the interview did not go well especially when I confronted my interviewer on this discrepancy.
Questions d'entretien [1]
Question 1
I was asked a fairly involved Objective C question.
J'ai postulé via un recruteur. Le processus a pris 1 semaine. J'ai passé un entretien chez Google (Ciudad de Mexico) en mars 2026
Entretien
Primero es una conversación usual de filtro de posición revisando match de experiencia. Luego explicación de todo el flujo, es largo. Solo realicé el primer filtro técnico que son dos sesiones de diseño/arquitectura de sistemas. Durante la explicación proveen bastante material como videos y FAQs. Incluso sugieren agendar una "mock interview" para preparar y tener feedback antes de la real. Esa fue la parte mala, ya que la agendé pero jamás me contactaron y por cuestiones de calendario me pidieron adelantar las sesiones que tenía para semanas mas adelante por lo que sentí que no me preparé adecuadamente
J'ai postulé via la recommandation d'un employé. J'ai passé un entretien chez Google (Mountain View, CA) en janv. 2026
Entretien
Recruiter screen > Tech screen (coding + projects) > Onsite. Onsite was 5 rounds: People, Projects, Sys design, Coding/Code review, and Googlyness. Tech screen had some graph/dsa stuff but not super hard, more about the tradeoffs. Onsite is interesting. People and project rounds are standard: handling conflict and growing teams, project management style and thought process. System design: large scale distributed stuff and tradeoffs, and a coding/code-review round: they give a choice; I did code review and walked through a doc spotting bugs/efficiency issues (+1 if you think out loud). Googlyness: leadership philosophies and working with cross functional teams. Google EM guides on blind and reddit were helpful, also some grokking for sys design refresh. And yeah a mock on prepfully with a google em and it was very helpful; helped me realize I was being too humble and not showing enough so to say “emergent leadership" which is a huge signal there. Joined a week ago and loving the campus lol
Questions d'entretien [1]
Question 1
how would you design a system to monitor the performance of a machine learning model in real-time
I got a design interview. It was online.The design question was not too hard but there was a tricky part that the interviewer tried to get the a specific solution there.