Ho presentato la mia candidatura tramite segnalazione di un dipendente. Ho sostenuto un colloquio presso Uber (San Francisco, CA) nel mese di mag 2018
Colloquio
The process started by one of my LinkedIn connections referring me for the position. First I got a screen interview with the recruiter. She was nice and helpful. Then I was given a take home assignment and was given a week to complete it. It was a text-book machine learning assignment that you had to deal with missing values and perform modeling.
This was followed by a coding interview, which went pretty well and the person who was interviewing me enjoyed my work. Then, I was told that I have to do another coding interview focusing on machine learning. The interview started with one of the challenging Leetcode examples. I didn't do my best there. Then I was asked some tricky questions about modeling and SQL. Next morning I received rejection email, which I was expecting.
Pros of the interview:
I learned through the process a lot. The first codepair was very good and I enjoyed it. Take home challenge also provided me with the real-world data and application of machine learning.
Cons of the interview:
-I felt there is a lack of coordination in Uber's process. For example, I was asked to have a codepair on machine learning concepts, which I prepared myself for, however, I was mainly asked software engineering questions and non-practical statistic concepts.
-I felt UberATG R&D is a bit confused about the application of machine learning to this new area and it seems there is no real active project going on.
In total, although the process was a good learning experience for the future of my job hunting experience. However, comparing to other companies that I have been applying to, lack of transparency, coordination, and direction in the hiring process of Uber could be frustrating and discouraging.
Ho presentato la mia candidatura online. Ho sostenuto un colloquio presso Uber (San Jose, CA) nel mese di mag 2026
Colloquio
My interview started with a stats coding round where I was asked to code for expected value for a problem and the second interview was a case study which was quite easy
Domande di colloquio [1]
Domanda 1
Expected value for a dice problem and a case study about a Uber problem
The process was smooth and well organized. A recruiter initially reached out, followed by a first round consisting of two interviews—one with the team manager and another with a data scientist, both engaging and informative.
Failed at technical screening round. Recruiter told me I will be tested on SQL, but I got tested on Python as well. Did not prepare well for that interview and didn't get moved forward