Uber Frieght SDE 2 Interview | what to expect ?
Summary
I had a first-round DSA interview with Uber Freight for an SDE 2 role. I struggled with a 2D DP question, proposing a brute force solution and running out of time before optimizing it.
Interview Experiences & Insights
Uber Frieght SDE 2 Interview | what to expect ?
Uber | System Design Round | L5 | Design Kafka
Uber Intial Screening Question for Senior Software Engineering Role
Uber SDE 2 Fullstack Interview Experience
Uber Software Engineer Backend Role Interview Experience
63 more experiences below
I had a first-round DSA interview with Uber Freight for an SDE 2 role. I struggled with a 2D DP question, proposing a brute force solution and running out of time before optimizing it.
I recently interviewed at Uber for an L5 System Design role, where I was asked to design a distributed message broker similar to Apache Kafka. Although I felt the discussion went very well, covering deep Kafka internals, I received frustrating feedback, suggesting I might only be eligible for an L4 position due to a perceived lack of clarifying questions.
This post describes the initial screening questions for a Senior Software Engineering role at Uber, which focused on finding local minima in an array.
I applied to Uber via LinkedIn and underwent multiple interview rounds for an SDE 2 Fullstack role, encountering DSA, LLD, System Design, and behavioral questions. I am currently awaiting the results of my interviews.
I'm sharing my interview experience for a Software Engineer Backend Role, covering questions asked from the Online Assessment (OA) to the full-loop interviews.
Applied for Uber SDE2 role and faced multiple rounds of interviews, but ultimately got rejected. The interview process included a phone screening with a stack problem, followed by DSA and system design rounds. Despite clearing some rounds, the candidate was not able to solve certain problems and was rejected in the end.
During the Uber SDE 2 interview round, I encountered a challenging problem related to grouping people for trips with specific constraints. The problem required finding the maximum number of people who could go on a trip based on their group size requirements. Despite not being able to think of an approach, the problem provided valuable insight into handling complex grouping constraints.
I completed an 8-week interview process for an SDE-2 position at Uber, successfully securing an offer after multiple technical and behavioral rounds, including DSA, LLD, HLD, and a leadership assessment.
I interviewed for an L4 position at Uber and was ultimately accepted after multiple rounds covering coding, system design, and behavioral aspects.
I interviewed with Uber for an L4 SDE2 Android position and completed a CodeSignal OA, phone screen, DSA, Android Machine Coding, HLD, and Hiring Manager rounds. Unfortunately, I was rejected after the final assessment.
I interviewed for an SDE1 position at Uber and was challenged with a problem to find the kth smallest square in a sorted array, focusing on optimal time complexity.
I had a phone screen for an SDE 3 role at Uber, which focused on designing an API for scheduling meetings within a fixed set of conference rooms.
I recently had a screening round interview with Uber for a Senior Software Engineer role. During the interview, I was presented with a grid-based problem involving robot movement constraints, which ultimately led to a rejection.
I recently had my first coding round for the SDE 2 role at Uber. After successfully solving the Alien Dictionary problem, I received positive feedback and am now moving to the second coding round.
I interviewed for a Front End Software Engineer II role at Uber, completing a phone round and four onsite rounds covering DSA, System Design, Behavioral, and Front End specialization. Despite feeling I met minimum bars for most rounds, especially after struggling with a graph problem in Javascript, I'm quite pessimistic about the final outcome.
Applied for Uber's SSE (L5-A) backend position. The interview process included a technical phone round with two questions. The first was a LeetCode problem on water and jug problem, which required an optimized solution. The second was a system design problem involving managing a hierarchy of employees with specific functions. Both interviews resulted in rejection.
I successfully navigated through multiple technical and design rounds for a Software Engineer II role at Uber in Bangalore, ultimately receiving and accepting an offer.
I had a system design round with Uber where I was asked to design a chat application similar to Facebook Messenger, focusing on key features like 1:1 and group conversations, offline user handling, and message history.
I recently went through the interview process for an L4 Frontend position at Uber, which included a screening round, two coding rounds focusing on DSA and UI, a UI system design round, and a manager discussion. The questions spanned from implementing interactive UI components to designing a concurrent task queue and a full-fledged calendar application.
I successfully interviewed for a SWE II Backend role at Uber for their Grocery organization in the USA and received an offer. The interview process included an Online Assessment, two technical coding rounds, a system design interview for a cart management system, and a behavioral chat with the hiring manager.
I recently interviewed for a Frontend position at Uber where I was tasked with implementing a custom Promise function.
I interviewed for an SSE role at Uber in Bangalore. I successfully cleared the BPS and DSA rounds, but likely failed the LLD/MC round due to an issue with meeting all requirements for a vending machine design problem, leading to an anticipated rejection.
I successfully navigated the L4 interview process at Uber in the US, securing an offer after several rounds including coding, behavioral, and system design challenges. The overall experience was positive, and I found the interviewers to be very friendly and supportive.
I successfully navigated through a multi-stage interview process for a Frontend Engineer L5A position at Uber. The process, which spanned three weeks, included coding, system design, and behavioral rounds, ultimately resulting in an offer.
I interviewed with Uber for an L4 Software Engineer position, navigating through several rounds including Data Structures & Algorithms, Machine Coding, and System Design. While my DSA round was strong, the machine coding round proved challenging due to an emphasis on HLD over LLD under tight time constraints. I later faced a system design challenge for Uber Eats for train travelers, which I approached structurally. The process is ongoing, pending a final decision after some scheduling delays and an upcoming Bar-Raiser round.
I successfully interviewed for the Uber SDE-2 position in Bangalore, which involved 5 rounds including a coding elimination, DSA, Low-Level Design, High-Level Design, and a Managerial discussion, ultimately leading to an offer.
I was rejected after a phone screen for an SDE 2 role at Uber. I tackled a problem similar to LeetCode 305 but faced significant interruptions and time constraints from the interviewer, which hampered my performance and debugging.
I successfully navigated a multi-round interview process at Uber India for an L5 Staff Software Engineer role, which spanned approximately two months, ultimately resulting in an offer.
I interviewed for an SDE1 role at Uber, successfully solving two problems fully and one partially, but ultimately did not receive an offer as Uber emphasized 'coding profile strength' and encouraged me to reapply.
I interviewed for a Senior Frontend Engineer position at Uber, which involved rounds on JavaScript problem solving and Data Structures & Algorithms, including graph problems like Topological Sort and Cycle Detection.
I interviewed for a Senior Software Engineer (L5A) position at Uber. Despite an initial 'NO-HIRE' feedback in one of the technical rounds, the hiring manager and bar-raiser managed to flip the decision, leading to a successful offer.
I was selected for the Uber SDE1 role after four interview rounds, which included Data Structures & Algorithms, projects, Low-Level Design, and a behavioral hiring manager interview.
I interviewed for an SDE-2 Frontend role at Uber, undergoing multiple coding rounds, Low-Level Design, High-Level Design, and a Hiring Manager discussion, but was ultimately rejected.
I interviewed for a Software Engineer 2 position at Uber, which included a Code Signal assessment, a Zoom interview, and two on-site rounds focusing on Data Structures and Low-Level Design. My experience concluded with a rejection after completing all scheduled rounds.
I interviewed for the SDE-1 role at Uber, completing four rounds covering technical coding, a graph-based problem with a real-world scenario, low-level design, and a hiring manager round focusing on behavioral aspects. I am currently awaiting the final decision.
I applied off-campus to Uber for an SDE 1 role and successfully received an offer after completing an online assessment, an elimination round, two coding rounds (one focusing on System Design), and a hiring manager behavioral round. The overall experience was great, and I found the interviewers and process logical.
I successfully interviewed for an SDE 2 position at Uber, clearing several rounds including coding, object-oriented design, distributed system design, and behavioral discussions. I received positive feedback and am currently moving forward in the offer process.
I interviewed for the SDE-2 role at Uber in India. The interview process included a phone screen, two data structures and algorithms rounds, one low-level design round, one high-level design round, and a managerial discussion.
I had a 1 hour 15 minutes onsite system design round at Uber where I was asked to detail the hardest technical problem I recently solved from my projects, focusing on system scale and complexity.
This post details my interview experience for an SDE-2 Frontend Engineer role at Uber, which involved three rounds. The rounds focused on implementing a memoize utility, an async scheduler with concurrency limits, and a task runner with dependencies.
I successfully navigated the Uber SDE2 interview process, which involved five rounds covering coding, DSA, LLD, HLD, and behavioral aspects, ultimately leading to a hire decision which I declined due to personal reasons.
I interviewed for an SDE-2 Frontend role at Uber, completing 5 rounds including a hiring manager round. Despite a strong performance in early rounds, I received a 'No hire' decision due to a lean hire in system design and a 'No hire' from the HM, though I was asked to reapply after 6 months.
I appeared in an Uber interview recently and was asked a coding question in the first round, which I solved but failed some test cases, leading to rejection.
I was asked to design a reservation system in a DSA interview round.
I interviewed for an L4 role at Uber in Bangalore and received an offer. The interview process included a HackerRank round, a phone screen, two DSA rounds, LLD, HLD, and a Hiring Manager round, with initial negative feedback in LLD and HM rounds that was later overturned.
I had a technical interview for an L4 role at Uber, where I was asked a grid-based problem involving robot placement and blocker detection. Unfortunately, I was not selected.
I had a phone screen interview with Uber for an L5-A role. The interview involved a data structures and algorithms problem where I had to implement methods to ingest numbers into a stream and find the minimum missing number so far.
I successfully completed my interview process for an SDE 1 (L3) position at Uber in Bangalore, receiving and accepting an offer. The rounds included an Online Assessment, DSA, System Design, and a Behavioral discussion, ultimately leading to a positive outcome.
This post details a specific coding question encountered during a phone screen round for a Senior Software Engineer position at Uber in Hyderabad.
I successfully interviewed for an SDE II position at Uber, navigating various technical and behavioral rounds, and ultimately received an offer.
I had a positive experience interviewing for an SSE L5-A role at Uber in Bangalore, covering various rounds including coding, LLD, HLD, and a hiring manager discussion. I successfully received an offer.
I interviewed for an SDE 2 role at Uber, which included an online assessment and five interview rounds covering Data Structures & Algorithms, Low-Level Design, High-Level Design, and behavioral questions. Despite receiving positive feedback, I was ultimately rejected for not exceeding the bar.
I interviewed for an SDE-2 role at Uber in Bengaluru, India, and was ultimately rejected despite positive outcomes in most rounds, including DSA screening and onsite. My final verdict was rejected after failing the Machine Coding and Bar Raiser rounds.
I interviewed for a Senior Software Engineer role at Uber in Bangalore and was rejected due to issues in the managerial and low-level design rounds. The process included an online assessment, two coding rounds, a managerial interview, high-level design, and low-level design.
I interviewed with Uber for an SDE 2 role and encountered a challenging QuadTree compression problem during a virtual onsite round, ultimately receiving a rejection.
I recently interviewed with Uber for an SDE 2 role and faced a challenging QuadTree compression problem during a virtual onsite round, ultimately receiving a rejection.
I applied for a Software Engineer 1 position at Uber Amsterdam. After a coding assessment, I had a technical interview involving a graph problem on currency conversion. Despite solving the problem efficiently, I received a rejection a month later without any feedback.
I recently interviewed for a Senior Software Engineer position at Uber, going through three rounds focused on Data Structures & Algorithms and Machine Coding. Despite the overall difficulty not being excessively high, I was ultimately rejected after the third round, which I suspect was due to my limited background in Object-Oriented Programming (OOPS) for the machine coding challenge.
I successfully secured a Software Engineering Intern offer for Winter 2025 at Uber, after navigating through their application process which included an online assessment and three interview rounds focusing on DSA, Low-Level Design, and a Hiring Manager discussion.
I recently underwent an online assessment for an L4 role at Uber, which included four technical questions. My performance was not satisfactory, especially on the final question, and I did not receive any feedback.
I interviewed for a Software Engineer (Data) role at Uber and was asked to design a flight booking system that handles both user and admin functionalities.
I recently interviewed at Uber for an SDE 2 role in Bangalore and successfully received an offer after a comprehensive process that included an OA, a technical phone screen, and four onsite rounds focusing on DSA, LLD, HLD, and behavioral aspects.
I successfully navigated multiple rounds of interviews at Uber for an SE 2 role, culminating in an offer. The process included an Online Assessment, DSA-focused screening and technical rounds, a System Design round, a Hiring Manager discussion, and an additional DSA round.
I interviewed for an SDE Intern role at Uber in India, which involved an online test, a machine coding round, a problem-solving round focused on dynamic programming, and an HR discussion. I successfully received an offer.
I successfully interviewed for an SDE 2 position at Uber in India, receiving an offer after six rounds covering coding, system design, and behavioral aspects. Despite facing challenges with a segment tree problem and complex system design requirements, I managed to clear all rounds.
I recently completed the online assessment for Uber, which featured two distinct coding challenges: a Word Wrap problem with a dash-separated output and a Nearest Exit problem on a 2D board.
I experienced a behavioral interview at Uber in San Francisco, where I was asked to describe a time I had to grow and stretch myself.
I was asked a challenging node-sharing system design question during my Uber interview for a Senior position in San Francisco, involving the implementation of hardware request and release functions.