DirectJobHub
Jobs · Engineering

Principal Stat Programmer(ADAM & TLF)

Syneos Health · Marion County, IN · 1 mo ago
RemoteRemoteEngineeringFull-time
We need to produce HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes description about company (maybe About the role?), responsibilities list, qualifications list, skills list (maybe overlapping). No explicit Benefits, Pay, Schedule. So we should not include those sections. Also we should not repeat job title as heading. We need to include sections: About the role (maybe the introductory paragraph about Syneos Health?), Responsibilities, Requirements, Qualifications, Skills. However we need to avoid duplication. The posting includes "Job Responsibilities" section with many bullet-like sentences. Then "Qualifications:" with list. Also there is "Get to know Syneos Health" etc. Also "Additional Information" etc. We need to preserve all substantive info, but remove boilerplate like EEO, legal, navigation, etc. Also remove duplicated lines. We need to decide what goes into each section. About the role: Could be the initial description about Syneos Health and the role context. The posting starts: "Description Principal Stat Programmer(ADAM & TLF) Syneos Health® is a leading fully-integrated life sciences services organization..." That's about the company and role. Could be considered About the role. We'll put that in

About the role

with paragraphs. Responsibilities: Use the "Job Responsibilities" block. We'll convert each sentence into
  • items inside
      . Ensure we keep all details. Requirements: Might be similar to Qualifications? The posting has "Qualifications:" then list. There's also "Requirements" maybe not explicit. Could treat Qualifications as Requirements. But we have both Requirements and Qualifications as possible headings. We need to decide based on content. The posting includes "Qualifications:" with bullet-like items. There's no separate "Requirements" heading. So we could put that under Qualifications. Or we could treat "Qualifications" as Requirements and also have Skills section for things like communication skills, problem-solving, etc. The qualifications list includes both technical and soft skills. We could split: Requirements (experience, years, specific SAS experience) and Skills (communication, problem-solving, mentoring, etc.). Let's parse. Qualifications list: - Require 8+ experience in Clinical SAS, Base SAS, Advance SAS, SAS/Macros. - Strong experience in ADAM & TLF programming including ADaM specifications, dataset generation, - Good to have experience of ISDB-ISS, pooling study - Must have experience of client handling, leading studies. - Good to have experience of both safety & efficacy data. - Experience in mentoring others in clinical trial process and CDISC Standards. - Strong communication skills, problem-solving abilities, and ability to work collaboratively in a dynamic environment. Thus we can separate: Requirements (hard experience) and Skills (soft skills). But the instruction says use headings only when posting has real specific content for it. We have both. We could make:

      Responsibilities

      with ul.

      Requirements

      with ul for the hard requirements: 8+ experience in Clinical SAS, Base SAS, Advance SAS, SAS/Macros; Strong experience in ADAM & TLF programming including ADaM specifications, dataset generation; Good to have experience of ISDB-ISS, pooling study; Must have experience of client handling, leading studies; Good to have experience of both safety & efficacy data; Experience in mentoring others in clinical trial process and CDISC Standards.

      Skills

      with ul for: Strong communication skills, problem-solving abilities, ability to work collaboratively in a dynamic environment. But note that mentoring etc could be skill as well. However we already put mentoring under Requirements; could move to Skills. But we need to preserve all info; duplication not needed. We'll decide. Better: Requirements: technical experience (SAS, ADaM/TLF, ISDB-ISS, client handling, safety/efficacy). Skills: communication, problem-solving, collaboration, mentoring, CDISC standards. Let's extract: Technical requirements: - 8+ experience in Clinical SAS, Base SAS, Advance SAS, SAS/Macros. - Strong experience in ADAM & TLF programming including ADaM specifications, dataset generation. - Good to have experience of ISDB-ISS, pooling study. - Must have experience of client handling, leading studies. - Good to have experience of both safety & efficacy data. Skills/Other: - Experience in mentoring others in clinical trial process and CDISC Standards. - Strong communication skills, problem-solving abilities, and ability to work collaboratively in a dynamic environment. We could also include "Experience in mentoring others..." as skill. Thus:

      Requirements

      • 8+ years of experience in Clinical SAS, Base SAS, Advance SAS, SAS/Macros.
      • Strong experience in ADAM & TLF programming including ADaM specifications and dataset generation.
      • Good to have experience of ISDB-ISS and pooling studies.
      • Must have experience of client handling and leading studies.
      • Good to have experience of both safety and efficacy data.

      Skills

      • Experience in mentoring others in clinical trial process and CDISC Standards.
      • Strong communication skills, problem‑solving abilities, and ability to work collaboratively in a dynamic environment.
      Now About the role: We'll take the initial paragraph(s) up to maybe before "Job Responsibilities". Let's capture: "Description Principal Stat Programmer(ADAM & TLF) Syneos Health® is a leading fully-integrated life sciences services organization built to accelerate customer success. We partner with innovators at every point across the drug development and commercialization continuum, helping them navigate complexity, anticipate change and accelerate progress. Our Clinical Solutions team members act with a drug development mindset, applying their years of experience and deep expertise to truly understand customer needs and represent those in the solutions we shape. Whether you join us in a Functional Service Provider partnership or a Full-Service environment, you’ll collaborate with passionate problem solvers, innovating as a team to help our customers achieve their goals. We are agile and driven to deliver – for one another, our customers, and, most importantly, for those in need. Discover what your 25,000 future colleagues already know: Why Syneos Health We are passionate about developing our people, through career development and progression; supportive and engaged line management; technical and therapeutic area training; peer recognition and total rewards program. We are committed to building an inclusive culture – where you can authentically be yourself. Central to this is our purpose – Driven to Deliver – which captures the passion of our colleagues to show up each day and shape solutions that have the ability to dramatically impact someone’s life. We are continuously building the company we all want to work for and our customers want to work with. Why? Because we know that when we bring together smart colleagues from across the world, we can shape the future of healthcare, driving impact for customers and defining the pace of patient progress." That's a lot; we can keep as paragraphs. Might be too long but we must preserve all substantive info. We'll put into

      elements. We should remove boilerplate like "Get to know Syneos Health Over the past 5 years..." etc? That is also substantive but maybe belongs to About the role as well. However "Get to know Syneos Health" includes stats; that's also substantive. We could include that as part of About the role. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Get to know Syneos Health" is not boilerplate; it's info about the company. So we should keep. Thus About the role will include the initial description plus the "Get to know Syneos Health" paragraph(s). Also maybe "Summary Roles within the Statistical Programming job family..." is more generic description of the job family; could be considered About the role as well. But we might treat that as part of About the role or maybe as a separate section? There's no heading for it. It's substantive. We could include it in About the role as additional paragraphs. We need to avoid duplication: The "Summary Roles within the Statistical Programming job family..." appears near the end. It's generic but still substantive. We'll include. We also have "Additional Information Tasks, duties, and responsibilities as listed in this job description are not exhaustive..." That's boilerplate-ish (legal). Should be removed per instruction: remove boilerplate. So we will omit that. Also "Equivalent experience, skills, and/or education will also be considered..." also boilerplate-ish; remove. Also "The Company, at its sole discretion..." etc. Remove. Also "Occasionally, required skills/experiences for jobs are expressed in brief terms..." Remove. Thus we keep: initial description, "Get to know Syneos Health" stats, maybe "Summary Roles within the Statistical Programming job family..." (makes sense). Also maybe "Impact and Contribution" section? That's also substantive about role level. Could include in About the role as well. We'll parse the rest: After Qualifications list, there is: "Get to know Syneos Health Over the past 5 years, we have worked with 94% of all Novel FDA Approved Drugs, 95% of EMA Authorized Products and over 200 Studies across 73,000 Sites and 675,000+ Trial patients. No matter what your role is, you’ll take the initiative and challenge the status quo with us in a highly competitive and ever-changing environment. Learn more about Syneos Health. http://www.syneoshealth.com" That's substantive. Then "Additional Information Tasks, duties, and responsibilities as listed in this job description are not exhaustive..." (remove). Then "Equivalent experience, skills, and/or education will also be considered..." (remove). Then "Further, nothing contained herein should be construed to create an employment contract." (remove). Then "Occasionally, required skills/experiences for jobs are expressed in brief terms..." (remove). Then "Any language contained herein is intended to fully comply..." (remove? It's legal compliance; maybe remove as boilerplate). The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is legal compliance; likely remove. Then "The Company is committed to compliance with the Americans with Disabilities Act..." (remove). Then "Summary Roles within the Statistical Programming job family are responsible for developing programs and providing statistical programming support for statisticians or for client or business use to address needs for sourcing, organizing (creating statistical tables, listings, and graphs), and interpreting complex data sets utilizing codes and programs. This includes developing codes that create analysis datasets, tables, and figures, evaluating programming processes, and suggesting revisions geared toward increasing productivity." (keep). Then "Impact and Contribution Individual contributors with responsibility in a professional or technical discipline or specialty, but may manage two or fewer employees. May direct the work of lower level professionals or manage processes and programs. The majority of time is spent contributing to the design, implementation or delivery of processes, programs, and policies, using knowledge and skills typically acquired through advanced education. Leading expert individual contributor who is viewed as a valuable resource by peers. Works to achieve organizational, functional, and/or business targets with measurable impact on department results. Manages or contributes to projects, programs, or processes that span multiple related areas. Comprehensive knowledge and skills in a professional discipline, understanding the impact of work on related areas." (keep). Thus About the role will include all those paragraphs. Now we need to format as HTML fragment:

      About the role

      then

      ...

      possibly multiple paragraphs. We must not include any markdown fences. Let's craft. We'll need to escape any HTML special characters? Not needed. We'll produce:

      About the role

      Description Principal Stat Programmer(ADAM & TLF) Syneos Health® is a leading fully-integrated life sciences services

    • Similar jobs