# Uber Software Engineer Interview Experiences

Aced (formerly Exponent) publishes a public search API over its indexed pages; the guide is at https://www.aced.io/agents/agent-access.

Source: https://www.aced.io/guides/uber-software-engineer-interview/experiences
Source observed: 2026-11-04T21:42:49.945Z
Last checked: 2026-11-04T21:42:49.945+00:00
Indexed: 2026-11-05T21:54:57.008+00:00

---

# Uber Software Engineer Interview Experiences

Updated a month ago by Uber candidates. We provide candidate-reported experiences for the Uber software-engineering interview process through Aced, formerly Exponent.

![Uber logo](https://exponent-static.s3.amazonaws.com/company_logos/uber.png)

## Guide sections

- [Expert guide](https://www.aced.io/guides/uber-software-engineer-interview)
- [Interview experiences — 8](https://www.aced.io/guides/uber-software-engineer-interview/experiences)
- [Questions — 39](https://www.aced.io/guides/uber-software-engineer-interview/questions)
- [Resumes — 71](https://www.aced.io/guides/uber-software-engineer-interview/resumes)

These are real experiences from candidates who went through this interview process. [Share your experience](https://www.aced.io/questions/contribute?src=guide).

## Interview overview

- **Difficulty:** Most candidates rate the Uber interview as **difficult**.
- **Reported outcomes:** **17%** of reported interviews at Uber result in an offer; the displayed breakdown is **No offer 5** and **Accepted 1**.
- **Question emphasis:** Uber focuses most on **Coding** and **System Design**. The displayed categories and counts are **Coding 4**, **System Design 3**, **Data Structures & Algorithms 3**, and **Other 5**.

## Candidate experiences

### [Staff Software Engineer (L5B), Ads](https://www.aced.io/experiences/uber-staff-software-engineer-interview-6b1b44?returnPath=%2Fguides%2Fuber-software-engineer-interview%2Fexperiences)

**Uber · Staff / L6 · United States**  
Submitted May 12, 2026 · Verified April 2026 · In Progress · Difficult

The candidate entered through a referral, followed by a lightweight recruiter call, an initial coding screen, and a five-round final. The final consisted of two coding rounds, one system-design round, one past-project round that became a behavioral deep dive, and one behavioral round. The candidate emphasized Uber’s focus on technical depth over polished cross-functional storytelling for a staff role. Coding rounds also involved system-design-style trade-off thinking, including a Number of Islands variant in the final coding round.

**Questions shown:**

- [Tell me about a time you had a conflict with someone. How did you resolve it and what did you learn?](https://www.aced.io/questions/140)
- [Tell me about the most complex project you've worked on.](https://www.aced.io/questions/926)
- [Describe a time when your project failed.](https://www.aced.io/questions/932)
- [+11 more questions](https://www.aced.io/experiences/uber-staff-software-engineer-interview-6b1b44?returnPath=%2Fguides%2Fuber-software-engineer-interview%2Fexperiences)

[Read full experience](https://www.aced.io/experiences/uber-staff-software-engineer-interview-6b1b44?returnPath=%2Fguides%2Fuber-software-engineer-interview%2Fexperiences)

### SDE 2

The process reportedly took around five weeks, with high expectations in each round. Working code was required for low-level design, and the candidate advised not neglecting the hiring-manager round because it felt more heavily weighted.

Questions included:

- Diameter of a binary tree
- Shortest distance between two points
- Designing a stock ticker system

### Software Engineer

The process began with a recruiter screen, followed by a technical phone interview and a virtual onsite with 4–5 rounds covering coding, system design, and behavioral questions. The candidate described communication and scheduling as smooth, but found the system-design round rushed and feedback after rounds limited.

Questions included:

- A medium-to-hard DSA problem
- Low-level design for getting nearby open restaurants
- Low-level design for first-time visitors

### Software Engineer

The interview had a 45-minute LeetCode-style coding segment and a 15-minute conversation about prior projects. The coding problem was to build an arithmetic evaluator using the Shunting Yard algorithm, with `+`, `-`, `(`, and `)`. The candidate reported difficulty understanding the interviewer and later learned through Chat that contacting the recruiter immediately would be appropriate in that situation.

Questions included:

- [Tell me about the most complex project you have led.](https://www.aced.io/questions/926)
- [Tell me about your past projects.](https://www.aced.io/questions/932)
- Arithmetic evaluator

### Software Engineer

The online technical assessment was described as difficult: two medium-to-hard questions in 90 minutes, with hidden CodeSignal test cases presenting a challenge.

Questions included:

- Minimum edge reversals so every node is reachable
- Minimum jumps to reach the end via prime teleportation

### Software Engineer

The reported sequence was:

1. Recruiter screening — 30 minutes
2. Online assessment — 1 hour, with 2 coding questions
3. Technical screening — 1 hour, with 1 coding question
4. Loop interview — 2 DSA rounds, 1 system-design round, and 1 behavioral round

The candidate said that focusing on recent Uber questions in LeetCode could have helped more in the DSA rounds.

Questions included:

- [Find the closest palindrome of a given number.](https://www.aced.io/questions/140)
- [Given a sorted array of integers, which may include negatives, return the squares in sorted order; as a follow-up, find the k-th smallest squared value.](https://www.aced.io/questions/926)
- [Given an array of integers and a number N, find the longest contiguous subarray whose elements differ by less than N.](https://www.aced.io/questions/932)
- [Design Robinhood.](https://www.aced.io/questions/932)

### Software Engineer

The process involved two coding rounds and a system-design interview. The candidate felt comfortable with the data structures, including a binary indexed tree (Fenwick tree) question for range-sum queries. The system-design round was difficult to assess because the interviewer provided little feedback or direction, and recruiter communication between rounds was slow.

Question shown:

- [Balanced Tree](https://www.aced.io/questions/140)

### Software Engineer

This candidate interviewed for the UberSTAR sophomore internship, described as easier than the regular software-engineering internship. The candidate secured the offer and a return offer to be a regular software-engineering intern the following summer.

Questions and topics included:

- [Custom Sort String](https://www.aced.io/questions/140)
- LeetCode medium
- Standard behavioral questions

## Access to all experiences

We provide trial access when you share your own experience; membership unlocks all interview experiences.

- [Share your experience](https://www.aced.io/questions/contribute?src=guide-experiences)
- [Become a member](https://www.aced.io/upgrade?src=guide-experiences)

---

[Read this page’s summary](https://www.aced.io/agents/api/public/v1/page-tldr?url=https%3A%2F%2Fwww.aced.io%2Fguides%2Fuber-software-engineer-interview%2Fexperiences&trace=t_679ff9ab98f3)

## Ask a follow-up about this page

Need a more specific answer? Ask the exact question you have. It returns a fresh, cited answer from Aced (formerly Exponent)’s knowledge base. No account or API key required.

Open this URL with your own question, URL-encoded. Include your question in q. All research inputs are optional; no account or setup.

`GET https://www.aced.io/agents/agent/faq?q={question}&trace=t_679ff9ab98f3`

[Tool guide and examples](https://www.aced.io/agents/agent-access) · [OpenAPI](https://www.aced.io/agents/api/public/v1/openapi.json) · [Page TLDR form](https://www.aced.io/agents/agent-tools/page-tldr?url=https%3A%2F%2Fwww.aced.io%2Fguides%2Fuber-software-engineer-interview%2Fexperiences). Opening a form does not execute a tool.