I applied through a recruiter. The process took 1 day. I interviewed at Uber (San Francisco, CA) in Apr 2016
Interview
The recruiter was nice and reached out to me. I scheduled a technical phone interview and the interviewer asked me to code online where you can submit the code and run test cases.
I had few issues with the syntax. I completed one of the coding questions. Did not have time to complete the second one.
Maybe i should have asked recruiter more and not assumed this was a normal online code editor.
Interview questions [1]
Question 1
Multiply 2 long numbers without using multiplication.
I applied through a recruiter. The process took 1 week. I interviewed at Uber (San Francisco, CA) in May 2016
Interview
I was contacted by recruiter in LinkedIn, we scheduled a call and he described the current openings. After a couple of days I had a call from one of tech leads and he described his project and we scheduled a phone coding screen.
The coding screen was very standard, a little discussion about my current role and coding question. The coding question was familiar for me because it's very standard question, I told it's a standard problem and described the solution in deep details and wrote the most optimal solution in time.
After a week of silence I send a message to recruiter and he replied that he forgot to follow up with me and team decided not to move forward. I was a complete surprise for me since I'm sure I performed the screen very well. I'm doing phone screens at work and currently interviewing with other companies, so I have pretty good understanding when the interview was good. As expected the recruiter was completely useless, didn't provide me any details and didn't reply anymore.
I'm not sure what exactly happened, but anyway it's pretty unhealthy recruiting process and it was complete waste of time.
I applied online. The process took 2 weeks. I interviewed at Uber (San Francisco, CA) in Apr 2015
Interview
Couple for phone screen interview which include hackerRank coding test. Then 4/5 on-site interviews followed by meeting the recruiters at the end. Questions related to Concurrency, locking, semaphore, blocking and non-blocking queues. Got selected. Overall very positive experience.
Interview questions [1]
Question 1
Mostly discussed my previous internship project. Questions related to load-balancing and scheduling and system design questions.