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

      2 may 2011
      Empleado anónimo
      Mountain View, CA
      Oferta aceptada
      Experiencia positiva
      Entrevista difícil

      Solicitud

      Solicité el puesto a través de un captador. El proceso duró 3 meses. Acudí a una entrevista en Google (Mountain View, CA) en abr 2011

      Entrevista

      A google recruiter cold-called me on 3 Feb 2011 (I guess they got my résumé from an old co-worker?) and I was kinda bored so I aksed her to send me more info about the job. The recruiter sounded eerily stoked on both the company and the project (kept describing it all as "exciting"). By the end of the next week we had scheduled a phone interview for 22 Feb. (I wasn't in any sorta hurry). Then I rescheduled the phone interview for a week later, 1 Mar. Shared google doc, the interviewer pasted some code and aksed me to find bugs in it and repair them. Some other question I don't remember. The topics were like race conditions in multi-threaded systems or something. It was nothing shocking, and the interviewer seemed to have a more muted stoke about working for google. Two days later, the ultra-stoked recruiter called back with a second recruiter to invite me for an in-person. The second recruiter sounded pretty hepped up on the brand-name too. I think the second was a more senior recruiter. We scheduled an interview for 2 weeks later, 17 Mar. They put me up in a hotel in Mtn View. The hotel was perfectly fancy, and had lots of nerd-themed items in the desk in the room (think weird Rubik's Cubes, puzzles made of heavy wire, &c). Next morning I woke up and drove to the googleplex. It was pretty, with ample parking, and a kinda agrestic setting. Flowers, vegetables, nerds. I waited in building 43 and watched people come in and out. it was easy to tell the difference between the home team and the visitors -- the googlers were the ones who looked super-jazzed, and the others looked uneasy. I mean, noticeably super-jazzed. The senior recruiter came `round and took me to the first interview room. I'd been scheduled for three interviews, but he told me they had found a fourth interviewer and would I mind staying longer for more probing. (I said I wouldn't mind.) The first interviewer came in, aksed a question about like statefulness in distributed systems or something, I wrote a big long answer on the board. he was mellow, genial, and helpful. The interview question wasn't too hard, and afterwards (when prompted) he expressed satisfaction with the company. He left, and another helpful, genial, and mellow engineer came in and aksed me some more basic cs stuff, and a question about how to build the back-end of a particular google product. She also expressed contentment with google as a place of employment. The guy who gave me the phone interview came and took me to lunch. We went to yet another building for my next interviews. A frankly-kinda-stressed-out-seeming engineer aksed questions about code prettification: namely, how to prettify the Java code I wrote on the white board. She took me to the next interview where a young guy aksed me a question about c-language bit-twiddling, and aksed a question about dynamic programming. my undergraduate cs courses were like 18 years previous, and I drew a blank. after futzing around w/ it for a bit, time was called and I drove home. I sorta figured that it would end there, so I wasn't suprised when they didn't call back. Two weeks later though, the senior recruiter called back to tell me they almost had all the interview reports, and that they just needed one guy's report before making a decision. Three days later, around 5 Apr, both recruiters started calling me and emailing me. I ignored them for a while, then finally phoned them back. They said they wanted me to talk with a few potential teams there to see if we could find a match. Over the next two weeks I spoke with six or seven folks, engineers and managers both. The tone of the calls went from testing my domain-awareness to openly soliciting my membership in their teams. Eventually (over the course of about a week) the recruiter reported the progress of my hiring order from hiring committee to I guess a second hiring committee to some kind of executive committee to the compensation manager to the executive approval, then they phoned me to tell me the nitty-gritty of the job offer. It was pretty good, so I accepted.

      Preguntas de entrevista [1]

      Pregunta 1

      They made me promise not to tell. There were questions about thread-safety, computational complexity, and dynamic programming. Also other questions.
      Responder pregunta
      6

      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

      3 jun 2026
      Candidato de entrevista anónimo
      Mountain View, CA
      Sin oferta
      Experiencia positiva
      Entrevista fácil

      Solicitud

      Acudí a una entrevista en Google (Mountain View, CA)

      Entrevista

      Round 1 consists of coding and behavioural interviews. In behavioural, it was basic questions; it can be found online, so make sure you have all the stories ready. For DSA, it was a pretty much easy question related to Intervals or Heaps, don't want to reveal the questions directly!!

      Preguntas de entrevista [1]

      Pregunta 1

      DSA question based on Intervals, Heaps
      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
      Booking.com
      4.2★Remuneración y beneficios