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

      12 may 2010
      Candidato de entrevista anónimo
      New York, NY
      Sin ofertas
      Experiencia neutra
      Entrevista difícil

      Solicitud

      Me postulé a través de un reclutador. El proceso tomó 5 semanas. Acudí a una entrevista en Google (New York, NY) en abr 2010

      Entrevista

      I was contacted by a Google recruiter by phone. My resume was on file from a previous interview 3 years ago which did not result in an offer. We had a short conversation about what was available at Google and about what my experience was. The questions and information were very high level and it didn't seem like this was even a phone screen of any sort. She then passed me on to the HR person at the NY office. I was told that there would be a phone interview where I would need to be at a computer and would need to be able to code, but since I has already been onsite previously they decided to skip this. I was handed on to yet another person to actually schedule the interview and then back to the HR person. The onsite interview was from 10 to 3 and consisted of 5 interviews and a lunch conversation. Each interview was 45 minutes and they ran pretty much right on schedule. They were difficult, but pretty much what was expected. There almost no discussion of work history or anything other than technical questions. Most of the time was spent at the whiteboard working on and then refining the answer to a question. They mainly focused on data structures and algorithms around them. Things like BST, hash tables, tree traversals. The questions were not standard algorithm questions that you tend to see around, but a bit more involved. They were interested in your speaking about the algorithmic complexity of your solution and how to choose appropriate data structures. Hash vs. BST came up a bit. The coding that had to be done was a bit awkward for a whiteboard. The solutions were not necessarily short. One interview revolved around a higher level system design question that was refined throughout the discussion. There was very little to no time to ask questions or discuss working at google and the inteviewers did not seem interested in selling me on google. The lunch conversation was not an interview and did not contribute towards the assessment. The person I ate with was very nice and seemed honest about the way things are at google. Over 2 weeks after the interview I was contacted with the rejection. Overall the process was smooth and people were helpful and nice. Though I did not find anyone to be particularly interested in selling the company. The interviewers were hard but fair for the most part. One interviewer did not describe the problem particularly well and had me coding a solution to the wrong problem for a while.

      Preguntas de entrevista [1]

      Pregunta 1

      General algorithm questions. particularly focused on algorithmic complexity. Know average and worst case time for operations on hash tables, trees, etc. The questions are not puzzles and if you know your data structures, algorithms, etc, they aren't too hard.
      Responder pregunta
      2

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

      Entrevista para Software Engineer

      4 may 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

      3 jun 2026
      Candidato de entrevista anónimo
      Sin ofertas
      Experiencia negativa
      Entrevista difícil

      Solicitud

      Acudí a una entrevista en Google

      Entrevista

      Etapa de RH para filtragem de curriculo e fit inicial, e Screening Técnico com código em leetcode focado em algoritmos, onde o código era feito em um bloco de notas, sem uso de IDEs.

      Preguntas de entrevista [1]

      Pregunta 1

      Você conhece sobre Big O notation?
      Responder pregunta

      Entrevista para Software Engineer

      3 jun 2026
      Candidato de entrevista anónimo
      Mountain View, CA
      Sin ofertas
      Experiencia positiva
      Entrevista fácil

      Solicitud

      Acudí a una entrevista en Google (Mountain View, CA)

      Entrevista

      Round 1 consists of coding and behavioural interviews. In behavioural, it was basic questions; it can be found online, so make sure you have all the stories ready. For DSA, it was a pretty much easy question related to Intervals or Heaps, don't want to reveal the questions directly!!

      Preguntas de entrevista [1]

      Pregunta 1

      DSA question based on Intervals, Heaps
      Responder pregunta

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

      avatar
      Amazon
      3.7★Remuneración y prestaciones
      avatar
      Maze
      4.5★Remuneración y prestaciones