# 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-42bcae
Source observed: 2026-11-05T00:02:54.263Z
Last checked: 2026-11-05T00:02:54.263+00:00
Indexed: 2026-11-06T18:36:41.315+00:00

---

# Uber Software Engineer Interview Experience

We provide interview preparation through Aced, formerly Exponent. This entry records an Uber candidate’s Senior / L5 software-engineering interview experience in the United States for a hybrid role.

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

**Updated:** a month ago by Uber candidates  
**Result:** Rejected  
**Interview date:** 8 months ago  
**Timespan:** 2 weeks  
**Difficulty:** Difficult  
**Location and arrangement:** United States, Hybrid

## Interview guide and related 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)

## Interview process

The online technical assessment was described as difficult: **2 Medium-to-Hard questions in 90 minutes**. Hidden test cases in CodeSignal were identified as a challenge.

- Online assessment

## Interview rounds

There were **2 questions across 1 round**.

### Online assessment

**Question count:** 2  
**Question types:** [Coding](https://www.aced.io/questions?type=coding), [Technical](https://www.aced.io/questions?type=technical)

**Specific questions asked:**

1. Minimum edge reversals so every node is reachable
2. Minimum jumps to reach end via prime teleportation

## Interview tips

Practice out loud with a timer, keep a framework ready for every round, and ask the recruiter what each interviewer focuses on so you can tailor examples.

## Company culture

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

## Membership and contribution

Aced offers access to **1.8k+ interview experiences**, including the remainder of this interview and new experiences added weekly, through [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 — Uber · Apr 2026](https://www.aced.io/experiences/uber-staff-software-engineer-interview-6b1b44?returnPath=%2Fguides%2Fuber-software-engineer-interview%2Fexperiences) — “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.” **Verified; 7 rounds, 6 questions.**
- [SDE 2 — Uber · Jun 2026](https://www.aced.io/experiences/uber-software-engineer-interview-db9df6?returnPath=%2Fguides%2Fuber-software-engineer-interview%2Fexperiences) — “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 ” **3 rounds, 4 questions.**
- [Software Engineer — Uber · May 2026](https://www.aced.io/experiences/uber-software-engineer-interview-dece4d?returnPath=%2Fguides%2Fuber-software-engineer-interview%2Fexperiences) — “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.” **3 rounds.**

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

## Other Aced preparation resources

We offer preparation 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 provide interview questions, practice, coaching, resume review, salary negotiation, job referrals, resources, and interview courses.

---

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