Interview experience at Uber Amsterdam
I have never thought I would be applying for Uber in this lifetime, the tag of premium and top-notch competitive programing to scare me away, but out of the blue I applied to Uber AMS and even forgot all about the application, because I never thought I will even clear the resume shortlisting.
So, imagine my surprise when I got the mail from Uber HR to schedule a call for SDE1 position, and viola, the next minute I was talking to her all about AMS and the team.
After 3 weeks, I received a test link where I have to code 4 questions in 3 hr and the results were announced next week, which I cleared and moved onto the onsite rounds held virtually due to Covid’19.
I started off reading Cracking the Coding Interview book to build up my basics along with these Git Repo https://github.com/jwasham/coding-interview-university and https://github.com/kdn251/interviews.
I used to work on Medium/Hard based Leetcode problems everyday and some of the Uber tagged questions which helped me gain knowledge of what was being expected of the interview, the pattern of the interview is quite simple, a round of coding and a round of system design followed by the hiring manager round.
The first round was a coding round, where the interviewer gave a medium LC question and I have to explain my thought process, the DS used, the edge cases and then code it up. When you are interviewing for Uber, you are expected to write code on the IDE, compile and run it on the test cases. The second one was System Design, more of a OOD design, where a problem statement was given, vague and I was expected to ask clarifying questions and code the compliable and working solution.
The third was hiring manager round, where the manager asks the questions about the work experience, the projects worked on, the conferences attended and gives time to ask about the culture about Uber.
Overall, the process smooth and amazing, the HR’s tend to communicate with the candidate at each and every point of time.
— Arpita
