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

      Chi siamo
      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

      7 gen 2015
      Dipendente anonimo
      Offerta accettata
      Esperienza positiva
      Colloquio difficile

      Candidatura

      Ho presentato la mia candidatura tramite un selezionatore. La procedura ha richiesto 3 settimane. Ho sostenuto un colloquio presso Google nel mese di nov 2014

      Colloquio

      CONTEXT: I had been contacted by different Google recruiters over the past few years (and had been referred internally but I didnt know about that) and I had kept asking them to contact me later. FIRST CONTACT: I was then again contacted first for an S.R.E position. The recruiter took a mini 5-10 interview about time complexities and some Linux systems questions which they expected people to be well versed in. The recruiter was a little misleading about what the position was about and made it sound alot closer to S.W.E than it actually is. I did my research spoke with people who interviewed for SRE. I then insisted that I wanted to interview for SWE. The recruiter tried hard to convince me to apply for SRE but my heart was not in it. EVENTUAL CONTACT: After 1-2 conversations with the recruiter, I was then handed over to another recruiter for SWE. I had multiple conversations so that they can ascertain which team should interview me and what should be a good fit. They really do try to set you up for success, I can assure you that much. They were unable to initially be precise about which team I would be a fit for. So they suggested that I atleast do the phone interview (which would be reaosonably generic) and then that would give them some clues. PHONE INTERVIEW STAGE: I gave the phone interview and next day got an email that they want to move forward. I then spoke with a different recruiter who was supposed to handle my case. I again had some clarifying conversations with her about my strengths and interests and made sure that my onsite interview would be something that I expected it to be. This recruiter was fantastic and very detail oriented. I had limited time because I had 2 existing offers whose deadlines were approaching. They scheduled my interview on a day of my choosing. ONSITE INTERVIEW STAGE: The onsite interview went well. The interviewers were friendly and polite. Some young, some slightly older. They were excited to be a part of Google. I had a great time talking and solving questions. The interview questions were not very difficult. I concentrated alot on code organization, cleanliness and correctness. Debugging my code in the interviews and convincing myself and the interviewer of the absolute correctness was very important. If you are comfortable with recursion, Dynamic programming, Arrays, Trees etc that should be fine. I dont think they really wanted to test knowledge of advanced concepts. They concentrated more on basic fundamentals, good solutions, clean & correct code. There were 5 technical interviews and 1 lunch interview. The lunch interview was not technical. It was me who was asking the constant questions in that time. POST INTERVIEW STAGE: Since I was on a tight timeline, things moved at LIGHTNING SPEED. I couldnt imagine that it was possible for this to be done so soon. On the SAME DAY of my interview, I got a positive response and my packet for the Hiring Committee was being prepared. They checked out my references the NEXT day and by nightfall the next day, I knew I was approved by the hiring commitee. OFFER PHASE: The verbal offer was given 2 days later. 2 days of negotiation. I was given the final written letter basically within a week of my interview which I signed. Over all: The recruiter was diligent and FAST. I couldnt keep up, it was that quick. I was very lucky I would say to work with the right people. I made sure i myself was prompt at every stage.

      Domande di colloquio [1]

      Domanda 1

      I cannot disclose the questions. Some system programming, fact based questions were unexpected.
      Rispondi alla domanda
      1

      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

      30 giu 2026
      Candidato anonimo a colloquio
      Nessuna offerta
      Esperienza positiva
      Colloquio difficile

      Candidatura

      Ho presentato la mia candidatura online. Ho sostenuto un colloquio presso Google

      Colloquio

      OA - Round1 (1 tech + 1 bh) - Round2 two tech interview OA 1 Leetcode easy + 1 lc medium R1 tech 1 lc medium ask what is Fibonacci function R2 hard + medium greedy + game design

      Domande di colloquio [1]

      Domanda 1

      - why google - pround proj - time mgmt issue - ask about the resume proj - ask about your comments to previous manager
      Rispondi alla domanda

      Colloquio per Software Engineer

      29 giu 2026
      Candidato anonimo a colloquio
      New York, NY
      Nessuna offerta
      Esperienza neutra
      Colloquio difficile

      Candidatura

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

      Colloquio

      Interview process consists of 2 rounds: 1st screening round (1 technical, 1 behavioral interview) 2nd onsite round (2 technical interviews) All technical interviews are still typical leetcode style DSA interviews, not the new AI based ones.

      Domande di colloquio [1]

      Domanda 1

      They asked typical behavioral and technical interviews.
      Rispondi alla domanda