Senior Medical Director, Oncology Clinical Development (GI)

We need to output HTML fragment with sections: About the role? Actually the job description includes responsibilities etc. We need to use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include a section only when posting has real, specific content. The posting includes Company Description (About AbbVie) but that is not a section heading we need? The instructions: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections are present. We have: - Company Description: about AbbVie. Could be "About the role"? Actually "About the role" is generic; but we have company description. Might treat as "About the role"? The instruction says use those headings as examples, not mandatory. We can create sections that match content: maybe "About AbbVie" as a heading? But they said use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings if appropriate. But we can also use other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to use those exact headings when applicable. So we need to map content to those headings. We have: - About the role: could be the job description overview (first paragraph after Job Description). That is "Oversees the direction, planning, execution, and interpretation of clinical trials...". That's a description of the role. So we can put that under

About the role

with

. - Responsibilities: we have many bullet-like sentences describing duties. We can extract list items. - Requirements: maybe qualifications? Actually Qualifications section is separate. Requirements could be similar to Qualifications? But we have Qualifications section with MD etc. We could treat that as Qualifications. Requirements maybe not present distinct; but we could combine? The instruction: prefer a few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one? But they are separate headings examples. We need to decide. We have Qualifications: MD, residency, fellowship, 2 years experience, ability to run program, etc. Also skills: ability to interact, knowledge of clinical trial methodology, excellent oral/written English. We have Benefits: mention of comprehensive package of benefits including paid time off, medical/dental/vision insurance and 401(k), long-term incentive programs. Pay: The posting includes compensation range description under Additional Information: "Applicable only to applicants applying to a position in any location with pay disclosure requirements under state or local law: The compensation range described below is the range of possible base pay compensation...". However they didn't actually give numbers. It says range described below but no numbers provided. So we have no actual pay numbers. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. For Benefits, they do state benefits (paid time off, insurance, 401k, long-term incentive). So we can include Benefits. For Pay, they mention compensation range but no actual numbers; they say "The compensation range described below is the range of possible base pay compensation..." but they didn't give the range. So it's placeholder; we should not create Pay section because no specific numbers. Schedule: not mentioned. Thus sections: About the role, Responsibilities, Qualifications (maybe also Skills?), Benefits. We could also include Requirements if we have distinct content beyond Qualifications. The Qualifications section includes education, experience, abilities. That could be considered Requirements. But we have both Qualifications and Skills. The posting includes "Ability to run a clinical research program..." etc under Qualifications. Also "Knowledge of clinical trial methodology..." etc. Those could be skills. But we can combine. Given instruction to prefer few substantive sections, we could have About the role, Responsibilities, Qualifications (which includes education, experience, skills), Benefits. We must not repeat job title as heading. Not include Job ID etc. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The Additional Information includes EEO statements at end; we should remove those. Also remove the links to accommodation etc. Also remove the "Applicable only to applicants..." paragraph? That is about pay disclosure; we might keep it as part of Pay? But we are not including Pay because no numbers. However the paragraph about compensation range is part of Additional Information; but it's not concrete numbers, so we should not create Pay section. Should we keep that paragraph elsewhere? It's not a responsibility or qualification. It's about pay disclosure; maybe we can omit as it's not substantive content? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep that info if it's substantive. But it's about pay disclosure; it's not a concrete range but it's still info about pay policy. However we cannot create a Pay section because no actual range. Could we embed that info in Benefits? Not appropriate. Could we create a Pay section with that explanatory text but no numbers? The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It says "unless the posting actually states them." The posting does state something about pay (the compensation range description). So maybe we can include Pay section with that explanatory text (though no numbers). But they also said never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). The text "The compensation range described below is the range of possible base pay compensation that the Company believes in good faith it will pay for this role at the time of this posting based on the job grade for this position. Individual compensation paid within this range will depend on many factors including geographic location, and we may ultimately pay more or less than the posted range. This range may be modified in the future." This is not a specific range but it's a description. It might be considered placeholder? It's not a specific number, but it's not "not specified". It's a statement about range being described below (but not given). Since no actual numbers, it's essentially not providing a range. Might be considered filler. Safer to omit Pay section. Benefits: we have concrete benefits: paid time off (vacation, holidays, sick), medical/dental/vision insurance, 401(k), long-term incentive programs. So we can include Benefits. Thus final HTML:

About the role

Oversees the direction, planning, execution, and interpretation of clinical trials or research activities of one or more clinical development programs. Participates in cross-functional teams to generate, deliver, and interpret high-quality clinical data supporting overall product scientific and business strategy. Manages the design and implementation of one or more clinical development programs in support of an overall Product Development Plan, based on strong medical and scientific principles, knowledge of compliance and regulatory requirements, AbbVie’s customers, markets, business operations, and emerging issues. Oversees project-related education of investigators, study site personnel, and AbbVie study staff. Has overall responsibility for oversight of clinical studies, monitoring overall study integrity, and review, interpretation, and communication of accumulating data pertaining to safety and efficacy of the molecule. Along with Clinical Operations, is responsible for oversight of study enrollment and overall timelines for key deliverables. Responsible for assessment and reporting of serious adverse events per corporate policy and regulations for those protocols on which assigned. Responsible for design, analysis, interpretation, and reporting of scientific content of protocols, Investigator Brochures, Clinical Study Reports, regulatory submissions and responses, and other program documents. May oversee the work of Medical Directors and/or Scientific Directors, and of Clinical Scientists working on the same or related programs. Provides in-house clinical expertise for the molecule and disease, coordinating appropriate scientific and medical activities with internal stakeholders as they relate to ongoing clinical projects. May participate in due diligence or other business development activity. As required by program needs, contributes in partnership with Discovery colleagues to design and implementation of translational strategies. May serve on or chair a Clinical Strategy Team (CST), with responsibility for development of a rigorous, cross-functionally-aligned, vetted Clinical Development Plan with full consideration of contingencies and alternative approaches. In the role of CST Chair, responsibilities may include supervision of matrix team members and serving as Clinical Research representative to lend clinical development and medical expertise to an Asset Development Team (ADT), ADT Leadership Board (ALB). Acts as a clinical interface and actively solicits opinion leader interactions related to the molecule and disease area; partners with Medical Affairs, Commercial and other functions in these activities as required, consistent with corporate policies, to ensure that broad cross-functional perspectives are incorporated into Clinical Development Plans and protocols as appropriate. Stays abreast of professional information and technology through conferences, medical literature, and other available training, to augment expertise in the therapeutic area. Responsible for understanding the regulatory requirements related to the clinical studies and global drug development and accountable for complying with those requirements. Serves as a clinical representative for key regulatory discussions. Ensures adherence to Good Clinical Practices, pharmacovigilance standards, standard operating procedures and to all other quality standards in conducting research.

Responsibilities

• Oversee direction, planning, execution, and interpretation of clinical trials or research activities
• Participate in cross-functional teams to generate, deliver, and interpret high-quality clinical data
• Manage design and implementation of clinical development programs
• Oversee project-related education of investigators, study site personnel, and AbbVie study staff
• Oversee clinical studies, monitor study integrity, review, interpret, and communicate safety and efficacy data
• Oversee study enrollment and timelines for key deliverables (with Clinical Operations)
• Assess and report serious adverse events per policy and regulations
• Design, analyze, interpret, and report scientific content of protocols, Investigator Brochures, Clinical Study Reports, regulatory submissions and responses, and other program documents
• May oversee Medical Directors, Scientific Directors, and Clinical Scientists
• Provide in-house clinical expertise for the molecule and disease, coordinating scientific and medical activities with internal stakeholders
• May participate in due diligence or other business development activity
• Contribute to translational strategies with Discovery colleagues as needed
• May serve on or chair a Clinical Strategy Team (CST)
• Act as clinical interface and solicit opinion leader interactions; partner with Medical Affairs, Commercial, etc.
• Stay abreast of professional information and technology via conferences, literature, training
• Understand and comply with regulatory requirements for clinical studies and global drug development
• Serve as clinical representative for key regulatory discussions
• Ensure adherence to GCP, pharmacovigilance standards, SOPs, and quality standards

But note we already included many responsibilities in the About the role paragraph; we might be duplicating. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we put the long paragraph in About the role, we still need to keep the details; we could keep them there and not duplicate in Responsibilities. However we need to avoid duplication. The About the role paragraph already contains many of those responsibilities. So we could keep About the role as a summary paragraph, and Responsibilities as a list of specific duties (maybe not repeating the same sentences). But we risk omitting some details if we only list a subset. Better to keep About the role as a brief overview (maybe one or two sentences) and then list responsibilities in detail. However the posting's initial paragraph is quite detailed; we could treat that as About the role (overview) and then break out responsibilities as list items derived from the same content but not duplicate exact sentences. But we must preserve all substantive information; we can re