Ir al contenidoIr al pie de página
  • Empleos
  • Empresas
  • Sueldos
  • Para empleadores

      Impulsa tu carrera profesional

      Averigua cuánto podrías ganar, encuentra el empleo perfecto y comparte información sobre tu vida laboral y personal de forma anónima.

      employer cover photo
      employer logo
      employer logo

      Google

      Empleador activo

      Información
      Evaluaciones
      Pago y prestaciones
      Empleos
      Entrevistas
      Entrevistas
      Búsquedas relacionadas: Evaluaciones de Google | Empleos en Google | Sueldos en Google | Prestaciones en Google
      Entrevistas en GoogleEntrevistas para el cargo de Software Engineer en GoogleEntrevista en Google


      Glassdoor

      • Acerca de
      • Premios
      • Blog
      • Contacto

      Empleadores

      • Cuenta de empleador gratuita
      • Centro de empleador

      Información

      • Ayuda
      • Pautas
      • Condiciones de uso
      • Privacidad y opciones de anuncios
      • No vender ni compartir mi información
      • Herramienta de autorización de cookies

      Trabaja con nosotros

      • Anunciantes
      • Oportunidades laborales
      Descargar aplicación

      • Buscar por:
      • Empresas
      • Empleos
      • Ubicaciones

      Copyright © 2008-2026. Glassdoor LLC. "Glassdoor", "Worklife Pro", "Bowls" y sus logotipos son marcas comerciales registradas de Glassdoor LLC.

      Empresas seguidas

      Sigue a tus empresas favoritas para estar al tanto de las últimas oportunidades y disponer de información desde adentro.

      Búsquedas de empleo

      Recibe recomendaciones y actualizaciones personalizadas al iniciar tu búsqueda.

      Entrevista para Software Engineer

      1 de abr de 2013
      Candidato de entrevista anónimo
      Sin ofertas
      Experiencia negativa
      Entrevista difícil

      Solicitud

      Me postulé a través de un reclutador. El proceso tomó 9 meses. Acudí a una entrevista en Google en feb 2012

      Entrevista

      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.

      Preguntas de entrevista [1]

      Pregunta 1

      Splitting a search query between different machines
      1 respuesta
      7

      Otras evaluaciones sobre las entrevistas para el cargo de Software Engineer en Google

      Entrevista para Software Engineer

      4 de may de 2014
      Empleado anónimo
      Auburndale, FL
      Oferta aceptada
      Experiencia positiva
      Entrevista difícil

      Solicitud

      Me postulé a través de una recomendación de un empleado. Acudí a una entrevista en Google (Auburndale, FL) en abr 2014

      Entrevista

      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

      Entrevista para Software Engineer

      7 de jun de 2026
      Candidato de entrevista anónimo
      Los Altos, CA
      Sin ofertas
      Experiencia neutra
      Entrevista difícil

      Solicitud

      Acudí a una entrevista en Google (Los Altos, CA)

      Entrevista

      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.

      Preguntas de entrevista [1]

      Pregunta 1

      Why do you want to work at Google?
      Responder pregunta

      Entrevista para Software Engineer

      7 de jun de 2026
      Empleado anónimo
      Seabrook, NH
      Oferta aceptada
      Experiencia positiva
      Entrevista fácil

      Solicitud

      Acudí a una entrevista en Google (Seabrook, NH)

      Entrevista

      Had a good interview. Easy problems not leetcode but if you know how to solve problems and use which DSA to use for what problem then you are good.. system design as well.

      Preguntas de entrevista [1]

      Pregunta 1

      Tell me about yourself ?
      Responder pregunta

      Las mejores empresas en cuanto a "Remuneración y prestaciones" cerca de ti

      avatar
      Amazon
      3.7★Remuneración y prestaciones
      avatar
      eBay
      4.0★Remuneración y prestaciones
      avatar
      Amazon Web Services
      3.9★Remuneración y prestaciones
      avatar
      Wix
      3.8★Remuneración y prestaciones