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 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.

      Colloquio per Software Engineer

      29 apr 2010
      Candidato anonimo a colloquio
      Nessuna offerta
      Esperienza neutra
      Colloquio nella media

      Candidatura

      Ho presentato la mia candidatura tramite segnalazione di un dipendente. La procedura ha richiesto 3 giorni. Ho sostenuto un colloquio presso Google nel mese di mar 2010

      Colloquio

      Quick phone call with a recruiter to schedule two interviews. She asked me what language I'd like to be interviewed in. My recent experience is primarily C, but I was expecting to be given the sort of high-level algorithmic problems for which having to build my own data structures would be too time consuming, so I said I would prefer C++. We scheduled my interview to be two weeks away to give me some time to teach myself C++ and the STL. I was supposed to have two interviews on the same day, but one of the interviewers never called me. The one who did call was very friendly and intelligent, but I was caught a bit off guard that all he wanted to ask me were C string manipulation questions. I'd normally be good at this sort of stuff, but I was surprised and I panicked, and I didn't do as well as I should have. My other interview was rescheduled for a couple of days later. Once again, I really liked me interviewer. He asked me some higher-level algorithmic questions, with a bit of an AI bent to the them. Interesting stuff. It was interesting stuff, and I eventually came to the solutions he was looking for, but it took some prompting. In the end, I wasn't invited to a second round of interviews and I wasn't particularly surprised by this. There's a huge difference between writing your own code on your own time or even on a test in school and writing code with someone watching your every keystroke. I found it very stressful. The questions they asked me weren't particularly difficult, but the context in which I had to solve them wasn't something I was ready for.

      Domande di colloquio [1]

      Domanda 1

      Design and write a sudoku solver.
      1 risposta

      Altre recensioni di colloqui per Software Engineer presso Google

      Colloquio per Software Engineer

      4 mag 2014
      Dipendente anonimo
      Auburndale, FL
      Offerta accettata
      Esperienza positiva
      Colloquio difficile

      Candidatura

      Ho presentato la mia candidatura tramite segnalazione di un dipendente. Ho sostenuto un colloquio presso Google (Auburndale, FL) nel mese di apr 2014

      Colloquio

      Direct onsite because I interviewed in the past and did well that time. From the time I sent my resume to interview day: 2 weeks. From interview day to offer over the phone: 2 weeks. The syllabus for the interviews is very clear and simple: 1) Dynamic Programming 2) Super recursion (permutation, combination,...2^n, m^n, n!...etc. type of program. (NP hard, NP programs) 3) Probability related programs 4) Graphs: BFS/DFS are usually enough 5) All basic data structures from Arrays/Lists to circular queues, BSTs, Hash tables, B-Trees, and Red-Black trees, and all basic algorithms like sorting, binary search, median,... 6) Problem solving ability at a level similar to TopCoder Division 1, 250 points. If you can consistently solve these, then you are almost sure to get in with 2-weeks brush up. 7) Review all old interview questions in Glassdoor to get a feel. If you can solve 95% of them at home (including coding them up quickly and testing them out in a debugger + editor setup), you are in good shape. 8) Practice coding--write often and write a lot. If you can think of a solution, you should be able to code it easily...without much thought. 9) Very good to have for design interview: distributed systems knowledge and practical experience. 10) Good understanding of basic discrete math, computer architecture, basic math. 11) Coursera courses and assignments give a lot of what you need to know. 12) Note that all the above except the first 2 are useful in "real life" programming too! Interview 1: Graph related question and super recursion Interview 2: Design discussion involving a distributed system with writes/reads going on at different sites in parallel. Interview 3: Array and Tree related questions Interview 4: Designing a simple class to do something. Not hard, but not easy either. You need to know basic data structures very well to consider different designs and trade-offs. Interview 5: Dynamic programming, Computer architecture and low level perf. enhancement question which requires knowledge of Trees, binary search, etc. At the end, I wasn't tired and rather enjoyed the discussions. I think the key was long term preparation and time spent doing topcoder for several years (on and off as I enjoy solving the problems). Conclusion: "It's not the best who win the race; it's the best prepared who win it."
      2501

      Colloquio per Software Engineer

      4 giu 2026
      Candidato anonimo a colloquio
      Varsavia, Masovia
      Nessuna offerta
      Esperienza positiva
      Colloquio nella media

      Candidatura

      Ho sostenuto un colloquio presso Google (Varsavia, Masovia)

      Colloquio

      remote round - on the same day, 45 minute technical interview, then 45 minute behavioral interview. there was also plenty of time to ask questions afterwards, so be prepared at least three or so to show interest

      Domande di colloquio [1]

      Domanda 1

      a list of ranges like [0,1], [2, 5], ... . create a class with methods to find if element is in any range and insert a new range
      Rispondi alla domanda

      Colloquio per Software Engineer

      4 giu 2026
      Candidato anonimo a colloquio
      New York, NY
      Nessuna offerta
      Esperienza positiva
      Colloquio difficile

      Candidatura

      Ho sostenuto un colloquio presso Google (New York, NY)

      Colloquio

      Didn't pass the phone screen. It was a leetcode medium question. I think I got it right, but maybe I was too slow in finishing the problem. Maybe it was something else

      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