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

      1 apr 2013
      Candidato anonimo a colloquio
      Nessuna offerta
      Esperienza negativa
      Colloquio difficile

      Candidatura

      Ho presentato la mia candidatura tramite un selezionatore. La procedura ha richiesto 9 mesi. Ho sostenuto un colloquio presso Google nel mese di feb 2012

      Colloquio

      For the reading impatient, in a nutshell: I found the interview process (non-US citizen) extremely long, very tedious, and in a sense dehumanizing (in your phone interviews you get your code questions, write the answers and very little else matters). Overall, the whole ordeal was very life draining, and comparing with peers that were going through it at the same time (as I later learned), very focused on a specific type of developer/engineer: without exception very experienced people were rejected. Google can hire whom they please, but if they know the profile of the person they want to hire, why bother contacting people with 10+ years of experience only to reject them all later? It's a waste of time for them and the interviewees even more so. One could arguably say that it is disrespectful as well. For those caring for all the details: I was contacted by a recruiter mid 2012, asking if I was interested in discussing a position. I'm not a US citizen, so I was dumbfounded. Of couse I was interested, but why would they contact me then? (I had sent a resume to Google Brasil years prior, with no response). So a month after I responded I finally heard back, and we agreed because of the project I was in and their timelines to start the process in December. Apparently someone had recommended me, and wanted to remain anonymous. So here we had about 5 months worth of time that I took to practice Portuguese again, brush up my resume with competitions, study, and get Android experience. During that time, I started to learn that certain other people in my country had also been contacted, some with a similar set of skills and experience. So clearly there was a larger, coordinated effort going on, not just an interest in myself, this made sense but it also made me more wary of it. December came and I contacted the recruiter once more, and they requested that we start the process in January. So New Years' studying and January came, and finally got a call. I was expecting a technical interview at once, but got another screening (similar to the one the year before) instead. After some email back and forth, a coding interview was scheduled for mid February. The interview itself was a coding problem of some calculations, and I thought I blew it. To my surprise I was contacted again the next week, and another interview set for the beginning of March. That one started by the engineer unable to call my phone, I had to call him international, and explain how to call me. Some 15 minutes were spent there. So finally I got some web system design and scalability questions, that (with guidance mind you) I think I answered successfully. I felt much better after that interview. But weeks rolled by with no response, I was a nervous wreck, so I wrote back asking what the status was (as April was a deadline for H1B), and eventually I got a response that because of the engineer's feedback the process was over for me. I honestly appreciated getting the response, but obviously was not happy. I was taken aback, but what surprised me even more was that engineers that I consider better than myself, were also getting interviews and also didn't get a lot further. The pattern seemed to be people with plenty of experience (10+ years), multiple team positions, and a history of leadership as well. A pattern hard to ignore. In the end, like I said, the experience was very life draining, I would not enter into it again lightly. Consider a hiring process that takes months and months (unnecessarily, ie. 3 months for 2 coding interviews), that is not a good indicator of the health of the hiring workflow.

      Domande di colloquio [1]

      Domanda 1

      Splitting a search query between different machines
      1 risposta
      7

      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

      9 giu 2026
      Candidato anonimo a colloquio
      Nessuna offerta
      Esperienza neutra
      Colloquio nella media

      Candidatura

      Ho sostenuto un colloquio presso Google

      Colloquio

      First call with recruiter. Mainly resume questions nothing too technical. Then methods round, was a tagged question from leetcode. Interviewer pushed back on first design and steered me to the optimal solution.

      Domande di colloquio [1]

      Domanda 1

      Why are you leaving your current role.
      Rispondi alla domanda

      Colloquio per Software Engineer

      7 giu 2026
      Candidato anonimo a colloquio
      Los Altos, CA
      Nessuna offerta
      Esperienza neutra
      Colloquio difficile

      Candidatura

      Ho sostenuto un colloquio presso Google (Los Altos, CA)

      Colloquio

      Went with an OA which was pretty easy. Then got to second round (1 coding and 1 behavioral). Both were pretty straight forward. Then got to the onsite. They asked me leetcode hard questions. I was able to do well in one but failed the other one.

      Domande di colloquio [1]

      Domanda 1

      Why do you want to work at Google?
      Rispondi alla domanda

      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