Associate Director, Real-World Analytics Programing
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should only include sections that have real specific content. The posting includes a description of company and opportunity (maybe "About the role" or "Overview"). We can treat the initial paragraphs as "About the role". Then "Responsibilities" section is present. Then "Required Skills, Experience and Education" could be split into Requirements, Qualifications, Skills? The posting has "Required Skills, Experience and Education:" then bullet list of requirements. Then "Preferred Skills:" separate. Also there is Pay: Base Pay Salary Range $177,000 - $221,000 USD. Also mention location: onsite at headquarters in Redwood City, CA. That could be part of Pay or maybe Schedule? No schedule info. Benefits not mentioned explicitly except "robust equity awards, strong benefits". That's a mention of benefits but not detailed. The instruction: include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text. Benefits: they mention "robust equity awards, strong benefits, and significant learning and development opportunities." That's somewhat generic but still specific? It mentions strong benefits but not details. Might be considered filler? Probably we should include Benefits section with that sentence. However they said "prefer a few substantive sections over many thin ones." Might be okay to include Benefits with that sentence.
Schedule: no info, so omit.
Pay: we have base pay range, include Pay section.
Qualifications: maybe combine with Requirements? The posting has "Required Skills, Experience and Education:" which includes education and experience. Could be Requirements. Qualifications maybe same. We could have Requirements section covering required skills/experience/education. Then Skills section for preferred skills? Or we could split: Requirements (education/experience), Qualifications (maybe same), Skills (preferred). But to avoid thin sections, maybe combine Required and Preferred into Skills? However they ask to use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include those that have content.
Let's map:
- About the role: initial paragraphs describing company and opportunity (The Opportunity). That's substantive.
- Responsibilities: the bullet list under "Responsibilities:" (actually they list responsibilities as paragraphs). We'll put that.
- Requirements: the "Required Skills, Experience and Education:" list (education, experience, etc.)
- Qualifications: maybe we could treat "Required Skills, Experience and Education:" as Qualifications? But we already used Requirements. Could put Qualifications as same content? Might be duplication. Better to treat Requirements as the education/experience, Qualifications as the required skills (SAS/R, SQL, etc.)? But the list includes both. Could split: Requirements: education/experience; Qualifications: technical skills (SAS/R, SQL, etc.) ; Skills: preferred skills. However the instruction: prefer few substantive sections over many thin ones. Splitting may create thin sections. Maybe better to have Requirements (includes education/experience and required skills) and Skills (preferred skills). Omit Qualifications if no distinct content. But they said use headings for those categories if content exists. If we omit Qualifications, that's okay.
- Skills: preferred skills list.
- Benefits: mention of robust equity awards, strong benefits, learning and development.
- Pay: base salary range.
- Schedule: none, omit.
Now we need to preserve all substantive information, not invent or summarize away detail. We must not omit any required details. We need to include all responsibilities, requirements, etc. We'll convert bullet lists to - . For prose, use
.
We must not repeat job title as heading. No Job ID.
We must remove boilerplate: EEO, privacy, scam warning, etc. Also remove navigation/cookie/legal. So we will exclude those paragraphs.
Let's extract content.
First part: "Revolution Medicines is a global, commercial-state oncology company dedicated to discovering, developing and delivering innovative medicines for patients with RAS-addicted cancers. Leveraging its differentiated RAS(ON) tri-complex inhibitor platform, the company is advancing a broad, integrated portfolio of oral RAS(ON) inhibitors designed to directly target the active, cancer-driving state of RAS. Founded on rigorous scientific inquiry and a willingness to challenge long-held assumptions, Revolution Medicines is committed to changing the trajectory of disease for patients with RAS-addicted cancers worldwide. Our people are united by a shared way of working: follow the science, challenge assumptions, act with urgency and hold ourselves to a high standard of rigor—all in service of patients. The Opportunity: This position will serve as the lead statistical programmer for assigned real-world analytics and programming studies, independently managing programming activities from study initiation through final deliverables. The individual will be responsible for translating study protocols, statistical analysis plans (SAPs), and analysis specifications into high-quality, reproducible programming solutions and study outputs. The Real-World Analytics Programmer will partner closely with HEOR/RWE scientists, data scientists, biostatisticians, and other cross-functional stakeholders to support the successful execution of observational research studies. The role requires strong technical expertise, attention to detail, and the ability to manage multiple studies and competing priorities in a fast-paced environment."
We can treat that as About the role.
Now Responsibilities: list after "Responsibilities:" Actually they have a paragraph "Responsibilities:" then a list of items each starting with a verb. We'll capture each as
- .
Let's list them:
- Serves as the lead statistical programmer for assigned real-world studies and manage programming activities from study kickoff through final delivery.
- Leads programming deliverables from study initiation through final report, including analysis dataset specifications, TLF shells, validation plans, programming documentation, and final study outputs.
- Reviews and understand study-specific documents including protocols, SAPs, analysis specifications, and study concept documents to ensure accurate implementation of study requirements.
- Translates study designs and analytic specifications into efficient, scalable, and reproducible programming solutions.
- Independently develops, validates, and maintains SAS, SQL, R, Python, and other programming solutions for cohort construction, endpoint derivation, analysis dataset creation, and study deliverables.
- Generates and quality-control analysis datasets, tables, listings, and figures (TLFs) in accordance with study protocols, SAPs, analysis specifications, and internal standards.
- Supports a broad range of HEOR/RWE studies, including treatment pattern analyses, burden of illness studies, comparative effectiveness and safety studies, natural history studies, and external control arm analyses.
- Implements and validate analytic methods specified in study protocols and SAPs, including survival analyses, propensity score approaches, confounding adjustment methods, and sensitivity analyses.
- Works with multiple oncology-focused real-world data assets, including claims, electronic health records (EHR), genomic testing databases, and linked clinical-genomic datasets.
- Assesses data quality, completeness, and fitness-for-purpose and provide recommendations regarding data availability and implementation feasibility.
- Independently performs quality control and validation activities for programming code, analysis datasets, and study outputs.
- Develops and maintains technical documentation, programming specifications, reusable code, macros, and reproducible analytic workflows for assigned studies.
- Collaborates closely with HEOR/RWE scientists, Data Scientists, and Biostatisticians to ensure accurate implementation of study methodologies and successful delivery of study objectives.
- Communicates programming assumptions, implementation decisions, timelines, and risks to study teams and stakeholders.
- Contributes to real-world programming standards, quality frameworks, and best practices.
- Provides technical guidance to junior programmers as appropriate.
- Stays current with evolving industry best practices, technologies, and regulatory expectations related to oncology real-world data and evidence generation.
Note some grammar issues but we keep as is.
Now Required Skills, Experience and Education: list:
- BS/MS degree in Statistics, Biostatistics, Computer Science, Data Science, Epidemiology, Mathematics, or a related quantitative discipline.
- 8+ years of statistical programming experience in pharmaceutical, biotechnology, CRO, healthcare research, or related settings for Senior-level candidates.
- Demonstrated experience independently leading programming activities for observational research, HEOR, epidemiology, or real-world evidence studies.
- Strong SAS or R programming experience required, including experience developing analysis datasets and study deliverables from complex healthcare data sources.
- Experience with SQL required and working knowledge of R or other programming language for data manipulation, analytics support, and quality control activities preferred.
- Experience developing analysis datasets, tables, listings, and figures (TLFs) from complex healthcare or real-world data sources.
- Experience working with large healthcare databases, including claims, EHR, genomic, registry, or linked clinical-genomic datasets.
- Strong understanding of observational research workflows and implementation of study specifications.
- Demonstrated ability to manage multiple projects simultaneously while meeting timelines and quality expectations.
- Excellent written and verbal communication skills.
- Strong analytical, problem-solving, and organizational skills with exceptional attention to detail.
- Thrives in a collaborative team environment and is motivated to drive high-quality technical execution and continuous process improvement.
Now Preferred Skills: list:
- Oncology drug development or oncology real-world evidence experience.
- Experience working with major oncology or healthcare real-world data assets, such as Flatiron Health, ConcertAI, COTA, Tempus, Guardant, Merative MarketScan, Komodo, Optum, TriNetX, or similar datasets.
- Experience supporting HTA, market access, indirect treatment comparison (ITC), external control arm, or regulatory-grade real-world evidence studies.
- Experience developing reusable programming frameworks, standardized macros, and validation tools.
- Experience with Git, version control systems, and reproducible analytics workflows.
- Experience working in a fast-paced and growing biotechnology organization.
Now Pay: Base Pay Salary Range $177,000 - $221,000 USD. Also mention location: onsite at headquarters in Redwood City, CA. Could include in Pay section or maybe as part of About the role? But we have no separate heading for Location. Could add a short
under About the role mentioning location? The instruction: do not put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. Location is minor metadata, we can fold into About the role paragraph. We'll add a sentence: "This is a full-time onsite position at the headquarters in Redwood City, CA."
Now Benefits: mention: "competitive cash compensation, robust equity awards, strong benefits, and significant learning and development opportunities." Also earlier they said "Our base pay salary ranges are determined by role, level, and location. Individual base pay salary is determined by multiple factors, including job-related skills, experience, market dynamics, and relevant education or training. Please note that base pay salary range is one part of the overall total rewards program at RevMed, which includes competitive cash compensation, robust equity awards, strong benefits, and significant learning and development opportunities." We'll include that as Benefits section.
Now we must not include EEO, privacy, scam warning. So we will omit those paragraphs.
Now construct HTML.
We'll start with maybe not required; just output HTML fragment with headings and content.
We'll do:
About the role
... (including company description and opportunity and location)
Responsibilities
- ...
...
Requirements
- ...
...
Skills
- ...
...
Benefits
... (total rewards)
Pay
Base Pay Salary Range $177,000 - $221,000 USD (full-time onsite at headquarters in Redwood City, CA).
We might also include note about location inside Pay.
Check that we didn't miss any substantive info: The description about company mission, opportunity, responsibilities, required skills, preferred skills, benefits, pay. All covered.
Now ensure we didn't include any boilerplate like "Revolution Medicines
. We must not repeat job title as heading. No Job ID. We must remove boilerplate: EEO, privacy, scam warning, etc. Also remove navigation/cookie/legal. So we will exclude those paragraphs. Let's extract content. First part: "Revolution Medicines is a global, commercial-state oncology company dedicated to discovering, developing and delivering innovative medicines for patients with RAS-addicted cancers. Leveraging its differentiated RAS(ON) tri-complex inhibitor platform, the company is advancing a broad, integrated portfolio of oral RAS(ON) inhibitors designed to directly target the active, cancer-driving state of RAS. Founded on rigorous scientific inquiry and a willingness to challenge long-held assumptions, Revolution Medicines is committed to changing the trajectory of disease for patients with RAS-addicted cancers worldwide. Our people are united by a shared way of working: follow the science, challenge assumptions, act with urgency and hold ourselves to a high standard of rigor—all in service of patients. The Opportunity: This position will serve as the lead statistical programmer for assigned real-world analytics and programming studies, independently managing programming activities from study initiation through final deliverables. The individual will be responsible for translating study protocols, statistical analysis plans (SAPs), and analysis specifications into high-quality, reproducible programming solutions and study outputs. The Real-World Analytics Programmer will partner closely with HEOR/RWE scientists, data scientists, biostatisticians, and other cross-functional stakeholders to support the successful execution of observational research studies. The role requires strong technical expertise, attention to detail, and the ability to manage multiple studies and competing priorities in a fast-paced environment." We can treat that as About the role. Now Responsibilities: list after "Responsibilities:" Actually they have a paragraph "Responsibilities:" then a list of items each starting with a verb. We'll capture each as
under About the role mentioning location? The instruction: do not put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. Location is minor metadata, we can fold into About the role paragraph. We'll add a sentence: "This is a full-time onsite position at the headquarters in Redwood City, CA." Now Benefits: mention: "competitive cash compensation, robust equity awards, strong benefits, and significant learning and development opportunities." Also earlier they said "Our base pay salary ranges are determined by role, level, and location. Individual base pay salary is determined by multiple factors, including job-related skills, experience, market dynamics, and relevant education or training. Please note that base pay salary range is one part of the overall total rewards program at RevMed, which includes competitive cash compensation, robust equity awards, strong benefits, and significant learning and development opportunities." We'll include that as Benefits section. Now we must not include EEO, privacy, scam warning. So we will omit those paragraphs. Now construct HTML. We'll start with maybe not required; just output HTML fragment with headings and content. We'll do:
About the role
... (including company description and opportunity and location)
Responsibilities
- ... ...
Requirements
- ... ...
Skills
- ... ...
Benefits
... (total rewards)
Pay
Base Pay Salary Range $177,000 - $221,000 USD (full-time onsite at headquarters in Redwood City, CA).
We might also include note about location inside Pay. Check that we didn't miss any substantive info: The description about company mission, opportunity, responsibilities, required skills, preferred skills, benefits, pay. All covered. Now ensure we didn't include any boilerplate like "Revolution Medicines