Site Reliability Engineer (Cloud & Platform Reliability)

Site Reliability Engineer (Cloud Platform Reliability)

Location: Hyderabad

Working Hours: Pacific Time (PST/PDT), aligned with US West Coast

Role Overview

We are growing our Site Reliability Engineering team with a Senior Officer, Site Reliability Engineer who will help make the cloud platforms behind our products measurably more reliable. Our SRE team brings together engineers who care about instrumentation, incident response and the health of production systems, all working toward a common mission: giving product and engineering teams the observability, guardrails and operational practices they need to run their services with confidence.

This role is for an SRE who comes from a cloud and platform engineering background. You will spend your time where reliability meets infrastructure: operating Kubernetes clusters (EKS and AKS) and the workloads on them, managing cloud infrastructure across AWS and Azure through Terraform, and building the observability and automation that keep it all healthy. Expect to work on autoscaling and capacity, cluster and cloud networking, resilience and failover, cost and performance tuning, and the automation that removes repetitive operational work, then prove the results with SLOs rather than assertions.

Our platform runs around the clock and so does the team behind it. On-call coverage moves naturally across time zones as the day progresses. This position anchors the US West Coast (PST/PDT) window of that follow-the-sun rotation, and as part of it you should expect to step in on weekends from time to time.

This is a strong fit for an experienced individual contributor who enjoys hands-on infrastructure work, both building and running it, and wants to deepen their expertise in site reliability engineering within a regulated financial services environment.

On-Call Coverage

On-call is a core, ongoing part of this role and not an occasional add-on. Please read this section carefully before applying.

• Your standard working hours align with Pacific Time (PST/PDT) and cover the US West Coast business day from our Hyderabad office.
• You will take part in a shared on-call rotation with the wider SRE team, following a follow-the-sun model in which coverage hands over between regions as each working day ends.
• While on rotation you are expected to be reachable, to acknowledge and respond to pages within the agreed response targets, and to drive or support incidents through to resolution and handover.
• Weekend and public holiday coverage is part of the rotation and comes around periodically; you should expect to step in from time to time.
• Escalation and paging run through PagerDuty. You will help keep escalation policies, schedules and alert routing accurate and low-noise.
• After significant incidents you will take part in blameless postmortems and follow through on the resulting action items.

What You'll Do

Build: Observability, Automation Reliability Tooling

• Build and maintain the observability stack that the organization relies on: OpenTelemetry collectors and pipelines, Prometheus-based metrics, and Grafana dashboards for platform and workload health.
• Define and implement SLIs, SLOs and error budgets for platform services, and make burn-rate alerting the basis of paging where it fits.
• Improve alert quality: remove duplicate and low-value alerts, tighten thresholds, add runbook links and make sure every page is actionable.
• Build and maintain PagerDuty integrations, services, escalation policies and schedules so that alerts reach the right people with the right context.
• Build and maintain infrastructure-as-code (e.g., Terraform) so that reliability controls, monitoring and environments are provisioned consistently and repeatably.
• Maintain GitOps-based deployment workflows using tools such as Helm, Flux or ArgoCD, and keep reliability configuration versioned alongside the platform it describes.
• Write code and automation (e.g., Python, Go, Bash) to reduce toil, automate recurring operational tasks and remove manual steps from routine platform work.
• Use AI-assisted tools (e.g., coding assistants, infrastructure and incident copilots) in your own day-to-day work and help other engineers adopt AI tooling effectively.

Operate: Incident Response Production Ownership

• Monitor platform health, respond to incidents and take part in our on-call rotation, including occasional weekend coverage.
• Act as incident responder and, where needed, incident commander: triage, coordinate responders, communicate status and drive to mitigation.
• Debug production issues across the platform, including node and pod-level failures, scheduling and eviction problems, resource saturation, ingress and DNS issues, certificate expiry, and degraded cloud services.
• Operate and tune our EKS and AKS clusters, including autoscaling (Karpenter or Cluster Autoscaler, KEDA/HPA) and cluster networking (CNI, ingress, workload identity).
• Run blameless postmortems, identify contributing causes and track corrective actions to completion.
• Support disaster recovery efforts, including backup and restore testing and failover exercises, to validate platform resilience.
• Contribute to capacity planning, cost optimization and performance tuning across cloud environments.
• Help maintain security and compliance controls across the platform (access management, network security, audit evidence, policy-as-code) in line with financial services requirements.

Engineering: Resilience Platform Hardening

• Design for failure: multi-AZ and multi-region posture, pod disruption budgets, graceful degradation, safe rollout and rollback patterns.
• Review infrastructure and deployment changes from a reliability standpoint, and raise the bar on defaults, quotas, limits and guardrails.
• Identify recurring sources of instability and toil, and drive systemic fixes rather than repeated manual intervention.
• Make platform reliability visible: capacity headroom, saturation, error budgets and cost per workload.