Envié una solicitud electrónica. El proceso duró 2 días. Acudí a una entrevista en Google (Hyderabad) en jun 2022
Entrevista
The interview process was smooth, consisting of three rounds: a screening test, a job role interview, and a managerial round. Each step was clear, well-organized, and professional throughout. Overall a great experience with the interviewer.
Preguntas de entrevista [1]
Pregunta 1
Basic questions like a scenario was given and was asked how would I respond to that and reach to the solution
Solicité el puesto a través de la escuela superior o la 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
Solicité el puesto a través de un captador. Acudí a una entrevista en Google (Hyderabad) en sept 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.
