DevOps / SRE Engineer

About the role

We look after platforms that other businesses run on — production floors, hospitals, call centres. When something breaks at 2 a.m., someone's operations stop. This role exists to make that rare, and to make the recovery boring when it does happen.

What you will do

• Build and run deployment pipelines that let engineers ship on a Tuesday afternoon without ceremony.
• Manage infrastructure as code across AWS and Azure — no console clicks that nobody can reproduce.
• Own observability: metrics, structured logs, tracing and alerts that fire on symptoms customers feel, not on CPU noise.
• Run backup and disaster recovery for client environments, including the restore drills that prove it works.
• Harden what we operate: least-privilege access, secret rotation, patch cadence, network segmentation.
• Lead incident response, then write the post-mortem that stops it recurring — blameless, and actually read.
• Right-size infrastructure. Cloud cost is a client's money, and we treat it that way.

What we are looking for

• 3–7 years in DevOps, SRE or platform engineering with production on-call experience.
• Solid Linux fundamentals — you can debug a box, not just restart it.
• Docker and Kubernetes in anger, plus Terraform or an equivalent IaC tool.
• CI/CD with GitHub Actions, GitLab CI, Azure DevOps or Jenkins.
• Scripting in Bash and Python or Go.
• A monitoring stack you have actually operated: Prometheus, Grafana, CloudWatch, the ELK stack or similar.
• Calm judgement during an incident, and the discipline to write it up afterwards.

Nice to have

• Hyper-V or VMware, and backup tooling such as Altaro.
• Cloud certification (AWS SA, Azure Administrator) — useful, not required.
• Database operations: PostgreSQL or SQL Server tuning, replication and failover.

What we offer

• ₹15–26 LPA depending on experience, reviewed annually.
• On-site at Baner, Pune, with a compensated and genuinely shared on-call rotation.
• Health cover for you and your immediate family.
• Certification and training budget.
• Authority to fix the root cause, not just clear the alert.

Interview process

1. An introductory conversation about the systems you have run.
2. A practical troubleshooting session on a realistic broken environment.
3. An architecture discussion on availability, backup and cost for a client scenario.
4. A closing conversation on team fit and offer.