Le processus a pris 4 semaines. J'ai passé un entretien chez Google (New York, NY) en févr. 2011
Entretien
I had two phone interviews: the first was more product-focused: Let's talk about some Google products you use. What would you improve in them? How exactly would you improve this? Alright, now let's talk about Google Docs. If we wanted to add offline functionality and we wanted to automatically cache some documents, how would you go about deciding which ones?
The second interview also had some more general-purpose thinking questions. Like, if you are on a chessboard and you want to move a piece from the top left to the bottom right corner according to these rules, what is the minimum number of moves that would take?
All in all, a pleasant enough process with a responsive recruiter managing it.
Questions d'entretien [1]
Question 1
Let's talk about Google Docs. Let's say we wanted to offer offline functionality, and we want to automatically make some documents available offline. How would you go about deciding which ones?
J'ai passé un entretien chez Google (Kirkland, WA)
Entretien
You would have to do a hiring assessment first, then a recruiter screening follows. First round interview with the hiring manager. Majorly product sense and product improvement. The questions were not direct though.
Overall a lot of steps to the interview process. Talked to different people and had opportunities to ask questions. Many different stages which made it a lengthy process overall. Wasn't too bad.
resume screening, a recruiter call, and technical or role-specific interviews. Candidates complete coding, system design, or behavioral rounds. Onsite or virtual panels assess problem-solving, communication, and leadership. Feedback goes to a hiring committee, followed by team matching and final offer discussions.