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. Indeed, Inc. "Glassdoor", "Worklife Pro", "Bowls" y sus logotipos son marcas comerciales registradas de Indeed, Inc.

      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

      27 de feb de 2015
      Candidato de entrevista anónimo
      Sin ofertas
      Experiencia neutra
      Entrevista promedio

      Solicitud

      Me postulé a través de un reclutador. El proceso tomó 1 día. Acudí a una entrevista en Google

      Entrevista

      I prepared by reading many parts of Skienna’s algorithm design manual, and watching MIT algorithm lectures. I was already good at algorithms considering my previous class performances so I was just brushing up my knowledge. I spent particular attention to Graph theory following the advice of steve-yegge Blog post on the same topic. Solved as many algorithm problems as I could (I would say I spent a total of 30 hours preparing before my interview over one month), especially graphs because I figured graphs were important at google and if I could dazzle them with my ability to do graph problems then I was in. The day started gray to begin with and went downhill from there. The recruiter got there 15 minutes later than our meeting time and meanwhile I went from being mildly nervous to almost hysteric. When we met the first interviewer who was visibly annoyed because of the delay (or maybe that was just my perception), the recruiter blamed me for being late. That’s right. I was so shocked, it took me some seconds to actually figure out he really was saying this and after that I didn’t know what to do to make it right (pathetic, I know). I had five interviews back to back and one additional lunch interview in between. During my first interview it was as if I had a block in place of my brain, I must have asked the poor engineer 10 times to explain the question to me. It was as if he was talking gibberish. I could not focus, I was too nervous and pissed off at the recruiter. Needless to say, I could not write even one single line of code, mainly I stared at the whiteboard. I still don’t remember what the question was actually. I was so embarrassed. No algorithm question was ever asked. Yes, you heard it right. Not even something involving binary tree or search; nothing. There was one design question and three coding question. In short, there were things that were under my control. I didn’t do any whiteboard coding (big mistake) and didn’t have time for mock up interviews (another big mistakes). Given all that happened at the beginning to unhinged me (I am skipping something else that happened on the morning of the interview), had I practiced solving questions on the whiteboard and had I done mock up interviews I should have been able to handle it beautifully. The engineers who did the interviews, were all so nice and smart. The recruiters, oh well.

      Preguntas de entrevista [1]

      Pregunta 1

      A question about playing a game of two players.
      Responder pregunta

      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

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

      Solicitud

      Me postulé en línea. Acudí a una entrevista en Google

      Entrevista

      OA - Round1 (1 tech + 1 bh) - Round2 two tech interview OA 1 Leetcode easy + 1 lc medium R1 tech 1 lc medium ask what is Fibonacci function R2 hard + medium greedy + game design

      Preguntas de entrevista [1]

      Pregunta 1

      - why google - pround proj - time mgmt issue - ask about the resume proj - ask about your comments to previous manager
      Responder pregunta

      Entrevista para Software Engineer

      29 de jun de 2026
      Candidato de entrevista anónimo
      New York, NY
      Sin ofertas
      Experiencia neutra
      Entrevista difícil

      Solicitud

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

      Entrevista

      Interview process consists of 2 rounds: 1st screening round (1 technical, 1 behavioral interview) 2nd onsite round (2 technical interviews) All technical interviews are still typical leetcode style DSA interviews, not the new AI based ones.

      Preguntas de entrevista [1]

      Pregunta 1

      They asked typical behavioral and technical interviews.
      Responder pregunta