← Adobe Interview InsightsMachine Learning Engineer

Adobe·Machine Learning Engineer·Technical Phone Screen·Senior

Senior
Apr 2026

Summary

Adobe ML Engineer technical screen, pretty much one big deep-dive question on missing data handling. The breadth they expected was a bit more than I anticipated, felt like they wanted a full lecture not just a quick answer.

Questions Asked (1)

Q1

Walk me through how you handle missing data in a machine learning pipeline, from identifying why data is missing all the way through to choosing an imputation strategy.

Technical Trade-offsData ModelingAlgorithms & Data Structures
Author's notes

I started with MCAR/MAR/MNAR which felt right, but I could tell they wanted me to actually connect that diagnosis to the downstream choice, not just recite definitions.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Structure your answer as a systematic pipeline: first diagnose the missingness mechanism (MCAR, MAR, MNAR), then assess the impact on your model and business context, and finally select an imputation strategy that balances statistical validity with practical constraints. Emphasize that the best approach depends on the data type, missingness pattern, and downstream model, and that you validate choices through experimentation.

Pro tip: Always start by quantifying the missingness and its relationship to the target variable—if missingness itself is predictive, consider adding a missing indicator feature rather than just imputing. Also, be prepared to discuss how you'd handle missing data in production, ensuring your imputation logic is reproducible and monitored.

1. Diagnose the missingness mechanism

Determine whether data is missing completely at random (MCAR), at random (MAR), or not at random (MNAR) by analyzing patterns and correlations with other variables. Use statistical tests (e.g., Little's MCAR test) and visualizations to guide your understanding.

2. Assess impact and define success criteria

Evaluate how much data is missing, which features are affected, and how missingness might bias your model or business outcomes. Define what a successful imputation looks like in terms of model performance and interpretability.

3. Choose an imputation strategy

Select from simple (mean, median, mode), model-based (KNN, MICE), or advanced (deep learning) methods based on data type, missingness mechanism, and computational budget. Consider adding missing indicators if missingness is informative.

4. Validate and iterate

Test the imputation strategy using cross-validation and compare model performance against baselines (e.g., dropping missing rows). Monitor for overfitting and ensure the imputation doesn't leak information from the test set.

5. Implement in production

Deploy the imputation as part of a reproducible pipeline, ensuring it handles new data consistently. Set up monitoring to detect shifts in missingness patterns and retrain or adjust as needed.

Key Points to Mention

  • Missingness mechanisms: MCAR, MAR, MNAR and their implications
  • Simple imputation methods (mean, median, mode) and their limitations
  • Model-based imputation (KNN, MICE, EM) and when to use them
  • Adding missing indicator features to capture informative missingness
  • Validation techniques to avoid data leakage and overfitting
  • Production considerations: reproducibility, monitoring, and pipeline integration

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.