Uber·Software Engineer

Uber Software Engineer interview experience

No offer

Hard

Negative

Candidate report, summarized by Dataford

I failed an Uber phone screen for a senior dev position, and the reason it hit me harder than expected was the difficulty level.

The problem felt tougher—probably LeetCode hard—and I got to a working solution at the end that compiled and passed the couple example cases the interviewer started with.

The task was to find the least number of route changes to get from one station to another, given a set of bus routes represented as lists of integers. I initially modeled it as stations being nodes, but the interviewer hinted at a different trick: building the graph with each route as a node instead.

Even though I eventually arrived at a correct working solution, the rejection made it clear that the phone screen wasn’t

Create a free Dataford account to unlock the full round-by-round breakdown, the questions asked and the outcome.

Read the full report Read the full report

Preparing for this interview?

Uber Software Engineer interview guideThe full process, round by round, with the question bank Practice Software Engineer interview questionsReal questions from this role across companies All Uber interview guidesEvery role we cover at this company