# Uber Software Engineer 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-dece4d
Source observed: 2026-11-05T00:02:56.829Z
Last checked: 2026-11-05T00:02:56.829+00:00
Indexed: 2026-11-05T21:41:37.244+00:00

---

# Uber Software Engineer Interview Experience

We provide interview-preparation content through Aced, formerly Exponent. This page records one candidate’s Uber software-engineering interview experience and links to the broader [Uber Software Engineer Interview Guide](https://www.aced.io/guides/uber-software-engineer-interview).

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

## Guide navigation

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

Updated a month ago by Uber candidates.

## Experience overview

- **Company:** Uber
- **Role level:** Mid Level / L4
- **Location:** Netherlands
- **Format:** Onsite
- **Result:** Rejected
- **Interview date:** 6 months ago
- **Submission:** 6 months ago
- **Timespan:** 2 weeks
- **Difficulty:** Difficult

## Interview process

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 interviewers were communicative and scheduling was smooth. The system-design round felt rushed, leaving little time to explore trade-offs. Feedback after each round was limited.

The listed process stages were:

- Online assessment
- Phone interview
- Technical interview

## Interview rounds

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

### Online assessment

- **Questions:** 1
- **Access:** Free preview
- **Question types:** [Technical](https://www.aced.io/questions?type=technical), [Coding](https://www.aced.io/questions?type=coding)
- **Specific question:** DSA Medium - hard problem

### Phone interview

One question was listed. The accessible preview describes a 45-minute conversation with a senior interviewer, mostly open-ended questions, a short follow-up near the end and substantial pushback on trade-offs.

The question shown in the preview was:

> How would you improve a product you use every day for a new market?

The candidate’s approach was to choose a segment first, size it, compare three options, then select one option and its success metric.

### Technical interview

One question was listed. The accessible preview describes a 45-minute conversation with a senior interviewer, mostly open-ended questions, a short follow-up near the end and substantial pushback on trade-offs.

The question shown in the preview was:

> How would you improve a product you use every day for a new market?

The candidate’s approach was to choose a segment first, size it, compare three options, then select one option and its success metric.

## Interview tips and culture notes

- Practice answers aloud with a timer.
- Keep a framework ready for every round.
- Ask the recruiter what each interviewer focuses on and tailor examples accordingly.
- The candidate described interviewers as collaborative and focused on the user.
- Structured thinking appeared more important than polish, and interviewers left time for questions.

## Membership and contribution

We offer access to the rest of this interview and new experiences added weekly through [Become a member](https://www.aced.io/upgrade?src=experience). Candidates 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. “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.”
- [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. “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 ”
- [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, 2 questions. “The interview consists of two parts: a 45 min LC style coding and 15 mins conversation on your prior projects. The 45 min question was to build an arithmetic evaluator. For that, you have to use the Shunting Yard algorithm. It was only "+", "-", "(" and ")". I'm not sure if we would have used more operators, maybe some with precedence, if I had gone further. I had a hard time understanding the interviewer. I learned later on from Chat that you should contact your recruiter immediately if this happens.”

[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-software-engineer-interview-dece4d&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-dece4d). Opening a form does not execute a tool.