Software Engineer II @ Uber
Software Engineer II @ Uber
-
Scale is huge. You need to do good optimizations to keep runtime and cost under cap.
-
Lots of open-source contributions from the teams.
-
Most things are built in-house rather than bought from third parties, which gives good opportunities for developers to build tools and frameworks.
-
Focus on engineering. Uber has some great software developers, and the focus is always on quality, optimizations, and best software design.
-
Still growing. Lots of opportunities for improvement and contribution.
-
A lot of teams, because it's a huge organization, sometimes cross-team collaboration takes time.
-
On-call is frustrating on weekends.
Additional Ratings
Was this helpful?
Uber Interview Questions
Uber Interview Experiences
Software Engineer II
I had 1 technical phone interview and 1 onsite interview. The onsite interview had 5 rounds: - 2 coding interviews - 1 system design interview - 1 behavioral questions interview - 1 hiring manager interview
Software Engineer II
I applied for the Reliability position because of my experience at AWS. The initial call went pretty smoothly, and it ended 25 minutes early. The questions were straightforward, involving sorting version numbers. I was then invited for an on-site in
Software Engineer II
The interview process started well with one recruiter call and one technical 1-hour round. I received an email saying I was moving forward in the process. A couple of days after, they stated they weren't moving ahead with my candidacy, which was ve
Software Engineer II
San Francisco, California, United StatesMarch 1, 2018I had 1 technical phone interview and 1 onsite interview. The onsite interview had 5 rounds: - 2 coding interviews - 1 system design interview - 1 behavioral questions interview - 1 hiring manager interview
Software Engineer II
San Francisco, California, United StatesFebruary 1, 2019I applied for the Reliability position because of my experience at AWS. The initial call went pretty smoothly, and it ended 25 minutes early. The questions were straightforward, involving sorting version numbers. I was then invited for an on-site in
Software Engineer II
United StatesMay 1, 2025The interview process started well with one recruiter call and one technical 1-hour round. I received an email saying I was moving forward in the process. A couple of days after, they stated they weren't moving ahead with my candidacy, which was ve
