There's a lot of opportunity for career development. A lot of roles at Uber are loosely defined, and there are a lot of orgs eager to train and develop entry-level candidates to develop incredibly valuable skills that can make you very marketable elsewhere. Lots of personal and professional development and training programs are sponsored by Uber, especially for entry-level employees.
The organizational structure for support level employees versus the L-ladder or salaried employees is very different.
Lots of benefits are cut off from S-ladder employees, with slower growth and fewer opportunities.
Essentially, the company feels like two organizations: one with great perks, etc., and one with a customer support focus with very restrictive policies.
More parity between the S-ladder and L-ladder. Obviously, customer-facing roles need some constraints regarding PTO, etc. However, a lot of S-ladder roles are not customer-facing and should not be subject to the same rules. It's incredibly alienating to work with cross-functional partners who have tons of perks you don't have access to merely because your job level doesn't rate that level of benefits.
It was rigorous but exciting, and I learned a lot. There were multiple coding challenges as well as people interviews. I had an overall good experience, despite not getting the role. I will try again another time.
The interview process was overall smooth. The coding question was not easy, but it was also not difficult. There were behavioral questions as well. Be sure to prepare yourself for a long coding question, which is followed by four to five behavioral
Tough but fair. I thought it could have been more involved, but they seemed to have their ideal candidate in mind before the interview began. I would interview again for an engineering role.
It was rigorous but exciting, and I learned a lot. There were multiple coding challenges as well as people interviews. I had an overall good experience, despite not getting the role. I will try again another time.
The interview process was overall smooth. The coding question was not easy, but it was also not difficult. There were behavioral questions as well. Be sure to prepare yourself for a long coding question, which is followed by four to five behavioral
Tough but fair. I thought it could have been more involved, but they seemed to have their ideal candidate in mind before the interview began. I would interview again for an engineering role.