Me postulé en línea. El proceso tomó 3 semanas. Acudí a una entrevista en Uber (San Francisco, CA) en sept 2021
Entrevista
This was for a research position in Economics.
First Step: Recruiter phone call for 15 minutes going over some of my past experience and resume
Second Step: A coding challenge to complete within a week (once open it had 24 hours). A lot of open ended questions which included SQL, python and product knowledge
Third Step: A 1 hour interview with a member of the team. Questions included a very easy algorithm question (fizzbuzz), going over past experience (have you ever been in a position where you had to explain technical concepts to a non-technical person), and a case study. She was nice and made me very interested in the position. Not the coldness PhD graduates usually have.
Virtual Onsite: 5 separate 1 hour interviews spread between 2 days. One of them was coding, two of them were economics related (just case studies). one problem solving (algorithms) and a behavioral interview. Everyone in the team seemed crazy accomplished.
1st round coding + stats 2nd round with hm onsite round has 5 interviews, coding, business case, stakeholder management, and 2 more technical round. Need to know stats, experimentation, ML, NLP well.
Preguntas de entrevista [1]
Pregunta 1
How would you reduce the variance in control and test group?
The initial interview was fine, just some basic python/sql manipulation and creatinga simple function in python along with a few causal inference case questions. However it seems the hiring manager might be a bit picky even if you vibe well and can answer his questions relatively decently. As you can tell by the other reviews, it seems the interview request rate is relatively high while the rejection rate during interview process is VERY high.
Preguntas de entrevista [1]
Pregunta 1
when to use synthetic control, a/b testing, DiD designs.
Me postulé en línea. Acudí a una entrevista en Uber en ene 2026
Entrevista
The call with their talent acquisition was great because he was very nice and did not want to waste anyone's time! But the next stage which was a SQL exercise with someone from their team was not pleasant. The questions were fine, but she obviously didn't want to be there! And despite the fact that they said previously in their email that they'll be using HackerRank, she asked me to write my codes in a word doc because apparently she didn't have any link for that!
Preguntas de entrevista [1]
Pregunta 1
Basic SQL codes about filtering Uber drivers data to specific dates etc.
