Ho presentato la mia candidatura tramite segnalazione di un dipendente. Ho sostenuto un colloquio presso Google (Mountain View, CA) nel mese di mar 2026
Colloquio
The process took about seven weeks from start to finish. It kicked off with a 30-minute recruiter call where we talked through my background, target teams, and compensation expectations. About a week later I had a technical phone screen over Google Meet with a senior engineer — one medium-hard coding problem on a shared doc, no autocomplete, no run button. I got passed through to the onsite loop, which was five back-to-back virtual interviews on a single day: two coding rounds, one system design, one "Googleyness and Leadership" behavioral, and one coding round that leaned more into problem-solving and edge cases than raw algorithms. After the loop, my recruiter told me packets go to the hiring committee weekly, so I waited about ten days for a decision. Once HC approved me, I did two team match calls — one with a Search Infra team and one with a team working on internal developer tools — and I picked the second. Offer came through roughly two weeks after team match, then negotiation took another week.
1
Altre recensioni di colloqui per Software Engineer L4 presso Google
Ho sostenuto un colloquio presso Google (Waterloo, ON)
Colloquio
They give you standard leetcode question and you need to answer while explaining your though process. You code on whiteboard and need to test your code without using an IDE.
Ho presentato la mia candidatura tramite un selezionatore. La procedura ha richiesto 5 mesi. Ho sostenuto un colloquio presso Google nel mese di apr 2023
Colloquio
i did several mock interviews, a technical screen, and the final round which was three technical interviews and a behavioral. i set the timeline for the whole process, personally it took four months but you can go faster if you want
Domande di colloquio [1]
Domanda 1
fairly straightforward, no tricks or gimmicks or even complicated algorithms, can be solved using hashmaps and lists, but require you to know basic runtime complexities and thoroughly evaluate tradeoffs, you kind of drive the design yourself