Uber·Software Engineer

Uber Software Engineer interview experience

No offer

Hard

Negative

Candidate report, summarized by Dataford

My Uber onsite was brutal for me in a very specific way: I felt like I was being asked to do well in different categories, but I stumbled in several places that mattered.

In the first round, the screening focused purely on data structures and algorithms, and I was given a graph problem that turned out to be a dynamic version of “Number of Islands II.” I used DSU/union-find to manage connected components as nodes were added, and I optimized the approach.

Round two was the hardest backend problem solving for me: I had to construct a BST from given distinct words and costs so that an inorder traversal produced lexicographic order while the total cost was minimized. I wasn’t confident in how smoothly that part landed.

For round three, I was asked to design APIs

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

Uber Software Engineer interview experience | Dataford