# Uber SDE 2 Interview Experience

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-db9df6
Source observed: 2026-11-05T00:43:06.934Z
Last checked: 2026-11-05T00:43:06.934+00:00
Indexed: 2026-11-06T15:56:54.719+00:00

---

# Uber SDE 2 Interview Experience

We publish interview experiences and preparation resources through Aced, formerly Exponent. This entry concerns an Uber **Mid Level / L4** software-engineering interview submitted by a candidate in **India**, with a **hybrid** work setting.

## Interview overview

- **Result:** Rejected
- **Interview date:** 4 months ago
- **Timespan:** 5 weeks
- **Difficulty:** Very difficult
- **Submitted:** 3 months ago
- **Location and arrangement:** India, hybrid

The candidate described a lengthy process lasting about five weeks, with high expectations in every round. They noted that working code was required for low-level design (LLD) and felt the hiring-manager round carried substantial weight.

## Interview process

The listed stages were:

1. Online assessment
2. Phone interview
3. Technical interview

The experience contains **5 questions across 3 rounds**.

### Online assessment

- **Questions:** 1
- **Specific question:** Tree or graph question
- **Access:** A free preview is available; the remaining experience is member-gated.

### Phone interview

- **Questions:** 1
- The rendered page describes a 45-minute conversation with a senior interviewer, mostly open-ended questions, a short follow-up near the end, and substantial discussion of tradeoffs.
- Example question: “How would you improve a product you use every day for a new market?”
- The example response says the candidate first selected and sized a segment, compared three options, and chose one with a success metric.

### Technical interview

The rendered page describes another 45-minute conversation with a senior interviewer, including open-ended questions, a short follow-up, and pushback on tradeoffs. The same example product-improvement question and response are shown repeatedly in the rendered content.

## Interview tips and company culture

The page recommends practicing aloud with a timer, keeping a framework ready for every round, and asking the recruiter what each interviewer focuses on so examples can be tailored.

The candidate describes interviewers as collaborative and focused on the user. In the candidate’s impression, the team valued structured thinking over polish and left time for questions.

## Access and contribution

The rest of this interview and new experiences added weekly require membership. A 24-hour trial starts once a submitted experience is approved. [Become a member](https://www.aced.io/upgrade?src=experience) or [share your experience](https://www.aced.io/questions/contribute?src=experience).

## Uber interview guide

Our related Uber guide includes:

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

## 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 and 6 questions. The candidate recommends spending less time grinding every Uber-tagged LeetCode problem and more time on Uber’s engineering blog and behavioral framing for staff-level interviews.
- [Software Engineer](https://www.aced.io/experiences/uber-software-engineer-interview-dece4d?returnPath=%2Fguides%2Fuber-software-engineer-interview%2Fexperiences) — Uber, May 2026; 3 rounds. The candidate describes a recruiter screen, technical phone interview, and virtual onsite covering coding, system design, and behavioral questions, while finding the system-design round rushed and feedback limited.
- [Software Engineer](https://www.aced.io/experiences/uber-senior-software-engineer-interview-861a3e?returnPath=%2Fguides%2Fuber-software-engineer-interview%2Fexperiences) — Uber, Apr 2026; 2 rounds and 2 questions. The candidate describes a 45-minute LeetCode-style coding interview plus 15 minutes on prior projects, involving an arithmetic evaluator using the Shunting Yard algorithm with `+`, `-`, `(`, and `)`.

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

---

[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-db9df6&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-db9df6). Opening a form does not execute a tool.