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

      10 juil. 2024
      Candidat à l'entretien anonyme
      São Paulo,
      Aucune offre
      Expérience négative
      Entretien moyen

      Candidature

      J'ai postulé en ligne. J'ai passé un entretien chez Uber (São Paulo, ) en avr. 2024

      Entretien

      I applied for the position in March/2024 via Linkedin. A few days later I received an email from the recruiter for a conversation. We talked a little about my experiences, the challenges they face, salary expectations, that sort of thing. She explained the following phases of the selection process to me, I participated in all of them. 1. Online test on Code Signal (algorithms and data structure, 4 questions, 70 minutes) 2. Onsite (literally in the office) with 4 steps: 1 specific code (backend in my case), 1 collaboration (using Uber's values as a reference), 1 algorithms (leetcode style), 1 system design. They give little or no information about interview details. I had to ask a lot to get any information. They share some mock interview videos but it doesn't help much. About the steps: 1. Online test: there are 4 leetcode style challenges. There is no time to solve all 4 in the time available. There are 2 easy, 1 medium and 1 difficult. I managed to solve the 2 easy ones, the medium one and partially the difficult one. The worst part is that the platform is very buggy, they record your screen all the time so the connection can drop and you waste a lot of time. 2. Onsite (a whole afternoon at the Uber office). * Collaboration: these are situational questions whose answers must be connected to Uber's values. Tip: Take all the values, select stories from your career that relate and it should be enough. I had this interview with a manager and the experience was good overall. * Specific (Backend): they didn't give me any information about this step before so I didn't know what to expect. It was a simpler Leetcode style problem. I don't really know what they were evaluating at this stage since there was another similar one later. I think the experience here was OK. * System Design: they present a very generic system design problem and you must ask questions to clarify and offer solutions to the problem. In the middle of the solution, the interviewer asks questions about it. My experience was terrible. The interviewer introduced himself by proudly saying that he was the "bar raiser", when the person says that you already know what to expect. He was by far the most arrogant person who has ever interviewed me in my career. And like every arrogant person there are many things he doesn't know and won't admit. He said wrong information about databases, laughed at some of the answers I gave, and kept putting pressure on me to redo some of the answers. My desire at the end of this stage was to abandon the process, but I was so stunned that I didn't do it. * Algorithms: they present a leetcode-style problem (middle level perhaps) and you must present the solution. The interviewer was good and I was able to solve the problem without difficulty. I knew I wouldn't be approved because of that system design interview. A few days later the recruiter sent a generic message saying that I didn't pass without giving more details.

      Questions d'entretien [1]

      Question 1

      Solve this system design problem while I laugh on your answers
      Répondre à cette question
      18

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

      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

      Entretien pour Software Engineer

      27 mars 2026
      Candidat à l'entretien anonyme
      Sydney
      Aucune offre
      Expérience neutre
      Entretien difficile

      Candidature

      J'ai postulé en ligne. J'ai passé un entretien chez Uber (Sydney)

      Entretien

      The Uber Software Engineer interview typically takes 4–6 weeks and begins with a recruiter screen focused on your experience, motivation, and role fit, followed by an online coding assessment or live coding screen with one or two algorithm problems that test correctness, efficiency, and communication. If you pass, you’ll have a technical phone interview solving a medium-to-hard coding problem with complexity discussion, and then a virtual onsite loop of about four to five one-hour rounds: a data-structures/algorithms coding interview, a machine-coding or low-level design round where you build a small system with clean, runnable code, a system design interview focused on large-scale distributed systems (often Uber-style problems like ride dispatch or surge pricing), and a behavioral interview assessing ownership, teamwork, and decision-making. Senior roles may include a project deep dive, and after all rounds a hiring committee reviews feedback before team matching and a final offer, with Uber evaluating problem solving, engineering fundamentals, system thinking, communication, and real-world impact throughout the process.

      Questions d'entretien [1]

      Question 1

      Tell me about a time you took ownership of a problem and solved it end-to-end.
      Répondre à cette question