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

      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

      Empresa activa

      Información
      Opiniones
      Sueldos y beneficios
      Empleos
      Entrevistas
      Entrevistas
      Búsquedas relacionadas: Opiniones sobre Google | Ofertas de empleos en Google | Sueldos en Google | Beneficios en Google
      Entrevistas de GoogleEntrevistas para el puesto de Software Engineer en GoogleEntrevista de Google


      Glassdoor

      • Acerca de
      • Premios
      • Blog
      • Contacto

      Empresas

      • Cuenta gratuita de empresa
      • Centro de empresas

      Información

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

      Trabaja con nosotros

      • Anunciantes
      • Empleo
      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 de primera mano.

      Búsquedas de empleo

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

      Entrevista de Software Engineer

      29 dic 2009
      Empleado anónimo
      Oferta aceptada
      Experiencia positiva
      Entrevista difícil

      Solicitud

      El proceso duró 8 semanas. Acudí a una entrevista en Google en dic 2009

      Entrevista

      One of my friends was contacted by a Google recruiter. He was not interested in interviewing at the time, but gave my name to the recruiter, who emailed me and requested my resume. After receiving my resume, the recruiter arranged a 45min technical phone interview, which consisted of one "soft" question (e.g. describe a current project and its challenges), one algorithm question, one Java question, and one design question involving concurrency. The recruiter had previously mentioned there might be a second phone interview, but I did well enough in the first phone interview that my candidacy was forwarded to the on-site interviews. I had five on-site interviews, all of which focused on technical knowledge and problem solving skills. My lunch conversation was truly a conversation and not an interview - I was the one asking all the questions! :) Although I enjoyed the interviews themselves, lunch was a wonderful experience. It was great to see all the engineers sitting together talking and interacting. There was an incredible sense of community, friendship, and potential. (that sounds pretty weird, but it's really what it felt like) I was asked only two soft questions the entire day and was not asked any brainteaser or logic puzzle questions. There was more emphasis on Java knowledge than I expected. Even though I was not asked any brainteaser or logic puzzle questions, I feel like studying them helped me improve my technique in approaching a new problem.

      Preguntas de entrevista [2]

      Pregunta 1

      Describe a current project. What was challenging about it? What did you learn from it?
      Responder pregunta

      Pregunta 2

      What is the relationship between equals(Object o) and hashCode() in Java? How would you implement each method?
      2 respuestas
      4

      Otras opiniones sobre las entrevistas para el puesto de Software Engineer en Google

      Entrevista de Software Engineer

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

      Solicitud

      Solicité el puesto a través de la 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 de Software Engineer

      4 jun 2026
      Candidato de entrevista anónimo
      Varsovia, Mazovia
      Sin oferta
      Experiencia positiva
      Entrevista normal

      Solicitud

      Acudí a una entrevista en Google (Varsovia, Mazovia)

      Entrevista

      remote round - on the same day, 45 minute technical interview, then 45 minute behavioral interview. there was also plenty of time to ask questions afterwards, so be prepared at least three or so to show interest

      Preguntas de entrevista [1]

      Pregunta 1

      a list of ranges like [0,1], [2, 5], ... . create a class with methods to find if element is in any range and insert a new range
      Responder pregunta

      Entrevista de Software Engineer

      4 jun 2026
      Candidato de entrevista anónimo
      New York, NY
      Sin oferta
      Experiencia positiva
      Entrevista difícil

      Solicitud

      Acudí a una entrevista en Google (New York, NY)

      Entrevista

      Didn't pass the phone screen. It was a leetcode medium question. I think I got it right, but maybe I was too slow in finishing the problem. Maybe it was something else

      Las mejores empresas en cuanto a «Remuneración y beneficios» cerca de ti

      avatar
      Amazon
      3.7★Remuneración y beneficios
      avatar
      Meta
      4.6★Remuneración y beneficios
      avatar
      Fiverr Inc.
      3.5★Remuneración y beneficios
      avatar
      Booking.com
      4.2★Remuneración y beneficios