Staff Devops Engg

Responsibilities

• Then you'll build those systems and make sure they keep working after you move on to the next problem.

Architecture

• Set the long-term direction for LeadSquared's cloud infrastructure across all products and environments through design documents and Architecture Decision Records (ADRs).
• Lead migrations from today's estate to a standardised platform without customer impact.
• Infrastructure as Code
• Bring all infrastructure under reviewed code with safe change practices, including PR-driven plan and apply, policy as code, drift detection, and production guardrails.
• Runtime and Delivery
• Own the compute, Kubernetes, and CI/CD platforms so that shipping a service or onboarding a tenant becomes self-service.
• Reliability
• Define SLOs, own observability, lead major incidents and postmortems, and regularly test disaster recovery.

Security and Compliance

• Enforce least-privilege access, secrets management, and encryption by default.
• Support audits through automated evidence collection.
• Cost Optimisation
• Treat cloud spend as an engineering metric, with visibility into costs per product, tenant, and service.
• Leadership
• Mentor engineers, represent CloudOps to product teams, and eliminate operational toil through automation.

Requirements

• Minimum Qualifications 10+ years of experience in DevOps, SRE, infrastructure, or platform engineering, with clear ownership of production systems at meaningful scale.
• Deep, hands-on AWS expertise, including multi-account organisations, networking, IAM, compute, containers, managed data services, and edge delivery.
• Expert-level Infrastructure as Code experience with Terraform or equivalent tools, including designing reusable modules and structuring code across multiple environments.
• Expert-level Kubernetes experience in production, including cluster upgrades, autoscaling, networking, RBAC, and debugging under pressure.
• Production experience with CI/CD and GitOps practices.
• Experience running and migrating a large, existing production estate, not just building greenfield environments.
• Strong programming or scripting skills in at least one language, with the ability to build production-grade tooling.
• A track record of leading incidents, writing postmortems, and delivering the reliability improvements that follow.
• Proven ability to write clear technical documents and influence decisions across teams without formal authority.

Preferred

• Experience designing or operating highly available, active-active, or disaster recovery (DR) architectures in the cloud.
• Experience leading large-scale migrations, such as moving from virtual machines to containers, with zero or near-zero customer impact.
• Experience building an observability practice with SLOs and error budgets.
• Experience with policy as code and software supply chain security.
• Experience with multi-tenant SaaS platforms, including tenant isolation models, per-tenant routing, and capacity management.
• FinOps experience with demonstrable cloud cost reductions.
• Contributions to open-source infrastructure tooling or public speaking and writing on platform engineering.

What Success Looks Like

• First 90 Days Understand LeadSquared's infrastructure end to end across products, accounts, and environments, and join the on-call and incident commander rotation.
• Deliver at least one meaningful improvement to change safety or developer experience across teams.
• Produce a written assessment of the platform's top reliability, security, and cost risks, along with a proposed roadmap.
• First Year New environments can be provisioned from code in days, not weeks.
• Most production infrastructure is managed as code and changed only through reviewed pull requests.
• SLOs are defined for critical customer journeys, alerting is driven by them, and error budgets inform release decisions.
• Disaster recovery has been tested end to end, with documented results.
• Cloud spend per unit of load is measurably lower.
• At least two engineers on the team are operating at the next level as a result of your mentorship.

How We Work

Everything is code, everything is reviewed: Infrastructure changes go through pull requests, plans are visible, and production applies are deliberate.

Standards over snowflakes

One consistent way to build an environment, deploy a service, and manage observability.

Blameless by default

Incidents are opportunities to improve systems, not to blame people.

Writing is how we decide

Design documents and Architecture Decision Records (ADRs) come before major changes.

Equal opportunity

• LeadSquared is an equal opportunity employer.
• We welcome candidates from all backgrounds and do not discriminate on the basis of gender, religion, caste, disability, sexual orientation, or any other protected characteristic.