Aller au contenuAller au pied de page
  • Emplois
  • Entreprises
  • Salaires
  • Pour les employeurs

      Boostez votre carrière

      Découvrez votre salaire potentiel, décrochez des emplois de rêve et partagez vos témoignages de manière anonyme.

      employer cover photo
      employer logo
      employer logo

      Uber

      Employeur impliqué

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur Uber | Offres d’emploi chez Uber | Salaires chez Uber | Avantages sociaux chez Uber
      Entretiens chez UberEntretiens d’embauche pour Site Reliability Engineer chez UberEntretien chez Uber


      Glassdoor

      • À propos
      • Récompenses
      • Blog
      • Nous contacter
      • Guides

      Employeurs

      • Compte employeur gratuit
      • Centre employeur
      • Blog pour les employeurs

      Informations

      • Aide
      • Règles de la communauté
      • Conditions d'utilisation
      • Confidentialité et choix publicitaires
      • Ne pas vendre ni partager mes informations
      • Outil de consentement aux cookies

      Travailler avec nous

      • Annonceurs
      • Carrières
      Télécharger l'application

      • Parcourir par :
      • Entreprises
      • Emplois
      • Lieux

      Copyright © 2008-2026. Indeed, Inc. « Glassdoor », son logo, « Worklife Pro » et « Bowls » sont des marques déposées de Indeed, Inc.

      Entreprises suivies

      Tenez-vous au courant des dernières opportunités et profitez de conseils d’initiés en suivant les entreprises de vos rêves.

      Recherche d’emplois

      Obtenez des recommandations et des mises à jour personnalisées en démarrant vos recherches.

      Entretien pour Site Reliability Engineer

      28 juil. 2016
      Employé (anonyme)
      San Francisco, CA
      Offre acceptée
      Expérience positive
      Entretien difficile

      Candidature

      J'ai postulé via un recruteur. Le processus a pris 4 semaines. J'ai passé un entretien chez Uber (San Francisco, CA) en avr. 2016

      Entretien

      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.

      Autres retours d’entretien d’embauche pour un poste comme Site Reliability Engineer chez Uber

      Entretien pour Site Reliability Engineer

      14 déc. 2020
      Candidat à l'entretien anonyme
      Amsterdam
      Aucune offre
      Expérience positive
      Entretien difficile

      Candidature

      J'ai postulé en ligne. J'ai passé un entretien chez Uber (Amsterdam) en mai 2019

      Entretien

      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.

      Questions d'entretien [1]

      Question 1

      It's not interview question but steps were: - Design interview - Reliability interview - Bar raiser - Coding interview - Desing interview
      Répondre à cette question
      1

      Entretien pour Site Reliability Engineer

      20 sept. 2018
      Candidat à l'entretien anonyme
      Palo Alto, CA
      Aucune offre
      Expérience négative
      Entretien facile

      Candidature

      J'ai postulé via un recruteur. Le processus a pris 2 semaines. J'ai passé un entretien chez Uber (Palo Alto, CA) en mars 2018

      Entretien

      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.

      Questions d'entretien [1]

      Question 1

      Asked about experience at my last job.
      Répondre à cette question
      1

      Entretien pour Site Reliability Engineer

      11 mai 2017
      Candidat à l'entretien anonyme
      San Francisco, CA
      Aucune offre
      Expérience neutre
      Entretien facile

      Candidature

      J'ai postulé via un recruteur. Le processus a pris 4 semaines. J'ai passé un entretien chez Uber (San Francisco, CA) en mai 2017

      Entretien

      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.

      Questions d'entretien [6]

      Question 1

      design a system to process a large text file produced by a client
      Répondre à cette question

      Question 2

      based on previous, design system handle 100TB of data a day and work in a worldwide context
      Répondre à cette question

      Question 3

      Linux questions, how and with commands used to investigate a VM with no ssh access? step through process
      Répondre à cette question

      Question 4

      1/20 requests are failing in this stack (drawn application stack containing LB, frontend, backend, DB) talk me through finding the problem
      Répondre à cette question

      Question 5

      whiteboard an LRU cache in the language of choice
      Répondre à cette question

      Question 6

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