Cytel · Salt Lake City, UT

Salary
Posted
Jul 16, 2026
Location
Salt Lake City, UT
Last confirmed open
Jul 21, 2026

What this job asks for AI summary

This role centers on building and maintaining R-based tooling — including reusable packages, utilities, and visualization solutions — to support clinical trial data workflows from collection through submission. The work involves gathering requirements, writing well-documented and tested code, and collaborating with study teams to improve data analysis processes within a regulated pharmaceutical environment. It suits an experienced R programmer with a background in clinical development.

Senior level · 5+ years · Remote

Must have (2)
Rtidyverse
Nice to have (4)
SASPosit WorkbenchPositronPosit Connect

Posted 12 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 the occupation pays Median $90,896 (middle half $69,863–$128,761).

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 (6)

No work location is specified in the posting — the CBSA and state fields are left blank. The role is at Cytel Inc., which has offices in multiple US and international locations; remote status cannot be confirmed from the text.

The role sits at the intersection of clinical-data analysis (15-2031) and R package/software development (15-1252). The primary day-to-day work is building R packages, utilities, and data pipelines in a clinical-trials context, which leans toward software development; however, the strong emphasis on data manipulation, analysis, visualization, and clinical reporting also fits 15-2031. 15-2031 was chosen as primary given the clinical-data and analysis framing, with 15-1252 as a close runner-up.

SAS/MACRO experience is explicitly marked 'preferred' in the posting and is treated accordingly.

Posit products (Workbench, Positron, Connect) are introduced with 'Familiarity with' — a preference signal rather than a hard gate — and are treated as preferred.

R visualization skills (static outputs and dashboards) are called out as a distinct required capability but map to the R skill and tidyverse ecosystem rather than a separately named tool; no standalone visualization library (e.g. ggplot2, Shiny) is explicitly named.

Ignored 1 non-technology phrase(s) as skills (responsibilities/concepts, not named tools): R package development.

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 ↗