remote

Salary
Posted
Jul 15, 2026
Location
Last confirmed open
Jul 21, 2026

What this job asks for AI summary

A contract-based clinical programming role embedded with a single sponsor client through a CRO. The position centers on building and validating SDTM and ADaM datasets in R to CDISC standards, producing tables/listings/figures, and supporting regulatory submissions. It suits an experienced clinical programmer with deep R expertise and working SAS knowledge who is comfortable with QC processes and automated pipeline development.

Senior level · 4+ years · Remote · Contract

Advertised as Principal, but the requirements read as Senior.

Must have (5)
RSDTMADaMCDISCSAS
Nice to have (6)
tidyversehavenadmiral or TidycdiscR MarkdownShinyGit

“or” means any one of them counts — you don't need all of them.

Posted 2 times — it's one opening, so apply once.

We read this from the posting text with AI. Skim the description below before ruling yourself out.

How this req sits in the market our data

What won't set you apart
R42%

Most people in this occupation already list these. Still required — just not what gets you shortlisted.

What the occupation pays Median $122,874 (middle half $87,544–$162,374).

Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 28, 2026. It is a model, not a headcount.

Why we read it this way (8)

The title blends two roles — 'Clinical R Programmer / Principal Data Scientist Consultant' — reflecting a clinical programming focus (SDTM/ADaM dataset development) rather than a traditional data science (ML/modeling) role; 15-2051 was chosen over 15-1252 because the statistical/analytical framing and CDISC standards work align more closely with Data Scientists, but the runner-up is plausible.

The posting is tagged '#LI-Remote' and '#contract', confirming fully remote and contract engagement.

The advertised title says 'Principal' but the required experience (4–6+ years) and scope of work are consistent with a Senior-level role; the Principal label appears to be a client-facing title rather than a true org-wide technical authority designation.

The degree requirement lists Bachelor's or Master's as acceptable options with no equivalent-experience clause, but since either degree satisfies the gate, the minimum is Bachelor's — however, the JD frames it as 'Bachelor's or Master's … or related field,' which is a standard educational preference rather than a hard gate, so the degree requirement is set to None.

No compensation figures were provided in the posting.

GxP validation and automated workflows appear alongside Git under Preferred Qualifications; Git is the only concrete named tool extracted from that grouping.

Posting is for a contract engagement — the market benchmarks below price full-time roles, so read the comp comparison with that in mind.

This posting reads as a fully-remote role, so it was scored against the national candidate pool rather than a single metro.

Read the full posting

The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.

Apply

Apply on employer site ↗