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. 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 desde adentro.

      Búsquedas de empleo

      Recibe recomendaciones y actualizaciones personalizadas al iniciar tu búsqueda.

      Entrevista para Software Engineer

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

      Solicitud

      El proceso tomó 1 semana. Acudí a una entrevista en Google (Mountain View, CA) en abr 2011

      Entrevista

      The Google interview process typically includes a phone interview or two as well as an on-site, in a process that takes a couple of weeks to a month. I had a pending offer from another company, so they expedited my interview (skipped the phone), and expedited the hiring committee review. I got flight info for two days later, flew out, interviewed the next day (Friday), and had an offer by Monday. At the on-site interview, they put you up in a pretty nice hotel and provide a rental car. GPS is recommended, as the Mountain View / Sunnyvale suburbs can be difficult to navigate. The Google campus is simply spectacular. They have dozens of buildings, with bikes for transportation between bulidings, buses in and out of different neighborhoods, multiple dining cafes, multiple gyms, etc. Google is also located all over the country (and world) - you can actually pick your location if MV suburbia isn't your cup of tea. Projects/teams are distributed across separate offices. As for the actual interview: 5 separate 45 minute interviews with other Software Engineers. The interviewers come from a wide background (infrastructure, front end, etc). Questions were all technical in nature, mostly coding oriented. They did ask pointed questions about previous experience, projects, general resume stuff, etc. The interview questions were well thought out and relatively innovative. The interviewers presented them clearly, and were very helpful in discussing solution possibilities. Some of the questions were pretty straightforward, but the trickier ones were excellent - we were able to devise solutions and optimize them multiple times, discussing what was better about different approaches. Everyone I talked to was very upbeat, intelligent, and nice. The last interviewer I had seemed a bit surly at first, but quickly warmed up and became very affable. The hiring process was very informative. The recruiters gave loads of information when asked, and were very up front about a lot of aspects of the company. The interviewers themselves were able to answer many questions about the gritty details of working at Google. The hiring itself is actually done by a separate group of people from the interviewers, and is decided somewhat up the chain of command.

      Preguntas de entrevista [1]

      Pregunta 1

      Google asks interviewees to not share specific details on interview questions. They were coding-oriented questions. They required a varied set of algorithms and data structures to solve, especially including graphs, heaps, linked lists, and hash tables. Sorting algorithms were also emphasized. Some of the interview questions were quite unique, but could be abstracted in neat ways. Google does provide a significant amount of material before the interview(s) to help you study, including links to reading material and the types of questions you can expect. They were relatively difficult, but the interviewers were helpful.
      1 respuesta
      3

      Otras evaluaciones sobre las entrevistas para el cargo de Software Engineer en Google

      Entrevista para Software Engineer

      4 may 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

      9 jun 2026
      Candidato de entrevista anónimo
      Sin ofertas
      Experiencia neutra
      Entrevista promedio

      Solicitud

      Acudí a una entrevista en Google

      Entrevista

      First call with recruiter. Mainly resume questions nothing too technical. Then methods round, was a tagged question from leetcode. Interviewer pushed back on first design and steered me to the optimal solution.

      Preguntas de entrevista [1]

      Pregunta 1

      Why are you leaving your current role.
      Responder pregunta

      Entrevista para Software Engineer

      7 jun 2026
      Empleado anónimo
      Seabrook, NH
      Oferta aceptada
      Experiencia positiva
      Entrevista fácil

      Solicitud

      Acudí a una entrevista en Google (Seabrook, NH)

      Entrevista

      Had a good interview. Easy problems not leetcode but if you know how to solve problems and use which DSA to use for what problem then you are good.. system design as well.

      Preguntas de entrevista [1]

      Pregunta 1

      Tell me about yourself ?
      Responder pregunta

      Las mejores empresas en cuanto a "Remuneración y prestaciones" cerca de ti

      avatar
      Amazon
      3.7★Remuneración y prestaciones
      avatar
      Maze
      4.5★Remuneración y prestaciones