ML Ops Technical Specialist - DevOps, Python
ML Ops Technical Specialist - DevOps, Python
Posted 13 days ago
SENIORITY
Senior
About the role
- Architect and implement ML Ops solutions using Python, MLflow, Kubeflow Pipelines, and TFX to automate model training, deployment, and monitoring processes.
- Design and manage CI/CD pipelines for ML projects utilizing Jenkins, GitLab CI/CD, CircleCI, and GitHub Actions to ensure seamless integration and delivery of machine learning models.
- Develop infrastructure-as-code templates with Terraform and AWS Cloud
- Formation to provision and manage scalable cloud environments for ML workloads.
- Integrate monitoring and logging solutions using Prometheus, Grafana, ELK Stack, and Fluentd to enable real-time performance tracking and issue resolution for ML systems.
- Lead the adoption of DevOps practices by configuring version control systems such as Git, GitHub, GitLab, and Bitbucket for collaborative development and reproducibility.
- Serve as a technical SME for ML Ops, providing guidance on best practices, tool selection, and workflow optimization within the team.
- Mentor and train team members on ML Ops tools, automation strategies, and cloud-native ML pipeline development to build technical capability and mitigate delivery risks.
- Review and validate project deliverables to ensure alignment with client specifications, quality standards, and industry benchmarks.
- Recommend and implement client-focused value creation initiatives by leveraging advanced ML Ops frameworks and industry best practices.
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.
