Don’t send a generic resume — generate a resume and cover letter tailored to this exact role.
CSL Vifor in Maidenhead seeks a Senior Clinical Statistical Programmer to own one or two trials from first line of code to submission-ready package. You will design, validate SDTM/ADaM datasets and outputs, work with statisticians and data managers, and mentor junior programmers.
You will lead end-to-end programming across the study lifecycle, review CRO deliverables, and ensure audit-ready analyses and documentation for regulatory submission.
CSL is looking for a Senior Programmer to take technical ownership of one or two clinical trials from first line of code to final submission package. This is a hands‑on statistical programming role with real authority attached to it: you'll be the person a study team turns to when the data needs to hold up under regulatory scrutiny, and the person who decides how a dataset gets built, not just who builds it. You'll work alongside statisticians, data managers, medical writers and regulatory colleagues as a peer, not a downstream resource — reading protocols and SAPs early enough to shape how a study's analysis gets structured, then seeing that structure through to submission‑ready SDTM and ADaM datasets, TFLs, and supporting documentation.
Hybrid Based (3 days a week onsite) in Maidenhead
Clinical data is only as useful as the programming behind it is trustworthy. Every regulatory decision downstream — every safety signal caught or missed, every submission accepted or queried — traces back to whether the datasets and outputs were built right the first time. This role sits at that pressure point. You're not just executing specifications; you're often the one writing them, catching the ambiguity in a protocol before it becomes a data problem three months later, and making the judgment calls that keep a study's analysis both scientifically sound and audit‑ready.
You’ll lead end‑to‑end programming for your assigned studies — in‑house or outsourced — spanning the full clinical development lifecycle from study setup through analysis, reporting, and regulatory submission. That means building and validating datasets and outputs yourself where the work is done internally, and holding CRO‑delivered work to the same bar where it isn't. You’ll also be a technical reference point for less experienced programmers, and a contributor to how the wider programming function does its work.