Developer applicants have rated the interview process at Uber with 3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 100% positive. To compare, the company-average is 44.4% positive. This is according to Glassdoor user ratings.
Here are the most commonly searched roles for interview reports -
the hiring process is kinda messy, but the people there including recruiters seem very nice, so they are making efforts to make things work. The team hire structure can be hit or miss, interviewers are less prepared, nothing ensures a consistent high bar. less of getting talents more of filling the positions.
the offer making process really shows the philosophy of the company. people are hired for working on tasks, not to help building a great company. Very much a top down structure than eng driven like google. Seems that engs are just expected to follow orders, not to think or improve.
the stock option is offered without mentioning the current fair market value, only throwing big potential growth, red flag 1, getting arrogant and cold when trying to negotiate, red flag 2.
If future employees are not treated with respect, hard to imagine how things would be when actually working there.
I spoke with a technical recruiter at Uber and answered his questions. It was more of an investigation into my background and experience. At the end of the interview my information was passed on to the hiring manager but I never heard back which just seems like poor etiquette on their part.
Interview questions [1]
Question 1
There weren't really any difficult or unexpected question since this was a preliminary interview.
I interviewed at Uber because they are an impressive company and probably a great place to work. I didn't receive and offer. I cannot say that I was surprised. I do believe there were a few things they could have done better to increase my chances as well as to treat their candidates better.
As others have mentioned, they encourage their candidates to handle a coding challenge. While this is not unreasonable, they did not set clear expectations. Specifically, if you are invited on-site, they will carefully review your submission in person. I might have performed better at the interview if I didn't have to admit so many areas for improvement in my submission. Had I been aware that my code would be part of the interview, I probably would have done a better job. This is something to be aware of because they failed to mention it prior to my submission.
Otherwise, the interviews were tough and tiring. The questions were somewhat less structured than many other companies.
The office seemed quite disorganized. I doubt it's always like that, but it did appear that I was invited at an especially hectic time, both at the office and in the neighborhood outside. I might have benefited from them inviting me at a more reasonable time. The recruiter had rushed me through the whole process. Maybe I would have been more prepared if I hadn't allowed this to happen.
Finally, they repeatedly volunteered to pay to reimburse my transportation costs and then failed to do so. It wasn't a significant amount, but it was more than I have spent anywhere else. The only reason I splurged was that, with no suggestion of my own, the recruiter volunteered to cover the costs multiple times. Of course, after I was rejected I was not reimbursed. It's an easy empty promise to make.
Interview questions [1]
Question 1
Be prepared for very general design oriented questions that require a great deal of discussion.