Machine Learning Engineer
Owns: Model development, the feature and data pipeline it depends on, training and evaluation, productionization, inference and monitoring, with software engineering discipline throughout.
Production signals we look for
- A model they trained that is still serving traffic, and what happened when it drifted
- Feature pipelines they built or debugged, not only consumed
- Evaluation beyond a single offline metric: slices, baselines, online checks
- Inference constraints they solved: latency, batch vs real time, cost
Resume signals that mislead
- Kaggle or course projects listed as production experience
- Framework lists with no system attached
- Team-level outcomes claimed as personal ownership
How NeoIntelli evaluates
- Walk through one system end to end: data, model, deployment, monitoring
- Trade-off questions on feature freshness, retraining cadence, serving
- Code and design review on a realistic problem
- Reference-style questions on what broke and who fixed it