A great place for learning and growth, a playground for builders and hackers
A great place for learning and growth, a playground for builders and hackers
Hypergrowth company with a deeply rooted startup culture. Things are rolling fast.
Both builders and hackers are valued here. Innovations and experimentations are greatly encouraged. Mistakes and failures are embraced as long as you learn from them.
The leadership is strong. There are many interesting, challenging technical problems to solve.
How many companies out there are tackling all these areas, including real-time infrastructure, logistics, big data, machine learning, geomatic engineering, and mobile development?
Hours are long, but thankfully they make it fun.
Was this helpful?
Uber Interview Questions
Uber Interview Experiences
Software Engineer
The typical process involved a phone screen with a coding question, followed by four back-to-back interviews on-site. One aspect I disliked, though understood, was the secrecy throughout the process. The interviewers could not share much detail abo
Software Engineer
I only had the chance to speak with an engineer for the telephonic round. The interviewer was terrible with communication skills, arrived late for the interview, and then had no idea how to judge a programming exercise based on C++. Overall, it was
Software Engineer
- The phone interview was a live coding session. It is a pretty difficult front-end problem. - The onsite was 4 panels with 2 engineers each. Mostly white boarding with culture questions with the manager. - My interview was 9 a.m. in the morning and
Software Engineer
San Francisco, California, United StatesMarch 1, 2016The typical process involved a phone screen with a coding question, followed by four back-to-back interviews on-site. One aspect I disliked, though understood, was the secrecy throughout the process. The interviewers could not share much detail abo
Software Engineer
San Francisco, California, United StatesSeptember 1, 2016I only had the chance to speak with an engineer for the telephonic round. The interviewer was terrible with communication skills, arrived late for the interview, and then had no idea how to judge a programming exercise based on C++. Overall, it was
Software Engineer
San Francisco, California, United StatesDecember 1, 2014- The phone interview was a live coding session. It is a pretty difficult front-end problem. - The onsite was 4 panels with 2 engineers each. Mostly white boarding with culture questions with the manager. - My interview was 9 a.m. in the morning and
