Senior Platform Engineer

Why Semble: Are you looking to impact and be part of something special, such as shaping the future of healthcare? At Semble, we are on a mission to enable health professionals to amplify their impact. We improve the way healthcare is delivered to millions of people by providing doctors and their teams with powerful, innovative, intuitive, and secure software. Our cloud-based clinical system is already used by thousands of clinicians, making their lives easier and saving them money, while structuring their health data to help research. We are a passionate and driven team, lucky to unite under strong cultural drivers: Impact - We do work that matters. Collaboration – We are in it together. Human touch – We care deeply. This role can be fully remote in the UK or France. We are unfortunately not able to consider candidates located outside these locations and time zones at this stage. About the Team We're guided by one core question: how do we help our colleagues reduce cognitive load and get more done? Whether that's building tools to make operating code in production easier, running foundational shared services, or educating engineers on AWS and Kubernetes, our work has a direct multiplier effect on the rest of the business. We work closely with security and Implementation teams to make sure our infrastructure decisions serve the wider organisation's goals. The Platform team exists to make the whole engineering organisation more effective. We're responsible for: Developer Productivity and Experience, including the tooling engineers rely on every day; Developer Enablement and Engagement, helping teams self-serve and grow their skills Cloud Infrastructure, spanning AWS, Kubernetes (EKS) and MongoDB Cloud Agentic platform enablement, workflows and automation Infrastructure as Code, primarily through Terraform Modern CI/CD, using GitOps patterns and tools such as ArgoCD The Role As a Senior Platform Engineer, you'll be a driving force behind the evolution of Semble's engineering platform and the day-to-day experience of every engineer who builds on top of it. You'll champion infrastructure best practices, shape team goals, and influence the wider engineering roadmap. Just as importantly, you'll obsess over friction: the small (and large) things that slow engineers down, and how to remove them through better tooling, clearer paths, and stronger enablement. This is a senior, high-trust role: you'll be expected to make sound architectural judgement calls, mentor other engineers, and represent the Platform team's priorities in cross-functional conversations, all while keeping empathy for the end-user (your fellow engineers) at the centre of what you build. In One Year, You'll Know You Were Successful If You... Developer productivity and enablement Reduced the barrier for every engineer to build, ship, and operate their own code in production, measured through faster lead time for changes and fewer hand-offs Built or improved self-service tooling and "golden paths" (e.g. project templates, standard CI/CD pipelines, scaffolding tools) so teams can spin up new services without needing Platform's direct involvement Improved onboarding for new engineers, shrinking the time it takes someone to make their first meaningful production contribution Ran or contributed to developer experience initiatives such as office hours, internal workshops, or "lunch and learn" sessions to build AWS/Kubernetes/CI-CD literacy across the wider engineering org Wrote and maintained clear, discoverable documentation and runbooks, treating docs as a product with the same quality bar as code Gathered and acted on developer experience signals (e.g. surveys, feedback loops, usage metrics on internal tools) to prioritise the roadmap based on real pain points, not assumptions Partnered with engineering teams to understand their workflows first-hand (shadowing, pairing, dogfooding your own tools) rather than building in isolation Brought innovative ideas to the team and contributed meaningfully to the Platform roadmap, balancing infrastructure evolution with tooling and enablement work Established objective measures of "done" and documented assumptions clearly, so both infrastructure and tooling initiatives had transparent success criteria Contributed to observability as code initiatives, both inside the team and across engineering Infrastructure