Senior Platform Engineer

## About the role The Platform Engineer is responsible for the cloud estate, deployment automation, integration validation, and test infrastructure that ensure phoenix runs reliably, securely, and cost-effectively across deltaflare's own environments and the client environments we deploy into. ## Role Purpose Phoenix is delivered as a working platform across a hybrid estate: deltaflare-operated cloud infrastructure in AWS, and client environments with their own network topologies, hardware configurations, and operational constraints. The Platform Engineer is accountable for keeping that estate healthy, deploying phoenix into pre-production and production environments using the established blueprint, validating that what is deployed meets requirements, and building the automated test infrastructure that supports release confidence. The role requires a strong networking and linux systems foundation, hands-on cloud operations experience across AWS, fluency with Docker containerisation and infrastructure as code, and a methodical approach to integration validation and test automation. The Platform Engineer also needs enough breadth across the software stack (IaaS, PaaS, SaaS) to triage issues wherever they surface and either resolve them or route them to the right owner with sufficient diagnostic detail. The role sits within the Technology function and reports to the Head of Technology. Cloud optimisation, platform security review, and the broader technology agenda sit within that business unit's remit; the Platform Engineer contributes to that agenda day-to-day. The Platform Engineer also supports the Head of Assurance in meeting deltaflare's internal and external obligations, providing the integration, deployment, and test evidence that assurance activity and regulatory engagement depend on. Training on phoenix architecture, the blueprint methodology, and the OT environments the platform operates in will be provided. ## Key Responsibilities ### Cloud Estate Operations - Operate deltaflare's AWS estate day-to-day, contributing to the Technology function's wider remit for cloud optimisation, availability, and security. - Manage, maintain, and continuously improve the environments, with explicit responsibility for performance, cost optimisation, and the security posture of what runs on them. - Establish and maintain monitoring, alerting, and operational runbooks. ### Blueprint Deployment - Deploy the phoenix blueprint (Docker Swarm and AWS infrastructure as code) into pre-production and production environments. - Maintain and evolve the deployment automation so releases are repeatable, auditable, and low-risk. - Take delivered phoenix software and stand it up in target environments to meet the deployment specification. ### Test Environment and Test Infrastructure Support - Provide and maintain the test environments and supporting infrastructure that the product/test engineer relies on for test automation. - Ensure environments are stable, representative of production, and aligned with the deployment configurations under test. - Build infrastructure-level test capabilities (IaC validation, deployment smoke tests, environment health checks) as part of the platform layer, complementing the product-level test work owned by the product/test engineer. ### Integration Validation - Validate phoenix integration across different deployment configurations and blueprints. - Confirm each integration behaves as designed at the technical level and produce the deployment evidence that supports broader sign-off. - Identify, document, and communicate any integration failures, gaps, or deviations clearly and promptly. ### Blueprint Development and Maintenance - Build and maintain the deployment blueprints that define how phoenix is configured across different client applications, sectors, and hardware tiers. - Ensure blueprints are accurate, current, and documented to a standard that supports repeatable deployment and client handover. ### Full-Stack Triage - When issues surface, whether in the IaaS, PaaS, or SaaS layers, in application code, networking, or the underlying OT environment, lead triage with enough breadth across the stack to localise the problem quickly. - Either resolve it directly or route it to the right owner with sufficient diagnostic detail to support root cause analysis. ### URS Validation Support - Support the product/test engineer and the Head of Assurance in their URS validation work by providing deployment evidence and platform-layer context. - Where the URS makes platform-layer demands (infrastructure topology, network segregation, hardening, monitoring, change control), ensure those demands are met in deployment and clearly documented. - Flag platform-layer URS ambiguities to the relevant owner before they become deployment issues. ### Release Notes and Technical Documentation - Write clear, accurate release notes for each platform release, capturing changes, dependencies, known issues, and deployment guidance. - Maintain technical documentation that is accessible to assurance, development, and client-facing colleagues. - Treat documentation as a core deliverable, not an afterthought. ### Development Team Liaison - Participate in development planning cycles, providing input from a deployment, operations, and test perspective. - Flag issues encountered during integration validation or in production back to the development team with sufficient detail to support resolution. - Contribute to improving the handover process between development and deployment. ### Assurance Support - Support