Uber Software Engineer Onsite Coding Questions
281+ questions from real Uber Software Engineer Onsite Coding rounds, reported by candidates who interviewed there.
What does the Uber Onsite Coding round test?
The Uber onsite coding round is the core technical evaluation. Software Engineer candidates typically see 2-3 algorithm and data structure problems. Problems range from medium to hard difficulty, and interviewers evaluate both correctness and code quality.
Top Topics in This Round
Uber Software Engineer Onsite Coding Questions
Uber Onsite
Given a list[[s,e],[s1,e2],[s2,e2]]. Return the frequency of intervals [[0,3],[1,4],[2,7]] [0,1]->1 [1-2]-> 2 [2-3]-> 3 [3-4]-> 2 [4-7]->1
Uber Onsite Interview Question [DSA Round]
How to solve this? Got this in Uber BPS coding interview. Do you know of any leetcode question similar to this? you are given a list of intervals [1, 3], [4,...
UBER || 2022 || Onsite(India)
Given n drivers on a road with position of ith driver defined as Xi and maximum speed of vehicle Si. Find the minimum time taken for the cars to arrive...
Number of Islands
## Problem Given an `m x n` 2D grid `grid` consisting of characters `'1'` (land) and `'0'` (water), return the number of **islands**. An island is surrounded by water and is formed by connecting adja
Uber Onsite Interview Experience: SDE Fulltime Currency Exchange Problem
The interview was conducted by a Middle Eastern guy who speaks very slowly. We first talked about my resume, and then I was lucky enough to get a frequently asked question that had been mentioned in t
Uber Backend SDE2 Onsite Interview Experience and Insights
I've been job hunting for a while now, targeting mid-level positions, but haven't received my ideal offer yet. I'm posting this to share my interview experiences and ask for some points 🙏. My backgrou
Uber Fulltime Onsite Software Engineer Interview Experience
Coding 1: Sanlingwu Coding 2: Design a Global Rate Limiter, allowing each client to make a maximum of n requests per second with 0-latency. (Failed on this coding task; the interviewer required demons
Uber L5A Frontend Engineer Onsite Interview Experience (7.5 YOE)
**Candidate Profile** Frontend Engineer with 7.5 years of experience, currently working in Big Tech. **Round 1: Business Phone Screen (1 Hour)** * **Problem:** Implement a JavaScript memoization utili
Uber L4 Software Engineer Onsite Interview Experience and Offer Details
**Candidate Profile** * **Experience:** 2.5 Years **Online Assessment (CodeSignal)** * **Performance:** Solved problems 1, 2, and 4. Did not solve problem 3. * **Result:** Passed. **Phone Screen** * *
Uber L4 Frontend Engineer Interview Experience: Detailed Process
**Candidate Profile** * **Role:** Front End Engineer * **Experience:** 4.5 Years **Screening Round: Voting Poll Component** Design and implement a voting poll UI using a front-end framework (React, Vu
Uber Fulltime Onsite Interview Experience for SDE Position
Phone: LeetCode, bulk wine, the question asks for the optimal path value when a graph has multiple paths. VO: Round 1: SD, WhatsApp, the special requirement is to mark one checkmark if a message is se
Uber | Onsite-DSA | Customer creation and query
Implement the following functions: 1.addCustomer(double revenue) \u2192 Adds a new customer with a unique ID and assigns the specified revenue, representing the amount the customer brings to the company. 2. addCustomer(double revenue,...
Uber USA Onsite Technical Problems
Had onsite for Software Engineer II on a team within Marketplace organization. Technical questions were very fair (id say medium difficulty) and used common DSA (not any esoteric stuff). #...
Uber | Onsite | XOR of leaf nodes
Given a tree with root node id starting with 1. Each node has a value associated with it. We are given function f where f(n) = xor of values of...
Uber | Onsite | Implement a Rate limiter
Recently this question was asked in Uber Onsite. Can someone please help solving this question? Every request comes in with a customerID, implement this method boolean rateLimit(int customerId). Allow X requests in...
UBER SENIOR SOFTWARE ENGINEER
Interview question: - https://leetcode.com/problems/bus-routes/description/ modified version of above question problem statement:- need to find minimum bus change to reach to the destination from source. and every bus run in the infinite loop Ex:- [[1,5,7],[3,6,7],[9,8,7]] source =...
Uber | Onsite | metric collector
Design a metric collector, which has procide two function: add(string metricName) -> add 1 to the metric getMetricCount(string metricName) -> get the count of the metric within 100s e.g. Time 1 add(Test) 99 add(Test) 100 getMetricCount(Test)...
Uber | Onsite | 2021
Find the lowest, highest, median price of a stock, you will be altered when the price of a stock is updated.. so the stock will be comming like a stream...Finding...
Uber on-site question - Rejected!
There is a grid. O represents a Robot, X represents obstacle, E represents empty space where you can move. Borders are also considered as an obstacle. [O E E E...
Given a 2D plane, list of lines parallel to X-axis or Y-axis and list of rectangles (perimeter lines are parallel to either X-axis or Y-axis). Find the number of intersection...
What to Expect in the Uber Onsite Coding Round
The Uber Software Engineer Onsite Coding round has a specific calibration purpose distinct from other rounds in the loop. Across 281+ verified reports on LeakCode for this exact round type, the consistent expectations: clear scoping of the problem before diving into a solution, explicit reasoning about complexity, structured handling of edge cases, and the ability to discuss trade-offs between two reasonable approaches.
Reports tagged with the Onsite Coding round at Uber show recurring patterns in difficulty and topic distribution. The Onsite Coding round is typically 45-60 minutes; the interviewer is calibrated against a specific rubric. The discriminator between candidates who advance and candidates who do not is rarely the final correctness of the answer. It is the path: did you clarify, did you verbalize your approach, did you handle edge cases, and did you communicate throughout.
How To Prepare for This Specific Round
Filter the questions below to the most recent reports (past 6-12 months). Questions tagged for this exact round type from this exact company at this exact role level are the highest-signal data available. Older reports may reference questions that have since rotated out of the company's pool.
Practice 4-6 representative problems from this set under timed conditions. The goal is not memorization (companies rotate questions); the goal is to internalize the patterns the interviewer typically reaches for and the depth of follow-up to expect. Reports on LeakCode also tag the typical follow-up depth at this round type, which is the discriminating signal between hire and no-hire calibration.
Onsite Coding Round Timing and Format
The Onsite Coding round at Uber typically runs 45-60 minutes. Use the first 2-3 minutes to clarify requirements; you should never start coding or designing without verifying the input/output format, constraints, and edge cases out loud. Use the next 5-7 minutes to verbalize your approach before writing any code. The middle 20-30 minutes are implementation. Reserve the final 10 minutes for testing with concrete examples and discussing optimization or trade-offs.
Time budget discipline is one of the most reliable senior-vs-junior discriminators in this round. Strong candidates verbalize where they are in their budget out loud ("I've used about 20 minutes, I have 15 minutes left for testing and one optimization"). This signals engineering maturity to the interviewer and creates positive feedback they can capture in writing.
Common Failure Modes in This Round
Reports tagged "no hire" at Uber Software Engineer Onsite Coding commonly cite: coding silently without verbalizing approach, jumping to implementation before clarifying requirements, missing edge cases (empty input, single element, very large input), producing working code that the candidate cannot refactor when asked, and failing to test their solution with concrete examples before declaring done.
The single most predictive failure mode in 2025-2026 reports: not asking clarifying questions. Interviewers at all FAANG companies are explicitly trained to weight this dimension. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's notes.
See All 281 Questions from This Round
Full question text, answer context, and frequency data for subscribers.
Get Access