Lead DevOps Engineer

About the role

Lead DevOps Engineer

As a Lead DevOps Engineer at Particle41, you will own the DevOps strategy and the design, automation, and operation of the cloud infrastructure that powers our clients’ most complex digital projects. Working closely with cross-functional teams, you will champion DevOps culture and practices, set the standards other teams build on, and ensure the delivery of innovative and high-quality projects. Your role will also involve mentoring and coaching team members, fostering a culture of collaboration, automation, and continuous learning.

In This Role, You Will:

Strategy & Practice Ownership

- Own the DevOps technical roadmap and vision, in collaboration with architects and stakeholders, and align it with business goals.

- Define the "golden path": reference architectures, reusable IaC modules, pipeline templates, and standards that teams across projects adopt.

- Be accountable for platform reliability, security posture, and delivery velocity outcomes across the engagements you lead; measured through SLOs, not just activities performed.

- Represent the DevOps practice with clients: participate in discovery and pre-sales conversations, estimate and scope infrastructure workstreams, and advise client leadership on cloud and platform decisions.

- Contribute to growing the practice interview and assess DevOps candidates, and help shape team structure and capability development.

Infrastructure & Platform Engineering

- Lead the design and implementation of cloud infrastructure across AWS, Azure, and GCP using infrastructure-as-code tools such as Terraform, CloudFormation, or Pulumi.

- Architect and operate container platforms, including Kubernetes (EKS, AKS, GKE) and managed container services, to support scalable, resilient workloads.

- Define landing zones, account/subscription structures, and network topologies that balance security, cost, and developer velocity.

- Evaluate and recommend platform tooling and managed services to support business requirements.

CI/CD & Automation

- Own the CI/CD strategy and pipeline architecture (e.g., GitHub Actions, GitLab CI, Azure DevOps, Jenkins) that makes releases fast, repeatable, and safe across teams.

- Drive an automation-first culture across build, test, deployment, and environment provisioning — setting the standard for eliminating manual toil, and staying hands-on where it matters most.

- Establish GitOps workflows (e.g., ArgoCD, Flux) for declarative, auditable deployments.

Reliability & Observability

- Define the observability strategy - monitoring, logging, and tracing (e.g., Prometheus, Grafana, Datadog, CloudWatch, OpenTelemetry) and drive its adoption across teams.

- Own SLIs, SLOs, and error budgets in partnership with engineering and product teams, and hold teams accountable to them.

- Own incident response, on-call practices, and blameless post-incident reviews to continuously improve system resilience.