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

      27 mar 2009
      Candidato de entrevista anónimo
      New York, NY
      Sin oferta
      Experiencia positiva
      Entrevista difícil

      Solicitud

      Solicité el puesto a través de la recomendación de un empleado. El proceso duró 6 semanas. Acudí a una entrevista en Google (New York, NY) en abr 2008

      Entrevista

      I had have put my name on Google's candidate list through my advisor who worked there in the past. They called me to arrange a phone interview and some paperwork. In that paperwork, I was asked in what areas, at which locations and on which dates I would like to have internship. My first interview was scheduled a few weeks after that. My first interviewer was working in New York office. Two weeks after that I was told that I passed the first stage and my name had been put into the pool of candidates. I was going to be contacted if a group needs an intern that matches to my interests and specialties. However they didn't contact me for a couple of weeks even I told them that I had an offer from another company, so I decided to accept the other offer.

      Preguntas de entrevista [2]

      Pregunta 1

      This is an open ended question? How would you differentiate the same keywords in different contexts? For example, how can a search engine understand which of them represent the hotel brand name and which of them represent the celebrity, if a user searches for "Hilton"?
      1 respuesta

      Pregunta 2

      What kind of data structure would you use to index annagrams of words? e.g. if there exists the word "top" in the database, the query for "pot" should list that...
      4 respuestas
      1

      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

      3 jun 2026
      Candidato de entrevista anónimo
      Sin oferta
      Experiencia negativa
      Entrevista difícil

      Solicitud

      Acudí a una entrevista en Google

      Entrevista

      Etapa de RH para filtragem de curriculo e fit inicial, e Screening Técnico com código em leetcode focado em algoritmos, onde o código era feito em um bloco de notas, sem uso de IDEs.

      Preguntas de entrevista [1]

      Pregunta 1

      Você conhece sobre Big O notation?
      Responder pregunta

      Entrevista de Software Engineer

      2 jun 2026
      Candidato de entrevista anónimo
      Mountain View, CA
      Sin oferta
      Experiencia positiva
      Entrevista normal

      Solicitud

      Envié una solicitud electrónica. Acudí a una entrevista en Google (Mountain View, CA)

      Entrevista

      I was a bit nervous since it was my first big interview with a company like this. Wish I could of done better, but thats all learning experience for next time.

      Preguntas de entrevista [1]

      Pregunta 1

      "Design and implement an LRU cache supporting get and put in O(1) average time".
      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.6★Remuneración y beneficios
      avatar
      Fiverr Inc.
      3.5★Remuneración y beneficios
      avatar
      Netflix
      4.6★Remuneración y beneficios