Machine Learning & Data Science

A 22-point AUC jump is both an opportunity and a red flag. Weaker candidates cheer; sharp ones grow wary and know precisely which leakage checks belong before anything ships.

The most frequent ML fundamentals question, and a subtle seniority check: anyone can repeat the definition, but can you break down the error and convert it into a concrete debugging plan?

The interviewer wants to see whether you choose metrics to fit the problem or just recite definitions. The signal that counts is recognizing when accuracy and even AUC mislead, and linking each metric to a decision.

Shipping a model is itself an experiment, and this question tells apart people who run A/B tests from those who p-hack them. The signal is pre-registering the metric, sizing the test, and holding back from peeking.

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

A standard stats question that also works as a numeracy check. The signal is linking MLE/MAP to regularization and getting the base-rate calculation right, the one that surprises most people. Here is the intuition along with the worked numbers.

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

Tabular ML is won on features, and this question checks whether you navigate the practical traps: target leakage in encodings, informative missingness, 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 fit the approach to data availability and hold 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 genuine 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 recite 'L1 is lasso, L2 is ridge'; the signal is the gradient-and-geometry reason L1 forces weights to exactly zero and when you'd choose each. Here is that answer.

Ensembles dominate tabular ML, and this question tests whether you grasp that 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 sort the candidates who memorized 'maximize the margin' from those who can explain how a kernel delivers non-linear separation without ever touching the high-dimensional space. Here is the answer that lands the second signal.

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

Dimensionality questions probe linear-algebra intuition and practical judgment together. What interviewers reward is what PCA really does (project onto max-variance directions), why high dimensions hurt, and the honest catch: it is unsupervised, so it can discard the exact direction your label needs. Here is the answer.

EM is the classic latent-variable algorithm, and a GMM is how it appears in practice. What interviewers reward is the E-step/M-step alternation, why it is soft clustering where k-means is hard, and the honest caveat that it only reaches 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.' What interviewers reward 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. What interviewers reward 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 connects why deep nets were hard to train with the cluster of tricks that solved it. What interviewers reward is the multiplicative-gradient cause and naming the real fixes: ReLU, He/Xavier init, residuals, normalization. Here is the answer.

CNNs remain foundational even as transformers rise, and this checks whether you grasp why convolution suits images. What interviewers reward 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. What interviewers reward 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. What interviewers reward 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 beyond the randomized A/B test. What interviewers reward 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 output meaningless probabilities. The signal is knowing precisely 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 grasping 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 genuine difference between contrastive and masked-prediction objectives.

Multimodal is now table stakes, and this tests 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 can make or break a real-time voice agent.

Sequence models remain interview staples, particularly the gating that repaired RNNs and the reason attention took over. What matters is linking the vanishing-gradient narrative to the parallelism case that let transformers ride the scaling wave.

GANs shaped generative modeling for years, and interviewers look for the minimax game, the failure modes (mode collapse, instability), and the exact reason diffusion overtook them for images while GANs still lead on speed.

Autoencoders and VAEs sit beneath representation learning and generative modeling, including the VAE inside latent diffusion. What matters is the difference between a plain autoencoder and a variational one, and why sampling blocks backprop without the reparameterization trick.

Transfer learning is the reason you seldom train from scratch, and the real question is how much of the pretrained model to reuse versus adapt. What matters is a clean decision grid across data size and task similarity, plus knowing when a low LR guards against catastrophic forgetting.

Two simple classifiers that keep showing up in interviews because they check whether you grasp assumptions and tradeoffs, not just sklearn calls. What matters is k-NN's laziness and curse of dimensionality against Naive Bayes' independence assumption. Here is the answer.

Distribution questions check whether you can map a data-generating process to the right model. What matters is knowing what each distribution describes plus a concrete use case, not memorizing PDFs. Here is the practical map.

Hypothesis testing sits under every experiment, and what matters is reading the p-value correctly (it trips most people) and picking the right test. Here is the rigorous, plain-language answer.

Labels are the costly bottleneck in ML, and these two techniques tackle it from different angles. What matters is knowing active learning picks what to label while semi-supervised draws on unlabeled data directly. Here is the answer.

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

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

A bandit learns and optimizes at the same time, moving traffic toward the winning arm during the experiment rather than holding the split fixed like an A/B test. Interviewers look for the explore-exploit tradeoff, the three core algorithms, and a clear sense of when a bandit wins over a clean A/B test.

Outlier detection appears in data cleaning, fraud, and monitoring, and no single method wins everywhere. Interviewers want you to match the statistical, distance, or model-based families to the dimensionality, distribution, and labels you actually have.

One model, multiple objectives, a single shared backbone. Interviewers want you to explain precisely why sharing helps (regularization, data efficiency) and the failure mode that wrecks naive setups. Here is the answer.

The learning rate is the single hyperparameter that can NaN your run at step 50 or stall it indefinitely. Modern training schedules it rather than pinning it to one value. Interviewers want you to know precisely what warmup and decay each give you. Here is the answer.

Ranking is not classification, so accuracy is the wrong instrument. What you need to show 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 tests whether you know why ReLU displaced sigmoid and how to pair the output activation with the loss. What matters is telling the vanishing-gradient story correctly. Here is the answer.

Everyone says 'gradient descent,' but the batch-size decision and momentum are the actual interview content. What earns credit is the noise-vs-cost tradeoff across batch/SGD/mini-batch and why momentum pays off.

The loss sets what the model optimizes, and the wrong choice silently sinks it. What counts is matching the loss to the task and data (outliers, imbalance), rather than reflexively reaching for MSE or cross-entropy.

Regression calls for different metrics than classification, and each tells its own story. What matters is knowing what RMSE vs MAE vs R² vs MAPE really measure and their failure modes around outliers, scale, and zeros.

Cross-validation yields a reliable performance estimate, but the wrong scheme leaks data and misleads. What matters is matching the CV scheme to the data (stratified, grouped, time-series) and fitting preprocessing inside the fold.

These three get lumped together, yet they answer different questions: one is a preprocessing tool, two are eyeballing tools. The candidates who pass know precisely which structure each keeps and which it silently discards.

k-means is the reflex answer, yet it silently assumes round, equal-size clusters and requires you to know k in advance. What earns credit is positioning each alternative by the specific assumption it drops, and knowing when to use it.

LDA is the supervised cousin of PCA, and the contrast is a favorite. What matters is knowing that LDA uses the labels to maximize class separation while PCA only chases variance, plus the C minus 1 dimension cap that trips up most candidates.

These four quantities sit under cross-entropy loss, decision-tree splits, distillation, and the KL penalty in RLHF. What matters is deriving them from one another and pointing to precisely where each turns up in a real training loop.

Preprocessing quietly decides whether a model trains well, and the right choice depends on the model. What matters is knowing when scaling counts 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. What matters 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. What matters 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. What matters is naming the concrete effects (distances concentrate, data goes sparse, overfitting climbs) and the mitigations that actually move the needle.

Feature selection trims noise, overfitting, and serving cost, but the three method families pull in different directions. What 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.' What matters 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. What matters 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. What matters 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 what matters 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 produces labels programmatically instead, and what matters 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 what matters 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. What matters 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. What matters 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. What matters is the message-passing mechanism, why k-hop matters, and why you keep them shallow. Here is the answer.

RL sits under RLHF, robotics, and recommendation, and interviewers want the core framing. What matters 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. What matters is the label-preserving constraint and why text is the hard one. Here is the answer.

Two inexpensive regularizers that cure overconfident classifiers. What proves you understand them is knowing that one softens the target while the other softens the input, and precisely why gentler signals produce calibrated models. Here is the answer.

Ranking differs from regression: a wrong absolute score is acceptable, a wrong ordering is not. What shows depth is the pointwise/pairwise/listwise breakdown and why pairwise (LambdaMART) remains the practical default. Here is the answer.

Classic bias-variance predicts that larger models eventually overfit, but deep nets keep improving even after they memorize the data. What shows depth is explaining the second descent and why over-parameterized models generalize. Here is the answer.

Wrap any model and obtain prediction sets with a provable coverage rate, with no distributional assumptions needed. What shows depth 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) conceal a twist that quietly biases ordinary regression. What shows depth is naming that twist and choosing the right framing. Here is the answer.

Plenty of real problems hand you confirmed positives but never confirmed negatives, only unlabeled data. The shortcut everyone grabs quietly biases the model. What shows depth is naming the regime and its fix. Here is the answer.

Some models are multiclass out of the box; others need a wrapper to extend a binary classifier to K classes. What shows depth is knowing the three strategies and exactly when each one wins. Here is the answer.

A model can rank perfectly yet lie about its probabilities; its 0.9 may hold only 70% of the time. What shows depth is knowing the three fixes, the data size each requires, 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 depends on your model and what you want from it. This is the answer that tells rote apart from real understanding.

Anyone can recite 'linearity and normality.' Few can say which assumption matters for predictions versus inference, how to catch 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 entire experiment is suspect. Strong candidates spot sample-ratio mismatch immediately. Here is the full diagnosis and the disciplined response.

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

'The model won't train' comes down to 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.

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

Defaulting to 0.5 leaves 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 base decisions on that bar chart. Here is why default importance misleads and what a careful answer reports instead.

Two models landing at the same accuracy is common, and accuracy was rarely the deciding factor to begin with. The real tiebreakers are the ones a junior candidate leaves out. This is the checklist a staff engineer works through before shipping either one.

'The model got worse' can mean three very different things with three different fixes. Retrain a model that a pipeline bug actually broke and you just bake in garbage. Here is the order to triage it in.

A small labeled set is the normal place to start, not an excuse. The strong answer is a ladder of techniques that pull signal from unlabeled data, pretrained models, and the labeling budget. Here it is.

Most real datasets carry wrong labels, and they quietly cap your accuracy. Hand-cleaning all of it does not scale. Here is how to surface the bad labels and train robustly around them.

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

Generative training breaks in distinctive ways: GANs collapse to a handful of outputs, diffusion samples come out noisy or blurry. The symptom points to which knob to turn. Here is the diagnosis.

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

In search and recommendation, A/B tests can be slow and noisy because they pit different users against each other. Interleaving compares two rankers inside the same user's results and spots winners with far less traffic. Here is how.

Boxes and labels, not a single tag per image. The signal is picking two-stage versus one-stage from your latency and accuracy budget, knowing what NMS and anchors really do, and reporting mAP correctly. Here is the answer interviewers score highest.

Most CV systems break at the seams: a preprocessing mismatch between training and serving, not the model itself. The signal is naming every stage from ingestion through serving and the single consistency invariant that trips teams up. Here is the answer.

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

Semantic labels every pixel by class; instance pulls each object apart. The signal is knowing that the first 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 call for deep learning. The signal is reasoning from dimensionality, data type, inference latency, and label budget, then noting where KNN quietly lives on as approximate nearest neighbor. Here is the answer.

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

A Gaussian mixture trained by EM has a well-known trap: one Gaussian shrinks onto a single point and the likelihood races to infinity. Understanding the cause, plus the three standard remedies, tells apart people who merely ran sklearn from those who grasp it.

Both label sequences, but one is generative and one is discriminative, and that gap decides whether you can add overlapping features. Here is the comparison that proves you understand the modeling tradeoff, not merely the acronyms.

Anyone can say 'ensemble of trees'. The real answer concerns decorrelating those trees and why that, not averaging alone, 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 carrying a real tradeoff. Here is what they do and where they hurt.

Bayesian inference requires an intractable normalizing constant, and MCMC works around it. The signal is explaining the acceptance ratio, detailed balance, and why you can drop the constant entirely. Here is the answer.

The 'naive' independence assumption is wrong on real data, yet the classifier remains 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 picking k, why distances lose meaning in high dimensions, and how to keep prediction fast on millions of points. Here is the tradeoff-aware answer.

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

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

Lasso delivers sparsity, Ridge copes with correlated features, and each stumbles where the other excels. Elastic Net combines them for a specific, common failure. Here is when it earns its two hyperparameters.

Resampling, reweighting, and focal loss tackle class imbalance from different angles, and each carries 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 cannot defend. The signal is spelling out the two conditions an instrument must meet, why one is testable and one is not, and what 2SLS actually estimates. Here is the answer.

Propensity scores promise to imitate 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 sets careful candidates apart.

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 an individual's lift is never observed. Here is the answer.

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

Checking an experiment daily and stopping the moment 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 does not 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 amounts to 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, rather than 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 alarms page you all weekend yet sleep through Monday's actual outage. What interviewers reward is stripping out seasonality first, matching the detector to the anomaly, and tuning against alert fatigue. Here is the answer that holds up in production.

Fairness has no single number, and a well-known result proves the main three cannot hold together. What interviewers reward is defining each metric precisely and explaining the impossibility rather than picking one blindly. Here is the answer.

Both explain one prediction by crediting features, but only one is backed by a uniqueness theorem. What interviewers reward is knowing SHAP's game-theory guarantees, LIME's instability, and when each fits. Here is the answer.

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

Most teams run human eval as a vibe check with ten examples and a 1-5 slider. The signal is treating it as a designed experiment: pairwise, blinded, powered, and agreement-measured. Here is the protocol that survives scrutiny.

Accuracy against a held-out label is the wrong instrument for a system with no single right answer, an open failure space, and a metric that is itself a model. Here is what breaks, what survives, and what replaces it.

You observe repayment only for applicants you approved, so your training data is censored by your own past policy and your offline test set is censored the same way. The fix starts with something you must have logged years ago.

A model that never looks at the image can score respectably on VQA, which tells you most of what you need to know about the benchmark. Here is what the scores hide, and the one-line ablation that exposes it.

An eval suite that never varies the image will happily pass a model that has stopped looking at it. Start with the modality ablation, then pick metrics by what the system actually produces. Here is the full stack.