ML Ops Engineer, Chanakya
Sarvam AI Β· DelhiOverview
Own model serving infrastructure, deployment pipelines, and observability for AI systems at Sarvam AI.
Skills
Responsibilities
- Design and operate model serving infrastructure across cloud and on-prem
- Build CI/CD pipelines for evaluation-gated model deployments and rollbacks
- Monitor production model performance for latency, drift, and throughput
- Manage containerised model serving in constrained and air-gapped environments
- Own incident response and operational runbooks for model-layer failures
Requirements
- 3-5 years in ML engineering or MLOps with production systems
- Expertise in model serving tools like vLLM, TGI, or Triton
- Containerisation experience with Docker and Kubernetes or edge alternatives
- Observability experience using Prometheus and Grafana
- Python fluency with CI/CD tooling for ML pipelines
About Sarvam AI
Sarvam builds sovereign AI models and platforms for India.
What to prepare
Full job post Β· as written by Sarvam AI
About Sarvam
Sarvam is building the bedrock of Sovereign AI for India. The company is developing India's full-stack sovereign AI platform, building across research, models, infrastructure and applications with a singular focus on making AI genuinely work for India. Sarvam works with leading enterprises and public institutions and is backed by Lightspeed, Peak XV, and Khosla Ventures. Sarvam partners with India's leading brands, including Tata Capital, SBI Life, CRED, IDFC, and LIC.
About the Role
The MLOps Engineer owns the model lifecycle across all defence and strategic sector deployments β from serving infrastructure and monitoring to evaluation pipelines and environment management. You ensure the system is always on, always accurate, and always auditable.
You will work across both layers: supporting Strategic Deployment Engineers in the field, and owning the model deployment infrastructure for new products being built by the product engineering team. The standards here are uncompromising β a model failure is not a UX problem, it is an operational risk.
What You'll Do
- Design and operate model serving infrastructure across on-prem and cloud deployments
- Build and maintain CI/CD pipelines for model updates, rollbacks, and evaluation-gated deployments
- Monitor model performance in production β latency, accuracy drift, throughput, failure modes β and build systems that surface issues before clients do
- Build evaluation infrastructure: harnesses, A/B testing, and model comparison tooling for field and lab use
- Manage containerised model serving in constrained, air-gapped, and edge environments
- Collaborate with Data Scientists on eval pipelines; own the infrastructure layer underneath
- Create runbooks and operational playbooks that Strategic Deployment Engineers can use in the field
- Own incident response for model-layer failures across all active deployments
What We're Looking For
- 3β5 years in ML engineering or MLOps with at least one production LLM or ML system in continuous operation
- Deep expertise in model serving: vLLM, TGI, Triton Inference Server, or equivalent; experience with quantised model formats (GGUF, AWQ, GPTQ)
- Experience fine-tuning and adapting models in constrained, on-prem, or air-gapped environments, including managing data pipelines and compute limitations specific to the environment
- Containerisation experience with Docker, Kubernetes, or lightweight alternatives (K3s, K0s) for constrained and edge environments; familiarity with deploying across heterogeneous hardware and infrastructure configurations
- Monitoring and observability using Prometheus, Grafana, or equivalent; ability to build custom eval dashboards
- Python fluency; familiarity with fine-tuning workflows and model evaluation frameworks
- Hands-on experience with CI/CD tooling for ML pipelines: GitHub Actions, ArgoCD, DVC, or similar
Signals We Look For
- You've kept a production ML system running under load β and debugged it when it broke
- You don't wait for things to fail; you build systems that tell you when they're about to
- You write documentation that actually gets used, by people who aren't you
Who You Are
- You treat uptime and correctness as equally non-negotiable
- You understand that operational reliability is a form of trust-building
- You're as comfortable optimising inference throughput as you are writing a field runbook for a deployment engineer
- You take ownership of modelβ¦