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

      15 nov 2012
      Empleado anónimo
      Oferta aceptada
      Experiencia positiva
      Entrevista difícil

      Solicitud

      Solicité el puesto a través de la escuela superior o la universidad. Acudí a una entrevista en Google

      Entrevista

      The hiring process usually begins with one or two phone screens, followed by a day of onsite interviews. I applied through my university, so the initial phone screens were replaced by two more back-to-back in-person interviews. If all goes well during the onsite interviews, there is a series of three hiring meetings behind closed doors, each higher level than the last, after which an offer is made.

      Preguntas de entrevista [1]

      Pregunta 1

      I do take my NDA seriously, but in general terms: the interview questions at Google are extremely difficult and often very tricky. With that said, contrary to popular opinion, they are not necessarily any harder than the questions that any tech company with high standards would ask. Know your data structures and algorithms back to front; be prepared for questions as high-level as very general OOP design problems and as low-level as bit manipulations; and know your resume cold, because every interviewer was interested in at least one item on it. I HIGHLY recommend finding a copy of at least one coding interview book (Cracking the Coding Interview, Programming Interviews Exposed, and Design & Analysis of Algorithms served me well) and tackling the problems in it -- they will give you a good idea of what to expect. I will say that I had never seen any of the questions I was asked in my Google interviews (whereas the rest of the industry seems to recycle the same 20 questions over and over), but my practice with general interview-style coding questions was extremely useful nonetheless. Remember that the interviewer wants to see how you approach a problem you haven't necessarily seen before, so think out loud a lot, and don't forget your edge cases!
      Responder pregunta
      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

      15 jun 2026
      Candidato de entrevista anónimo
      Sin oferta
      Experiencia positiva
      Entrevista normal

      Solicitud

      Acudí a una entrevista en Google

      Entrevista

      There are two back-to-back rounds, the first is a code interview, and the next is a BQ interview. I think my interviewees gave me positive feedback, and they are nice.

      Preguntas de entrevista [1]

      Pregunta 1

      Asked me a question to design a function to find a simpler Wordle game.
      Responder pregunta

      Entrevista de Software Engineer

      12 jun 2026
      Candidato de entrevista anónimo
      Oferta rechazada
      Experiencia positiva
      Entrevista normal

      Solicitud

      Acudí a una entrevista en Google

      Entrevista

      3 rounds of coding + 1 behavior Questions from leetcode google question bank, mostly medium level questions, ask about complexity. Interviewers are generally nice, there are no test cases but need to write ur own tests and think of the edge cases.

      Preguntas de entrevista [1]

      Pregunta 1

      For behavior describe a project u have worked on
      Responder pregunta

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

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