ML DevOps Engineer
reuben cooleyEvanston (IL)
ML DevOps Engineer
Posted yesterday
reuben cooleyEvanston (IL)
SENIORITY
Senior
About the role
We are looking for an ML DevOps Engineer to build and run the pipelines and infrastructure that take machine learning and AI models from development into production. You'll work with data scientists, engineers and platform teams to make sure models are deployed reliably, monitored well and kept secure as they scale. Experience 5+ years overall, with 3+ years in MLOps or DevOps for machine learning and AI workloads
Required Skills:
- Strong hands-on experience with at least one major cloud platform: AWS, Azure or GCP.Experience with MLOps tools such as MLflow, Kubeflow, SageMaker, Azure ML or Databricks.
- Skilled with Docker and Kubernetes.
- Experience with CI/CD tools such as Jenkins, GitHub Actions, GitLab CI or Azure DevOps.
- Infrastructure as Code with Terraform, Cloud
- Formation or similar tools.
- Good scripting skills in Python and Bash.
- Experience with monitoring and observability tools such as Prometheus, Grafana, Datadog or CloudWatch.
- Good understanding of the ML lifecycle and how models are served in production.
- Good to Have Skills
- Experience deploying and running Generative AI or LLM-based applications, including API gateways and model serving.
- Cloud certifications such as AWS DevOps or ML Specialty, or Azure DevOps Engineer.
- Exposure to finance or other regulated industries.
- Experience in large enterprise or client-facing consulting settings.
Roles & Responsibilities:
Design, build and maintain CI/CD pipelines for ML and AI models.
Automate model training, testing, deployment and rollback.
Set up and manage cloud infrastructure for model hosting and serving.
Containerize models and services, and manage them on Kubernetes or similar platforms.
Put monitoring in place for model performance, data drift, latency and cost.
Manage model versioning, experiment tracking and the model registry.
Work with data science teams to make models production-ready.
Apply security, access control and compliance standards across ML environments.
Troubleshoot production issues and support reliable, always-on operations.
Document processes and promote best practices across teams.
Before you apply
Applying takes about a minute. These four things decide how fast it moves after that.
Your profile is current
It's what we read first. Occupations, seniority and locations matter more than a long history.
Two examples you can talk through
Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.
A number in mind
What you're on now and what would make you move. We negotiate better when we know both.
Your notice period
Employers plan around it, and it's the question that stalls offers most often.
Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.