Senior Site Reliability Engineer

FundApps; London Borough of Islington; Hybride; GBP 95 000 - 105 000; Plein temps

Avantages offerts par ce poste

Private health insurance

Matched pension contribution

Learning budget

Flexible hybrid working

Bonusly micro-bonuses

Birthday off

Résumé du poste

FundApps is seeking a Senior Site Reliability Engineer to own the health and scalability of our production estates hosted in AWS. You will work primarily with Terraform, Kubernetes manifests, and code, ensuring client environments are isolated, scalable, and reliable.

You will extend monitoring, push ownership of alerts to engineering teams, and keep deployments boring and fast. The role blends hands-on engineering with strong cost management and incident learning culture.

Qualifications

• Experience running production infrastructure on AWS, with multi-account and regional considerations.

Responsabilités

• Manage and scale the Kubernetes estate across client environments.
• Extend and own monitoring and alerting, and drive service-level ownership to product teams.
• Keep deployment pipelines fast, boring, and predictable with infrastructure as code.
• Design for graceful failure: retries, limits, queues, and recoveries.
• Optimize hosting costs and understand per-client environment economics.

Connaissances

AWS

Kubernetes

Terraform

Python/Go

CI/CD

GitOps

Data-heavy systems

Incident management

Outils

EKS

Helm

FluxCD

Prometheus

Grafana

Kafka

Elasticsearch

PostgreSQL

ClickHouse

Terraform

GitHub Actions

Description du poste

Senior Site Reliability Engineer

Department: Engineering

Employment Type: Full Time

Location: London, UK

Compensation: £95,000 - £105,000 / year

Description

SteelEye, now merged with FundApps, provides communications, trade and order surveillance to some of the world's largest financial institutions. Clients run on shared or dedicated infrastructure depending on what they need, which means we operate a large estate of clusters, data pipelines and client environments for the size of our engineering team.

This role keeps that estate healthy. Not just up, but doing its job: client data arriving completely, surveillance running against the right window, the alerts our clients depend on actually firing. When something is wrong we want to know before they do.

It is a hands-on engineering role. You will spend your time in Terraform, Kubernetes manifests and code rather than in meetings about them.

Running the Kubernetes estate.

We run many client environments across EKS. You will keep them properly separated, sensibly sized and able to scale when a client sends us more data than we expected. Isolation between clients is a client assurance commitment, not just good practice, so the boundaries matter.

Knowing what is happening.

We have a substantial monitoring and alerting setup and it needs to keep pace with the platform. You will extend it, keep the signal useful, and push ownership of alerts and service levels out to the teams that build the services rather than holding it all centrally.

Making deployment boring.

Changes should reach production frequently, in small pieces, without drama. You will keep our pipelines fast and our deployments predictable, and make it easy for engineers to ship safely without needing to understand how any of it works underneath.

Making things fail gracefully.

You will work with the engineers building our services on how the platform behaves when something is slow, something is down, or a message cannot be processed. Retries, resource limits, queue handling and recovery, designed in rather than discovered during an incident.

Keeping the cost sensible.

Our hosting cost grows as we add clients. You will work on right sizing, compute efficiency and understanding what each client environment actually costs us.

Incidents.

You can volunteer to join a compensated, out of hours rota shared across the team, and take part in making sure the same incident does not happen twice.

What success looks like

• Engineers can answer normal operational questions without needing production access.
• We find out about problems from our monitoring rather than from a client.
• Deploying is routine enough that nobody plans their week around it.
• Adding a new client is routine and automated.
• Cost per client environment is understood and trending the right way.
• Nothing in the estate depends on one person knowing how it works, including you

What you'll bring

• You have run production infrastructure on AWS for several years and know it properly: EKS, IAM and networking in particular, across multiple accounts and regions.
• You are strong with Kubernetes beyond the basics. Multi tenancy, Helm, scaling behaviour, and what actually happens when a cluster is under pressure.
• You write Terraform that other people can safely change, and you treat infrastructure code with the same standards as application code.
• You write code. Python, Go, or something comparable. Enough to automate properly, build the small services and controllers that fill the gaps, and read the applications you are supporting.
• You have built or run CI/CD properly, and have worked with GitOps as a way of managing what is deployed.
• You have operated data heavy systems. Message queues, search clusters, pipelines that move a lot and cannot quietly lose anything.
• You treat an incident as something to learn from rather than something to survive.
• You work well with the engineers building the product. Much of this role is making other teams faster and safer, which means being someone they come to early rather than after something has gone wrong.

Our estate, for context

• AWS and Azure · Kubernetes and EKS · Karpenter · Terraform · Helm · FluxCD · GitHub Actions · Prometheus, Grafana, Loki and OpenTelemetry · Kafka · Elasticsearch · PostgreSQL · ClickHouse · Python and Go services ·
• You do not need to have used all of it. You should recognise most of it and be genuinely deep in some of it.

How you work

• You prefer automated guardrails to manual approvals and paved paths to documentation. You would rather fix the cause than add a runbook entry.

You are pragmatic about what is worth automating and what is worth leaving alone, and you can tell the difference under time pressure.

A Few Things To Know Before You Apply

Work Eligibility

We require candidates to have permission to work in the UK without visa sponsorship.

We work hybrid and ask that new FundAppers spend 3 days per week at our shiny London office during their first 6 months, to make the most of getting to know the business and other FundAppers.

After that, our policy is at least 2 days per week in the office to collaborate, connect and enjoy our shared space and team activities.

Life at FundApps

• Work/life balance with flexible hybrid working
• Wellbeing benefits such as private health insurance, life insurance, a flexible stipend and mental health coaching
• Matched pension contribution up to 10%
• Peer micro-bonuses through Bonusly
• £1,000 learning budget each year and unlimited professional development leave
• Peer-led 'Brown-bag lunch' learning sessions and an annual Learning Festival
• 25 days holiday leave + an extra day next year if you use it all + an extra day after 3 & 5 years
• 5 Years @ FundApps - additional 4 weeks paid holiday leave during your 5th year as a FundApper
• 26 weeks leave for all new parents regardless of gender, location or family structure
• Volunteering leave
• Birthday off

We are proud of the diversity of all FundAppers - it makes us strong. We provide flexibility around religious observances and embrace a variety of cultural celebrations! If you're looking for a workplace where you can just be yourself, you're in the right place.