Ir para o conteúdoIr para a pasta
  • Vagas
  • Empresas
  • Salários
  • Para empresas

      Avance em sua carreira

      Descubra qual pode ser seu salário, conquiste a vaga dos seus sonhos e compartilhe insights de qualidade de vida com sigilo.

      employer cover photo
      employer logo
      employer logo

      Google

      Empresa engajada

      Sobre
      Avaliações
      Remuneração e benefícios
      Vagas
      Entrevistas
      Entrevistas
      Buscas relacionadas: Avaliações da empresa Google | Vagas da empresa Google | Salários da empresa Google | Benefícios da empresa Google
      Entrevistas da empresa GoogleEntrevistas do cargo de Software Engineer da empresa GoogleEntrevista da empresa Google


      Glassdoor

      • Sobre
      • Prêmios
      • Blog
      • Fale conosco

      Empresas

      • Conta gratuita de empresa
      • Área da empresa
      • Blog para empresas

      Informações

      • Ajuda
      • Regras da Comunidade
      • Termos de Uso
      • Privacidade e opções de anúncios
      • Não venda nem compartilhe minhas informações
      • Ferramenta de consentimento de uso de cookies

      Trabalhe conosco

      • Anunciantes
      • Carreiras
      Baixe o aplicativo:

      • Busque por:
      • Empresas
      • Vagas
      • Localizações

      Copyright © 2008-2026. Glassdoor LLC. “Glassdoor”, “Worklife Pro”, “Bowls” e o logotipo do Glassdoor são marcas comerciais pertencentes à Glassdoor LLC.

      Empresas seguidas

      Fique por dentro de todas as oportunidades e dicas internas seguindo as empresas de seus sonhos.

      Buscas de vagas

      Comece a buscar vagas para receber atualizações e recomendações personalizadas.

      Entrevista para Software Engineer

      20 de mar. de 2014
      Funcionário(a) sigiloso(a)
      Los Angeles, CA
      Oferta aceita
      Experiência positiva
      Entrevista difícil

      Candidatura

      Candidatei-me por meio de recrutador(a). O processo levou 7 semanas. Fui entrevistado pela Google (Los Angeles, CA) em mar. de 2014

      Entrevista

      I was first contacted by a recruiter. He emailed me out of the blue, and said he really liked my github profile. Honestly, at first, I didn't believe it was real. We emailed back and forth a few times, but I wasn't really looking to moving to the Bay Area, so I never actually sent in my CV. About a month goes by, and he emails me back. He just wanted to follow up. Said that he never received the resume, and hoped I would get back in touch. So I told him about my situation, and he mentioned that they had an LA office. This was news to me, and much closer to home. So I sent in my resume, and he connected me to a recruiter who was closer to me. All in all, I talked with about 4 different people in recruiting. All of them were incredibly nice and helpful. My first "interview" was with the second recruiter. It was really just getting to know me, what my interests were, and trying to get a feel for my fit with the company. After that interview, we scheduled a technical phone interview. Gave me to weeks to study up. Lots of review material was sent my way, which was awesome. Ended up reading my algorithms text book again, it was quite a nice read, but I don't believe I would have done poorly on the phone interview, even had I not read it. The tips/references they sent to me were extremely helpful. They sent me Titles/Authors of some amazing books, I recommend reading them even if you aren't interviewing with Google. After passing the phone interview, we had an on-site scheduled about a week later. This was much harder than the phone interview. I get the idea that the phone was just to weed out the weaker candidates. The on-site consisted of 5 one-on-one interviews, plus one lunch "interview" where I was able to ask all of my questions. All of them were about 45 minutes each. Every interviewer I talked to was very interesting, and we always had something in common to talk about. The questions were all very interesting problems. There was one point in one of the questions where one of the interviewers put a star next to a line I wrote to remind him to go back and follow up on a comment I made that sounded interesting. I enjoyed the interviews, because it felt like I was back in college, talking to my peers about fascinating problems. There were one or two interviews that I feel I didn't do so hot on. I only managed to get through one of the questions on two of the interviews. However, I figured they really just wanted to see how I approached the problems, so I made sure to explain myself very thoroughly.

      Perguntas de entrevista [1]

      Pergunta 1

      I can't go into details about the problems. But I wish I had studied my graph algorithms a little more closely. Make sure you know your big-O algorithm classifications. Almost every interviewer asked me something to do with that.
      3 respostas
      18

      Outras avaliações de entrevista de vagas de Software Engineer da empresa Google

      Entrevista para Software Engineer

      4 de mai. de 2014
      Funcionário(a) sigiloso(a)
      Auburndale, FL
      Oferta aceita
      Experiência positiva
      Entrevista difícil

      Candidatura

      Candidatei-me por indicação de um funcionário. Fui entrevistado pela Google (Auburndale, FL) em abr. de 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

      30 de jun. de 2026
      Candidato(a) sigiloso(a) à entrevista
      Nenhuma oferta
      Experiência positiva
      Entrevista difícil

      Candidatura

      Candidatei-me online. Fiz uma entrevista na empresa Google.

      Entrevista

      OA - Round1 (1 tech + 1 bh) - Round2 two tech interview OA 1 Leetcode easy + 1 lc medium R1 tech 1 lc medium ask what is Fibonacci function R2 hard + medium greedy + game design

      Perguntas de entrevista [1]

      Pergunta 1

      - why google - pround proj - time mgmt issue - ask about the resume proj - ask about your comments to previous manager
      Responder à pergunta

      Entrevista para Software Engineer

      29 de jun. de 2026
      Candidato(a) sigiloso(a) à entrevista
      New York, NY
      Nenhuma oferta
      Experiência neutra
      Entrevista difícil

      Candidatura

      Fiz uma entrevista na empresa Google (New York, NY).

      Entrevista

      Interview process consists of 2 rounds: 1st screening round (1 technical, 1 behavioral interview) 2nd onsite round (2 technical interviews) All technical interviews are still typical leetcode style DSA interviews, not the new AI based ones.

      Perguntas de entrevista [1]

      Pergunta 1

      They asked typical behavioral and technical interviews.
      Responder à pergunta