Evaluate technical trade-offs for scaling search ranking, reviews, ads, and personalization pipeline

Problem Statement Description

Zomato’s restaurant discovery experience must help urban diners quickly find trustworthy, relevant options for delivery, dining out, or table booking. A key user segment includes people with dietary constraints—such as vegetarian, vegan, Jain, halal, allergy-sensitive, or health-driven preferences—who rely heavily on search ranking, reviews, restaurant metadata, ads, and personalization to make confident decisions.

You are asked to evaluate the technical trade-offs involved in scaling the systems behind search ranking, review quality, sponsored placements, and personalization pipelines. The focus is not to design a full architecture from scratch, but to reason through how product requirements translate into data, platform, reliability, privacy, and ranking trade-offs as Zomato grows across cities, cuisines, user behaviors, and restaurant inventory.

The experience should consider:

- How search ranking balances relevance, freshness, distance, availability, ratings, dietary fit, delivery speed, booking availability, and business monetization.

- How review systems maintain trust while handling spam, fake reviews, low-quality content, recency, and reviewer credibility.

- How ads or sponsored listings can be integrated without damaging user trust or reducing discovery quality.

- How personalization uses user behavior, dietary preferences, location, cuisine affinity, order history, and session intent while respecting privacy and consent.

- What data pipelines, APIs, ranking services, and experimentation systems are needed to support near-real-time updates at scale.

- Reliability and latency expectations for high-traffic discovery surfaces, especially during meal peaks, weekends, festivals, or city-level demand spikes.

- Observability needs, including logging, ranking diagnostics, data quality monitoring, model drift detection, and alerting.

- Rollout considerations such as A/B testing, fallback behavior, guardrails, accessibility, restaurant fairness, and operational cost.

Your goal is to frame the major technical and product trade-offs clearly, explain what you would prioritize and why, and show how you would make scaling decisions that improve booking and order conversion while preserving customer trust, review integrity, and a high-quality restaurant discovery experience.