I applied online. The process took 2 weeks. I interviewed at Uber (San Francisco, CA) in Jul 2014
Interview
Applied online through their career section. Immediately got call from HR (in an hour; They are pretty efficient). They asked if I have any open source projects that they can take a look at. I sent some of my open source code but they wanted to see some concrete. So they sent me coding exercise which I finished in a week (It was simple exercise developing web app).
Again got call from HR the next day saying they liked it and wants to talk further. Had another phone interview with the engineer. It was very basic interview with questions like what are you working on, why are you looking to move etc. (nothing much technical).
Then interviewer asked me if I am open to come for onsite interview. They scheduled onsite interview immediately. Onsite was tough with 3 technical interviews testing my coding skills. I know i didnt do well in 1 interview (some rude guy with european accent -- as someone said earlier about him in another review) but other 2 went all right.
Next week got rejection email saying didnt meet the requirements. As far as company is concerned, it looks on the right path with lots of talented people around. But its not the best I have seen. If you are interviewing for the engineering position, read and practice system algorithms (especially caching related)
Interview questions [2]
Question 1
Implement LRU cache with get and set operations in constant time O(1).
I applied online. The process took 5 days. I interviewed at Uber (San Francisco, CA) in Jan 2014
Interview
I applied online and got contacted by a recruiter very soon after. He was very nice and told me about the company in some detail. He then proceeded to tell me that there was a coding challenge that I had to complete before applying. I agreed to do the challenge and got the details.
For the challenge you get to pick one of a few applications that they want you to build. They say that it should only take you 4 hours, but I actually worked on it for the better of 2 days and still felt like I was missing details when I went through the code during the phone screen.
The phone screen is a 40 minute interview about the code you wrote. I got the feeling they were expecting a much more thorough job than the challenge suggests. In retrospect, I would have taken care of a lot more of my TODOs.
Interview questions [1]
Question 1
My coding challenge had to calculate the nearest transit stop given your current location. They asked for an efficient way to do this. The answer ended up being something I was not familiar with, Mongo DB and such database geo location built in functions.
I applied online. The process took 1 week. I interviewed at Uber (San Francisco, CA) in Sep 2013
Interview
Had an initial call with a recruiter who wanted to gauge my understanding of Uber's business model and interest in the company. Then had a phone call with the hiring manager before coming in for four onsite interviews. The interviewers all spent a good amount of time getting to know me before moving on to the technical portion, which was mostly coding on a whiteboard. Things were a bit hectic when I interviewed - Uber had outgrown the office and interviews were done in a quiet corner. Also, the list of interviewers changed quite a bit. Another notable thing was Uber was the only company that asked how I handle stress. All signs of rapid growth, but not necessarily a bad thing.