Role preparation
Machine Learning Engineer interview questions and answers.
Production models, drift, and reproducible ML systems.
Questions
Technical questions to practise out loud
- 01
How do you design a model serving system?
Design serving from latency, throughput, availability and freshness targets: version model and features together, validate inputs, batch where suitable, autoscale bounded workers, cache safely, expose fallback, and monitor predictions.
Read the full breakdown - 02
How do you monitor model drift?
Monitor input schema and quality, feature distribution, prediction distribution, calibration and delayed outcome performance against a versioned baseline; segment alerts and distinguish drift from data-pipeline defects.
Read the full breakdown - 03
How do you build a reproducible ML pipeline?
Version code, data snapshot, features, parameters, environment and random seeds; run transformations as deterministic pipeline steps, record lineage and metrics, and promote immutable artifacts rather than retraining during deployment.
Read the full breakdown - 04
When do you need a feature store?
Use a feature store when multiple models need governed reusable features with consistent offline and online definitions, point-in-time correctness, lineage and low-latency serving; avoid it when a simple pipeline suffices.
Read the full breakdown - 05
How do you test an ML system?
Test schemas and transformations, point-in-time feature correctness, deterministic training, model invariants and thresholds, serving contracts, load and fallback behavior, plus monitored canary outcomes with representative data.
Read the full breakdown - 06
When do you choose batch versus online inference?
Choose batch inference for predictable high-volume scoring when delayed results are acceptable; choose online inference for per-request freshness and low latency, accepting stricter availability, feature parity, and cost requirements.
Read the full breakdown - 07
How do you scale model inference?
Scale inference by profiling preprocessing and model compute, batching compatible requests, selecting efficient runtimes and hardware, autoscaling on queue and latency, bounding concurrency, caching safe results, and applying load shedding.
Read the full breakdown - 08
How do you secure an ML pipeline?
Protect the ML pipeline with least-privilege data access, isolated training, verified dependencies and artifacts, encrypted secrets, input validation, model authorization, audit lineage, and defenses against poisoning and extraction.
Read the full breakdown - 09
How do you control ML infrastructure costs?
Attribute cost by training run and endpoint, right-size accelerators, use spot capacity for restartable work, schedule and stop idle notebooks, batch inference, cache features, set quotas, and compare cost per useful prediction.
Read the full breakdown - 10
How do you roll back a model release?
Keep model, preprocessing, feature schema and configuration as one immutable release; route traffic through a version switch, retain the prior artifact, define health and quality rollback signals, and avoid incompatible feature changes.
Read the full breakdown