PracHub
QuestionsCoachesLearningGuidesInterview Prep
|Home/Analytics & Experimentation/Meta

[Analytics Reasoning] Impact of Malicious Accounts on Meta

Last updated: Mar 29, 2026

Quick Overview

Solve a Meta analytics case on malicious accounts and friend-request risk. Covers base-rate probability, Bayes precision, bad-account features, prevalence measurement, platform impact, and safe enforcement.

  • medium
  • Meta
  • Analytics & Experimentation
  • Data Scientist

[Analytics Reasoning] Impact of Malicious Accounts on Meta

Company: Meta

Role: Data Scientist

Category: Analytics & Experimentation

Difficulty: medium

Interview Round: Onsite

Context & Assumptions On a large social network (similar to Facebook), only 1% of accounts are malicious or "bad" Bad accounts send friend requests at a rate ten times higher than good accounts You have developed a classification model that achieves a 95% true positive rate (TPR) and a 95% true negative rate (TNR) Questions 1. Single Friend Request Probability Estimate the probability that a received friend request comes from a bad account. 2. Multiple Friend Requests Determine the likelihood that, out of five friend requests, at least one originates from a bad account. 3. Model Reliability If the model flags an account as bad, how likely is it to be truly malicious, given the stated TPR and TNR? 4. Data & Features Identify which types of data (e.g., behavior logs, friend-request patterns, reported incidents) would be most relevant to classify accounts accurately. 5. Assessing "Bad Account" Prevalence Propose methods (such as stratified or random sampling) to determine whether the bad-account issue is substantial enough to warrant further intervention. 6. Defining a "Bad User" Outline what characteristics or behaviors would qualify an account as "bad" (e.g., spammer, scammer, bot). 7. Platform Impact Discuss how the presence of malicious users could affect the platform's trust, user experience, and reputation. 8. Friend Request Implications Examine how frequent friend requests from bad accounts might impact legitimate users and overall community health. Follow-Up Considerations Threshold Tuning Discuss how adjusting the classification threshold could alter false positives and false negatives. Cost-Benefit Analysis Evaluate the resource investment needed for automated detection vs. manual review. Long-Term Effects of False Positives Consider how incorrect labeling of legitimate users might erode trust. Advanced Feature Engineering Suggest additional signals (e.g., content quality, login behavior) that could enhance detection accuracy. Scaling & Fairness Explain how to maintain model performance and fairness across billions of accounts, ensuring no disproportionate impact on certain demographics.

Quick Answer: Solve a Meta analytics case on malicious accounts and friend-request risk. Covers base-rate probability, Bayes precision, bad-account features, prevalence measurement, platform impact, and safe enforcement.

Related Interview Questions

  • Evaluate a Live-Stream Group Notification Under Network Effects - Meta (medium)
  • Estimate ads ranking revenue impact - Meta (medium)
  • Measure scheduled posts feature success - Meta (medium)
  • How should you evaluate unconnected content? - Meta (medium)
  • Should WhatsApp launch group calls? - Meta (medium)
|Home/Analytics & Experimentation/Meta

[Analytics Reasoning] Impact of Malicious Accounts on Meta

Meta logo
Meta
Apr 7, 2025, 3:24 AM
mediumData ScientistOnsiteAnalytics & Experimentation
10
0

You are analyzing malicious accounts on a large social network. Assume:

  • 1% of all accounts are malicious.
  • Malicious accounts send friend requests at 10 times the rate of normal accounts.
  • A binary bad-account classifier has 95% true positive rate and 95% true negative rate.
  • Unless otherwise stated, treat friend requests as independent over a short time window.

Answer the following analytical and product-safety questions.

Constraints & Assumptions

  • Be explicit about whether you are reasoning over all accounts or over accounts that send friend requests.
  • Use base rates correctly; do not assume model precision equals TPR.
  • State any independence assumptions for the five-request calculation.
  • Discuss both detection accuracy and user/platform impact.
  • Avoid proposing enforcement that ignores false-positive harm.

Clarifying Questions to Ask

  • Are we classifying all accounts, only accounts that send friend requests, or individual friend-request events?
  • What costs are associated with false positives and false negatives?
  • What actions follow a bad-account prediction: friction, review, rate limit, or removal?
  • Are labels from manual review, user reports, confirmed enforcement, or a sampled audit?

Part 1 - Probability and Model Reliability

Calculate:

  1. The probability that a received friend request comes from a bad account.
  2. The probability that at least one of five received friend requests comes from a bad account.
  3. The probability an account is truly bad if the classifier flags it as bad, under both the all-account population and the friend-request-sender population.

What This Part Should Cover

  • Rate-weighted base rates.
  • Complement rule for at least one bad request.
  • Bayes' rule for precision/positive predictive value.
  • Explanation of why prevalence changes model reliability.

Part 2 - Data, Features, and Prevalence Measurement

Describe what data you would use to classify malicious accounts and how you would estimate the true prevalence of bad behavior.

What This Part Should Cover

  • Friend-request behavior, graph features, content, reports, login/device signals, and enforcement history.
  • Random or stratified sampling with human audit.
  • Confidence intervals and biased-label concerns.
  • Honeypots, capture-recapture, or active-learning ideas if useful.

Part 3 - Product Impact and Enforcement

Explain why malicious friend requests matter and how you would design detection or intervention safely.

What This Part Should Cover

  • Effects on trust, user experience, retention, graph quality, brand, and operations.
  • Definition of a bad account.
  • Threshold tuning, manual review, friction, appeal paths, and fairness monitoring.

What a Strong Answer Covers

  • Correct arithmetic and clear population definitions.
  • Awareness of the base-rate problem.
  • Practical feature families and data-quality risks.
  • A product-safety perspective that balances harm reduction with false-positive risk.
  • Scalable and fair enforcement strategy.

Follow-up Questions

  • How would you choose the classifier threshold?
  • How would you estimate harm prevented by detection?
  • How would you monitor adversarial adaptation?
  • What would you do if one region has worse precision than others?
Loading comments...

Browse More Questions

More Analytics & Experimentation•More Meta•More Data Scientist•Meta Data Scientist•Meta Analytics & Experimentation•Data Scientist Analytics & Experimentation

Write your answer

Your first approved answer each day earns 20 XP.

Sign in to write your answer.
PracHub

Master your tech interviews with 8,500+ real questions from top companies.

Product

  • Questions
  • Learning Tracks
  • Interview Guides
  • Resources
  • Premium
  • For Universities
  • Student Access

Browse

  • By Company
  • By Role
  • By Category
  • Topic Hubs
  • SQL Questions
  • AI Coding Questions
  • Compare Platforms
  • Discord Community

Support

  • support@prachub.com
  • (916) 541-4762

Legal

  • Privacy Policy
  • Terms of Service
  • About Us

© 2026 PracHub. All rights reserved.