Passa al contenutoPassa al piè di pagina
  • Lavori
  • Aziende
  • Stipendi
  • Per le aziende

      Migliora la tua carriera

      Scopri le tue potenzialità di guadagno, trova lavori da sogno e condividi approfondimenti su lavoro e vita privata in forma anonima.

      employer cover photo
      employer logo
      employer logo

      Google

      Azienda coinvolta

      Circa
      Recensioni
      Stipendi e benefit
      Lavori
      Colloqui
      Colloqui
      Ricerche correlate: Recensioni su Google | Offerte di lavoro di Google | Stipendi di Google | Benefit di Google
      Colloqui di GoogleColloqui per Software Engineer L4 presso GoogleColloquio di Google


      Glassdoor

      • Chi siamo
      • Contattaci

      Aziende

      • Account Business gratuito
      • Spazio per le aziende
      • Blog per le aziende

      Informazioni

      • Aiuto
      • Linee guida
      • Condizioni d'uso
      • Privacy e scelte pubblicitarie
      • Non vendere né condividere le mie informazioni
      • Strumento per l'accettazione dei cookie

      Lavora con noi

      • Inserzionisti
      • Carriere
      Scarica l'app

      • Cerca:
      • Aziende
      • Lavori
      • Località

      Copyright © 2008-2026. Glassdoor LLC. "Glassdoor," "Worklife Pro," "Bowls" e il relativo logo sono marchi registrati di Glassdoor LLC.

      Aziende seguite

      Non lasciarti sfuggire opportunità e informazioni privilegiate seguendo le aziende dove vorresti lavorare.

      Ricerche di lavoro

      Ricevi suggerimenti e aggiornamenti personalizzati avviando le tue ricerche.

      Le migliori aziende per "stipendio e benefit" vicino a te

      avatar
      Amazon
      3.7★Stipendio e benefit
      avatar
      HENNGE
      3.8★Stipendio e benefit
      avatar
      xneelo
      3.8★Stipendio e benefit

      Colloquio per Software Engineer L4

      29 set 2023
      Candidato anonimo a colloquio
      Bengaluru

      Altre recensioni di colloqui per Software Engineer L4 presso Google

      Colloquio per Software Engineer L4

      19 apr 2026
      Dipendente anonimo
      Mountain View, CA
      Offerta accettata
      Nessuna offerta
      Esperienza positiva
      Colloquio difficile

      Candidatura

      Ho presentato la mia candidatura tramite un selezionatore. La procedura ha richiesto 3 mesi. Ho sostenuto un colloquio presso Google (Bengaluru) nel mese di gen 2022

      Colloquio

      1. Call from recruiter, with basic questions about competency 2. Request to apply on job portal for a specific job. 3. Email from recruiter with a ton of preparation material and job expectations. 4. We can choose our own interview dates; we can take a couple of weeks' time for preparation 5. Minimum 3 rounds of technical interview. If you do so bad at any round, then there may not be a further round. 6. System design round. 7. Personality round 8. The final result The overall process is slow and could vary anywhere between 1 - 3 months.

      Domande di colloquio [1]

      Domanda 1

      Leetcode-type questions for all the coding rounds. We have to think out loud, explain the trade-offs. There will be incremental questions. System design: A problem statement of a complex system will be given and we have start off with requirement clarification and work our way up to a solution, we should constantly check with the interviewer if we are going on the right direction and get their guidelines because the question would be vague and vast, we need to make sure we focus on those areas which the interviewer is expecting.
      Rispondi alla domanda
      Esperienza positiva
      Colloquio difficile

      Candidatura

      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

      Colloquio per Software Engineer L4

      7 mar 2024
      Candidato anonimo a colloquio
      Waterloo, ON
      Nessuna offerta
      Esperienza neutra
      Colloquio nella media

      Candidatura

      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.

      Domande di colloquio [1]

      Domanda 1

      Leetcode graph question that you solve with dps.
      Rispondi alla domanda

      Colloquio per Software Engineer L4

      21 apr 2023
      Candidato anonimo a colloquio
      Nessuna offerta
      Esperienza positiva
      Colloquio nella media

      Candidatura

      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
      Rispondi alla domanda