I applied through an employee referral. The process took 1 week. I interviewed at Uber
Interview
I was referred by a friend and set up with a phone screen with the technical recruiter within a few days of the referral. It was a brief fifteen-minute conversation, and the recruiter scheduled a tech screen with an engineer afterwards.
During this tech screen, the interviewer asked me to solve one coding challenge through a pair programming module. I completed it, then made sure to solve for edge cases, and then asked some questions at the end.
My interviewer seemed rushed for time, since he ended the conversation right on time and left with an abrupt "goodbye!".
I received a rejection within 48 hours, but knew exactly what I messed up on and definitely can't blame the interviewer -- he was very helpful in delivering feedback at the end of the interview.
I applied online. The process took 3 weeks. I interviewed at Uber (San Francisco, CA) in Jun 2015
Interview
Meet with software engineers. They asked me coding and design questions. I felt they mostly cared about design and not that much about code.
At the end I met with a manager who asked me about my previous work.
I had lunch in their offices about halfway during the interview. Lunch was good.
I applied through an employee referral. The process took 2 days. I interviewed at Uber (San Francisco, CA) in Aug 2015
Interview
Got called by the recruiter. Scheduled the technical phone interview soon after. The process was quick and smooth. The interview was focused mainly on mobile architecture. I've done mobile development in the past but wasn't too familiar with architecture details, so faltered a bit while answering. This was followed by a question on a design pattern. I had never heard of this pattern before. I took my time to understand the question with some help from the interviewer. He was quickly frustrated within 3-4 minutes and told me he was looking for developers with better coding skills. I disagree that I have bad coding skills just because I couldn't answer the question without frustrating the guy. Also, he should have understood that it's really hard for someone to implement a design pattern if they have never heard of it before. I would have expected him to move on to another question. Instead, he just gave up and ended the interview. I found it unfair to gauge someone's knowledge by asking one question when there is an entire ocean of other equally relevant CS topics to touch upon. All in all, an opportunity lost because of the interviewer's mood/impatience!
Interview questions [1]
Question 1
1. Say there are a bunch of records (either photos/news feed/videos) to be displayed as feed on a mobile app, how would you improve the performance of such an interface
2. Implement bus event design pattern