A lot of reviews on Glassdoor are from Drivers/Partners that don't capture how the engineering culture is.
Company is solving a really big & tough problem: ground transportation. There is a whole new level of reliability that is needed for Uber's systems, due to the fact that it is moving real people and things. Facebook/Twitter/... not loading for 20 minutes is bad for the company's business. But Uber not working for 20 minutes means someone misses their interview, or someone might be stranded for a while.
So, the company seems to be ready to invest in a lot of long-term technology pieces needed to get there. If you are a developer hungry for working & experimenting with new software systems, I would say Uber should rank among the top 3 places right now in the Valley.
People are nice and generally willing to help you out. Everyone is tuned (the onboarding process is very good at tuning new people also towards this) to working towards getting things out of the way and marching towards the company's goals. So, if you believe in the vision of Uber and have an attitude of making progress, you will do absolutely fine here!
As with any high-growth company, not everything is necessarily figured out. There is lots and lots and lots of work to do, which could mean longer working hours.
Please provide Caltrain GoPass and BART passes for employees commuting daily (at least until Uber is cheap enough to commute daily from San Jose to SF).
Very pleasant interviewers, but my software skills didn't cut it. I came away thinking that the people at Uber were very smart yet humble. There was a one-hour phone screen. After the usual chit-chat about my resume, I was asked a programming questi
Applied through employee referral. 20-minute recruiter call, followed by a telephonic coding interview. Implement a Rate Limiting algorithm and make it executable code. It was not a very interactive session, so you need to write it yourself.
Phone interview: Previous projects, then two standard technical questions. Onsite interview: Somewhat of a joke. The whole process felt quite disorganized, and two of the interviewers on the loop quite plainly didn't know what they were talking ab
Very pleasant interviewers, but my software skills didn't cut it. I came away thinking that the people at Uber were very smart yet humble. There was a one-hour phone screen. After the usual chit-chat about my resume, I was asked a programming questi
Applied through employee referral. 20-minute recruiter call, followed by a telephonic coding interview. Implement a Rate Limiting algorithm and make it executable code. It was not a very interactive session, so you need to write it yourself.
Phone interview: Previous projects, then two standard technical questions. Onsite interview: Somewhat of a joke. The whole process felt quite disorganized, and two of the interviewers on the loop quite plainly didn't know what they were talking ab