Ho presentato la mia candidatura online. Ho sostenuto un colloquio presso Google (Tel Aviv) nel mese di mag 2025
Colloquio
The interview process was intense but well-structured. It started with an online assessment that included data structures and algorithm questions. After passing that, I had two technical interviews focusing on system design, problem-solving, and backend architecture. I studied independently using resources like LeetCode, Grokking the System Design Interview, and YouTube mock interviews. The interviewers were friendly and gave hints when I got stuck, which helped reduce the pressure. Preparation required serious dedication, especially for the system design round. I also reviewed computer science fundamentals like operating systems, networks, and databases.
Domande di colloquio [1]
Domanda 1
Q: What was the one thing that they asked you?
Design a URL shortening service like TinyURL. They wanted to hear about the API design, database schema, how to handle collisions, rate limiting, and scaling it to millions of users.
Ho presentato la mia candidatura tramite segnalazione di un dipendente. Ho sostenuto un colloquio presso Google (Gurgaon, Haryana) nel mese di set 2025
Colloquio
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
Domande di colloquio [1]
Domanda 1
Dynamic programming based dsa questions, prototypes and promises in javascript
Ho sostenuto un colloquio presso Google (Washington, DC)
Colloquio
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.
Domande di colloquio [1]
Domanda 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.
Ho sostenuto un colloquio presso Google (Los Angeles, CA)
Colloquio
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.
