Me postulé en línea. El proceso tomó más de 2 meses. Acudí a una entrevista en Google
Entrevista
Fully online, it was the messiest and the longest interview process ever. It took over 10 weeks for the final decision and 7 meetings. The first two meeting were with a recruiter who conducted a quick screening and on the next meeting explained the recruitment process and interviews order.
First interview (3rd meeting) was with a hiring manager who was asking mainly behavioral questions. That went well.
The second interview (4th meeting) was a technical one, during the first half I was being asked about linux, that went well too and during the second half the engineering guy said: "I can see you have chosen Java for your programming skills evaluation." Nothing in my resume says anything about Java, I provided my language preferences but the recruiter wasnt prepared for it so he started making up random questions , he became nervous and so did I.
The third interview (5th meeting) was db related. It was actually interesting sparring because I was providing answers in a technical context that my recruiter wasn't very familiar. A couple questions were related about tech I didn't know (and not included in cv).
The 4th interview (6th meeting) supposed to be about googliness but to my surprise it was another technical interview, mix of db, os questions. It went well.
I had to wait couple weeks to get a feedback response and the feedback was... 'a hiring committee is not ready to provide a feedback' :). I was once again asked to participate in another interview.
The 5th interview and the last one (7th meeting) was actually lost and found googliness with a support lead. It was again kinda behavioral/scenario/situational, the interviewer was friendly, I think it was a really good meeting.
Couple weeks of silence again. I emailed my recruiter twice, asking for a decision. I got the reply back that they are still very interested in my profile and they are setting up a meeting a site lead to introduce me. Then two weeks later a reject mail came.
Preguntas de entrevista [1]
Pregunta 1
networking on linux
db blocks
network mask
support questions
Me postulé a través de una facultad o universidad. Acudí a una entrevista en Google (California, MD) en feb 2026
Entrevista
Went fine, didn't get the job. The questions were really difficult and they did not give me time to prepare. I don't think they were very good at interviewing. Would not recommend this place to interview at
Great people and challenging questions. The process included about an hour with HR, followed by a second round with the team, making for a well structured and engaging interview experience
Me postulé a través de un reclutador. Acudí a una entrevista en Google (Hyderabad) en sep 2025
Entrevista
Very hard DSA round. It was scheduled for a 1-hour interview, but the problem was much more involved and could easily take longer than the allotted time. The question required strong algorithmic thinking, careful handling of edge cases, and the ability to reason through complexity under pressure. It was not just about writing code quickly; the interviewer expected a clear approach, optimizations, and clean implementation despite the time constraint. Overall, it felt like a round designed to test depth in data structures and algorithms rather than a standard timed coding exercise.
Preguntas de entrevista [1]
Pregunta 1
It was a very hard DSA round with a complex tree-based problem. Although the interview was scheduled for 1 hour, the problem felt like it could easily take much longer to solve fully. It required deep understanding of tree traversal, recursion, state management across nodes, and careful handling of edge cases. The challenge was not just arriving at a working solution, but also optimizing it and explaining the reasoning clearly under time pressure. Overall, it felt like a round meant to test strong problem-solving depth rather than a typical interview-length coding question.
