Company guides

⬛ Uber — Frontend Interview Guide

← Back to Company guides

Emphasis: Real-time, data-heavy UIs and maps. Practical component building plus system design around live location and streaming data.

Related: Company index · ROADMAP


The loop (typical)

Round Focus Prep section
Phone screen JS/DSA 03-javascript
Coding UI component / machine coding 16-machine-coding
Frontend system design Real-time "Design X" 15-system-design
Behavioral Ownership, collaboration

What they emphasize

  • Real-time data — live location, ETAs, streaming updates (WebSocket/SSE).
  • Maps & geospatial UI — rendering markers, routes, viewport performance.
  • State management for complex, frequently-updating UIs.
  • Reliability — handling flaky networks, retries, offline.

Frequently asked (community-sourced)

System design

Machine coding

  • Build a Data Grid (trips table) → flagship
  • Build an Autocomplete (location search) → flagship
  • Build an infinite scroll list → flagship

JS / patterns

Prep plan (2 weeks)

  1. Master real-time patterns (WS/SSE/polling, reconnect).
  2. Study map-rendering perf + virtualization.
  3. Build data-heavy components (grid, live list).
  4. Practice a live-tracking system design.

🟢 Green flags · 🔴 Red flags

🟢 Do: handle real-time updates + reconnect/backoff · manage complex, frequently-updating state · plan for flaky networks and offline · keep the map/list performant. 🔴 Avoid: ignoring message ordering/dedupe · no retry/offline handling · blocking the UI on the network · unbounded re-renders on every update.

📝 Sample interviewer prompts

  • "Build a live-updating trips list."
  • "Design rider↔driver live tracking on a map."
  • "How do you keep a WebSocket stream ordered and duplicate-free across reconnects?"

Interviewed at Uber? Add the questions you got (role + year) via a PR.

ESC

Type to search across every question bank.

navigate open 3,610 questions indexed