# Uber Software Engineer Interview Experience (2025)

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/experiences/uber-software-engineer-interview-301aa2
Source observed: 2026-11-05T00:02:51.624Z
Last checked: 2026-11-05T00:02:51.624+00:00
Indexed: 2026-11-06T17:24:51.286+00:00

---

# Uber Software Engineer Interview Guide

We provide interview preparation resources through Aced (formerly Exponent), including company guides, interview experiences, questions, resumes, courses, practice, and coaching. This page records a candidate-submitted experience for an Uber software engineering interview.

Updated a month ago by Uber candidates.

- [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)

## Interview experience

**Role:** Software Engineer  
**Company:** Uber  
**Level:** Mid Level / L4  
**Location and format:** India, onsite  
**Result:** Rejected  
**Interview date:** a year ago  
**Timespan:** 2 weeks  
**Difficulty:** Very difficult

## Interview process

The candidate described two coding rounds and a system design interview. The coding rounds went smoothly, with familiar data structures, including a binary indexed tree (Fenwick tree) question for range-sum queries. The system design round was more difficult because the interviewer provided little feedback or direction, making it difficult to assess progress. Recruiter communication between rounds was also slow.

- Phone interview

## Interview rounds

The accessible preview identifies one question across one round:

### Phone interview

**Question type:** [Coding](https://www.aced.io/questions?type=coding)  
**Specific question:** [Balanced Tree](https://www.aced.io/questions/3626)

The accessible page also includes these candidate-provided preparation and culture notes:

- Practice out loud with a timer.
- Keep a framework ready for every round.
- Ask the recruiter what each interviewer focuses on so you can tailor your examples.
- Interviewers were described as collaborative and as nudging candidates toward the user.
- The team appeared to value structured thinking over polish, and interviewers left time for questions at the end.

## Access and contribution

The full interview and new experiences added weekly are available through membership. [Become a member](https://www.aced.io/upgrade?src=experience). You can also [share your experience](https://www.aced.io/questions/contribute?src=experience); a 24-hour trial starts once your submission is approved.

## More Uber interview 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 · Apr 2026 · **Verified** · 7 rounds · 6 questions. Candidate advice: spend less time grinding every Uber-tagged LeetCode problem and more time on Uber’s engineering blog and behavioral framing for staff interviews.
- [SDE 2](https://www.aced.io/experiences/uber-software-engineer-interview-db9df6?returnPath=%2Fguides%2Fuber-software-engineer-interview%2Fexperiences) — Uber · Jun 2026 · 3 rounds · 4 questions. Candidate described a process lasting around 5 weeks, high expectations in every round, a requirement for working code in low-level design, and substantial importance assigned to the hiring-manager round.
- [Software Engineer](https://www.aced.io/experiences/uber-software-engineer-interview-dece4d?returnPath=%2Fguides%2Fuber-software-engineer-interview%2Fexperiences) — Uber · May 2026 · 3 rounds. Candidate described a recruiter screen, technical phone interview, and virtual onsite with 4–5 rounds covering coding, system design, and behavioral questions. Scheduling and interviewer communication went well; the system design round felt rushed and feedback was limited.

[See all 8 Uber Software Engineer interview experiences](https://www.aced.io/guides/uber-software-engineer-interview/experiences)

## Related Aced resources

Our preparation catalog includes courses for Product Management, Forward Deployed Engineering, Engineering Management, Software Engineering, System Design, Data Science, Machine Learning, Data Engineering, AI Engineering, Investment Banking, Generative AI, Security Engineering, TPM, Solutions Architecture, UX / Product Design, and BizOps & Strategy. We also offer interview questions, practice, mock interviews and coaching, resume review, salary negotiation, job referrals, and interview guides.

---

[Read this page’s summary](https://www.aced.io/agents/api/public/v1/page-tldr?url=https%3A%2F%2Fwww.aced.io%2Fexperiences%2Fuber-software-engineer-interview-301aa2&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%2Fexperiences%2Fuber-software-engineer-interview-301aa2). Opening a form does not execute a tool.