Uber Interview Questions
& Process

The recruiter was a few minutes late and mentioned it wasn't a video call. I got a really off vibe from the start with her attitude, which made me feel like crap, so I ended the conversation. It clearly wasn't going well. She asked if I had done internships, and I said no. She didn't seem to understand the timeline of my resume and got upset with me, not outwardly, but I could feel it. I felt like I was wasting my time from the start with someone who seemed to have already decided not to move forward with me. It felt like none of the answers I gave were good enough, so I ended the conversation. I don't think an interview has ever made me feel this way. It felt like an interrogation, not a conversation.

The Uber Software Engineer interview usually runs 4–6 weeks and starts with a recruiter screen focused on your background, motivation, and fit for the role, then an online coding test or live coding screen with one or two algorithm questions that check correctness, efficiency, and how you communicate. If you pass that, you’ll move on to a technical phone interview where you solve a medium-to-hard coding problem and talk through its complexity, and then a virtual onsite loop with about four to five one-hour sessions: a data-structures/algorithms coding interview, a machine-coding or low-level design round where you build a small system with clean, runnable code, a system design interview on large-scale distributed systems (often Uber-style scenarios like ride dispatch or surge pricing), and a behavioral interview looking at ownership, teamwork, and decision-making. For senior roles there may also be a deep dive into one of your projects, and after all interviews a hiring committee reviews feedback before team matching and a final offer, with Uber consistently assessing problem solving, engineering fundamentals, system thinking, communication, and real-world impact throughout the entire process.

Awful. First I was put through an online assessment which I prepped for and cleared. Then I was put through a TA recruitment screening with an external uber recruiter from a provider called rec hub. Cleared that too. Then I was passed on to an internal uber recruiter who set up a zoom call with the hiring manager - the co-head of Uber for business UK. Then a couple of days later the internal recruiter says we need to reschedule for later this week. Then the internal recruiter vanishes and the external recruiter comes back saying I will reschedule this with the hiring manager. Waiting for a new date from him. Then silence and ghosting. No further update, no explanation, no feedback no apology. The preparation involved UBER values - which sound like a big joke given this awful - head does not know what the tail is doing - experience. Shame on you hiring manager and on uber.

The interview process had three rounds in total. Round 1 – JavaScript Fundamentals. The first round was about core JavaScript concepts. The interviewer asked a plain vanilla JavaScript question that checked understanding of the event loop, callbacks, and asynchronous behavior. A key part of the question involved using setTimeout with callbacks and reasoning about execution order. Example type of discussion: how setTimeout works in the event loop, difference between synchronous vs asynchronous execution, understanding callback execution order, predicting console output timing. The interviewer wanted a solid explanation of how the call stack, Web APIs, callback queue, and event loop interact in JavaScript. I wasn’t able to fully answer the question to the interviewer’s expectations, so I did not move forward to the later rounds.