AniUI Academy
UB

Frontend interview guide

Uber

Rides, Eats, Freight, driver apps, maps, dashboards. A frontend culture built around real-time data and operational dashboards.

Frontend engineers interviewing at Uber — React/TypeScript on web, with teams spread across rider, driver, courier, merchant, and internal operations.

Last reviewed 2026-10-04

What they emphasise

  • Real-time data — maps, trip progress, dispatch dashboards, pricing.
  • Map-centric UI — Uber's web surfaces lean heavily on map interaction.
  • Dense operational dashboards — internal ops teams run on them.
  • DSA fundamentals — Uber's loop is historically algorithmic even for FE roles.

The loop, round by round

6 rounds. Durations and formats are typical, not guaranteed — confirm the loop shape with your recruiter in the screen.

  1. Round 1

    Recruiter screen

    ~30 minCall

    What it covers

    • Resume, level, team orientation.

    What they're looking for

    • A specific "why Uber, why this team" answer.

  2. Round 2

    Technical phone screen

    45–60 minLive coding

    What it covers

    • An algorithmic problem + often a short JS/UI follow-up.

    What they're looking for

    • Correctness and complexity named explicitly.

  3. Round 3

    Onsite: coding (two rounds)

    60 min eachLive coding across two interviewers

    What it covers

    • One algorithmic round — commonly graphs, sliding window, or data-structure design.
    • One UI build — in Uber's domain (map markers, real-time trip card, pricing panel).

    What they're looking for

    • Clean complexity reasoning on the DSA side; polished, accessible UI on the build side.

  4. Round 4

    Onsite: system design

    60 minWhiteboard / shared doc

    What it covers

    • A frontend-shape prompt in Uber's domain — a live trip dashboard, a real-time map with hundreds of markers, a dispatch operations surface.

    What they're looking for

    • Real-time primitives treated correctly — WebSockets, reconnection logic, backpressure.
    • Map performance treated as a real concern.

  5. Round 5

    Onsite: behavioural / 'Uber values'

    45 minConversation

    What it covers

    • Behavioural stories mapped to Uber's values (post-2017 reset).

    What they're looking for

    • Specific, STAR-formatted stories.

  6. Round 6

    Hiring manager

    30–45 minConversation

    What it covers

    • Team shape and scope. Your questions.

    What they're looking for

    • Thoughtful specific questions about the team's current challenges.

What each level expects

The bar you're being measured against — plus the failure modes candidates most often trip on at that level.

SDE 2 / mid

~2–4 years

Ships features end to end with mentorship.

What they expect

  • DSA fundamentals and complexity analysis.
  • Can produce a working React/TS build in the time allowed.

Common failure modes

  • No complexity named — Uber's bar probes it directly.

Senior

~5–8 years

Owns a technical area, mentors.

What they expect

  • A system-design round where real-time primitives are first-class, not an afterthought.

Common failure modes

  • A system design that treats a real-time map the same as a static page.

Staff

~8+ years

Multi-team technical direction.

What they expect

  • Peer-level discussion.
  • Multi-team leverage.

Common failure modes

  • Senior+ output rather than Staff leverage.

How to crack it

Day-of advice. The specific moves that separate offers from no-offers when the content is already in your head.

  1. 1Prep one map-centric UI build — markers, cluster rendering, hover interactions, a trip-progress overlay.
  2. 2In the system-design round, lead with real-time primitives (WebSocket, reconnection, backpressure) rather than hand-waving them.
  3. 3Keep DSA fundamentals sharp — Uber's bar is explicit.
  4. 4Pre-write behavioural stories mapped to Uber's current values.

How to master it (over months, not days)

The longer-horizon work. These are the habits that pay off at Senior+ bars where cramming visibly fails.

  • Build a real-time dashboard end to end with WebSockets. The experience teaches more than reading does.
  • Learn Mapbox or Google Maps JS at a working level.
  • Study Uber's engineering blog — their H3 posts are a signal of the real work.
  • Make a habit of specific numbers in commits and PRs.

Resources

On-site content for the technical prep, plus short-list of external links worth your time.

A note on sources. This guide synthesises public engineering blogs, published job descriptions, widely cited level frameworks, and public interview reports. Nothing here is insider knowledge or NDA-sensitive. Loops evolve — confirm the current shape with your recruiter.

Jump into the FE Interview Essentials pathRehearse under a timer in Interview Mode