Principal Forward Deployed DevSecOps Engineer

About the Role We're after a hands-on engineer for our Forward Deployed team in Labs & CMC Digital & Tech, building the automation, data pipelines and AI tooling that take manual work out of the lab. You'll typically work closely alongside a Senior Principal Forward Deployed DevSecOps Engineer on the approach, coordinating with stakeholders as needed, while your own focus stays on turning that direction into working software: quickly, securely, and in a way that still holds up once it's live. As you build experience, you may take on more of that stakeholder relationship yourself, with support and guidance from leadership. Expect a lot of coding, pipeline work and cloud infrastructure, with security and testing built in as you go rather than bolted on at the end. Most weeks you'll be deep in one piece of the build: automating a lab workflow, wiring up a data pipeline, or getting an agentic prototype into decent shape, while staying close enough to the rest of the engagement to flag problems before they land on someone else's desk. As you get more experience, you'll be trusted with a bigger slice of the problem yourself, and eventually the whole thing. We care about software that scientists actually use. Less manual lab work, fewer errors, better data, medicines and vaccines moving faster through the pipeline. Why This Role Exists Labs & CMC is rebuilding how laboratory science and CMC work gets done, with automation, data and AI doing jobs scientists used to do by hand. Senior engineers typically lead and coordinate the relationship with the business side of that, working in close partnership with the wider team; this role exists to give them the extra hands to actually build what's agreed, while staying closely involved in how the work takes shape. You'll spend most of your time writing code, wiring up pipelines and getting things into production, picking up more ownership of the problem, and potentially of the stakeholder relationship itself, as you grow into the role and build a deeper understanding of what's needed. Turning direction into software: working with a Senior Forward Deployed DevSecOps Engineer to agree an approach, coordinating with stakeholders as needed, then building it properly rather than knocking together a demo. Keeping pace: most of what you'll build needs to land in days, not sprints, so you'll want to be comfortable shipping fast and adjusting as scientist feedback comes in. Automation that actually sticks: wiring up instruments, lab systems and data platforms so what you build is still running after the project wraps up. Getting the data right: pairing with data engineering so whatever you're building sits on data that's actually trustworthy. Production-ready by default: security, testing and monitoring go in as you build, not after something's already gone wrong. Leaving something behind: writing components and patterns that the next engineer, on this engagement or another one, can actually pick up and use.