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

      17 oct 2011
      Candidato de entrevista anónimo
      Boston, MA
      Sin ofertas
      Experiencia negativa
      Entrevista promedio

      Solicitud

      El proceso tomó 1 día. Acudí a una entrevista en Google (Boston, MA) en oct 2011

      Entrevista

      The interview was really bad. The interviewer was 15 minutes late because she was looking for a phone to call me. No phones available at Google? She asked 3 decent questions. But I don't think she was prepared at all for the interview. And I believe she picked these questions online quickly. 1. The classic: what happens when you type: google.com in the browser? Dumb and everyone knows the answer. 2. What is the difference between GET and POST in forms? Another dumb question. 3. Programming: Write code that translate an alphanumerical phone number into a valid phone number. e.g: 1(800)GO-FEDEX to 18004633339 (her example) I could tell she picked that question online and very quickly and probably didn't have a real answer herself. As I was trying to solve the problem, she was picking on little syntax, which even great programmers don't pick up on the first try. With this question, It takes a long time to simply check that the string is long enough and not too short. And then she said you can simply get the alphanumerics i.e: 1800GOFEDEX, but of course that doesn't work because someone can write: 1800()GOFEDEX, 18(00)GOFEDEX, 1800(G)OFEDEX. 1()800GOFEDEX, 1-(800)-GOFEDEX, etc... So going through these cases alone takes a long time not 10 minutes especially when she was late. As I pointed out how crazy it would be to write actual codes, she said time was over. She definitely didn't have any clue how that problem would be solved.

      Preguntas de entrevista [3]

      Pregunta 1

      what happens when you type: google.com in the browser
      1 respuesta

      Pregunta 2

      difference between get and post in forms.
      2 respuestas

      Pregunta 3

      write a program to translate alphanumeric phone number to numbers only
      6 respuestas
      1

      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

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

      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

      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

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

      avatar
      Maze
      4.5★Remuneración y prestaciones