Machine Learning & Data Science

A sudden 22-point AUC jump is a gift and a warning. Junior candidates celebrate; strong ones get suspicious and know exactly which leakage checks to run before anything ships.

The most common ML fundamentals question, and a quiet seniority test: anyone recites the definition, but can you decompose the error and turn it into a concrete debugging plan?

The interviewer is testing whether you pick metrics for the problem or recite definitions. The real signal is knowing when accuracy and even AUC lie, and tying each metric to a decision.

Shipping a model is an experiment, and this question separates people who run A/B tests from people who p-hack them. The signal is pre-registering the metric, sizing the test, and resisting the urge to peek.

Imbalance shows up in fraud, churn, and abuse, and the naive answer (oversample, done) leaks data and inflates offline metrics. The signal is preferring cost-sensitive learning, fixing the metric, and resampling correctly. Here is the full toolkit with tradeoffs.

A staple stats question that doubles as a numeracy check. The signal is connecting MLE/MAP to regularization and nailing the base-rate calculation that surprises most people. Here is the intuition plus the worked numbers.

Optimizer questions test whether you understand what each one adapts and the subtle AdamW fix that the whole field now uses. The signal is the per-parameter adaptivity story plus why coupling weight decay to Adam was a bug. Here is that answer.

Tabular ML is won on features, and this question checks whether you handle the practical traps: target leakage in encodings, missingness that is informative, and fitting transforms on the wrong data. The signal is leakage-safe preprocessing. Here is the toolkit.

Recsys underpins half of applied ML, and this question checks whether you match approach to data availability and have a real answer for the cold-start problem that breaks naive systems. Here is the foundations answer.

A point-estimate win on a metric is not a real win. The signal is testing significance with the right paired method on a clean held-out set, weighing effect size, and confirming online. Here is how to compare models without fooling yourself.

A near-universal ML fundamentals question. Anyone can say 'L1 is lasso, L2 is ridge'; the signal is the gradient-and-geometry reason L1 drives weights to exactly zero and when you'd pick each. Here is that answer.

Ensembles dominate tabular ML, and this question checks whether you know they attack different parts of the error. The signal is bagging-reduces-variance vs boosting-reduces-bias and why GBMs win on tabular data. Here is the answer.

SVMs separate the candidates who memorized 'maximize the margin' from the ones who can explain why a kernel gives you non-linear separation without ever touching the high-dimensional space. Here is the answer that lands the second signal.

Trees are the atom of the ensembles that dominate tabular ML, so interviewers check you can explain how a split is chosen and how a single tree overfits. The Gini-vs-entropy part is a trap: candidates over-weight a choice that barely matters. Here is the answer.

Dimensionality questions test linear-algebra intuition and practical judgment at once. The signal is what PCA actually does (project onto max-variance directions), why high dimensions hurt, and the honest catch: it is unsupervised, so it can throw away the exact direction your label needs. Here is the answer.

EM is the canonical latent-variable algorithm, and a GMM is how it shows up in practice. The signal is the E-step/M-step alternation, why it is soft clustering where k-means is hard, and the honest caveat that it only finds a local optimum. Here is the answer.

Backprop is the algorithm that makes deep learning trainable, and the interviewer wants the chain-rule mechanics, not just 'it computes gradients.' The signal is the forward-then-backward flow and why it is efficient. Here is the answer.

BatchNorm is one of the most-asked deep-learning questions, and the trap is the train/inference difference. The signal is what it normalizes, why it stabilizes and speeds training, and why it switches to running statistics at inference. Here is that answer.

This question ties together why deep nets were hard to train and the cluster of tricks that fixed it. The signal is the multiplicative-gradient cause and naming the real fixes: ReLU, He/Xavier init, residuals, normalization. Here is the answer.

CNNs are foundational even as transformers rise, and this checks whether you understand why convolution suits images. The signal is parameter sharing and local connectivity, what pooling buys, and how the receptive field grows. Here is the answer.

Patches as tokens, global attention from layer one, and a weaker inductive bias than a CNN. The signal is naming the data regime where each architecture wins and why. Here is the answer interviewers score highest.

Forward noising is fixed, reverse denoising is learned, and the training loss is a plain noise-prediction regression. The signal is why that beats a GAN's minimax and what the VAE and U-Net each do in latent space. Here is the answer.

Senior DS loops test causal reasoning past the randomized A/B test. The signal is naming the quasi-experimental method that fits and stating the single assumption it lives or dies on. Here is the answer for when randomization is off the table.

A model can rank perfectly and still emit meaningless probabilities. The signal is knowing exactly when calibration matters, how to measure it, and the post-hoc fixes. Here is the answer most candidates miss.

Core statistics screening that catches people who run tests without understanding why they work. The signal is what the CLT actually licenses, and a correlation-vs-causation answer that uses Simpson's paradox to expose a confounder.

Self-supervision is how modern models pretrain on unlabeled data, the engine behind LLMs and modern vision. The signal is the pretext-task idea and the real difference between contrastive and masked-prediction objectives.

Multimodal is now table stakes, and this checks whether you understand how images and text reach a shared model. The signal is CLIP's contrastive alignment and how modern VLMs feed image features into an LLM's token space.

Voice is a major modality and a common applied-AI surface. The signal is the audio-to-text pipeline, why Whisper is resilient, and the cumulative latency budget that makes or breaks a real-time voice agent.

Sequence models are foundational and still asked, especially the gating that fixed RNNs and why attention won. The signal is connecting the vanishing-gradient story to the parallelism argument that let transformers ride the scaling wave.

GANs defined generative modeling for years, and interviewers want the minimax game, the failure modes (mode collapse, instability), and the precise reason diffusion displaced them for images while GANs still win on speed.

Autoencoders and VAEs underpin representation learning and generative modeling, including the VAE inside latent diffusion. The signal is the gap between a plain autoencoder and a variational one, and why you cannot backprop through sampling without the reparameterization trick.

Transfer learning is why you rarely train from scratch, and the real question is how much of the pretrained model to reuse versus adapt. The signal is a crisp decision grid over data size and task similarity, plus knowing when a low LR saves you from catastrophic forgetting.

Two simple classifiers that still appear in interviews because they test whether you understand assumptions and tradeoffs, not just sklearn calls. The signal is k-NN's laziness and curse of dimensionality versus Naive Bayes' independence assumption. Here is the answer.

Distribution questions test whether you can match a data-generating process to the right model. The signal is knowing what each distribution describes and a concrete use case, not memorizing PDFs. Here is the practical map.

Hypothesis testing underlies every experiment, and the signal is interpreting the p-value correctly (it trips most people) and picking the right test. Here is the rigorous, plain-language answer.

Labels are the expensive bottleneck in ML, and these two techniques attack it from different angles. The signal is knowing active learning chooses what to label while semi-supervised uses unlabeled data directly. Here is the answer.

Time series breaks the usual ML assumptions: data is ordered and correlated, so random cross-validation quietly leaks the future and inflates your score. The signal is decomposition, point-in-time features, and time-aware validation.

Ensembles win Kaggle and quietly power most production tabular models. The signal is explaining why combining models beats one (error decorrelation), and knowing exactly how the four techniques differ in what they fix.

Bandits optimize while they learn, shifting traffic toward winners mid-experiment instead of fixing it like an A/B test. The signal is the explore-exploit tradeoff, the three core algorithms, and knowing exactly when a bandit beats a clean A/B test.

Outlier detection shows up in data cleaning, fraud, and monitoring, and there is no single right method. The signal is matching statistical, distance, or model-based families to the dimensionality, distribution, and labels you actually have.

One model, several objectives, one shared backbone. The signal is knowing exactly why sharing helps (regularization, data efficiency) and the failure mode that sinks naive setups. Here is the answer.

The learning rate is the one hyperparameter that can NaN your run on step 50 or stall it forever. Modern training schedules it instead of fixing it. The signal is knowing exactly what warmup and decay each buy you. Here is the answer.

Ranking is not classification, so accuracy is the wrong tool. The signal is matching the rank-aware metric to the task: one right answer versus many, binary versus graded relevance. Here is the answer.

A staple that checks whether you know why ReLU dethroned sigmoid and how to match the output activation to the loss. The signal is the vanishing-gradient story told correctly. Here is the answer.

Everyone says 'gradient descent,' but the batch-size choice and momentum are the real interview content. The signal is the noise-vs-cost tradeoff across batch/SGD/mini-batch and why momentum earns its keep.

The loss defines what the model optimizes, and picking the wrong one quietly dooms it. The signal is matching the loss to the task and data (outliers, imbalance), not defaulting to MSE or cross-entropy on reflex.

Regression needs different metrics than classification, and each tells a different story. The signal is knowing what RMSE vs MAE vs R² vs MAPE actually measure and their failure modes around outliers, scale, and zeros.

Cross-validation gives a reliable performance estimate, but the wrong scheme leaks data and lies. The signal is matching the CV scheme to the data (stratified, grouped, time-series) and fitting preprocessing inside the fold.

These three get conflated, but they answer different questions: one is a preprocessing tool, two are eyeballing tools. The candidates who pass know exactly which structure each preserves and which it quietly throws away.

k-means is the reflex answer, but it quietly assumes round, equal-size clusters and demands you know k upfront. The signal is positioning each alternative by the exact assumption it removes, and knowing when to reach for it.

LDA is the supervised cousin of PCA, and the contrast is a favorite. The signal is knowing that LDA spends the labels to maximize class separation while PCA only chases variance, plus the C minus 1 dimension cap that catches most candidates off guard.

These four quantities underlie cross-entropy loss, decision-tree splits, distillation, and the KL penalty in RLHF. The signal is deriving them from one another and pointing to exactly where each shows up in a real training loop.

Preprocessing quietly decides whether a model trains well, and the right choice is model-dependent. The signal is knowing when scaling matters versus when it is wasted effort, and how to encode a feature with thousands of categories without blowing up your matrix.

HMMs are the classic probabilistic sequence model behind speech and tagging, and Viterbi is how you decode them. The signal is the hidden-states plus transitions/emissions structure, and that Viterbi is dynamic programming for the single best state path, not a probability.

Bad initialization makes deep nets fail to train at all, with activations that vanish or explode through depth. The signal is knowing why zero init is fatal and how to match Xavier or He to your activation function.

High-dimensional data breaks the intuitions and methods that work in two or three dimensions. The signal is naming the concrete effects (distances concentrate, data goes sparse, overfitting climbs) and the mitigations that actually move the needle.

Feature selection cuts noise, overfitting, and serving cost, but the three method families pull in different directions. The signal interviewers want is filter vs wrapper vs embedded and the conditions under which you reach for each.

XGBoost and LightGBM win most tabular problems, and interviewers want more than 'it's boosting.' The signal is the fit-to-residuals mechanism plus the engineering (regularization, histograms, second-order) that makes it both fast and accurate.

Pick the wrong distance metric and you quietly break kNN, clustering, and retrieval. The signal is knowing what each metric actually measures and matching it to the data: magnitude vs direction, sets, correlated features.

Contrastive learning is how modern embeddings (CLIP, sentence encoders, SimCLR) are actually trained. The signal is the pull-positives-push-negatives objective, the InfoNCE loss, and why the number and hardness of negatives makes or breaks quality.

Dropout is the classic neural-net regularizer, but the signal is whether you can explain why zeroing activations forces redundancy, and the train-vs-inference scaling bug that trips most candidates. Here is the answer.

Hand-labeling at scale is the bottleneck. Weak supervision generates labels programmatically instead, and the signal is whether you can explain how a label model denoises conflicting sources into probabilistic labels. Here is the answer.

Grid and random search ignore past results. Bayesian optimization learns from them, and the signal is whether you can explain the surrogate plus acquisition loop and name the exact condition where the sample-efficiency is worth it. Here is the answer.

Gaussian Processes give predictions with principled uncertainty, which is why they power Bayesian optimization. The signal is the distribution-over-functions intuition, the kernel's role, and naming the O(n cubed) wall. Here is the answer.

Running an A/B test is easy; running a valid one is hard. The signal is naming the traps that produce confidently wrong conclusions and the fix for each. Here is the checklist a senior experimenter carries.

GNNs power recommendations, fraud, and molecule modeling by learning over graph structure. The signal is the message-passing mechanism, why k-hop matters, and why you keep them shallow. Here is the answer.

RL underpins RLHF, robotics, and recommendation, and interviewers want the core framing. The signal is the agent-environment-reward loop and the three things that make it harder than supervised learning. Here is the answer.

Data augmentation cheaply expands training data and regularizes models, but valid transforms differ by modality. The signal is the label-preserving constraint and why text is the hard one. Here is the answer.

Two cheap regularizers that fix overconfident classifiers. The signal is knowing that one softens the target and the other softens the input, and exactly why softer signals calibrate the model. Here is the answer.

Ranking is not regression: getting the absolute score wrong is fine, getting the order wrong is not. The signal is the pointwise/pairwise/listwise split and why pairwise (LambdaMART) is still the practical default. Here is the answer.

Classic bias-variance says bigger models eventually overfit, yet deep nets keep improving past the point where they memorize the data. The signal is explaining the second descent and why over-parameterized models generalize. Here is the answer.

Wrap any model and get prediction sets with a provable coverage rate, no distributional assumptions required. The signal is the calibration-set plus nonconformity-score mechanism and exactly what the guarantee does and does not promise. Here is the answer.

Time-to-event problems (churn, failure, conversion timing) hide a twist that quietly biases plain regression. The signal is naming that twist and reaching for the right framing. Here is the answer.

Many real problems give you confirmed positives but never confirmed negatives, only unlabeled data. The shortcut everyone reaches for quietly biases the model. The signal is naming the regime and its fix. Here is the answer.

Some models are natively multiclass; others need a wrapper to stretch a binary classifier to K classes. The signal is knowing the three strategies and exactly when each one wins. Here is the answer.

A model can rank perfectly and still lie about its probabilities; its 0.9 may be right 70% of the time. The signal is knowing the three fixes, which data size each needs, and how to measure the gap. Here is the answer.

The textbook reflex ('drop one') is usually the wrong instinct, and whether collinearity matters at all hinges on your model and what you need from it. This is the answer that separates rote from understanding.

Everyone can recite 'linearity and normality.' Few can say which assumption matters for predictions versus inference, how to spot a violation in a residual plot, and what to actually do about it. Here is that answer.

A pre-existing gap between your groups means randomization or instrumentation is broken, and the whole experiment is suspect. Strong candidates name sample-ratio mismatch on sight. Here is the full diagnosis and the disciplined response.

A 92% aggregate accuracy can hide 60% on the segment that matters most. Average metrics are exactly where these failures hide. Here is how to surface them and the menu of fixes that actually map to the cause.

'The model won't train' has a short list of usual suspects, each with a distinctive loss-curve signature. The shape of the curve names the bug before you touch a single hyperparameter. Here is how to read it.

If labels only exist for the cases you already acted on, the model learns a distorted world: great offline, blind to everyone you never saw. Worse, its own decisions pick the next labels. Here is how to spot it and counter it.

Defaulting to 0.5 is leaving money or safety on the table. The right cutoff comes from the cost of each error and the operating constraint, not the model. Here is how to set it deliberately.

The built-in importance scores from XGBoost can rank a random ID above a vital feature, and stakeholders will make decisions on that bar chart. Here is why default importance lies and what a careful answer reports instead.

Accuracy ties are common, and accuracy is rarely the deciding factor anyway. The real tiebreakers are the ones a junior candidate forgets to mention. Here is the checklist a staff engineer runs before shipping either one.

'The model got worse' has three very different causes and three different fixes. Retraining a model that's actually broken by a pipeline bug just bakes in garbage. Here is the triage order.

Small labeled sets are the normal starting condition, not an excuse. The strong answer is a ladder of techniques that squeeze signal from unlabeled data, pretrained models, and the labeling budget. Here it is.

Most real datasets have wrong labels, and they cap your accuracy invisibly. Cleaning all of it by hand doesn't scale. Here is how to find the bad labels and train robustly around them.

The idea that models, like students, learn better from easy examples first is intuitive, and sometimes it works and sometimes it does nothing. Knowing when it pays off is the real signal. Here is the honest answer.

Generative training fails in distinctive ways: GANs collapse to a few outputs, diffusion samples come out noisy or blurry. The symptom tells you which knob to turn. Here is the diagnosis.

Metric learning lives or dies on the pairs you feed it. Random negatives teach almost nothing, and the margin and mining strategy decide whether the embeddings are any good. Here is how the choices interact.

For search and recommendation, A/B tests can be slow and noisy because they compare different users. Interleaving compares two rankers within the same user's results and detects winners with far less traffic. Here is how.

Boxes and labels, not one tag per image. The signal is choosing two-stage vs one-stage by your latency and accuracy budget, knowing what NMS and anchors actually do, and reporting mAP correctly. Here is the answer interviewers score highest.

Most CV systems fail at the seams: a preprocessing mismatch between training and serving, not the model. The signal is naming every stage from ingestion to serving and the one consistency invariant that breaks teams. Here is the answer.

Cross-entropy is the start, not the answer. The signal is matching the loss to the task structure: focal for detection's background flood, IoU-family for box overlap, Dice for imbalanced masks. Here is how to reason about it.

Semantic labels every pixel by class; instance separates each object. The signal is knowing that one cannot count overlapping objects, why Mask R-CNN adds a mask branch on RoIAlign, and what RoIAlign fixed. Here is the answer.

A million rows does not automatically mean deep learning. The signal is reasoning from dimensionality, data type, inference latency, and label budget, then noting where KNN quietly survives as approximate nearest neighbor. Here is the answer.

Most candidates can recite 'maximize the margin'. The dual is where you show you actually understand why only support vectors matter and where the kernel trick comes from. Here is the derivation an interviewer wants.

EM on a Gaussian mixture has a famous failure mode: a Gaussian collapses onto one point and likelihood shoots to infinity. Knowing why, and the three standard fixes, separates people who used sklearn from people who understand it.

Both tag sequences, but one is generative and one is discriminative, and that difference decides whether you can throw in overlapping features. Here is the comparison that shows you know the modeling tradeoff, not just the acronyms.

Anyone can say 'ensemble of trees'. The real answer is about decorrelating those trees and why that, not just averaging, is what drops variance. Here is what makes the forest more than the sum of its trees.

XGBoost made boosting practical; LightGBM made it fast. The answer is histogram binning, gradient-based sampling, and leaf-wise growth, each with a real tradeoff. Here is what they do and where they bite.

Bayesian inference needs an intractable normalizing constant, and MCMC sidesteps it. The signal is explaining the acceptance ratio, detailed balance, and why you can skip the constant entirely. Here is the answer.

The 'naive' independence assumption is wrong on real data, yet the classifier is a strong baseline for text. The interesting answer explains why classification survives a broken assumption, plus smoothing and the variants. Here it is.

k-NN looks trivial until you ask about choosing k, why distances stop meaning anything in high dimensions, and how to make prediction fast on millions of points. Here is the tradeoff-aware answer.

k-means assumes round, equal-size blobs and a known k. DBSCAN finds arbitrary shapes and outliers but has its own knobs. The hard part is judging clusters without labels. Here is the comparison and the evaluation toolkit.

Univariate ranking is the trap everyone falls into: it keeps redundant features and drops ones that only matter in combination. Here is the filter/wrapper/embedded breakdown plus mRMR and Boruta, and where each one bites.

Lasso gives sparsity, Ridge handles correlated features, and each fails where the other shines. Elastic Net blends them for a specific, common failure. Here is when it earns its two hyperparameters.

Resampling, reweighting, and focal loss attack class imbalance from different angles, and each has a real downside. The signal is matching the method to the model and metric, not blindly oversampling. Here is the breakdown.

IV is the causal tool people name but can't defend. The signal is articulating the two conditions an instrument must satisfy, why one is testable and one is not, and what 2SLS actually estimates. Here is the answer.

Propensity scores promise to mimic an experiment from observational data. The signal is knowing what they can and cannot fix, the overlap trap, and why IPW blows up. Here is the answer that separates careful candidates.

A response model predicts who will convert; an uplift model predicts who converts because of the treatment. The signal is the four-quadrant intuition and how you evaluate uplift when you never observe an individual's lift. Here is the answer.

CUPED can cut the sample size an A/B test needs by half without touching validity. The signal is explaining why subtracting a pre-experiment covariate reduces variance but never biases the estimate. Here is the answer.

Checking an experiment every day and stopping when it hits significance can triple your false-positive rate. The signal is knowing why, and the family of methods that make continuous monitoring valid. Here is the answer.

Standard A/B math assumes one user's treatment doesn't affect another's outcome. In marketplaces and social networks that assumption breaks and your estimate is biased. The signal is naming SUTVA and the right randomization unit. Here is the answer.

The Kalman filter is optimal Bayesian tracking under linear-Gaussian assumptions, and it is two steps repeated forever. The signal is explaining what the gain trades off and when the assumptions break. Here is the answer.

Prophet treats forecasting as curve-fitting trend plus seasonality plus holidays, not as a stochastic process. The signal is knowing why that design wins on business data and where it quietly fails. Here is the answer.

Threshold alerts fire all weekend and miss the real outage Monday. The signal is decomposing seasonality first, choosing the right detector, and tuning for alert fatigue. Here is the answer that survives production.

There is no single fairness number, and a famous result proves you cannot satisfy the main three together. The signal is defining each metric precisely and explaining the impossibility, not picking one blindly. Here is the answer.

Both explain a single prediction by attributing it to features, but only one rests on a uniqueness theorem. The signal is knowing SHAP's game-theory guarantees, LIME's instability, and when each is the right tool. Here is the answer.

Raw gradient saliency maps are noisy and saturate. Integrated gradients fixes both with two axioms and a path integral, but the baseline choice quietly decides the answer. Here is what a careful candidate explains.