Back to jobs

Lead DevOps/MLOps Engineer

Pay
Pay not listed
Work setting
Remote — work setting source
Work setup in the employer’s posting: TELECOMMUTE
From the employer’s posting
Employment
Not stated

What you’ll work on

Full posting
  • Troubleshoot GPU resource bottlenecks and latency across production and dev workloads

  • Deploy and maintain the NVIDIA GPU Operator and manage GPU resources on Kubernetes and OpenShift

  • Implement GPU sharing and isolation to optimize memory and fault isolation

  • Scale the GPU environment as new H200 servers are added

  • Manage GPU monitoring with DCGM exporter, Prometheus and Grafana

From the employer’s posting
Troubleshoot and resolve daily resource bottlenecks and latency issues across competing production and development use cases
Deploy and maintain the NVIDIA GPU Operator and manage GPU resources across Kubernetes and OpenShift clusters
Implement GPU sharing and isolation strategies to optimize memory and fault isolation across workloads
Scale the GPU environment to accommodate growing compute demands as new H200 servers are added
Manage monitoring pipelines using NVIDIA DCGM exporter, Prometheus and Grafana to track GPU utilization and performance

Tools in this posting

  • Grafana
  • Kubernetes
  • MLflow
  • Airflow
Source — Tool mentions in context
We are looking for a Lead DevOps/MLOps Engineer to join our Data Science Department and work with the ML Engineering team to build out and harden our on-premises, GPU-backed ML platform. In this role, you will help enable multiple ML and LLM use cases to run simultaneously, reliably, and with low latency, while scaling the platform to support a wider user base across the organization. Responsibilities Build and harden the on-premises GPU-backed ML platform to support concurrent ML and LLM workloads Troubleshoot and resolve daily resource bottlenecks and latency issues across competing production and development use cases Deploy and maintain the NVIDIA GPU Operator and manage GPU resources across Kubernetes and OpenShift clusters Implement GPU sharing and isolation strategies to optimize memory and fault isolation across workloads Scale the GPU environment to accommodate growing compute demands as new H200 servers are added Maintain and improve platform services such as MLflow and the Agent Gateway Manage monitoring pipelines using NVIDIA DCGM exporter, Prometheus and Grafana to track GPU utilization and performance Collaborate with the Deep Learning and Traditional ML teams to support shared infrastructure, including Ray-based training workloads Ensure platform reliability and security given the confidential and sensitive nature of data handled on-premises Partner with the Data Analytics team to support the in-house agentic platform as it scales to a broader employee base Requirements 5+ years of experience running GPU workloads on Kubernetes or OpenShift in production, ideally on-premises Practical experience deploying and troubleshooting the NVIDIA GPU Operator, with clear understanding of each component's function Understanding of how GPUs differ from CPUs as a scheduled resource, including memory limits, utilization semantics and scheduling limitations Knowledge of GPU sharing and isolation methods such as MIG, time-slicing and MPS, along with their trade-offs Solid Linux fundamentals, including cgroups, namespaces, systemd resource controls and process-level resource management Experience with Prometheus, Grafana and NVIDIA DCGM, including GPU metrics at process or pod level Working knowledge of the CUDA stack, including drivers, CUDA toolkit and container runtime version compatibility Experience deploying with Helm and operating MLOps tools such as MLflow and Airflow on Kubernetes Nice to have Familiarity with LLM serving engines such as vLLM, SGLang or NVIDIA Triton Experience with Ray, KubeRay and GPU-aware schedulers such as Kueue or Volcano Hands-on work with H100/H200-class hardware and GitLab CI
Check the employer’s page ↗

Posting record

Report an error

Actively hiringFirst seen by us 11 days ago, still listed, and not a repost of an earlier posting.

Status in our records
Live
First seen by us
Nov 11, 202611 days ago
Recorded sightings
10
Last seen by us
Nov 21, 2026

These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.

How this job compares

Time since we first saw it

Day 11

Similar jobs usually come down between day 7 and day 76.

From 6,398 similar postings that came down. Coming down is not always a hire.

EPAM Systems is hiring

892 open jobs

Open jobs by the week we first saw them, last 12 weeks.

Hiring record

Your next step

Check the employer’s posting for the current role and application details.

Already applied? Track this application

Has EPAM Systems posted this job before?

Yes. We’ve followed 3 other Lead DevOps/MLOps Engineer jobs there since November 2026. All 3 are still up.

  1. Place not statedStill up after 20 days, first seen Nov 1
  2. Place not statedStill up after 20 days, first seen Nov 2
  3. Place not statedStill up after 11 days, first seen Nov 11
  4. This jobUp 11 days so far, first seen Nov 11

Large employers often post one title for several teams, so these can be separate openings.

Job description

View original posting ↗

We are looking for a Lead DevOps/MLOps Engineer to join our Data Science Department and work with the ML Engineering team to build out and harden our on-premises, GPU-backed ML platform. In this role, you will help enable multiple ML and LLM use cases to run simultaneously, reliably, and with low latency, while scaling the platform to support a wider user base across the organization. Responsibilities Build and harden the on-premises GPU-backed ML platform to support concurrent ML and LLM workloads Troubleshoot and resolve daily resource bottlenecks and latency issues across competing production and development use cases Deploy and maintain the NVIDIA GPU Operator and manage GPU resources across Kubernetes and OpenShift clusters Implement GPU sharing and isolation strategies to optimize memory and fault isolation across workloads Scale the GPU environment to accommodate growing compute demands as new H200 servers are added Maintain and improve platform services such as MLflow and the Agent Gateway Manage monitoring pipelines using NVIDIA DCGM exporter, Prometheus and Grafana to track GPU utilization and performance Collaborate with the Deep Learning and Traditional ML teams to support shared infrastructure, including Ray-based training workloads Ensure platform reliability and security given the confidential and sensitive nature of data handled on-premises Partner with the Data Analytics team to support the in-house agentic platform as it scales to a broader employee base Requirements 5+ years of experience running GPU workloads on Kubernetes or OpenShift in production, ideally on-premises Practical experience deploying and troubleshooting the NVIDIA GPU Operator, with clear understanding of each component's function Understanding of how GPUs differ from CPUs as a scheduled resource, including memory limits, utilization semantics and scheduling limitations Knowledge of GPU sharing and isolation methods such as MIG, time-slicing and MPS, along with their trade-offs Solid Linux fundamentals, including cgroups, namespaces, systemd resource controls and process-level resource management Experience with Prometheus, Grafana and NVIDIA DCGM, including GPU metrics at process or pod level Working knowledge of the CUDA stack, including drivers, CUDA toolkit and container runtime version compatibility Experience deploying with Helm and operating MLOps tools such as MLflow and Airflow on Kubernetes Nice to have Familiarity with LLM serving engines such as vLLM, SGLang or NVIDIA Triton Experience with Ray, KubeRay and GPU-aware schedulers such as Kueue or Volcano Hands-on work with H100/H200-class hardware and GitLab CI

About EPAM Systems

People
About 3,012 in 2024.Benefit plan filings (Form 5500)
Company
Listed as EPAM.
H-1B visas
21 approved for new hires in fiscal 2025.US Citizenship and Immigration Services

Demand for ML Engineer roles

New ML Engineer postings at the employers we follow are down 4% over the last 6 weeks compared with the 6 before.

Weekly new ML Engineer postings at the same employers, from the week of August 17 to the week of November 9. The fewest in a week was 508, the most 899, and the latest week had 508.
August 17Last week

Each bar is one week of new postings. The darkest bars are the last 6 weeks.

Counted from the hiring pages we’ve followed for at least five weeks, so employers we add don’t look like growth. Updated weekly.

About the role

We file this job under ML Engineer, by the work the posting describes.

ML engineers put machine learning models into products. They write the code that trains, ships, serves and monitors models so a recommendation or prediction works for real users.

Postings ask for strong Python and software engineering, a framework such as PyTorch, cloud services, and more and more often experience with large language models.

A data scientist often works out which model to build; an ML engineer makes it run reliably in production.

US government figures for computer and information research scientists

Median yearly pay, May 2025
$140,300
Expected change, 2025 to 2035
21.8% more jobsagainst 3.5% for all jobs

The government has no code for ML engineers, so these figures are for the closest group, computer and information research scientists.

Source: US Bureau of Labor Statistics, Occupational Employment and Wage Statistics (May 2025) and Employment Projections (2025 to 2035). Occupation code 15-1221.

Source details

View original posting ↗

Source notes

Source excerpts

Selected passages from the saved posting. Check the full description for conditions and exceptions.

Pay

No pay amount identified in the saved description.

Location & working pattern

Location not supplied.

Working pattern and location restrictions need checking in the full posting.

Work authorization

No clear work-authorization passage found. Eligibility is unconfirmed.

AI answers unavailable

We couldn’t identify enough role detail in this saved description to support an AI answer. Read the full posting