I applied through a recruiter. I interviewed at Uber (San Francisco, CA) in Jul 2018
Interview
Very Basic, Like an entry level SE role (when I had 4 years of experience) Nothing architectural, nothing practical, just rudimentary basic google questions that you can buy the book from Barnes and noble.
Interview questions [1]
Question 1
You have an array and you need to partition the array values into buckets so that each bucket sums to an equivalent value. Return a boolean if its possible or not on the array.
I applied through a recruiter. The process took 4 weeks. I interviewed at Uber (Palo Alto, CA) in Jun 2018
Interview
Done this process twice now. Probably won't ever again. I don't know if I'd take an offer here even if I had gotten one. It'd have to be really high comp since the palo alto office is crap.
Second time: Two phone screens. Onsite interview with about 5 technical interviews. What was weird is that I was interviewing almost directly with the team that I'd be working with. Didn't know that until the end. I didn't even really know the exact position until I met the hiring manager at the end (which I found out because he told me - there was no information up front!).
Almost all white boarding questions - not complaining there as that's normal. I don't think I interacted with a single American in the whole process - which was weird. And I do mean American. There was a white guy in my "group lunch" but he wasn't from the US. Speaks to the type of people who get hired at Uber, I guess. One weird note here too: My main lunch interviewer was also a white boarding interviewer later on in the day but I was never let on to that. That's /weird/.
Questions themselves were all leetcode medium to hard except for one which was closer to an easy (but it was just a question that was being thrown in for some reason). In fact, I wouldn't expect candidates to have even gotten the optimal answer to the first one I had been asked unless they had buffed up on a specific type of data structure recently (LRU cache). The questions themselves weren't important. I honestly don't know why I didn't get an offer because some of the people seemed to really like me and from my memory I did solve all of the questions with optimal answers. That first question I got - I gave the optimal solution verbally immediately. Which he was a bit surprised at but then immediately asked me to not solve it that way. I was like, "Uh, ok... So you want me to do a non-optimal solution?" He probably thought I had seen the problem before but I hadn't.
Overall, I was not emailed anything until I emailed them about it a week later... and since Uber provides absolutely no feedback after the interview - I will be declining any further interviews with them in the future. I would really recommend you don't bother with this place. I only interviewed here just for practice before I interviewed at big N but now it's just pointless. They'll take up the whole day and you could just spend that time more efficiently on leetcode. There are other companies I can go to for similar interview processes and they'll actually provide feedback when you don't get an offer.
There was an underlying feeling of racism and/or xenophobia that I felt with some people. Not going to even get into that too deeply other than saying that it was strongly felt in at least one of my interviews. If you've lived in the bay area, you know the feeling I'm talking about. Racial tension is high here. It's not new but just annoying that Uber didn't do significant bias training for that here.
Interview questions [1]
Question 1
Map Reduce large log files to get X amount of random lines, managing a Pool of IPs, rotated array search.
Very rigorous and professional, I felt like my time was valued throughout the entire process. I wish I would have had to wait less in hearing back about the job.
Interview questions [1]
Question 1
What types of experience do you have with front-end development?