314,552 interview questions from 6,000+ companies.
Tests whether you can translate technical complexity into business-relevant language for non-technical stakeholders and drive action.
Identify the main pitfalls that can distort A/B test interpretation and explain how to guard against them.
Explain what statistical significance means and why it matters when interpreting experimental or analytical results.
Outline the first checks to diagnose a sudden drop in a core product metric, starting with data quality, scope, and decomposition.
Explain how to profile, clean, and standardize missing or dirty data before analysis.
Tests how you gather requirements under ambiguity by using stakeholder management, structured communication, and problem clarification.
Design a personalized recommendation system that turns user preferences into ranked suggestions with retrieval, ranking, and feedback loops.
Explain how the bias-variance tradeoff guides algorithm selection and generalization performance.
Tests ownership and stakeholder management in leading a data project from vague problem definition through delivery and measurable impact.
Explain how feature engineering improves supervised model performance and how to validate its impact with proper evaluation.
Explain how bias and variance affect generalization, and how model complexity changes the balance.
Choose the right evaluation metric for an imbalanced dataset and explain why accuracy can mislead.
Design an A/B test for a new digital product launch with clear metrics, power, guardrails, and a defensible ship decision.
Define one primary feature metric and a set of guardrails that capture user value without missing broader product risk.
Tests how you lead through ambiguity in research, take ownership of setbacks, and turn technical roadblocks into measurable outcomes.
Explain how to choose between a simpler interpretable model and a more accurate black-box model.
