Platform Reliability Engineer

• Experience supporting trading, financial-services, or other highly regulated and time-sensitive production environments. \n

• Experience with Datadog, Terraform Enterprise, Backstage, Argo CD, GitHub Actions, or AWS CodeBuild and CodePipeline. \n

• Knowledge of high-throughput messaging and data platforms such as Kafka or Confluent. \n

• Operational experience with PostgreSQL/Aurora, CockroachDB, Redis/Valkey, QuestDB, Snowflake, or comparable data systems. \n

• Strong networking knowledge, including Transit Gateway, PrivateLink, DNS, hybrid connectivity, firewalls, and private-access platforms such as Zscaler. \n

• Experience designing multi-region systems and leading disaster-recovery or resilience-testing programmes. \n

• Familiarity with cloud cost management and designing systems that are both reliable and economically sustainable. \n

• Experience contributing to internal developer platforms, service catalogues, golden paths, or organisation-wide engineering standards. \n

• A strong track record of designing and operating large-scale, mission-critical production systems. \n

• Deep expertise in AWS architecture and operations, including networking, identity and access management, compute, storage, managed services, and multi-account environments. \n

• Advanced experience with infrastructure as code, particularly Terraform, including the design of reusable modules and controlled delivery workflows. \n

• Strong knowledge of distributed systems and reliability concepts, including failure modes, availability, consistency, capacity, recovery, and graceful degradation. \n

• Hands-on experience operating containerised workloads using Kubernetes/EKS, ECS, or comparable orchestration platforms. \n

• Demonstrated experience establishing effective observability, alerting, SLOs, incident-management practices, and post-incident improvement programmes. \n

• Strong software-engineering ability in Python, Go, TypeScript, or a comparable language, with an emphasis on maintainable operational tooling and automation. \n

• Experience leading ambiguous, cross-organisational technical initiatives without relying on formal authority. \n

• Sound judgement under pressure and the ability to make clear, risk-based decisions during production incidents. \n

• Excellent written and verbal communication, including the ability to explain complex technical decisions to engineering and non-engineering stakeholders. \n

• A pragmatic approach to engineering, with the ability to determine where standardisation is valuable, where flexibility is appropriate, and where complexity is unjustified. \n

• Set the technical direction for the reliability and evolution of our shared platform, balancing resilience, security, delivery speed, operational complexity, and cost. \n

• Lead high-impact initiatives spanning cloud infrastructure, compute platforms, networking, observability, deployment systems, and production operations. \n

• Design and evolve highly available AWS architectures across multiple accounts, environments, and regions. \n

• Improve the reliability and operability of workloads running across ECS, EKS/Kubernetes, serverless platforms, managed data services, and traditional compute. \n

• Establish practical SRE standards, including service-level indicators and objectives, error budgets, capacity planning, resilience testing, and production-readiness reviews. \n

• Identify recurring operational risks and eliminate them through automation, architectural improvements, safer defaults, and clear ownership. \n

• Advance our infrastructure-as-code and delivery capabilities using Terraform, Terraform Enterprise, AWS CDK, GitHub Actions, CodeBuild, and related tooling. \n

• Evolve internal platform capabilities and developer workflows, including reusable infrastructure modules, deployment pipelines, service templates, and Backstage-based self-service. \n

• Improve observability across the platform using Datadog, CloudWatch, distributed tracing, structured logging, actionable alerting, and service ownership metadata. \n

• Lead the technical response to significant production incidents, coordinate diagnosis and recovery, and ensure post-incident learning results in durable improvements. \n

• Strengthen disaster-recovery and business-continuity capabilities through tested recovery procedures, failure exercises, and the removal of hidden dependencies and single points of failure. \n

• Partner with Security to embed least-privilege access, secrets management, encryption, auditability, network controls, and policy enforcement into platform foundations. \n

• Work with engineering teams operating critical databases, streaming platforms, workflow systems, and external connectivity to improve end-to-end reliability. \n

• Develop technical strategies and roadmaps for major areas of the platform, communicate trade-offs, and build alignment across engineering and business stakeholders. \n

• Mentor engineers, improve the quality of technical design and operational practices, and act as a trusted reviewer for consequential architectural decisions. \n

• Participate in and continuously improve a sustainable production support and on-call model. \n

\n

\n