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 Software 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. Glassdoor LLC. « Glassdoor », son logo, « Worklife Pro » et « Bowls » sont des marques déposées de Glassdoor LLC.

      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 Software Engineer

      24 mars 2016
      Candidat à l'entretien anonyme
      San Francisco, CA
      Aucune offre
      Expérience neutre
      Entretien difficile

      Candidature

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

      Entretien

      Applied to a job listing online and heard back from a recruiter within a week. Scheduled a chat with the recruiter and went over the position and interview process (1-2 phone screens, depending on performance, and an onsite). Had my phone interview a week after that with two engineers (one shadowing, who didn't contribute to the interview). We spent the first 10 minutes or so chatting about the work we've been doing at our respective companies and after that, he gave me a CTCI-type question (although not one directly from the book). I came up with and coded a slightly inefficient solution in about ten minutes, did a space and runtime analysis, and spent the rest of the time optimizing it. The interviewer was friendly and encouraging and gave hints when I got stuck and we eventually arrived at the optimal solution. The interviewer was not too concerned with running code (it's easy to get tripped up on random compiler errors in that sort of environment) and mainly seemed to care about the algorithm. He ended the interview by asking "Why Uber?" and opened up the last five minutes to questions. The recruiter was very prompt and got back to me a couple hours later with next steps and we scheduled an onsite for a week and a half later. She was also open to giving feedback when I asked for more info on things I could improve on for the onsite. The onsite included five sections: one hiring manager, one coding, one software design, one architecture, and one Uber culture. All interviews started out with around 10 minutes of introductions and ended with 5 minutes of open Q&A. Every section, with the exception of system architecture, included coding on the whiteboard. Since this was my first interview and I had no idea what to expect with design and architecture, I struggled a lot during those sections. When I admitted I didn't have much experience or familiarity with certain topics during those interviews, the interviewers tended to drill down into those areas and expected me to make educated guesses (despite not having anything on which to base those educated guesses). One interviewer also seemed to get impatient when I tried to ask clarifying questions and continuously 'dumbed' down the original question or interrupted me when I tried to reason things out. By the end of the day, I was feeling pretty exhausted and discouraged and tilted on a relatively simple recursive problem that I figured out after walking out of the building. The recruiter got back to me less than a week after that with feedback and a rejection.

      Questions d'entretien [1]

      Question 1

      What would you do to improve Uber?
      Répondre à cette question
      9

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

      Entretien pour Software Engineer

      12 juin 2026
      Employé (anonyme)
      New York, NY
      Offre acceptée
      Expérience positive
      Entretien moyen

      Candidature

      J'ai passé un entretien chez Uber (New York, NY)

      Entretien

      Recruiter call, then Phone screen, then 5 stage interview onsite. Onsite Rounds: 2 programming questions -one algorithms & one general low-level design 1 system design 1 past projects 1 manager behavioral interview

      Questions d'entretien [1]

      Question 1

      Implement the game of minesweeper
      Répondre à cette question

      Entretien pour Software Engineer

      30 avr. 2026
      Employé (anonyme)
      Offre acceptée
      Expérience neutre
      Entretien moyen

      Candidature

      J'ai passé un entretien chez Uber

      Entretien

      The interview process started with a recruiter screen where they covered my background and the role's expectations. Next, I had a phone screen focused on technical skills where I faced a DSA question on frequent elements in an array. I had practiced similar problems on prachub.com beforehand, which helped me tackle it effectively. The technical rounds consisted of coding and system design questions, including rate limiting. Finally, I had a behavioral interview where they assessed cultural fit. Overall, the experience was average, but I received and accepted an offer.
      2

      Entretien pour Software Engineer

      3 avr. 2026
      Employé (anonyme)
      San Francisco, CA
      Offre acceptée
      Expérience positive
      Entretien moyen

      Candidature

      J'ai passé un entretien chez Uber (San Francisco, CA) en avr. 2026

      Entretien

      Recruiter screen then there was a hiring manager round which felt more like a mix of product sense + execution - mostly a mix of OOP algorithms in Python or Java and some high-level system design. The onsite was 5 back to back rounds covering data structures, database management (heavy on SQL and data lifecycles), deep sys design, and behavioral. The sys design round was the real test where I had to walk through building a scalable real-time gaming leaderboard, discussing tradeoffs ofcourse in architecture, APIs, and data flow. The coding rounds was around things like linked lists and tree traversals, while the behavioral part focused heavily on ownership of my code and handling feedback. When you prep, make sure you can go a level deeper on database management and object oriented patterns instead of just grinding LC I’d say. I did grind LC though but ensure you understand the depth behind everything you solve. I also did a few mocks with uber swe on prepfully specifically for the sys design and database rounds and that honestly helped me catch some blind spots in my architecture knowledge and practice explaining my tradeoffs clearly. I’d say get a mock or two from anywhere if you can - helped me a lot!
      3

      Meilleures entreprises pour « Rémunération et avantages » près de chez vous

      avatar
      Amazon
      3.7★Rémunération et avantages
      avatar
      Google
      4.5★Rémunération et avantages
      avatar
      Amazon Web Services
      3.9★Rémunération et avantages
      avatar
      TikTok
      3.6★Rémunération et avantages