Solicité el puesto a través de un captador. El proceso duró 4 semanas. Acudí a una entrevista en Google (Dublín, Dublín) en sept 2018
Entrevista
I was contacted by a recruiter, and went through a phone screening where they asked me basic data structures and algorithms questions (and the Big O complexity for insert/deletions etc).
I then went on to do a phone technical interview, which I was given a preparation demo for a week beforehand, which was very generous of Google.
The phone interview was very well conducted, the interviewer quickly made me feel comfortable and asked me some short quick questions about my CV (e.g. when did you last have a bug with socket.io? How did you resolve it?). I was then asked a coding question which was quite complex, and the more I tried to simplify it, the more the answer became clear, however I wasn't confident or skilled enough to approach it without wasting the interviewers time.
The interviewers and recruiters are brilliant, they genuinely seem to be egging you on and trying to back you up, I beleive they understand how these interviews can be, and are very good at making you feel you can pass it!
Preguntas de entrevista [1]
Pregunta 1
Given a data structure of rows (source, ratio, destination), find the value of conversion for a given source to a given destination. Example (EUR, 1.23, GBP)
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.
Envié una solicitud electrónica. Acudí a una entrevista en Google (Zúrich) en mar 2026
Entrevista
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.
Envié una solicitud electrónica. Acudí a una entrevista en Google (Dublín, Dublín) en mar 2026
Entrevista
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.