Solicité el puesto a través de un captador. El proceso duró 3 semanas. Acudí a una entrevista en Uber (San Francisco, CA) en feb 2015
Entrevista
Contacted by a recruiter. After the normal recruiter phone screen around background, fit, etc, he sent a data challenge given 2 days to complete. It has two part, sql part and a series of open end questions with a sample dataset. It was not very difficult. Sent it back to the recruiter, a week later was informed to have a phone interview with the hiring manager.
The phone screen was firstly around background, the team and then two cases study that uber had or may have in real life. Pretty open ended as well, no need to stress. I think it went really well, especially got really positive feedback from HM directly in the middle of it. So after two weeks, I was really surprised to get a rejection email from the recruiter.
The recruiter was not very responsive, and it would be really helpful to get some genuine feedbacks.
Envié una solicitud electrónica. Acudí a una entrevista en Uber (San Jose, CA) en may 2026
Entrevista
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
Preguntas de entrevista [1]
Pregunta 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
