J'ai postulé en ligne. Le processus a pris 3 semaines. J'ai passé un entretien chez Google (Sydney)
Entretien
I received an email from a Google recruiter asking for a time to schedule an initial phone call. After a few emails, the date was set for a week later
The first call came, it lasted about 60 minutes, it went from theoretical to a very technical level of questions
After a few days I received an invitation for a round of on site interviews in their premises in Sydney. Since the time I would have taken to get there for me was about 3 to 4 weeks (due to visa constrains) they decided to continue with the phone calls interviews
The next interview took almost 90 minutes
Questions d'entretien [1]
Question 1
During the first call, I was prompted at first with very basic questions about operating system and networking, then in went deeper on questions like: "what happen if you type telnet www.google.com", the questions within this one ranged from "tell me the process uses the OS to create that connection" to "how the data travels through the internet to reach the target server".
The second call went even deeper in troubleshooting Linux, web servers, dns, load balancing, IP, routing and so on. Also, the recruiter asked me to code some python and bash scripts in order to solve some problems made for that interview
J'ai passé un entretien chez Google (Waterloo, ON)
Entretien
HR round after applying, then coding screening round, if passes, then final round which consists of four coding round or three coding and one design round. Problem difficulty medium to hard.
J'ai postulé en ligne. J'ai passé un entretien chez Google (Zurich) en mars 2026
Entretien
Frist had one roughly 20 to 30 minutes screening call with a recruiter, then had one online 45 minutes technical interview with a Google Site Reliability Engineer. The technical interview covered data structure and algorithm topics.
J'ai postulé en ligne. J'ai passé un entretien chez Google (Dublin, Dublin) en mars 2026
Entretien
The interview lasted 45 minutes and was conducted one-on-one. I was required to walk through my thought process before coding and then implement an optimized solution with a focus on time complexity.