Associate Director, Statistical Programming

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real specific content. The posting includes: description of role (Associate Director, Statistical Programming responsibilities). There's a "Summary Of Key Responsibilities" list. There's "Qualifications" list. There's mention of pay range. Benefits described. No schedule info. So we should include sections: About the role (maybe the introductory paragraph?), Responsibilities, Qualifications, Benefits, Pay. Possibly Skills? The qualifications include many skill items; could be Skills section but we already have Qualifications. The instructions: Use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include. The posting includes responsibilities, qualifications, benefits, pay. There's also a brief "About Alnylam" but that's company description, not role. Could put under About the role? The role description includes responsibilities. The "Summary Of Key Responsibilities" is a list. Could treat that as Responsibilities. The "Qualifications" list is qualifications. Benefits described. Pay range given. No schedule. No explicit Requirements separate from qualifications; but we could combine Requirements with Qualifications? The instruction says include a section only when posting has real specific content for it. So we can have About the role (maybe a brief paragraph summarizing role). Responsibilities (ul). Qualifications (ul). Benefits (ul). Pay (p maybe). No Skills separate unless we extract skills from qualifications; but we could treat Qualifications as covering skills. Could also have Skills section if we want to list specific technical skills like SAS, R, CDISC etc. But we already have qualifications covering that. Safer to follow headings: About the role, Responsibilities, Qualifications, Benefits, Pay. We must not repeat job title as heading. So no heading for Associate Director, Statistical Programming. We need to preserve all substantive information. Must not invent or summarize away detail. Must not include boilerplate like EEO, E-Verify, privacy notice, etc. Must remove cookie/navigation/legal/EEO etc. Also remove application instructions. The posting includes "Before applying, please review Alnylam's Candidate Privacy Notice..." that's boilerplate; remove. Also "Alnylam is an E-Verify Employer." remove. Also "Learn more about these and additional benefits offered by Alnylam by visiting the Benefits section of the Careers website: https://www.alnylam.com/careers" maybe keep? It's a link to benefits; but it's more like a reference; could be considered boilerplate? It's part of benefits description; but it's a link to external site; maybe we can keep as part of benefits? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The link to benefits is not exactly boilerplate but could be considered navigation? It's a reference to benefits section; maybe we can keep it as part of benefits? However it's not substantive content about the role; it's a pointer. Safer to omit. We need to preserve all substantive information: responsibilities list, qualifications list, benefits description, pay range. Let's extract responsibilities bullet points from "Summary Of Key Responsibilities". The text after that heading is a long paragraph with many responsibilities separated by periods. We need to turn into list items. We should split by sentences that start with a verb. Let's parse: "Provides technical and/or operational leadership in the delivery of high quality and timely statistical programming for clinical studies, drug programs, and/or in support of NDA submissions." "Works closely with Biostatistics to implement statistical analysis of clinical trial data, working closely on the development and validation of CDISC ADaM specifications and datasets, and TLFs for analyses to support regulatory, medical affairs, and market access needs." "Works closely with Data Management on cross-functional data review and the development and validation of CDISC SDTM specifications and datasets and define packages, may also support Drug Safety to support safety data review and reporting needs, and/or Clinical Pharmacology to support their dataset creation and analytic needs." "Manages internal and vendor statistical programming support; Maintains strong collaboration and governance with preferred vendors." "Writes SAS and R code that produces or validates tables, listings, figures and analysis datasets, in support of clinical studies or complex integrated analyses for submission." "Performs, plans and coordinates project work to ensure timely, quality delivery across multiple projects, or across a drug program." "Writes specifications to describe programming needs, including development and maintenance of complex / ADaM specifications and reviewer guides." "May lead the creation and validation of global macros or systems that streamline repetitive operations to increase programming efficiency." "Provides input into, or leads general standardization efforts (e.g., CRFs, query checks, standard statistical programs, data presentations)." "Leads efforts to develop programming processes consistent with industry best practices." "Reviews and provides expert input to DMP, eCRF specs, and other clinical data management documents; Reviews and provides expert input to statistical analysis plans and other related documents." "Partners with or oversees CROs or Programming vendors to perform any of the above tasks." That's the responsibilities. Qualifications list: after "Qualifications". Let's extract each bullet separated by semicolons or line breaks. "At least 10 years’ industry (Pharmaceutical, Biotech, CRO) SAS programming experience or equivalent;" "Experience as a Programming manager (FTEs, Functional Service Providers or vendors);" "Experience leading programming teams in support of clinical trials to report the results of clinical trials, integrate analyses across a program, or prepare data/analysis for electronic NDA or BLA submission;" "Experience in constructing technical programming specifications and producing complex, validated SAS programs;" "Demonstrated experience in working with CDISC standards, including SDTM, and ADaM, and Define xml;" "Proficiency in understanding of statistical programming environments, processes, procedures, and roles;" "Excellent knowledge of SAS/Base, SAS/Macro, SAS/STAT, SAS/Graph, and SAS/SQL with a demonstrated mastery of SAS/STAT procedures;" "Hands-on experience with R programming for clinical trial data analysis, reporting, and regulatory submissions." "Knowledge of R packages and frameworks commonly used in clinical development, Posit Workbench (RStudio Server), Posit Package Manager, and enterprise R environments." "Experience developing SOPs, Standards or implement programming best practices;" "Experience overseeing vendors in the delivery of quality programming support;" "Excellent written and oral communication and organizational skills required;" "Bachelor’s Degree required, master’s degree Preferred, in areas of computer science, statistics, mathematics or information sciences." "Clear alignment with Alnylam Core Values:Commitment to PeopleInnovation and DiscoverySense of UrgencyOpen CulturePassion for Excellence" That last part is about core values; could be considered part of qualifications? It's not a qualification per se but maybe we can include as a bullet under Qualifications? It's about alignment with core values; could be considered a requirement. We'll keep as a bullet. Benefits: paragraph after "Alnylam’s robust Total Rewards package is designed to support your overall health and well-being. We offer comprehensive benefits including medical, dental, and vision coverage, life and disability insurance, a lifestyle reimbursement program, flexible spending and health savings accounts and a 401(k)with a generous company match. Eligible employees enjoy paid time off, wellness days, holidays, and two company-wide recharge breaks. We also offer generous family resources and leave. Our commitment to your well-being reflects our belief that caring for our people fuels the impact we create together." We can turn into list items: medical, dental, vision coverage; life and disability insurance; lifestyle reimbursement program; flexible spending and health savings accounts; 401(k) with generous company match; paid time off; wellness days; holidays; two company-wide recharge breaks; generous family resources and leave. Pay: "U.S. Pay Range $181,100 - $244,900 USD". Also mention eligibility for annual short-term incentive award and long-term incentive award. Also mention base pay determined based on factors. We'll include that as prose under Pay section. Schedule: none. About the role: maybe a brief paragraph summarizing role: The Associate Director, Statistical Programming is responsible for statistical programming activities in support of clinical trials including technical and project leadership overseeing the quality and timely delivery of all statistical programming deliverables for studies or for a submission. He/she ensures the team develops, maintains, validates and runs quality SAS programs that access, visualize, analyze, and report clinical trial data in accordance with statistical analysis plans, ICH guidelines, and applicable regulatory requirements. While SAS expertise is required, experience with R programming, particularly data visualization and exploratory analysis is strongly preferred. We can put that as About the role. Now produce HTML fragment with headings

for each section. Use

• for lists. Use

  for prose. We must not include any extra text outside HTML. No markdown fences. Let's craft. Structure:

  About the role

  ... (the paragraph)

  Responsibilities

  • ...
  ...

  Qualifications

  • ...
  ...

  Benefits

  • ...
  ...

  Pay

  ... (pay range plus incentive info)

  We should not include Requirements or Skills sections. Check that we didn't repeat job title as heading. Good. Now ensure we preserve all substantive information: The responsibilities list includes all points. Did we miss any? Let's double-check the original responsibilities paragraph: It started with "Provides technical and/or operational leadership..." then "Works closely with Biostatistics..." then "Works closely with Data Management..." then "Manages internal and vendor statistical programming support; Maintains strong collaboration and governance with preferred vendors." then "Writes SAS and R code that produces or validates tables, listings, figures and analysis datasets, in support of clinical studies or complex integrated analyses for submission." then "Performs, plans and coordinates project work to ensure timely, quality delivery across multiple projects, or across a drug program." then "Writes specifications to describe programming needs, including development and maintenance of complex / ADaM specifications and reviewer guides." then "May lead the creation and validation of global macros or systems that streamline repetitive operations to increase programming efficiency." then "Provides input into, or leads general standardization efforts (e.g., CRFs, query checks, standard statistical programs, data presentations)." then "Leads efforts to develop programming processes consistent with industry best practices." then "Reviews and provides expert input to DMP, eCRF specs, and other clinical data management documents; Reviews and provides expert input to statistical analysis plans and other related documents." then "Partners with or oversees CROs or Programming vendors to perform any of the above tasks." We have all. Qualifications list: Let's ensure we captured each bullet. Original qualifications text: "Qualifications At least 10 years’ industry (Pharmaceutical, Biotech, CRO) SAS programming experience or equivalent;Experience as a Programming manager (FTEs, Functional Service Providers or vendors); Experience leading programming teams in support of clinical trials to report the results of clinical trials, integrate analyses across a program, or prepare data/analysis for electronic NDA or BLA submission;Experience in constructing technical programming specifications and producing complex, validated SAS programs;Demonstrated experience in working with CDISC standards, including SDTM, and ADaM, and Define xml;Proficiency in understanding of statistical programming environments, processes, procedures, and roles;Excellent knowledge of SAS/Base, SAS/Macro, SAS/STAT, SAS/Graph, and SAS/SQL with a demonstrated mastery of SAS/STAT procedures;Hands-on experience with R programming for clinical trial data analysis, reporting, and regulatory submissions.Knowledge of R packages and frameworks commonly used in clinical development, Posit Work