← Uber Interview InsightsMachine Learning Engineer

Uber·Machine Learning Engineer·Technical Phone Screen·Senior

SeniorRejected
Jun 2026

Summary

ML engineer round at Uber focused on the Eats homepage recommendation system. The interviewer had an economics/operations research background and didn't actually work on recommendations, which made the whole thing feel off. Pretty sure I didn't pass.

Questions Asked (1)

Q1

How would you design a restaurant recommendation system for the Uber Eats homepage?

System DesignProduct Sense & IdeationTechnical Trade-offs
Author's notes

The mismatch between what I prepared for and who was actually interviewing me was rough.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by clarifying the product goals and constraints (e.g., homepage real estate, user intent, business metrics), then outline a two-stage recommendation architecture (candidate generation and ranking) with a feedback loop. Emphasize how you would evaluate offline and online, and discuss trade-offs like personalization vs. exploration, latency, and cold start.

Pro tip: Anchor your design in Uber Eats' unique context: real-time supply (restaurant availability, delivery time), user location, and multi-objective optimization (conversion, delivery time, restaurant partner value). Show awareness of the two-sided marketplace and how your system balances user satisfaction with restaurant exposure.

1. Clarify goals and constraints

Ask questions to understand the homepage's purpose (e.g., discovery vs. reordering), key metrics (CTR, conversion, delivery time), and constraints (latency, real-time data, diversity).

2. Define data and features

Identify relevant data sources: user history, restaurant attributes, real-time context (location, time, weather), and supply signals (availability, prep time). Discuss feature engineering for personalization and context-awareness.

3. Design a two-stage architecture

Propose candidate generation (e.g., collaborative filtering, popularity, rule-based) to narrow millions of restaurants to hundreds, then a ranking model (e.g., gradient boosted trees or deep learning) to score and order them.

4. Address trade-offs and challenges

Discuss cold start, exploration vs. exploitation, business rules (promotions, diversity), and latency constraints. Explain how to handle real-time supply and multi-objective optimization.

5. Plan evaluation and iteration

Outline offline metrics (NDCG, recall@k), online A/B testing (CTR, conversion, delivery time), and a feedback loop to continuously improve the model with new data.

Key Points to Mention

  • Two-stage recommendation architecture: candidate generation and ranking
  • Real-time features: location, time of day, restaurant availability, and delivery ETA
  • Cold start problem for new users and restaurants, and potential solutions (e.g., contextual bandits, content-based features)
  • Multi-objective optimization balancing user preferences, business metrics (conversion, delivery time), and restaurant partner value
  • Evaluation strategy: offline metrics (precision@k, NDCG) and online A/B testing with guardrail metrics
  • Scalability and latency considerations for serving recommendations at Uber Eats scale

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