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

      18 de mar. de 2009
      Candidato(a) sigiloso(a) à entrevista
      Austin, TX
      Nenhuma oferta
      Experiência neutra
      Entrevista com nível médio de dificuldade

      Candidatura

      O processo levou 1 semana. Fui entrevistado pela Google (Austin, TX) em set. de 2008

      Entrevista

      I had a phone conversation with a recruiter from the New York office, and a few days later she sent me detailed multi-page email on how the in-person interview will be conducted. I was told I will meet 3 engineers in the Austin office. When I arrived in the office, I was met by an engineering manager. An hour was spent discussing an algorithmic problem. I tried to ask questions about the culture of the Austin office, how requirements are gathered, how testing is done, what the technical environment is, but was pointed back to the code on the whiteboard. After an hour of conversation with this engineering manager, another engineering manager showed up, and the first hour was repeated with a different algorithm/code problem. And then yet another engineering manager. My questions were not answered, and these guys were not interested in anything other than my ability to reason about large sets of bits. A recruiter followed up about a week later, and Google send me a check for my interview expenses. I suppose it was a good interview experience - I quickly learned that I definitely did not want to work there.

      Perguntas de entrevista [1]

      Pergunta 1

      Something about poker, or baseball season, or some other game that I was not familiar with enough to reason about.
      1 resposta

      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

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

      Candidatura

      Fiz uma entrevista na empresa 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.

      Perguntas de entrevista [1]

      Pergunta 1

      Você conhece sobre Big O notation?
      Responder à pergunta

      Entrevista para Software Engineer

      2 de jun. de 2026
      Candidato(a) sigiloso(a) à entrevista
      Mountain View, CA
      Nenhuma oferta
      Experiência positiva
      Entrevista com nível médio de dificuldade

      Candidatura

      Candidatei-me online. Fiz uma entrevista na empresa 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.

      Perguntas de entrevista [1]

      Pergunta 1

      "Design and implement an LRU cache supporting get and put in O(1) average time".
      Responder à pergunta

      As melhores empresas na categoria “Remuneração e benefícios” perto de você

      avatar
      Amazon
      3.7★Remuneração e benefícios
      avatar
      Meta
      4.6★Remuneração e benefícios
      avatar
      Booking.com
      4.2★Remuneração e benefícios
      avatar
      Yandex
      3.8★Remuneração e benefícios