The four rounds
| Round | What it covers |
|---|---|
| ML fundamentals | Bias-variance, regularisation, evaluation metrics, overfitting |
| Coding | Standard data structures, plus occasionally implementing a model component from scratch |
| ML system design | End-to-end design of a production ML system - the differentiating round |
| Behavioral and project deep-dive | A model you shipped, and what it did in production |
Fundamentals questions
- Explain the bias-variance trade-off, and what you would actually change if you diagnosed high variance.
- Why does L1 produce sparse weights and L2 does not?
- Your model has 99% accuracy and is useless. What happened, and what would you measure instead?
- Precision versus recall - and which matters for fraud detection, and why.
- How do you detect and handle data leakage? Expect a follow-up asking for an example you have actually seen.
- When does gradient boosting beat a neural network, and when is the reverse true?
ML system design, the round that decides it
Open prompts - design a recommendation system, design fraud detection, design search ranking. The structure that works:
- Start with the problem, not the model. What is being predicted, for whom, and what does a good outcome look like in business terms?
- Data. Where does training data come from, and how are labels obtained? Label availability quietly decides most real ML designs.
- Features. What is available at serving time? Candidates routinely design features that cannot exist at inference - this is the single most common mistake in the round.
- Model choice, briefly, with a baseline. Always propose a simple baseline first.
- Offline and online evaluation. Which offline metric, and which online metric in an A/B test.
- Serving. Latency budget, batch versus real time, how the model is updated.
- Monitoring. Training-serving skew, data drift, and what triggers a retrain.
Training-serving skew and drift are the topics most likely to be probed and least likely to be prepared. If you have an example of a model that degraded in production and what you did about it, that story is worth more than any theory answer.
How this differs from a data scientist loop
Data science loops weight statistics, experiment design and analysis. ML engineer loops weight production systems - serving, pipelines, latency, monitoring. Candidates who have only done notebook work tend to struggle with the second, and the gap shows fastest in the serving and monitoring parts of the design round.
If you are early in your career, AI and ML internships at big tech covers that pipeline, which has its own timing.
Where CoPilot Interview fits
Disclosure: we build an interview assistant, so treat this as a disclosed pitch. CoPilot Interview is a native Windows and macOS app that puts suggested answers on your own screen in about two seconds, across coding, system design and behavioral rounds, with a permanent free tier that needs no credit card.
There is a role page at machine learning interview help, and the general design-round structure is in AI for system design interviews.
Frequently asked questions
What is asked in a machine learning engineer interview?
Four rounds: ML fundamentals such as bias-variance and evaluation metrics, a standard coding round, an ML system design round covering an end-to-end production system, and a project deep-dive on something you shipped. The system design round is usually the differentiator.
What is the difference between ML engineer and data scientist interviews?
Data science loops weight statistics, experiment design and analysis. ML engineer loops weight production systems - serving, latency, pipelines and monitoring. Candidates whose experience is mostly notebook-based tend to struggle with the serving and monitoring portions.
How do you answer an ML system design question?
Start with the problem and the success metric rather than the model, then work through data and label availability, features available at serving time, a simple baseline before anything complex, offline and online evaluation, serving constraints, and monitoring for drift and training-serving skew.
What is the most common mistake in ML system design interviews?
Designing features that cannot exist at inference time. It is extremely common, it invalidates the design, and interviewers probe for it specifically because it separates people who have shipped a model from people who have only trained one.
Walk into the round with a second pair of eyes
CoPilot Interview is a native Windows and macOS app that puts suggested answers on your own screen in about two seconds, across coding, system design and behavioral rounds. The free tier is permanent: 15 minutes a day, no credit card.
Try it free