← Uber Interview InsightsSoftware Engineer

Uber·Software Engineer·Onsite - System Design / Architecture·Senior

Senior
Jun 2026

Summary

Uber system design round for a software engineer role. The main prompt was designing the search component for Uber Eats, which spawned a bunch of follow-ups I wasn't fully prepared for, including having to design a metric monitoring system on top of it.

Questions Asked (2)

Q1

Design the search component for Uber Eats. How would you architect it end to end?

System DesignTechnical Trade-offsData Modeling
Author's notes

Started with the obvious stuff, indexing restaurants and dishes, ranking by relevance and distance.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by clarifying requirements and defining the scope — distinguish between restaurant search, dish/item search, and contextual filters like location, dietary preferences, and delivery time. Then walk through the architecture layer by layer: client, API gateway, search service, indexing pipeline, and data stores, explicitly calling out trade-offs at each decision point. Conclude by addressing scalability, latency targets, and how you'd handle real-time data like restaurant availability or surge pricing.

Pro tip: Uber operates at massive geo-distributed scale, so proactively discussing how search results are personalized and ranked using signals like past orders, proximity, and restaurant ratings — rather than treating it as a simple keyword lookup — will immediately signal senior-level thinking to your interviewer.

1. Clarify Requirements & Define Scope

Ask clarifying questions to nail down functional requirements (search by restaurant name, cuisine, dish, dietary tags) and non-functional requirements (latency < 200ms p99, high availability, geo-awareness). Establish scale assumptions such as QPS, number of restaurants, and geographic regions.

2. High-Level Architecture Overview

Sketch the major components: mobile/web client → API Gateway → Search Service → Elasticsearch/Solr cluster, backed by an indexing pipeline fed from a Restaurant Data Store. Briefly explain how each component interacts before diving deeper.

3. Data Modeling & Indexing Strategy

Define the search index schema — restaurant documents should include name, cuisine tags, menu items, geo-coordinates, ratings, and availability status. Discuss how to keep the index fresh using an event-driven pipeline (Kafka + Flink) that reacts to restaurant updates in near real-time.

4. Query Processing & Ranking

Explain the query flow: text tokenization and normalization, geo-filtering using bounding box or radius queries, and multi-factor ranking that combines textual relevance, distance, rating, estimated delivery time, and personalization signals from a recommendation model. Mention caching hot queries with Redis to reduce latency.

5. Scalability, Reliability & Trade-offs

Address horizontal scaling of the search cluster with sharding by geo-region, replication for read throughput, and circuit breakers for fault tolerance. Discuss trade-offs such as eventual consistency of the index vs. strong consistency, and the cost/benefit of a dedicated ML ranking service versus simpler heuristic scoring.

Key Points to Mention

  • Geo-aware search: using geohashing or bounding-box filtering to restrict results to deliverable zones before applying text relevance scoring
  • Elasticsearch or Apache Solr as the core search engine, with inverted indexes for text and geo-spatial indexes for location queries
  • Real-time index updates via an event-driven pipeline (e.g., Kafka + Flink) to reflect restaurant open/close status, menu changes, and surge pricing
  • Multi-signal ranking model incorporating relevance score, distance, delivery ETA, restaurant rating, and user personalization (past orders, preferences)
  • Caching strategy: Redis for caching popular or repeated queries, and CDN edge caching for static assets like restaurant thumbnails
  • Typeahead/autocomplete as a separate low-latency service backed by a trie or prefix-indexed store to power instant search suggestions

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.

Q2

How would you design a metric monitoring system for the Uber Eats search component you just described?

Product Analytics & MetricsSystem DesignA/B Testing & Experimentation
Author's notes

This one caught me mid-sentence basically.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by anchoring the monitoring system to the core business goals of Uber Eats search (relevance, conversion, latency), then layer in a tiered metrics hierarchy from high-level KPIs down to granular diagnostic signals. Conclude by describing the alerting, dashboarding, and experimentation feedback loops that make the system actionable.

Pro tip: Uber operates at massive scale, so impress the interviewer by distinguishing between real-time streaming metrics (sub-minute latency alerts) and batch aggregated metrics (daily business health), and explain why you need both — this signals production-level maturity.

1. Define Business & User Goals

Identify the north-star metric for search (e.g., search-to-order conversion rate) and tie every subsequent metric back to it. Clarify whose perspective matters — users, restaurants, and Uber's marketplace health.

2. Build a Metrics Hierarchy

Structure metrics into three tiers: top-level KPIs (conversion rate, GMV from search), mid-level product metrics (click-through rate, zero-result rate, time-to-first-result), and low-level system metrics (p50/p99 latency, error rate, index freshness). This hierarchy helps quickly isolate where a problem originates.

3. Design Data Collection & Pipeline

Instrument client and server events (query logs, impression logs, click/order events) and funnel them through a real-time streaming pipeline (e.g., Kafka + Flink) for live dashboards and a batch pipeline (e.g., Hive/Spark) for deeper analysis. Ensure event schemas are versioned and backward-compatible.

4. Set Up Alerting & Anomaly Detection

Define static thresholds for critical SLOs (e.g., p99 latency < 500ms, error rate < 0.1%) and layer on statistical anomaly detection for business metrics that have natural seasonality (meal-time spikes). Route alerts to on-call engineers with enough context to act immediately.

5. Close the Loop with Experimentation

Integrate the monitoring system with the A/B testing framework so that every experiment automatically tracks the full metrics hierarchy, enabling safe rollouts and quick rollbacks. Include guardrail metrics (e.g., restaurant fairness, diversity of results) to catch unintended side effects.

Key Points to Mention

  • North-star metric tied to business outcomes (search-to-order conversion, GMV attributed to search)
  • Tiered metrics hierarchy: KPIs → product metrics → system/infrastructure metrics
  • Real-time vs. batch pipelines and when each is appropriate (operational alerting vs. trend analysis)
  • Seasonality-aware anomaly detection to reduce false positives during peak hours
  • Guardrail metrics to protect restaurant fairness and result diversity alongside primary metrics
  • Integration with A/B testing infrastructure for safe, data-driven feature rollouts and automatic rollback triggers

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.