Uber Software Engineer interview questions

The process began with a 90-minute OA. It consisted of two medium-to-hard algorithm questions. The format was close to what I had seen while practicing on Hack2Hire, so that platform turned out to be quite helpful for simulation-style prep. I also regularly practiced DSA using LeetCode and followed curated guides like NeetCode to brush up on core patterns. After the OA, I was invited to a technical phone screen with one engineer. The interviewer shared a coding problem on a collaborative editor. We spent most of the time on the solution, going over edge cases, optimization ideas, and time complexity analysis. The environment was friendly but fast-paced, so thinking out loud and communicating clearly helped. For company-specific prep, I searched recent Uber interview questions using Hack2Hire, LeetCode Discussion, and 1point3acres. These resources were great for spotting trends in problem types and interview focus areas.

Full interview cycle comprised of three technical interviews and a business interview. Screening was leetcode hard, but emphasis on work process. Technical interviews were medium, emphasis on edge cases, clarification questions and thought process. Business interview focused a lot on previous project work.