Meta·Data Scientist·Onsite - System Design / Architecture
Sep 2025
This was a deep technical screen for a DS role at Meta, centered entirely on one massive open-ended ML system design problem. The question covered basically every angle you can imagine: features, labeling, modeling choices, evaluation, privacy, and deployment. Felt more like a take-home prompt than a 45-minute conversation.
- How would you design the features for a model that classifies whether a Facebook session is happening at home, in an office, or at a public venue, using only privacy-preserving signals like timestamps, ASN/ISP type, coarse location, device mix, and contact graph patterns?
- How would you generate labels at scale for this network-context classification problem without ground truth, and how do you correct for bias in those noisy weak labels?
- Compare rule-based classifiers, gradient boosted trees, and sequence models like HMMs or transformers for this session-context classification task. How do you handle aggregating session-level predictions up to the household level?
- How would you evaluate this model? Define your metrics, describe how you'd set up cross-geo temporal cross-validation, and explain how you'd prevent label leakage from Portal adoption data.
- What privacy and compliance constraints would you apply to this system, including data minimization, retention limits, on-device inference options, and re-identification risk?
- How would you deploy this system, monitor for drift, and design a holdout experiment to measure whether location-type targeting actually improves Portal ad conversion?
“This was the core of the whole interview and it's genuinely hard.” The rest of the author's notes on Data Scientist interview at Meta, Onsite - System Design / Architecture round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.
View Post