Diagnose rising account switching and falling actives

Quick Overview

This question evaluates a data scientist's competency in diagnostic analytics, experiment diffing, cohort and identity-resolution analysis, metric instrumentation, and SQL-based quantitative validation.

Diagnose rising account switching and falling actives

Company: Meta

Role: Data Scientist

Category: Analytics & Experimentation

Difficulty: hard

Interview Round: Technical Screen

Yesterday you observed: the number of users switching accounts increased, while overall active users decreased. Propose a concrete diagnostic plan. Include: (a) 5–7 plausible hypotheses spanning measurement artifacts (e.g., deduping by person_id vs user_id, SSO changes), product changes (friction in login/logout, session expiration), and behavior shifts (multi-account consolidation, spam mitigation); (b) the exact metrics and breakdowns you’ll pull (by client, geo, new vs returning, person_id vs user_id, cohorts, time-of-day); (c) at least three targeted slice analyses to confirm or refute cross-contamination between accounts; (d) event/experiment diffing to identify recent launches correlated with the shift; (e) a minimal SQL or pseudocode outline to quantify how many active user_ids map to the same person_id compared with last week; and (f) the immediate mitigations you’d try if the root cause is (i) a logging bug, (ii) authentication friction, or (iii) users gaming policy limits by rotating accounts.

Quick Answer: This question evaluates a data scientist's competency in diagnostic analytics, experiment diffing, cohort and identity-resolution analysis, metric instrumentation, and SQL-based quantitative validation.

|Home/Analytics & Experimentation/Meta
Meta logo
Meta
Oct 13, 2025, 9:49 PM
hardData ScientistTechnical ScreenAnalytics & Experimentation
3
0

Diagnostic Plan: Account Switching Up, Active Users Down

Context

You observed a sudden pattern: the number of users switching accounts increased, while overall active users decreased. Assume:

  • Active user = distinct user_id with any qualifying activity in a day (DAU) unless otherwise noted.
  • person_id is a cross-account identity (e.g., same human across multiple user_ids via SSO/identity graph).
  • An "account switch" is an explicit event (e.g., switch_account, add_account) or inferred by consecutive session logins to different user_ids from the same device/session.

Provide a concrete diagnostic plan covering (a)–(f).

Requirements

(a) List 5–7 plausible hypotheses spanning measurement artifacts, product changes, and behavior shifts.

(b) Specify the exact metrics and breakdowns you will pull (e.g., by client, geo, new vs returning, person_id vs user_id, cohorts, time-of-day).

(c) Describe at least three targeted slice analyses to confirm or refute cross-contamination between accounts (i.e., multiple accounts used by the same person/device).

(d) Outline event/experiment diffing steps to identify recent launches correlated with the shift.

(e) Provide minimal SQL or pseudocode to quantify how many active user_ids map to the same person_id compared with last week.

(f) List immediate mitigations if the root cause is: (i) a logging bug, (ii) authentication friction, or (iii) users gaming policy limits by rotating accounts.

Loading comments...