Design place-of-interest ML system
MetaSoftware Engineer · OnsiteLast updated
Design place-of-interest ML system evaluates ML product requirements, data/labeling, modeling, serving architecture, evaluation, monitoring, and trade-offs in a realistic interview setting. A strong answer states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.
Design a machine learning system that recommends places of interest (POIs) to users. Specify: (a) product goals and key requirements (personalization, freshness, latency, scale), (b) data sources (map metadata, reviews, check-ins, GPS pings, events), labeling strategy (defining positives, counterfactual logging, debiasing for position/exposure), and feature sets (user, POI, context, interaction, geographic features), (c) a two-stage architecture with candidate generation (e.g., embeddings/ANN) and ranking (e.g., GBDT or deep models), plus a re-ranker for diversity/novelty, (d) training pipeline (batch + streaming updates, feature store, backfills) and online serving (feature retrieval, caching, latency budgets, fallbacks), (e) exploration/exploitation strategy (bandits or epsilon-greedy) for cold start and long-term learning, (f) evaluation plan with offline metrics (AUC, NDCG, coverage) and online A/B metrics (CTR, save/visit rate, dwell), and (g) privacy, abuse/spam prevention, and geo-specific fairness considerations.
Solution walkthrough is for members
Get the full walkthrough with reference code and complexity analysis, plus Kitty Coach at 300 messages a day. Hints, the code runner and community answers stay free.