Identify non-table data for feature demand
MetaData Scientist · Technical ScreenLast updated
The question evaluates a data scientist's competency in triangulating product demand from non-table sources, defining and de-biasing signals, specifying metrics and guardrails, and designing evidence-driven experiments within the Analytics & Experimentation domain for a Data Scientist role.
You must decide whether to build a "group call" feature without relying solely on existing product tables. What specific non-table data sources would you use, what signal would you extract from each, and how would you quantify and de-bias them? Discuss at least: (a) qualitative channels (customer interviews, support tickets, sales call transcripts, app store reviews, community/social listening), (b) market/competitive intel (pricing pages, public docs, analyst reports), (c) operational data (infra costs, incident logs, capacity constraints), and (d) user research/UX telemetry (task success, time-on-task, heatmaps). Then design an evidence-driven experiment plan to validate demand: propose a fake-door test (exposed to X% of eligible users), a waitlist, and a limited beta. For each, specify the hypothesis, eligibility, primary success metric (e.g., new weekly active group-call hosts), guardrails (e.g., crash rate, setup failure rate, CSAT), and minimum detectable effect with rough sample-size math and timeline using "today" = 2025-09-01. Explain how you will segment results (e.g., team size, geography, plan tier), control for novelty effects, and ensure ethics (avoid dark patterns).
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.