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

      22 sept. 2013
      Candidat à l'entretien anonyme
      San Francisco, CA
      Offre refusé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 août 2013

      Entretien

      I was contacted by a recruiter via LinkedIn who was looking for a backend developer, I informed her that wasn't my speciality but if they were looking for <insert speciality here> I'd be happy to talk to them. She passed me off to another recruiter who set me up with a call with the hiring manager. Call with hiring manager mostly covered non-technical topics, largely about how my speciality might fit in at Uber. After that I had an onsite interview scheduled. The onsite was a technically rigorous interview with three sessions, it reminded me of the Google style interview process. Some whiteboard coding, lots of discussions about how my speciality could fit in at Uber and a lot of sysadmin style technology questions. Everyone I met was really pleasant and very smart. I got a call just under a week later saying that they I had done well but weren't convinced that I had demonstrated sufficient software engineering skills (outside my speciality) and asked if I could do a take home coding test. I finished the test in a handful of hours over two evenings and got it back to them. From the sounds of things the code test normally happens before the onsite interview. A few days after that I heard that they wanted to make an offer. At this point I was also waiting for an offer from another company and told them so and asked for some time. The recruiter was happy to give me time to consider other offers and went through the offer in some detail. The offer was a good (but not amazing) salary plus stock options, the stock options were worth almost as much as the salary at the present valuation of the company (according to the recruiter). The story takes an unexpected detour here as my other offer is delayed due to problems at the other company. The recruiter was very understanding but grew a little frustrated as the delay turned into a multiple week saga. Eventually the other company made an offer that had a similar salary component but a much larger equity component. It was a hard choice but I was more interested in the market segment of the other company so I declined Uber's offer. Everyone I met at Uber was great and I would have been delighted to work there.
      7

      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