Screening interview consists of SQL and product sense or analytics questions. SQL was needlessly difficult. They had a bunch of seemingly related questions that are, I believe ordered by difficulty level. Interview skipped first of couple of questions and went to one of the middle questions. After answering she moved to another question which were supposed to be an add on to the one I just answered but really was not. In the end it seemed like I was just put thru a SQL wringer just being asked follow up questions that were in themselves full questions that required a good amount of time to solve. It just seemed they wanted it to be difficult just to be difficult. It was a bit exhausting.
Candidatei-me online. Fui entrevistado pela Uber (San Jose, CA) em mai. de 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
Perguntas de entrevista [1]
Pergunta 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
