Envié una solicitud electrónica. Acudí a una entrevista en Google (São Paulo, ) en may 2023
Entrevista
Foi muito produtiva, gostei muito dos recrutadores mas não deu certo no final por falta de experiência, mas foi uma boa entrevista acho que as perguntas foram corretas e não teve muitas pegadinhas
Preguntas de entrevista [1]
Pregunta 1
Com qual recurso da gcp podemos armazenar dados em alta escala
Solicité el puesto a través de la recomendación de un empleado. Acudí a una entrevista en Google (Gurgaon, Haryana) en sept 2025
Entrevista
Four rounds Round 0 was dsa round , round 1 they provide an assignment with questions where we have to provide output to them, round 3 they review the project then in last they ask the techstack related questions
Preguntas de entrevista [1]
Pregunta 1
Dynamic programming based dsa questions, prototypes and promises in javascript
So, I recently went through the Google backend engineer interview process, and wow—it’s as intense as they say. It all started when a friend referred me, and within a week, a recruiter reached out. The initial chat was pretty chill; mostly about my background, projects, and why I was interested in Google. I mentioned my experience with distributed systems, API development, and scaling microservices. The recruiter gave me a rough idea of the upcoming rounds and told me to brush up on data structures and algorithms. I nodded confidently while quietly panicking inside. Still, it felt exciting to even get this far.
Preguntas de entrevista [1]
Pregunta 1
Oh man, one question really stuck with me—it was during one of the technical interviews. The interviewer asked me to design a URL shortening service, like Bitly, but with a twist: it had to scale to billions of URLs and support custom aliases. At first, I was like, “Cool, I’ve seen this on system design prep lists,” but then they hit me with follow-ups about handling high availability, rate limiting, and eventual consistency across data centers. We dove into hashing strategies, database choices (SQL vs NoSQL), and cache layers using Redis. They asked how I’d prevent collisions and how I’d handle abuse—like people using the service for malicious links. It turned into a full-blown distributed systems discussion, and my brain was both thrilled and slightly melting. Easily the most fun (and most humbling) part of the interview.
Acudí a una entrevista en Google (Los Angeles, CA)
Entrevista
Lots of technical questions and some skill tests. Took about two months but was in contact whole time. The process was smooth and controlled. The people were nice and I feel like they were looking for me to ask questions.
