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-Tools and Infrastructures 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-Tools and Infrastructures

      24 mar 2016
      Candidato anonimo a colloquio
      New Orleans, LA

      Altre recensioni di colloqui per Software Engineer-Tools and Infrastructures presso Google

      Colloquio per Software Engineer (Tools and Infrastructure)

      14 ago 2019
      Candidato anonimo a colloquio
      Sunnyvale, CA
      Nessuna offerta
      Nessuna offerta
      Esperienza positiva
      Colloquio difficile

      Candidatura

      Ho presentato la mia candidatura online. La procedura ha richiesto più di una settimana. Ho sostenuto un colloquio presso Google (New Orleans, LA) nel mese di mar 2016

      Colloquio

      They called you for an initial casual chat describing the interview process. Then a phone interview is scheduled several days after. They set up a Google Doc page to send you the problem and have you solve the problem on it. They are very nice and casual, and punctual too.

      Domande di colloquio [1]

      Domanda 1

      Past experience, Main programming language, A tricky Programming Problem to solve
      Rispondi alla domanda
      4
      Esperienza negativa
      Colloquio nella media

      Candidatura

      Ho presentato la mia candidatura online. La procedura ha richiesto 12 mesi. Ho sostenuto un colloquio presso Google (Sunnyvale, CA) nel mese di mag 2019

      Colloquio

      From beginning to end, the interview process was disorganized, drawn out, mistake driven, with a lot of "apologies" and "no exceptions" to the process, irregardless of the highly impersonal nature of the "process" or the lack of competence involved. I applied in the fall for a position and the recruiter I spoke with (4 months after my application... cough) warned the "process" takes time, so at least expectations that wall clock time would be exhausted was set, flexibility was required, and certainly acceptable (it's "Google", right?). The problems however started right away: scheduling a simple phone screen was a fiasco as while being asked to provide availability, time of day was consistently overlooked (the coordinators are not in the US and clearly unable to handle time zone differences). The candidate is often asked to overlook the mistake and take the interview anyway (refusing resulted in many rescheduling attempts). I ultimately withdrew from the opening, but seeing a very appealing opening reposted decided to try again... personal mistake. Another 2 months of mis-scheduling persisted before a phone screen finally was correctly scheduled. The On-Site interview was inclusive of confused travel plans with lost or incorrect reservations for transportation to/from the interview (which were resolved, albeit the day of travel on the way out the door... not at all a good impression). Arriving on-site no schedule was provided though at least when the interview would be over was in the e-mail. That's all that was provided regarding the interviews for the day and "going with the flow" seemed paramount if only leaving yet another bad impression. About a week later feedback from the On-Site interview was ready and "positive", so the recommendation was to move on to the Hiring Committee. The process is that a "packet" is created and feedback would come a week or two later. However, no "packet' was created for the interview for well in excess of 2 months, only then to receive the "last piece" of feedback which instead triggered more On-Site interviews. What is "positive" feedback if it takes months to write up the results of an interview? The real regret at this point was not pausing, reflecting, and recognizing the ridiculousness of the "process", and that simply withdrawing from the charade was more sensible when the feedback for the "packet" had mysteriously disappeared for such an extended period of time. Nevertheless, it's "Google" so the next on-site was scheduled, albeit scheduled to start in the middle of the night (which asking for that to be corrected took a week...), and upon arrival the schedule was completely incorrect (the schedule was for 2.5 hours of On-Site interviews, but the interviewer said I was expected to stay for 3.5 to 4 hours... ... really?!). Again, a lost opportunity to simply walk away and move on. The result of the process was a "no", though the other warning was the second On-Site was sold as an attempt to determine the proper hiring level (L3, L4, L5, L6, etc.). That sounded reasonable, but given the end result that statement by the recruiter was a false pretense and so caution is highly recommended _if_ asked for a second interview. Don't believe the recruiter if they state the additional interview is for level setting -- it's not, you're starting over, or perhaps losing a "packet" for over 2 months means no one apparently knows what's going on... not surprising in retrospect but also a sign of general incompetence. On a positive note: the cafeteria was indeed nice, and I now truly understand the term "brilliant jerk" after my experience. I personally can't envision ever applying again -- good life experience, but trying again after the experience would be the equivalent of "fool me twice". The benefits may be supposedly awesome, but some things just aren't worth it. I simply hope my drawn out tale helps someone recognize when Google's "process" is worth withdrawing from... I saw it three times and tried because it's "Google" and sincerely regret that.

      Domande di colloquio [1]

      Domanda 1

      Describe a time when your organization was in transition and how you helped them move forward?
      Rispondi alla domanda
      1

      Colloquio per Software Engineer, Tools and Infrastructure

      5 mag 2019
      Candidato anonimo a colloquio
      Mountain View, CA
      Nessuna offerta
      Esperienza positiva
      Colloquio difficile

      Candidatura

      Ho presentato la mia candidatura tramite l'università. La procedura ha richiesto 6 settimane. Ho sostenuto un colloquio presso Google (Mountain View, CA) nel mese di mar 2019

      Colloquio

      I will first start out by saying that Google's interview process was excellent (when it comes to HR and scheduling). The recruiters are extremely professional and friendly. I got an online test with two questions. It was of average difficulty. I didn't get any tricky questions (no recursion or graphs and such). Passed that. Then around a week after, I was contacted to schedule a phone interview. A week before the phone interview, I was suddenly informed that there are no more regular software engineer roles and that I would have to choose between SETI or Site Reliability. I chose SETI and was given an onsite immediately. I don't know why the phone interview was skipped. To my knowledge, it's either because I did extremely well on the online test and wrote beautiful code and/or because I informed them that I was interviewing with another company. I had two weeks to intensively prepare. I HIGHLY recommend Leetcode. Buy the premium membership and practice their most popular problems and attempt to finish the Google Interview Preperation module in the explore tab (at the very least). Focus on your weaknesses. In my case, it was dynamic programming, recursion and graphs. Feel free to memorize but do understand the problem solving process for different kinds of problems. Also, go over cracking the coding interview (after you're done with Leetcode) and try to quickly solve as many problems as possible out loud, write down pseudocode then check out solutions. PRO TIP: Try to minimize stress. Don't pressure yourself too much. The Google interview process has a very large number of factors. You can ace all questions and still not get the job. Your odds of getting the job are already low so don't make it worse with stress! Go there, do your best and enjoy yourself. In my case, all transportation was taken care of. Interview day, you check in at the main desk and you are greeted by your first interviewer. Each interviewer, including the lunch interviewer, have your schedule. When it comes to interview questions, they are all Leetcode questions and some have small twists on them. Make sure you are prepared for all sorts of questions. You really can get anything. You might get 4 string manipulations questions or 4 graph problems. Make sure you know everything: DP, recursion, Tree and graph traversal and how to implement them iteratively and recursively, data structures, etc. Also, note that one of the interviews will be by a SETI and this interview will involve some focus on how you test your code. Make sure you brush up on how to test code properly. At the end of the day, your last interviewer simply drops you off outside and that's it (that's how it was for me at least). After the interview, the feedback of each interviewer (the feedback they write is lengthy and extensive) is sent to your recruiter. She then forms a packet and sends to the hiring committee. The committee meets up every 1 or 2 weeks. Before the meeting, committee members receive the packets of candidates from the previous week or two, go over them and put a grade /4. At the time of the meeting, the scores of the candidates are processed and shown in front of the whole committee. Data stats (average, median, etc.) might be used to make sense of the scores. Usually, people below a certain score are let go and those with high scores have a very high chance of getting an offer. Those in the middle are most likely let go although some might receive follow-up extra interviews in rare cases. (This information is based on research that I did before the interview) All in all, it was a smooth process. Please don't stress out about this. The fact that you reached on-site interviews is a big achievement. Google gave me the confidence to tackle another interview that was scheduled a week later and I got the offer for that. Best of luck!!

      Domande di colloquio [1]

      Domanda 1

      Leetcode > CtCI. Focus on leetcode to iron out your weaknesses and CtCI to learn the best techniques for specific problems.
      Rispondi alla domanda
      12

      Colloquio per Software Engineer, Tools and Infrastructure

      11 feb 2019
      Dipendente anonimo
      Mountain View, CA
      Offerta accettata
      Esperienza positiva
      Colloquio difficile

      Candidatura

      Ho presentato la mia candidatura online. La procedura ha richiesto 3 mesi. Ho sostenuto un colloquio presso Google (Mountain View, CA)

      Colloquio

      Interesting questions with follow up that tackles scale, generics, and handling arbitrary input/conditions. The interviewers were friendly and well prepared. I did not feel rushed by them at all. Recommendations for others: - Identify proper DS(s) to use - Identify a brute force solution first - Manually solve by hand - Identify Big O before even writing code - Identify computational/space bottleneck - Reduce to sub-problem and/or optimize - Code it out
      5