Uber Software Engineer Interview Experience — Phone Screen, Onsite with Graph DB Design, Then Silence

Uber·Software Engineer·Jul 2026
OnsiteTechnical ScreenNo responsemedium

Phone screen: similar to the Design Meeting Scheduler on hack2hire, but simpler.

Onsite: coding 1 was serialization and deserialization of an n-ary tree. Coding 2 I really can't remember. The system design was about using a graph DB to store who can access which resources (this was role-related, not a general system design), how to migrate over from the existing DB, how to design the schema, scalability, etc. The technical deep dive round was mainly me introducing my projects. The HM asked some basic behavioral questions, like the most complex project, conflict, failure, etc.

After the interview I heard nothing for a month and a half, and I didn't follow up either. It's probably a tragedy.

Published

Curated and edited by PracHub

Practice the questions from this interview

Discussion

Sign in to join the discussion. The author is notified of every comment.

Loading comments…

Interview at a glance

Company
Uber
Role
Software Engineer
Rounds
Technical Screen → Onsite
Outcome
No response
Difficulty
medium
Interview date
Jul 2026
Questions from this interview
3 questions

Real Uber interview experiences

First-hand reports from Uber candidates — the rounds, the questions they were asked, and how it went.

All 57 Uber interview experiences