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

      Uber

      Empresa engajada

      Sobre
      Avaliações
      Remuneração e benefícios
      Vagas
      Entrevistas
      Entrevistas
      Buscas relacionadas: Avaliações da empresa Uber | Vagas da empresa Uber | Salários da empresa Uber | Benefícios da empresa Uber
      Entrevistas da empresa UberEntrevistas do cargo de Site Reliability Engineer da empresa UberEntrevista da empresa Uber


      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. Indeed, Inc. “Glassdoor”, “Worklife Pro”, “Bowls” e o logotipo do Glassdoor são marcas comerciais pertencentes à Indeed, Inc.

      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 Site Reliability Engineer

      28 de jul. de 2016
      Funcionário(a) sigiloso(a)
      San Francisco, CA

      Outras avaliações de entrevista de vagas de Site Reliability Engineer da empresa Uber

      Entrevista para Site Reliability Engineer

      14 de dez. de 2020
      Candidato(a) sigiloso(a) à entrevista
      Amsterdã
      Nenhuma oferta
      Oferta aceita
      Experiência positiva
      Entrevista difícil

      Candidatura

      Candidatei-me por meio de recrutador(a). O processo levou 4 semanas. Fui entrevistado pela Uber (San Francisco, CA) em abr. de 2016

      Entrevista

      The interview process is similar to that of Google or Facebook, but greater emphasis on the fit for that particular team/position. Phone screen, two phone interviews, all-day on-site. Culture fit and personality interview, laptop coding, technical troubleshooting, and non-abstract large systems design. The technical interviews seek to push candidates to their technical limits to see their problem-solving approach and ability to debug issues. This means interviews can be stressful. Practicing and memorizing algorithms problems as one would for a Google interview won't be sufficient; the "right" answer won't be accepted without the interviewer introducing a new requirement or changing the scenario. The code has to run on the laptop in order to be accepted.
      Experiência positiva
      Entrevista difícil

      Candidatura

      Candidatei-me online. Fui entrevistado pela Uber (Amsterdã) em mai. de 2019

      Entrevista

      Interview process started with HR reaching out upon basic HR Interview had couple of online session upon the success we had on-site interview. People were very friendly in general on-site took 5 hours(it generally took around 3 but mine was mixed since I've also interviewed for Backend as well). I generally liked the interview question couldn't get the offered because of my lack of experience in year.

      Perguntas de entrevista [1]

      Pergunta 1

      It's not interview question but steps were: - Design interview - Reliability interview - Bar raiser - Coding interview - Desing interview
      Responder à pergunta
      1

      Entrevista para Site Reliability Engineer

      20 de set. de 2018
      Candidato(a) sigiloso(a) à entrevista
      Palo Alto, CA
      Nenhuma oferta
      Experiência negativa
      Entrevista fácil

      Candidatura

      Candidatei-me por meio de recrutador(a). O processo levou 2 semanas. Fui entrevistado pela Uber (Palo Alto, CA) em mar. de 2018

      Entrevista

      I was contacted via LinkedIn by a recruiter. During the initial phone call with the recruiter I was assured junior level people were hired for this position and they hired people of all experience levels. I was then scheduled for a phone screen coding interview. The interviewer, however, barely asked any technical questions during the phone screen and mostly just asked questions on my background. They never asked the coding questions they were supposed to ask. I then reached out to the recruiter a few days after my interview and was told I will not be moving forward. The recruiter was nice and gave me a call with feedback, basically saying the interviewer felt I didn’t have the right skills. The interviewer barely asked any questions to assess my skills so how did they come to that conclusion? I feel like the interviewer already decided to not push me through before the screen and that I wasn’t fairly interviewed. Oh well, maybe I dodged a bullet considering Uber’s rep.

      Perguntas de entrevista [1]

      Pergunta 1

      Asked about experience at my last job.
      Responder à pergunta
      1

      Entrevista para Site Reliability Engineer

      11 de mai. de 2017
      Candidato(a) sigiloso(a) à entrevista
      San Francisco, CA
      Nenhuma oferta
      Experiência neutra
      Entrevista fácil

      Candidatura

      Candidatei-me por meio de recrutador(a). O processo levou 4 semanas. Fui entrevistado pela Uber (San Francisco, CA) em mai. de 2017

      Entrevista

      Contacted by internal recruiter through LinkedIn, I did not apply, for Pittsburgh or San Francisco as part of Advanced Technologies Group (autonomous vehicles). Recruiter did not request resume, asked very few questions about me and pushed to get a 1 hour phone interview the following week. Phone interview was with an SRE, consisted of short coding assignment then an open discussion web application architecture design question. Following day I was introduced to another recruiter to schedule an on-site in San Francisco despite saying I was only interested in the Pittsburgh position. Pretty typical making travel arrangements with their agency​, 2 nights hotel, flight, $60/day for meals, Uber rides from airport to hotel/office. Pre-interview arrival: watch short video and take online 90 question personality test (35 minutes) Interview: check in with door man, typical interview room, VTC, whiteboard and 1 running out red marker. First interviewer was remote, had me whiteboard a moving-target​-type software architecture problem. Second was in person, discussing Linux systems and troubleshooting. Lunch with second interviewer. Third interviewer was remote for 45 minutes, he spent 30 minutes telling me about what he did from an echo chamber, large conference room. Then 15 minutes about reliably monitoring large data migrations? Fourth interviewer was also remote, asked coding questions on the whiteboards as well as an interactive via my​ own computer I had to bring. Final interviewer (in person) talked about monitoring. I felt okay, not great in my responses. It was a good experience overall, everyone was really cool and nice and very accommodating, but I felt really cheated with all the remote interviews. Missing a day of work, spent 8+ hours traveling each way to an office I wouldn't work at only to have 3 out of 5 interviewer s not even be there in person.

      Perguntas de entrevista [6]

      Pergunta 1

      design a system to process a large text file produced by a client
      Responder à pergunta

      Pergunta 2

      based on previous, design system handle 100TB of data a day and work in a worldwide context
      Responder à pergunta

      Pergunta 3

      Linux questions, how and with commands used to investigate a VM with no ssh access? step through process
      Responder à pergunta

      Pergunta 4

      1/20 requests are failing in this stack (drawn application stack containing LB, frontend, backend, DB) talk me through finding the problem
      Responder à pergunta

      Pergunta 5

      whiteboard an LRU cache in the language of choice
      Responder à pergunta

      Pergunta 6

      (interactive coding) find the greatest difference in this array, language of your choice
      1 resposta