I applied online through their career section and immediately received a call from HR within an hour. They are quite efficient.
They asked if I had any open-source projects they could review. I sent some of my open-source code, but they wanted to see something more concrete. So, they sent me a coding exercise, which I finished in a week. It was a simple exercise involving the development of a web app.
I received another call from HR the next day, stating they liked my submission and wanted to discuss further. I had another phone interview with an engineer. It was a very basic interview with questions like, "What are you working on?" and "Why are you looking to move?" (nothing much technical).
Then, the interviewer asked if I was open to an onsite interview. They scheduled it immediately. The onsite was tough, with three technical interviews testing my coding skills. I know I didn't do well in one interview (with a rather rude interviewer who had a European accent, as mentioned by others in previous reviews), but the other two went all right.
The following week, I received a rejection email stating I didn't meet the requirements. As far as the company is concerned, it seems to be on the right path with many talented people. However, it's not the best environment I've experienced.
If you are interviewing for an engineering position, I recommend reading up on and practicing system algorithms, especially those related to caching.
Implement LRU cache with get and set operations in constant time O(1).
Given a regular expression pattern and a string, check to see if the pattern matches the string.
The following metrics were computed from 121 interview experiences for the Uber Software Engineer role in San Francisco, California.
Uber's interview process for their Software Engineer roles in San Francisco, California is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having very good feelings for Uber's Software Engineer interview process in San Francisco, California.