Site Reliability Engineer (Application Reliability)

Site Reliability Engineer (Application Reliability)

Location: Hyderabad

Working Hours: GMT/BST, aligned with London

Job Level: Senior Officer

Job Summary

We are growing our Site Reliability Engineering team with a Senior Officer, Site Reliability Engineer who will help make the applications and services 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 an application engineering background. You will spend your time close to the code and the telemetry it produces: instrumenting services with OpenTelemetry, building the dashboards, SLOs and alerts that tell us when something is wrong, and digging into application behaviour when it is. Expect to read and debug code in a stack such as .NET, Java, Node.js or Python, follow a request through HTTP, gRPC, queues and databases, and work out where latency, errors or resource exhaustion are actually coming from, then work with the owning team to fix it properly rather than restart it again.

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 London (GMT/BST) 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 has built and operated production software, enjoys the discipline of measuring reliability rather than guessing at it, and wants to deepen their expertise in site reliability engineering within a regulated financial services environment.

On-Call Coverage Expectations

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 London (GMT/BST) and cover the European 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 Youll Do

Build: Observability Reliability Engineering

• Instrument applications and services with OpenTelemetry (traces, metrics and logs), including SDK-based and auto-instrumentation, correct context propagation and sensible attribute and cardinality choices.
• Build and maintain Grafana dashboards and Prometheus-based metrics, recording rules and alerts that reflect real user-facing behaviour rather than raw infrastructure noise.
• Define and implement SLIs, SLOs and error budgets with product engineering teams, 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.
• Write code and automation (e.g., Python, Go, Bash, or your primary application language) to reduce toil, automate recurring operational tasks and codify observability configuration.
• Use AI-assisted tools (e.g., coding assistants, observability and incident copilots) in your own day-to-day work and help other developers adopt AI tooling effectively.

Operate: Incident Response Production Ownership

• Monitor service 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 in the application layer, including latency and error-rate regressions, memory and garbage-collection pressure, thread and connection pool exhaustion, retry storms, timeouts and cascading failures.
• Investigate data-layer problems alongside application code: slow queries and query plans, missing indexes, lock contention and deadlocks, connection pooling and replication lag.
• Run blameless postmortems, identify contributing causes and track corrective actions to completion.
• Contribute to release and change safety: readiness and liveness behaviour, graceful shutdown, canary and progressive rollout signals, rollback criteria.
• Support disaster recovery and resilience testing, including failover and restore exercises for the services you support.

Engineering: Reliability in the Application Stack

• Review application changes from a reliability standpoint: timeouts, retries with backoff and jitter, idempotency, circuit breakers, bulkheads and graceful degradation.
• Work with product teams on performance and capacity: profiling, load and soak testing, and understanding how services behave under saturation.
• Help teams design for observability from the start, so new services ship with useful telemetry, dashboards and alerts on day one.
• Contribute reliability improvements directly to application repositories rather than working around them from the outside.

Collaboration Continuous Improvement

• Partner with product engineering teams to understand their services, their failure modes and their reliability goals, and translate those into SLOs and operational practice.