Envié una solicitud electrónica. El proceso duró 2 meses. Acudí a una entrevista en Google (San Francisco, CA) en mar 2009
Entrevista
Interviewing with Google was not bad. They have a process of phone interviews, where you use Google Documents during the interview to write answers to programming questions. They ask a variety of computer science questions and are interested in seeing how you think. Overall, nothing too surprising.
The corporate culture seems very good, and this is what attracted me to the company in the first place. They seem genuinely interested in finding people who are excited by the prospect of solving challenging problems. The best questions during the interviews were the ones where the interviewer presented a problem from his relevant Google project and asked for ideas on how to address it.
Preguntas de entrevista [1]
Pregunta 1
Given this Google product, how would you address this technical challenge? What kinds of algorithms would you use?
Envié una solicitud electrónica. Acudí a una entrevista en Google (Sídney)
Entrevista
Online application, then reached out for a phone call with an external recruiter. Here was told to expect two (eliminatory) technical interviews, no behavioural assessment. These technical interviews were scheduled about two weeks apart. Heard back within a day or two from final round.
Preguntas de entrevista [1]
Pregunta 1
Standard medium, and hard leetcode questions respectively.
I recently had a Google interview that included two coding questions: one about binary trees and another about strings. Each interview lasted 45 minutes and focused on problem-solving, coding accuracy, and explaining my approach clearly. It was a challenging
Preguntas de entrevista [1]
Pregunta 1
Two questions, one about binary tree and the other about strings
There was an Online Assessment that you had to complete. Once you pass that, you'll have 2 Technical interviews. Finally, you reach the Team Match Phase, where you will have host calls with teams at Google. (1 call, 1 offer)
