# Uber Staff / L6 Software Engineer (L5B), Ads 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-staff-software-engineer-interview-6b1b44
Source observed: 2026-11-04T23:45:57.598Z
Last checked: 2026-11-04T23:45:57.598+00:00
Indexed: 2026-11-05T18:48:44.157+00:00

---

# Staff Software Engineer (L5B), Ads Interview Experience

We publish interview experiences to help candidates prepare for technology roles. This experience concerns a **Staff / L6 Software Engineer (L5B), Ads** interview at **Uber** and appears within our [Uber Software Engineer Interview Guide](https://www.aced.io/guides/uber-software-engineer-interview).

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

The guide was **updated a month ago by Uber candidates** and includes:

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

- **Verified:** Yes
- **Location:** United States
- **Submitted:** 6 months ago
- **Result:** In Progress
- **Interview date:** 7 months ago
- **Difficulty:** Difficult

> 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.

## Interview process

The candidate entered through a referral, completed a lightweight recruiter call, then an initial coding screen, followed by a five-round final stage. The final stage consisted of two coding rounds, one system-design round, one past-project round that became a behavioral deep dive, and one dedicated behavioral round. The candidate emphasized Uber’s focus on technical depth over polished cross-functional storytelling for a staff role. The coding rounds also required system-design-style tradeoff thinking, and the final coding round included a **Number of Islands variant**.

The process categories were:

1. Recruiter screen
2. Technical interview
3. Final round

## Interview rounds

There were **9 questions across 7 rounds**.

### Recruiter screen

The candidate described this as a very lightweight screen, sufficient to enter the process, and especially fast because the candidate came through a referral.

### Technical interview

The remaining interview content is available to members.

### Final rounds

The final stage had five rounds: two coding rounds, one system-design round, one past-project round that developed into a behavioral deep dive, and one straight behavioral round.

### Accessing more interview experiences

Members can read the rest 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**.

You can [Practice this loop](https://www.aced.io/questions/926/tell-me-about-the-most-complex-project-you-ve-worked-on-?interview=uber-staff-software-engineer-interview-6b1b44).

## More Uber interview experiences

- [SDE 2 — Uber, Jun 2026](https://www.aced.io/experiences/uber-software-engineer-interview-db9df6?returnPath=%2Fguides%2Fuber-software-engineer-interview%2Fexperiences): **3 rounds, 4 questions.** The candidate described a process lasting around five weeks, high expectations, a requirement for working code in LLD, and a hiring-manager round they considered especially important.
- [Software Engineer — Uber, May 2026](https://www.aced.io/experiences/uber-software-engineer-interview-dece4d?returnPath=%2Fguides%2Fuber-software-engineer-interview%2Fexperiences): **3 rounds.** The process included a recruiter screen, technical phone interview, and virtual onsite with 4–5 coding, system-design, and behavioral rounds. The candidate found scheduling communicative and smooth but said the system-design round felt rushed and feedback was limited.
- [Software Engineer — Uber, Apr 2026](https://www.aced.io/experiences/uber-senior-software-engineer-interview-861a3e?returnPath=%2Fguides%2Fuber-software-engineer-interview%2Fexperiences): **2 rounds, 2 questions.** The interview included 45 minutes of LeetCode-style coding and 15 minutes on prior projects. The coding prompt was to build an arithmetic evaluator using the Shunting Yard algorithm with `+`, `-`, `(`, and `)`.

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