Lead DevOps Engineer

We're looking for a DevOps Lead to own our AWS-based infrastructure end-to-end and build out the team around it. Today, that means a small team and a clear scope. As we grow, this becomes the foundation for a larger DevOps group, so we're looking for someone who can run things hands-on now and help shape what the function becomes.

Responsibilities:

• Infrastructure, end-to-end: Multi-environment architecture, containers and orchestration, release pipelines, runtime reliability, and cloud cost.
• Reliability and SRE practice: SLOs that reflect what users actually experience, observability that surfaces problems before customers report them, and an on-call rotation that doesn't burn people out. You'll run an incident command when things break and lead the review afterward. We'd like our reliability numbers to improve under you: fewer incidents, faster recovery, and less firefighting.
• Automation: Identifying automation opportunities where there are repetition patterns: provisioning, deployments, environment creation, rollbacks, and routine ops. The aim is a team that spends its time building rather than repeating itself.
• AI-native operations: We want agents to be part of how the team works day to day, not a side project. Incident triage and log analysis, IaC generation and review, cost anomaly detection, and runbook execution. You'd decide what agents can do in production, what needs human approval, and how their actions get logged.
• Infrastructure security. You'll work closely with our security engineering team, and the infrastructure side is yours to execute: IAM and least privilege, secrets management, secure
• Terraform defaults, security gates in CI/CD, patching, and image lifecycle. You'll also be involved when something in the infrastructure needs investigating.
• Team and direction. Hiring, growing, and supporting a small team of DevOps engineers, plus the infrastructure roadmap: what we build, what we buy, what we retire, and what it costs.

Requirements:

• 6-10 years in DevOps, SRE, or platform engineering, including time leading a team.
• You've owned a complete infrastructure boundary; a horizontal platform or a business vertical either works. What matters is that it was substantial, consumer-facing, and carried real traffic.
• Infrastructure at consumer scale: high-volume production systems with meaningful traffic peaks, where downtime is visible to customers and latency is a product problem.
• Strong hands-on AWS, Kubernetes, Terraform, CI/CD, and observability tooling.
• Hands-on security understanding of AWS infrastructure, IAM, KMS, Secrets Manager, network controls, and secure IaC.
• You've hired DevOps engineers and helped them grow.
• You already use agentic tooling in your daily work and have shipped something with it in a DevOps context.
• You've owned a cloud bill and brought it down without hurting reliability.

Nice to have:

• GPU infrastructure: provisioning, scheduling, utilization.
• LLM gateway operations: routing, rate limits, cost attribution, provider failover.
• Experience in a regulated environment (RBI digital lending, DPDP, PCI-DSS).
• You've scaled a DevOps function through a period of fast growth.