The setup is a Kaggle-style problem so it feels approachable at first, but the feature engineering part is where they actually probe you.
Frame the problem as a binary classification task: given a pair of POI records, predict whether they refer to the same real-world location. Walk through the end-to-end ML pipeline: feature engineering from raw attributes, model selection with trade-offs, and evaluation using appropriate metrics and business impact.
Pro tip: Emphasize that in production, precision often matters more than recall for deduplication to avoid merging distinct locations, and discuss how to handle class imbalance and scalability to millions of pairs.
Clarify the goal: determine if two POI records refer to the same physical place. Discuss data sources (name, address, coordinates, phone, category) and challenges like noise, missing values, and class imbalance.
Create features that capture similarity and agreement between record pairs: string similarity (Jaro-Winkler, Levenshtein) for names and addresses, geospatial distance (Haversine), phone number match, category match, and possibly embedding-based semantic similarity.
Choose a model suitable for pairwise classification: gradient boosted trees (XGBoost/LightGBM) for tabular features, or a Siamese neural network for learned embeddings. Discuss handling class imbalance via sampling or class weights.
Use precision, recall, F1, and AUC-ROC, but prioritize precision if false merges are costly. Tune the decision threshold based on business requirements and validate with cross-validation or a held-out set.
Address how to scale to millions of pairs: blocking/indexing to reduce candidate pairs, distributed training, and online serving with low latency. Monitor performance and retrain periodically.
AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.