Role Summary
The Lead DevOps Engineer is a senior technical leader responsible for one or more enterprise delivery domains—such as CI/CD pipeline platform architecture, IaC standard module libraries, and Kubernetes operational patterns.The role strengthens developer productivity, resilience, security posture, and automation maturity, while ensuring alignment with Platform, Security, and DBA teams on patterns, dependencies, and release sequencing.
Core Contribution Scope
· Leads DevOps domain(s) and sets the technical direction for enterprise delivery capabilities.
· Defines standards, guardrails, and reference architectures for CI/CD, IaC, and Kubernetes operations.
· Orchestrates cross-team delivery programs and drives large-scale improvements across pipeline platforms, infrastructure automation, and cluster operations.
Key Responsibilities
· Own and maintain domain roadmaps (e.g., Jenkins platform upgrades, Terraform/CloudFormation/ARM/Bicep module strategy, Kubernetes SLOs and add-on standards).
· Define reference architectures for CI/CD topologies, artifact and versioning practices, secrets management, policy-as-code, and environment promotion workflows.
· Lead major cross-team DevOps initiatives, including pipeline re-platforming, IaC modernization, fleet-wide upgrades, and cluster standardization.
· Serve as an escalation point for major delivery or platform incidents; lead PIRs and ensure systemic fixes.
· Influence organizational prioritization across product, platform, security, and database stakeholders.
· Ensure DevOps architectures comply with enterprise security, governance, audit, and operational risk requirements.
---
Typical Outputs
· Adopted DevOps standards, guardrails, and domain roadmaps across engineering teams.
· A highly secure, reliable, cost-efficient CI/CD and Kubernetes delivery platform.
· Measurable improvements in engineering performance (e.g., DORA metrics, pipeline SLOs, change failure rate).
· Executive-ready materials—risk registers, issue logs, dependency maps, and architecture decision records.
Required Experience (DevOps + SRE Background)
Candidates must demonstrate strong hands-on experience across Azure and AWS environments and modern DevOps/SRE engineering practices:
Cloud & Platform Experience
· 5–10+ years in DevOps and SRE roles supporting Azure or AWS enterprise environments.
· Strong understanding of cloud architecture concepts (landing zones, identity integration, networking, IAM, security baselines).
CI/CD & Pipeline Engineering
· Extensive experience designing and maintaining CI/CD pipelines using:
o Jenkins (Enterprise / scalable controllers)
o Azure DevOps Pipelines
o GitHub Actions
· Expertise in:
o Pipeline governance
o Artifact/versioning strategies
o Environment promotion
o Automated quality and security gates
Infrastructure-as-Code (IaC)
· Deep expertise in:
o Terraform (preferred enterprise standard)
o CloudFormation (AWS)
o ARM/Bicep (Azure)
· Experience building reusable IaC module libraries, enforcing policy-as-code, and orchestrating infrastructure deployment at scale.
Automation & Configuration Management
· Strong experience with:
o Ansible (playbooks, baselines, configuration standards)
o Bash/Python automation
o Desired State Configuration (DSC) is a plus
Kubernetes & Container Platforms
· Working knowledge of Kubernetes clusters (AKS, EKS), including:
o Cluster add-ons and extensions
o Secrets management
o Networking policies
o Policy engines (OPA/Gatekeeper/Kyverno)
o GitOps (ArgoCD/FluxCD) is highly desirable
SRE & Operational Engineering
· Hands-on experience in:
o Incident response & root-cause analysis
o Observability (Prometheus/Grafana/ELK/Azure Monitor/CloudWatch)
o SLO design, reliability engineering, autoscaling patterns
· Experience reducing MTTR and improving system reliability across complex environments.
Additional Expectations
· Ability to influence cross-functional teams, lead modernization programs, and define enterprise-wide engineering patterns.
· Strong documentation, decision-making, and communication skills.