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

      8 sep 2010
      Candidato de entrevista anónimo
      Seattle, WA
      Sin ofertas
      Experiencia neutra
      Entrevista difícil

      Solicitud

      Me postulé en línea. El proceso tomó más de 2 meses. Acudí a una entrevista en Google (Seattle, WA) en ago 2010

      Entrevista

      I was a recent US citizen Masters graduate in ECE from a top 10 engineering school. After passing my in-person interviews and being told that the "hard part was over", I was declined for hiring. Timeline: Day 0: Submitted resume online for 5 Software Engineering positions at Mountain View. Day 6: Received email invitation from Seattle/Kirkland college recruiter for phone interviews. Day 11: Non-technical phone interview with college recruiter. Scheduled two back-to-back technical interviews. Day 19: One technical phone interview. Second phone interview rescheduled. Day 21: Second technical phone interview Day 31: Invited for on-site interview. I did not provide an optional professor's letter of recommendation. Day 42: Scheduled for on-site interview at Kirkland site. Day 53-55: Flown on-site for interview, 1st class outbound, coach returning, hotel in Seattle. Arrived at Kirkland site, was told that the Kirkland address was a mistake on their part, and the interview would actually be in downtown Seattle. Drove rental car back to Seattle for interview (resulting in only a half-hour delay). Had 5 technical 1-on-1 interviews and an informal lunch interview. Performed well. Day 62: Notified of approval by local hiring committee. Day 70: Notified that final determination of candidacy could take another week. Day 75: Declined for hiring. Was encouraged to re-apply in 9-12 months after more work experience.

      Preguntas de entrevista [1]

      Pregunta 1

      Most questions were the typical, contrived algorithm problems, but a couple were more open-ended design questions. There was one problem that involved graphs. After giving a solution, they'll ask what the asymptotic complexity is, and how that can be improved. I was also asked what test cases I would write against the solution.
      1 respuesta
      3

      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

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

      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 para Software Engineer

      4 jun 2026
      Candidato de entrevista anónimo
      New York, NY
      Sin ofertas
      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 prestaciones" cerca de ti

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