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

      19 mar 2014
      Candidato de entrevista anónimo
      Sin oferta
      Experiencia negativa
      Entrevista fácil

      Solicitud

      Envié una solicitud electrónica. El proceso duró 3 meses. Acudí a una entrevista en Google en feb 2014

      Entrevista

      I had applied through their job portal online. I was contacted by the first recruiter in January 3rd week. We exchanged emails, she had me fill out a couple of forms, and then I was handed over to another recruiter. She, in turn, handed me over to yet another recruiter. The recruiter coordination was not good, their responses were all over the place. Two recruiters were working in tandem to schedule my phone interview and they managed to convert the interview time from PST to my local time with an 1hr error. This ended up with me waiting for the phone screen call one hour earlier than it actually was. I had given up and decided that the person would not call and then I receive a call 1 hour later. The interview itself was appallingly conducted. First of all, the interviewer seemed to be in a room with a lot of echo. Second, he must have been using some kind of phone system on speaker or something similar because I could hear my own voice echoed back. I mentioned this to him twice, since it made it difficult to hear his words with the reverberation in the room blurring his voice and my voice echoing. The first time, he said I must be using a headset and that the microphone was too far away from the mouth. I told him that I wasn't using a headset. He waved it away. The second time, he said the same thing. By then I had given up on the interview. I couldn't hear much, he wasn't helping. Trying to decipher the conversation and trying to code simultaneously had become a horrible adventure. Besides, he wasn't listening to half of what I'd said, be it trying to explain my problem-solving method or be it my concern regarding the fact I couldn't hear much over the garble. Some of the start-off questions (break-ice questions) he had asked regarding my resume were pointedly patronizing or so I felt. I understand however that a phone screen doesn't give you enough indicators about these things and I could be wrong. The questions themselves were basic programming, then some threading, concurrency, map-reduce trivia questions. I understand many people have the ambition or life-goal to work for the company. Perhaps to them this process might be forgivable. Most interviews probably aren't like this and I might have had something of an exception. I consider it disrespectful of my time and an unwillingness to listen to what I could potentially provide.

      Preguntas de entrevista [1]

      Pregunta 1

      nothing too difficult, many trivia questions
      Responder pregunta
      3

      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

      23 jun 2026
      Candidato de entrevista anónimo
      Sin oferta
      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 de Software Engineer

      24 jun 2026
      Candidato de entrevista anónimo
      Sin oferta
      Experiencia neutra
      Entrevista normal

      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