Senior Infrastructure & Data Platform Engineer

We're at an exciting stage in our growth as a digital Health Tech company, with increasing traction across clinical trials and life sciences.

Over the past year, we've invested significantly in our application and data and infrastructure to support a scalable, reliable, and secure platform for the next phase of growth. We're now looking for someone to take ownership of that platform, continuing to scale the capabilities and operational maturity in a health tech environment.

We're looking for a Senior Infrastructure and Data Platform Engineer to own and evolve the core infrastructure & data platform, and operational reliability of our health-tech product. This is a high-ownership role at the intersection of cloud infrastructure, data systems, Dev Ops, and operational resilience. You'll be the person responsible for making sure our platform supports a great DevX experience, is secure, observable, recoverable, and audit-ready, without slowing teams down.

You'll have significant influence over how the platform is designed and operated.

You will work closely with backend engineers, product squads, and leadership to design systems that scale safely, support regulated requirements, and are resilient in real-world operation. Our tech stack and tooling include GCP, Vercel, Git Hub, Bugsnag, Sanity CMS. You will report to the VP Engineering and will be part of our broader engineering team of about 10. This is a full-time role, either hybrid (Leeds) or fully remote in the UK.

We cannot sponsor visas to work in the UK.

• Own and operate our GCP environment (networking, IAM, compute, storage, managed services)
• Design and maintain infrastructure as code (e.g. Terraform)
• Ensure environments are secure, well-structured, and cost‑aware
• Act as a technical expert on cloud architecture decisions

• Own and evolve the data technology stack (data stores, pipelines, access patterns)
• Ensure data systems are reliable, observable, and fit for analytics and product use
• Define standards for data integrity, retention, access, and backup

• Own CI/CD pipelines and release safety practices
• Design and maintain observability (metrics, logs, tracing, alerts)
• Coordinate incident response, post‑incident reviews, and remediation
• Ensure teams can safely deploy and operate what they build

• Own infrastructure‑level security posture (IAM, secrets, network controls)
• Coordinate and support audits, penetration tests, and risk reviews
• Design and run backup and disaster recovery testing (regular, proven recovery)
• Proactively identify risks and lead mitigation planning

• Produce clear documentation for architecture, runbooks, and operational processes
• Partner with engineers to embed reliability and security into everyday delivery
• Act as an escalation point for complex operational and infrastructure issues

• Strong hands‑on experience running production infrastructure on GCP
• Experience designing and operating data platforms in production
• Deep understanding of cloud security, IAM, and network controls
• Practical experience with incident response, on‑call, and post‑mortems
• Experience planning and executing backup, recovery, and resilience testing
• Experience contributing to audits, managing penetration testing
• Confidence writing and maintaining infrastructure as code
• Confidence managing DevX tools e.g. CI/CD

• Experience in health‑tech or regulated domains is a plus but not required if you bring strong fundamentals.
• Understand how to make a top‑class developer experience that enables high velocity with control.
• Have worked in regulated environments

• A strong sense of ownership: you care about developer experience, reliability, security whilst maintaining a high delivery cadence; you care about responsible data handling.
• Ability to manage multiple work streams and stakeholders.
• Data‑driven: you use data and evidence to justify your decisions, thinking about now and next.
• Pragmatism: you design guardrails, not bureaucracy.
• Clear communication with both technical and non‑technical stakeholders.
• A mindset of…