J'ai postulé en ligne. J'ai passé un entretien chez Uber
Entretien
I've done quite a few coding interviews but this one was different, in a bad way. My code failed on one of the test cases and as I wanted to debug it the interviewer asked me not to print anything on the console. When I a pointed out that there was no other option to debug the code he said I should be able to always say why a code fails just by looking at it! He also gave me a "tip" that there was an issue at a certain line. After wasting quite a while on said line, I realized the issue was in fact with another line and after fixing it all test cases were passed. Then he abruptly cut the interview short and said he should leave for another meeting. TLDR: My interviewer not only did not allow me to debug my code, he also mislead me in finding the bug in it.
Questions d'entretien [1]
Question 1
Hard Leetcode question related to dynamic programming.
Got referred by a colleague from a previous project, which kickstarted the hiring process. It included a mix of technical rounds and a behavioral interview. The system design question focused on restaurant recommendations for Uber Eats, while the coding portion had me tackle a grid-based shortest path problem. What helped me the most was the design walkthroughs I went through on PracHub; they were incredibly relevant. Overall, the experience was straightforward, and I ended up accepting the offer!
The interview process started with a phone screen focused on machine learning fundamentals and coding. Then I passed that stage successfully, but unfortunately didn’t receive any further communication afterward q.
The interview process started with a phone screen focused on machine learning foundations, recommendation system and coding. I passed that stage successfully, but unfortunately didn’t receive any further communication afterward.
Questions d'entretien [1]
Question 1
one leetcode easy problem; what is calibration;what is logistic regression