# Uber Software Engineer Interview Experience — Senior / L5

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-senior-software-engineer-interview-861a3e
Source observed: 2026-11-04T22:43:02.307Z
Last checked: 2026-11-04T22:43:02.307+00:00
Indexed: 2026-11-05T22:56:07.94+00:00

---

# Uber Software Engineer Interview Experience

We are Aced, formerly Exponent. This page is a candidate-submitted interview experience for a **Senior / L5 Software Engineer** interview at **Uber**. It is part of our [Uber Software Engineer Interview Guide](https://www.aced.io/guides/uber-software-engineer-interview), which includes interview experiences, questions, and resumes.

![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)
- [Back to all experiences](https://www.aced.io/guides/uber-software-engineer-interview/experiences)

The guide was updated a month ago by Uber candidates. This experience was submitted five months ago and concerns an **onsite interview in the United States**.

## Interview outcome and timing

| Field | Details |
|---|---|
| Company | Uber |
| Role | Senior / L5 Software Engineer |
| Location | United States |
| Format | Onsite |
| Result | Rejected |
| Interview date | 7 months ago |
| Interview timespan | 4 weeks |
| Difficulty | Difficult |

## Interview process

The candidate described two parts:

1. **45-minute LC-style coding interview**
2. **15-minute conversation about prior projects**

The coding question was to build an arithmetic evaluator using the **Shunting Yard algorithm**. The stated operators were `+`, `-`, `(`, and `)`. The candidate was unsure whether the interview would have included additional operators, potentially with precedence, had the process continued.

The candidate also reported difficulty understanding the interviewer and said they later learned from Chat that a candidate should contact their recruiter immediately if this happens.

The listed process stages were:

- Recruiter screen
- Technical interview

## Interview rounds

There were **3 questions across 2 rounds**.

### Recruiter screen

**1 question — free preview**

Specific question asked: [Tell me about your past projects.](https://www.aced.io/questions/4229)

### Technical interview

**2 questions**

The accessible preview describes a 45-minute session with a senior interviewer. It involved mostly open-ended questions, a short follow-up near the end, and substantial discussion of tradeoffs.

Questions and candidate responses visible in the preview included:

- **How would you improve a product you use every day for a new market?**
  - The candidate chose a segment first, sized it, compared three options, and selected one option together with its success metric.
- **How would you improve a product you use every day for a new market?**
  - The same question and response appear twice in the accessible preview.

### Interview tips

The preview 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 accordingly.

### Company culture

The candidate described the interviewers as collaborative and said they repeatedly directed discussion toward the user. The team appeared to value structured thinking over polish, and interviewers left time for questions at the end.

## Access to additional experiences

The page invites readers to unlock **1.8k+ interview experiences**, including the remainder of this interview and new experiences added weekly. Readers can [Become a member](https://www.aced.io/upgrade?src=experience) or [Share your experience](https://www.aced.io/questions/contribute?src=experience). A **24-hour trial starts once a submitted experience is approved**.

## More Uber interview experiences

These additional Uber entries are separate candidate experiences:

1. **Staff Software Engineer (L5B), Ads — Uber · Apr 2026**
   - **Verified**; **7 rounds**; **6 questions**
   - “If I were doing it again, I would spend less time trying to grind every Uber-tagged LeetCode problem and more time on two things: their engineering blog and getting my behavioral framing right for staff.”
   - [Read the full interview](https://www.aced.io/experiences/uber-staff-software-engineer-interview-6b1b44?returnPath=%2Fguides%2Fuber-software-engineer-interview%2Fexperiences)

2. **SDE 2 — Uber · Jun 2026**
   - **3 rounds**; **4 questions**
   - “interview process is very lengthy took around 5 weeks, and expectations is very high in each round, for LLD working code is required, also dont mess your HM round since i felt like it contained more weightage ”
   - [Read the full interview](https://www.aced.io/experiences/uber-software-engineer-interview-db9df6?returnPath=%2Fguides%2Fuber-software-engineer-interview%2Fexperiences)

3. **Software Engineer — Uber · May 2026**
   - **3 rounds**
   - “The process was well-structured — it started with a recruiter screen, followed by a technical phone interview, and then a virtual onsite with 4–5 rounds covering coding, system design, and behavioral questions. What went well was that the interviewers were communicative and the scheduling was smooth. What didn't go well was that the system design round felt rushed — there wasn't much time to go deep into trade-offs before moving to the next topic. Feedback after each round was limited, which made it hard to gauge where I stood.”
   - [Read the full interview](https://www.aced.io/experiences/uber-software-engineer-interview-dece4d?returnPath=%2Fguides%2Fuber-software-engineer-interview%2Fexperiences)

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

---

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