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

      15 de dic de 2013
      Candidato de entrevista anónimo
      Sin ofertas

      Solicitud

      Acudí a una entrevista en Google

      Entrevista

      I was initially contacted by a recruiter who indicated that I had been referred by someone working there. First he inquired if I was interested to which I said yes. We briefly discussed a phone chat but quickly moved forward with an on site interview. Initially, I was to interview at their New York office but the recruiter felt my chances were better if I interviewed at their headquarters in Mountain View. So I agreed to a face-to-face interview at their headquarters. At this point, I was introduced to a second recruiter who helped set up my travel arrangements, discussed what to expect, and answered any additional questions I had. She had also given me a list of topics to study and a couple of websites to visit to help prep. She was the one I met with when I went onsite and she let me get a drink and use the bathroom before heading to a conference room where I would spend the next few hours. She then left me after giving me a chance to ask any more last minute questions. I had a schedule of 3 interviewers followed by a lunch break followed by 2 more interviewers to finish the day. The interviewers were nice and accommodating and happy to answer any questions but were very mindful of the time except for my final interviewer who probably spent 2 hours with me. They gave the impression they are passionate about what they're doing and did not dismiss anything I said as foolish or dumb (I mention this as I've read other interview accounts who said their interviewers were snobbish and elitist). After about a week, I emailed my recruiter asking about a status. She said they were still waiting on the feedback from some of the engineers and that she would find out where they were with this. About another week after that she called me to inform me they were not continuing with the process. I had tried to find out more about the reason but she said there was no feedback available and that it's a 'flaw' in their process. She encouraged me to apply again in another year or so indicating that people often did re-apply after their first try.

      Preguntas de entrevista [1]

      Pregunta 1

      I had been asked to write a program that would perform a basic regular expression search.
      Responder pregunta
      1

      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

      23 de jun de 2026
      Candidato de entrevista anónimo
      Sin ofertas
      Experiencia positiva
      Entrevista difícil

      Solicitud

      Acudí a una entrevista en Google

      Entrevista

      2 rounds of interviews with the first round being a technical and a behaverial. The second round being two technicals. The format was straight forward and the interviewer was professional.

      Preguntas de entrevista [1]

      Pregunta 1

      Talk about how you resolve a conflict.
      Responder pregunta

      Entrevista para Software Engineer

      24 de jun de 2026
      Candidato de entrevista anónimo
      Sin ofertas
      Experiencia neutra
      Entrevista promedio

      Solicitud

      Acudí a una entrevista en Google

      Entrevista

      There was a technical screen within their coding platform, followed by a first-round technical interview, followed by a first-round behavioral interview, followed by second-round interviews, both technical and behavioral interviews.

      Preguntas de entrevista [1]

      Pregunta 1

      What was your role on a technical project you've worked on?
      Responder pregunta