Technical screening questions
Ask for one example per question and listen for specifics.
- How do you detect model drift? A good answer: Monitoring input distributions and performance against labels.
- How do you prevent training-serving skew? A good answer: Shared feature code and a feature store.
- How do you choose an evaluation metric? A good answer: Tie it to the business cost of errors and class balance.
- How do you deploy a model with low latency? A good answer: Batching, model size, caching and hardware choices.
- Describe a model you shipped and how you monitored it. A good answer: Production ownership, not only notebooks.
Quick screening questions
Use these when you have only a few minutes.
- Which model did you take to production and how do you monitor it?
- How do you detect and handle drift?
- Describe your experience with LLM applications.
What separates the levels
Match the level to the requirement before you submit.
- Junior: trains models with guidance.
- Mid: ships and monitors models.
- Senior: designs the ML platform and standards.
Red flags
Any of these is a reason to probe further.
- Only notebook experience.
- Cannot explain overfitting.
- No deployment work.
Tools you should hear mentioned
A machine learning engineer with real experience usually names several of these without prompting.
- Python
- PyTorch or TensorFlow
- scikit-learn
- MLflow
- Docker and Kubernetes
- A cloud ML service
Run the call well
Ask for the last project first, then dig into the second or third question. Take notes on versions, team size and outcomes, and record them with the submission so the vendor’s later technical interview does not surprise you.
Frequently asked questions
How long should a machine learning engineer screening call take?
Fifteen to twenty minutes is enough to cover the project, three technical questions and availability, rate and work authorization.
Do recruiters need to know the technology?
Working vocabulary is enough. Use the sourcing guide for the role and listen for specifics instead of judging technical depth yourself.