Taro Logo

Backend Engineer Interview Experience

June 1, 2019
Neutral ExperienceNo Offer

Process

I was contacted by email to talk to an engineer.

After a few questions about my experience, I joined a shared Python session and was given a problem. I was first invited to describe my thinking about the problem, and was then given 35 minutes to solve it.

A few days after the interview, I was sent the engineer's feedback on my coding and was offered a second interview with a different engineer.

The second interviewer was not interested in my experience but wanted me to jump right into another interactive problem session. After I solved the problem, the engineer proceeded to quibble with some minor details, and I demonstrated how I could change the solution to fit his new requirements.

I was told a couple of days later in a follow-up call that the second engineer wanted to see 'a higher level of coding' and that I would not be proceeding any further.

Questions

Similar to HackerRank questions, doable in the allotted time.

Was this helpful?

Interview Statistics

The following metrics were computed from 5 interview experiences for the Uber Backend Engineer role in United States.

Success Rate

0%
Pass Rate

Uber's interview process for their Backend Engineer roles in the United States is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive40%
Neutral60%
Negative0%

Candidates reported having very good feelings for Uber's Backend Engineer interview process in United States.

Uber Work Experiences