Ho presentato la mia candidatura online. Ho sostenuto un colloquio presso Uber (New York, NY) nel mese di giu 2017
Colloquio
Definitely a dysfunctional company as all news items point to. UberEverything engineer interviewer - his lack of knowledge most likely is why I didn't get past the coding phone interview - he thought there was a retain cycle in my code (there was not, though a one way reference was kept), he thought sending a message to nil would cause a bad access exception, and he didn't understand part of my API functionality until I explained it to him at the end when he said 'ok that's a valid use case'. In hindsight, he generally did not understand my solution - interpreted the code incorrectly. Talk about thinking on the fly...
Domande di colloquio [1]
Domanda 1
Design a NSNotificationCenter API that accepts blocks
Ho sostenuto un colloquio presso Uber (Seattle, WA)
Colloquio
Remote/Virtual first round over zoom call with one of their engineers that had some knowledge of the tech stack. That being said they only ended up asking me one simple, standard/general DSA question.
Ho presentato la mia candidatura tramite un selezionatore. La procedura ha richiesto una settimana. Ho sostenuto un colloquio presso Uber
Colloquio
Typical big tech interview process. You have your phone screening and if you score high you will move on to the 1 hour coding challenge. DS & algorithms with runtime analysis, nothing out of the ordinary. However, communication was very bad. Never received any email after the first technical interview even though it went well. This speaks a lot about the interview process which directly reflects the company.
Domande di colloquio [1]
Domanda 1
Code up a function that meets specific criteria, analyze runtime and optimize.
Ho presentato la mia candidatura tramite segnalazione di un dipendente. La procedura ha richiesto 4 settimane. Ho sostenuto un colloquio presso Uber nel mese di mag 2022
Colloquio
Really interesting and challenging interview process.
The HR process was quite long.
There were 7 stages:
1 - LeetCode medium task
2 - 1 hour call with coding task
3 - 1 hour call with algorithms task
4 - 1 hour call with current architecture and design approaches
5 - 1 hour call with Engineering Manager to check motivation and soft skills
6 - 1 hour call with System Design task
7 - 1 hour call with iOS-specific coding task
All stages were interesting, with practical tasks. The interviewers were friendly and did their best to reduce stress and make a relaxed atmosphere.