Uber·Full Stack Engineer

Uber Full Stack Engineer interview experience

No offer

Hard

Negative

Sunnyvale, CAPosted Dec 2025 · Candidate report, summarized by Dataford

My process started with a recruiter call, then about the next step was a one-hour technical interview.

I was told the technical interview would be frontend-focused, but that didn’t match what I actually got. Instead, it was algorithmic, and the problem was hard—hard enough that it felt unfamiliar to me since I hadn’t worked on something like that before.

Because it was an algorithm-focused question inside a timed interview, I had to shift my mindset quickly from what I expected to what I was actually asked. The gap between the promised direction and the real content made the round feel tougher than it needed to be. I didn’t end up with an offer, and it left me reflecting that I was less

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 Full Stack Engineer interview guideThe full process, round by round, with the question bank Practice Full Stack Engineer interview questionsReal questions from this role across companies All Uber interview guidesEvery role we cover at this company