Technical data science interviews assess far more than textbook definitions — top tech firms evaluate your ability to think under pressure, reason through mathematical trade-offs, write optimized SQL on the fly, and defend architectural decisions. Below is a curated selection from our master question bank.
Answer: The Central Limit Theorem (CLT) states that given a population with arbitrary distribution, finite mean \(\mu\), and finite variance \(\sigma^2\), the sampling distribution of the sample mean approaches a Normal Distribution \(\mathcal{N}(\mu, \sigma^2/n)\) as sample size \(n \ge 30\). In practice, it justifies using parametric z-tests and t-tests on skewed real-world metrics like transaction spend or session times.
Answer: This is the classic Continuous Peeking Problem (multi-testing fallacy). Repeatedly evaluating significance before reaching predetermined sample sizes inflates the Type I error rate from 5% to over 30%! Furthermore, stopping on Day 4 misses weekly cyclical patterns (weekend vs. weekday behavior). The experiment must run for its full pre-calculated sample size and duration.
-- Robust solution using DENSE_RANK to handle salary ties gracefully
WITH RankedSalaries AS (
SELECT salary, DENSE_RANK() OVER (ORDER BY salary DESC) as rk
FROM employees
)
SELECT salary FROM RankedSalaries WHERE rk = 2;
Answer: In ANSI SQL, NULL represents an unknown state, not zero or an empty string. Any arithmetic or comparison with NULL evaluates to NULL (Three-Valued Logic: True, False, Unknown). NULL = NULL evaluates to UNKNOWN, which is why IS NULL and IS NOT NULL are mandatory syntax. COUNT(*) includes NULL rows, whereas COUNT(col) ignores them.
Answer: Data Drift (Covariate Shift) occurs when the distribution of input features changes: \(P(X)_{\text{prod}} \neq P(X)_{\text{train}}\), while the relationship between features and target remains constant (e.g., users getting younger). Concept Drift occurs when the relationship between features and target changes: \(P(Y|X)_{\text{prod}} \neq P(Y|X)_{\text{train}}\) (e.g., shopping habits shifting abruptly during a pandemic).
When interviewing for senior roles, always contextualize answers with engineering trade-offs: mention latency, memory footprint, data leakage risks, and how you would automate monitoring in production.
Broaden your statistical analysis, Python data wrangling, and production engineering expertise:
Review academic exam questions, viva defenses, and oral theory.
Quick revision of essential formulas, distributions, and code syntax.
Turn interview readiness into lucrative job offers and consulting contracts.
Review product sense and statistical experiment questions.