Uber coding screen for a software engineer role. One algorithmic problem, simulation-style, the kind that looks approachable until you're actually implementing it.
“The removal condition tripped me up at first.”
LIMITED TIME 🎁: Register now to get 60 minutes of AI Mock Interviewing for FREE!
JoinUber is a global technology company that operates a platform connecting riders with drivers for on-demand transportation, as well as food delivery through Uber Eats and freight logistics services. It is known for pioneering the ride-hailing industry and disrupting traditional transportation markets worldwide.
Every question, shortened answers
Browse all 609 notes for Uber. Each answer is trimmed to its first line — create a free account to read them in full.
Uber coding screen for a software engineer role. One algorithmic problem, simulation-style, the kind that looks approachable until you're actually implementing it.
“The removal condition tripped me up at first.”
Uber SWE interview, coding round. One problem the whole time, stack-based simulation. Felt okay about my solution but the timestamp math tripped me up more than I expected.
“My first instinct was right, use a stack to track which function is currently running.”
Uber data scientist interview with a pretty brutal causal inference question about a messy real-world A/B test. The kind of problem where you think you know the framework and then realize halfway through that there are like three simultaneous complications to untangle.
“This one took me a minute to even parse.”
Uber DS interview focused entirely on a deep system design problem around ETA prediction. The scope was massive and I felt like I was constantly playing catch-up trying to cover all the angles they wanted.
“This was basically seven questions duct-taped into one.”
Uber data science interview with a meaty end-to-end design question about the map search experience. One question, lots of surface area, and I definitely underestimated how deep they wanted to go on the ranking and experimentation side.
“This question is deceptively wide.”
Uber system design round for a software engineering role, focused entirely on a distributed data pipeline problem. The question was dense and technical, covering a lot of ground in one shot.
“This one hit me like a wall.”
Uber SWE coding round, just the one grid traversal problem. Pretty standard BFS territory but the constraints are large enough that you can't be sloppy about it.
“Classic BFS and I knew it immediately, which was both good and bad.”
Product sense interview for a Data Scientist internship at Uber. One big open-ended question that basically asked me to design a new rider feature from scratch, including metrics, experimentation, and marketplace tradeoffs. Pretty intense for an intern role.
“This was basically the whole interview in one prompt.”
SQL-heavy technical screen for a Data Scientist role at Uber. Two tables, one prompt, and a pile of edge cases that made me realize I'd been sloppy about age calculations for years.
“Felt pretty confident here.”
Uber SWE OA, one algorithmic problem about simulating round-trip mission scheduling across two sorted timetables. Pretty niche problem, felt like it was pulled from an older CodeSignal bank rather than something freshly written.
“I went with binary search first because two pointers felt fiddly to get right under pressure.”