Me postulé a través de un reclutador. Acudí a una entrevista en Google (Mountain View, CA)
Entrevista
Starts with a recruiter contacting you, followed by a pair of phone interviews that act as a pre-screen to see if it's worth bringing you in. After the first one, if it went well enough, you go on to a second phone interview.
If all went well so far, they bring you on campus for 5 consecutive interviews, each 45 minutes with a 45 minute lunch. The lunch "meeting" is a fun time getting to know potential peers and their experiences. You get to learn and corroborate what you hear about Google. It is a great place to work and why it's in high demand.
I didn't get a job offer, but was told the next step would've been to move it to a hiring committee, who acts as an unbiased neutral third party to ensure the recommendation is unbiased. They record all your answers and type a lot while you're talking and apologize in advance for doing so and inform you that it's part of the process to capture as much information to present to the hiring committee.
Presumably, had I made it that far the next step would've been a job offer. The whole thing from start (the onsite interviews) to finish (a job offer is extended) would've taken a minimum of three weeks.
Preguntas de entrevista [1]
Pregunta 1
Lots of questions that have an undertone of some of the things that make Google what it is, for instance, how would you build up the infrastructure for a search engine-where do you deploy servers and why? How would you identify keywords in search results? Etc. Try to understand how you'd do what Google already does is my advice and how'd you'd implement your own search engine. Although it's not a software engineer position, they expect you to know how to code. Make sure you know your syntax (whatever syntax you feel comfortable with). Brush up on algorithms, but no need to get fancy with your answer, just need something that works and is practical. Just remember, they will test you technically on software, which I found interesting considering the group I applied to it would've been more relevant to be tested on hardware knowledge, which I had zero questions about.
If you've been a project manager before, a lot of the questions are pretty easy if you can relate the answers to real life scenarios. Didn't think it was particularly hard, though no job offer was extended.
Four interviews broken up over 2-3 days. These include Role Related Knowledge, Googleyness & Leadership, General Cognitive Analysis, and Technical Judgement. This is about as much as I can provide on these topics.
Took over a year. The interview process was incredibly drawn out and insanely long. In the end I couldn't find a match. The manager I met with crossed her arms and actually rolled her eyes at me as soon as I said hello and asked her how her day was going.
Preguntas de entrevista [1]
Pregunta 1
How do you prioritize multiple projects with impeding timelines
Me postulé a través de un reclutador. El proceso tomó 4 meses. Acudí a una entrevista en Google (Mountain View, CA) en feb 2023
Entrevista
It was a long and tedious interview process. The recruiter forgot about me several times and they were the one who contacted me. I had to keep following up. I had a screen with the recruiter, then a follow up call with a TPM for questions the recruiter couldn't answer, then a first interview with TPM. After that I would have had an onsite day long interview.
Preguntas de entrevista [1]
Pregunta 1
You have 1000 cars and need to get photos of all the world into Google street view. How would you solve this problem, let's brainstorm.