Uber Software Engineer Phone Screen Questions
169+ questions from real Uber Software Engineer Phone Screen rounds, reported by candidates who interviewed there.
What does the Uber Phone Screen round test?
The Uber phone screen typically lasts 45-60 minutes and evaluates core Software Engineer fundamentals. Candidates should expect 1-2 algorithmic problems, basic system design discussion at senior levels, and questions about relevant experience. The goal is to confirm technical competence before bringing candidates onsite.
Top Topics in This Round
Uber Software Engineer Phone Screen Questions
Uber Phone Screen
Phone Screen One question https://leetcode.com/problems/bus-routes/
Uber Phone Screen
You\'re given a set of symbols for the elements in the periodic table [.... Li, Be, B, C, N, F, Ne, Na, Co, Ni, Cu, Ga, Al, Si.....] Write the function...
Uber Phone Interview
Problem Statement You\'re given a stream of user IDs visiting a website. Implement two functions: 1. void PostAddUser(int userId): Adds a new user ID to the stream. 2. int GetFirstOneTimeUser():...
Uber - Coding round 1 - for SDE II
"You are given an array A of N positive integer values. A subarray of this array is called Odd-Even subarray if the number of odd integers in this subarray is...
Uber SDE 2 Phone Interview: Union Find Graph Optimization Challenge
I shared the brute-force approach in the first 5 minutes, then spent the next 40 minutes grinding for the optimal solution he kept hinting it can be better. When I couldn't quite nail the optimization
Uber SSE L5A Technical Phone Interview One-Time Visitor Problem
**Problem** You are given a stream of customer visits. Each customer is identified by an integer customerId. A customer is called a one-time visitor if they have visited exactly once. **Implement the
Uber SDE 2 Front End L4 Interview Experience Round 1
**Round 1** The first round involved a medium-level DSA problem. The interviewer was friendly and made the discussion comfortable. Problem Statement: You are given an integer n representing the number
Uber Fulltime SDE Tech Phone Screen Experience with Confusing HR Process
The interviewer was very nice, and the experience was great, but the HR's actions were baffling. The following content requires a score of 140 or higher. You can already view it. Given a website's use
Uber Fulltime SDE Tech Phone Screen Interview on Number of Islands Problem
The store opened an Uber two days ago. The question is Number of islands, the title is as follows. # Build a 2-dimensional representation of terrain that can represent some land and water parts. # Par
Uber Technical Phone Screen: Meeting Room Scheduling Problem
I had a meeting room question. The input consists only of a series of room IDs. The starting available time for each room is [-inf, inf]. Then, I called `scheduleMeeting(start, end)`. The overall appr
Uber Senior Software Engineer (SSE) Backend Technical Phone Interview Experience
**Interview 1: SSE (L5-A) Backend** **Problem Statement:** Solve the "Water and Jug Problem" (determine if specific water amounts can be measured using two jugs of different capacities). **Context and
Uber SDE 3 Phone Screen Interview Experience: Meeting Room Scheduler
**Problem Statement** Design an API to manage meeting schedules for a predefined set of conference rooms. The system requires a method `scheduleMeeting(startTime, endTime)` that performs the following
Uber DSA round
1-> n cities are given and a threshold is given and there is a bi-directional road between x and y if x%z==0 y%z==0 z>threshold Make connections and later they will provide different source and...
Uber | Senior Software Engineer (SSE) Interview experience
Giving back to leetcode community who helped me with my next job! Round 1 (DSA): Trie based question - Find all words with certain prefix. It had some catch over and...
1) First I had a 90 minutes coding round with three questions:They had modified a few questions from SPOJ. I found these later on.https://www.spoj.com/problems/BALLOT/http...
SingleStore || Software Engineer || Remote
YOE: 3 years Title: Software Engineer (Golang and Kubernetes) Compensation Offered: 30 LPA + stocks Location: Remote A friend referred me to this organisation. Got a screening call from HR to discuss about my...
Uber | SSE | Phone
Recently had a phone interview with Uber. I was able to do the first question but wasn\'t able to do the follow up. Help me solve it please. Question 1 :...
Phone screen Uber
Problem Statement You have: n sticks, each initially colored. m painters, each performing an operation to paint a specified range of sticks with a new color. Each operation is defined by three integers: l: The...
Uber SDE2 Interview Onsite
There were total of 4 rounds which include 2 coding rounds, 1 Low Level and 1 Hiring Manager. Round 1: Screening Round 1 Coding problem. maximum-sum-iarri-among-rotations-given-array (Geeks for Geeks) Really bombed this round. But...
UBER L5
YOE: 6.5 Sharing question below Uber round 1: there is a tree with each node having value. A starts from root and B starts from node B. calcuate the maximum point A can collect...
What to Expect in the Uber Phone Screen Round
The Uber Software Engineer Phone Screen round has a specific calibration purpose distinct from other rounds in the loop. Across 169+ 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 Phone Screen round at Uber show recurring patterns in difficulty and topic distribution. The Phone Screen 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.
Phone Screen Round Timing and Format
The Phone Screen 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 Phone Screen 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 169 Questions from This Round
Full question text, answer context, and frequency data for subscribers.
Get Access