1415 real Uber interview questions (2026): Uber Onsite Software Engineer Interview Experience and Insights. Verified candidate reports — coding, system design, behavioral.

优步 VO 面经

Uber电面ghost经

黑车三戈面

黑车昂赛挂经

黑车热乎店面 求大米求大米求大米

黑车店面新题

Uber SDE II 面经

Uber六月底 Onsite面经

Uber 2027 SWE Intern OA 面经

Uber New Grad 电面｜排序题做满还主动扩展，BQ 聊嗨（求米&#128591;）

Temporal Phone Screen

Uber 6月 店面

Uber Senior Software Engineer

黑车Onsite面经

黑车sr全套面经

Uber Onsite

Uber Senior Software Engineer Tech Phone Screen

Uber 系统设计面试复盘与总结

Uber SDE 2 面经

uber phone screen

Uber's loop is short by FAANG standards: one OA, one phone screen, one onsite. The recruiter side is the main scheduling pain.

## End-to-end pipeline

1. **Recruiter screen / referral intake** — 15–20 min. Covers level target, location preference, visa status, comp expectations. Some loops skip this and go straight to OA when a referral is in place.
2. **OA** — Hack2Hire HackerRank-style or CodeSignal. 70–90 min. SDE2 / Senior typically 2 problems (90 min); some older SDE2 loops saw 3–4 problems (70 min, CodeSignal). Camera + screen share + mic required; ID check at start. No external IDE.
3. **Phone screen (tech screen)** — 60 min. Usually 1 coding round (1 medium + 1 follow-up or 2 short problems), occasionally an OOD prompt instead. MLE loops fold an ML knowledge check or ML coding into this slot.
4. **Virtual onsite (VO)** — 4 rounds, 60 min each, in one or two consecutive days:
   - 2 × coding (one is often OOD: parking lot, meeting scheduler, expression evaluator)
   - 1 × system design (L5+) or project deep-dive (L4 / NG)
   - 1 × hiring-manager BQ (often combined with a short BQ + previous-project walkthrough); this combined deep-dive + BQ round commonly runs ~75 minutes, noticeably longer than the other rounds
5. **Result & team match** — Most teams are organized as direct hire, not a separate team-match phase. Outcome lands in 1–2 weeks via the assigned recruiter.

## Typical cadence

- Application / referral → recruiter contact: 1–3 weeks.
- Recruiter → OA: 3–7 days.
- OA → phone screen: 1–2 weeks.
- Phone screen → VO: 2–4 weeks.
- VO → outcome: 1–2 weeks (longer if the recruiter is slow — see below).
- End to end: **6–10 weeks**; some pipelines slip to 3+ months when recruiters reschedule.

## Recruiter caveat

A recurring pain point: several Uber recruiters are notorious for sitting on results, double-rescheduling phone screens, or cancelling interviews when the candidate pushes back. Multiple candidates have lost a loop because the recruiter cancelled after two reschedules. If recruiter ghosting persists for more than 10 business days, escalate through a referrer or directly to the assigned coordinator — internal referrers can usually surface the result faster than a portal status check.

## Cooling period

- Failed phone screen → typically 6 months before re-applying to any Uber engineering role.
- Failed VO → 6–12 months depending on the team; recruiters sometimes set this explicitly in the rejection email.
- The cooling rule applies company-wide, not per team. Changing the application email is not a workaround — internal ATS dedupes by phone and identity.

## In-person vs virtual

Almost all loops in 2025–2026 remain fully virtual via Zoom / Google Meet, regardless of level. A few rare onsite VO conversions have been seen for staff-level candidates relocating to SF or NYC.

## 2026 Team-Match Timing Signal

Recent senior loops can still depend on team interest after a positive interview signal. A candidate may clear the loop, wait while the original team chooses another person, and later match to a different group. Treat the post-VO phase as active until the recruiter gives a final answer: keep recruiter communication warm, ask whether other teams can review the packet, and use internal referrers when scheduling stalls.

## 2026 SDE II BPS-style loop variant

A current SDE II sequence uses five named checkpoints after recruiter intake: a BPS-style screening round, DSA coding, runnable low-level design, high-level system design, and a hiring-manager behavioral round. The screening round can begin with high-level object modeling before expanding into executable code. The low-level-design round emphasizes design patterns and concurrency handling, while the high-level-design round explicitly grades architecture trade-offs and non-functional requirements such as storage and latency.

## 2026 phone-screen split variant

One current 60-minute phone screen allocates about 5 minutes to introductions, 20 minutes to coding, 30 minutes to a project deep-dive, and 5 minutes to candidate questions. Prepare the project narrative before the virtual onsite: this format moves architecture choices and ownership probes into the screen itself.

Loop Structure & Timeline

Leveling: L4 / L5a / L5b / Senior / Staff

OA Tooling, AI Rules & New Coding Round

MLE / Applied Scientist Loop Specifics

Intern / NG Flow

Uber's loop leans heavily on Uber Eats and rider/driver marketplace problems — Cart pricing, geo heatmaps, surge, and restaurant recommendation surface in nearly every onsite at L5+. Coding rounds are mostly tagged LeetCode patterns, but Hack2Hire OAs ship a small rotating set of original problems that rarely appear elsewhere. Coding bar is the gate; system design quality drives leveling between L5a / L5b / Senior / Staff.

OA: Jump Game with Prime-3 Steps

Uber interview questions (2026)

Real Interview Questionsfrom Real Candidates

Real Interview Questions
from Real Candidates