Senior Manager, Global Clinical Scientist - Neuroscience

We need to output HTML fragment with sections: About the role? The posting includes a purpose-driven culture paragraph at start. That could be "About the role" or maybe "About the company". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. Thus we need to extract substantive content: The posting includes: - Intro paragraph about BMS culture: "At Bristol Myers Squibb, our employees often ask, “Who are you working for?”—a question that fuels collaboration, accountability, and urgency in our work. Our purpose-driven culture inspires us to discover, develop, and deliver innovative medicines to prevail over serious diseases. We offer uniquely interesting and meaningful work, opportunities for growth, and a supportive environment that values inclusion, wellbeing, flexibility, and comprehensive benefits. This is work that transforms the lives of patients, and the careers of those who do it." - Position Summary / Objective: "Will be responsible for design and execution of assigned clinical trial activities and work closely with clinical team members within the assigned project to execute activities associated with the conductMay serve as Clinical Trial Lead for one or more trialsMay lead or support trial level activities for one or more trials with the necessary supervisionMay co-lead study team meetings in partnership with GDO protocol manager and collaborate with cross-functional study team members" That seems garbled due to missing spaces. We need to preserve as is? Probably we should keep the text but maybe fix missing spaces? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep exactly as given, but we could add spaces for readability? That would be altering content. Better to keep as is, but it's messy. However we could insert spaces where missing to make sense but that's altering. The instruction says do not invent or summarize away detail; adding spaces is not inventing new info, just formatting. Might be okay but risk. Probably keep as is. - Position Responsibilities: list of bullet-like sentences: "Collaborate and liaise with external partners (e.g., KOLs)Seek out and enact best practices with instructionProvide regular and timely updates to manager/management as requestedDevelop Protocol and ICF documents / amendments and present these to governance committee and development team meetings as requiredConduct literature reviewSubmit clinical documents to TMFDevelop site and CRA training materials and present these at SIVs and Investigator meetingsReview clinical narrativesMonitor clinical data for specific trendsDevelop Data Review Plan in collaboration with Data ManagementEnsure CRF design adequately supports data collection in alignment with the protocol in collaboration with Data Management/ProgrammingSubmit clinical contributions to clinical study reports (CSRs) and clinical portions of Regulatory Documents (e.g., IB, DSUR, PSUR, Orphan Annual Reports, HA, EC, IRB responses and contribute to regulatory submission.)" Again missing spaces. - Degree Requirements: "Degree in Life Sciences (MD, PhD, Pharm D, MS, RN or other scientific field preferred). Appropriate for new entrance to pharma (post fellowship/ new to industry)" - Experience Requirements: "Basic knowledge of GCP/ICH, drug development process, study design, statistics, clinical operationsAbility to understand assigned protocol(s) and their requirementsBasic knowledge skills to support program-specific data review and trend identificationIntermediate medical writing skills and medical terminologyBasic planning/project management skills (develop short range plans that are realistic and effective)" - Key Competency Requirements: list: "Detail-oriented with commitment to qualityBasic knowledge of disease area, compound, current clinical landscapeBasic knowledge of the establishment and operation of data monitoring committees, dose review teams, and independent response adjudication committeesIntermediate critical thinking and problem-solving skillsAdaptable / flexible (willing and able to adjust to multiple demands and shifting priorities; ability to meet day-to-day challenges with confidence and professionalism)Intermediate skills in Microsoft Word/Excel/PowerPoint and data review tools (e.g., Pt Profiles, report generating tools)" - Travel Required: "Domestic and International travel may be required." - Compensation Overview: includes three location pay ranges: Cambridge Crossing: $173,390 - $210,110; Madison - Giralda - NJ - US: $150,770 - $182,701; Princeton - NJ - US: $150,770 - $182,701. Also note about discretionary incentive cash and stock opportunities. - Benefits: paragraph about benefit plans, FTO, holidays, etc. - How We Work: description of work models. - Supporting People With Disabilities: paragraph. - Candidate Rights: paragraph. - Data Protection: paragraph. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The sections like "Supporting People With Disabilities", "Candidate Rights", "Data Protection" might be considered legal/EEO boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Those sections are legal/EOO statements. Likely we should remove them. Also "How We Work" maybe not boilerplate but could be considered generic; but it's substantive about work models. Might keep. We need to include sections only when posting has real, specific content. So we need to decide which sections to include: About the role (intro), Responsibilities, Requirements (maybe combine Degree, Experience, Key Competency), Qualifications? Could combine Degree Requirements and Experience Requirements into Requirements. Skills maybe from Key Competency. Benefits and Pay sections are present (Compensation Overview and Benefits). Schedule not present (no schedule info). So we should not create Schedule section. Thus sections: About the role (intro paragraph), Responsibilities (list), Requirements (maybe split into Degree Requirements, Experience Requirements, Key Competency Requirements as sub-sections? But we should prefer few substantive sections over many thin ones. Could combine all into one Requirements section with subheadings? But we only allowed

  for section headings; we could have multiple

  sections. The instruction: Prefer a few substantive sections over many thin ones. So maybe we have About the role, Responsibilities, Requirements (combining degree, experience, competencies), Benefits, Pay. That's five sections. We need to use

  • for any list of duties/requirements/benefits. So for Responsibilities we need a list. For Requirements we could also list items (degree, experience, competencies) as list. For Benefits we could list items (wellbeing support, retirement, etc.) as list. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from each section. Let's extract each piece precisely. Intro paragraph: exactly as given: "At Bristol Myers Squibb, our employees often ask, “Who are you working for?”—a question that fuels collaboration, accountability, and urgency in our work. Our purpose-driven culture inspires us to discover, develop, and deliver innovative medicines to prevail over serious diseases. We offer uniquely interesting and meaningful work, opportunities for growth, and a supportive environment that values inclusion, wellbeing, flexibility, and comprehensive benefits. This is work that transforms the lives of patients, and the careers of those who do it." We'll put that in

    . Position Summary / Objective: The text after "Position Summary / Objective". It seems to be a run-on. We'll keep as is, maybe treat as part of Responsibilities? Actually it's separate summary. Could include in About the role? But we already have intro. Might treat as part of Responsibilities? Better to have a separate "Position Summary" but not in allowed headings list. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we could put summary under About the role or Responsibilities. Since it's about what the role will be responsible for, maybe include in Responsibilities. But we already have Responsibilities list. Could add summary as a paragraph before the list. Thus About the role: intro paragraph only? Or include summary? The instruction: Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role containing the introductory culture paragraph. Then Responsibilities containing the summary and list of responsibilities. Let's do that. Responsibilities: first a paragraph: "Will be responsible for design and execution of assigned clinical trial activities and work closely with clinical team members within the assigned project to execute activities associated with the conductMay serve as Clinical Trial Lead for one or more trialsMay lead or support trial level activities for one or more trials with the necessary supervisionMay co-lead study team meetings in partnership with GDO protocol manager and collaborate with cross-functional study team members" Then a list of responsibilities (the bullet-like sentences). We need to split them into

    • . The sentences are currently concatenated without spaces. We need to separate them into list items. We need to infer where each responsibility begins. Let's parse: "Collaborate and liaise with external partners (e.g., KOLs)Seek out and enact best practices with instructionProvide regular and timely updates to manager/management as requestedDevelop Protocol and ICF documents / amendments and present these to governance committee and development team meetings as requiredConduct literature reviewSubmit clinical documents to TMFDevelop site and CRA training materials and present these at SIVs and Investigator meetingsReview clinical narrativesMonitor clinical data for specific trendsDevelop Data Review Plan in collaboration with Data ManagementEnsure CRF design adequately supports data collection in alignment with the protocol in collaboration with Data Management/ProgrammingSubmit clinical contributions to clinical study reports (CSRs) and clinical portions of Regulatory Documents (e.g., IB, DSUR, PSUR, Orphan Annual Reports, HA, EC, IRB responses and contribute to regulatory submission.)" We need to split at each capital letter that starts a new verb? Let's try: 1. Collaborate and liaise with external partners (e.g., KOLs) 2. Seek out and enact best practices with instruction 3. Provide regular and timely updates to manager/management as requested 4. Develop Protocol and ICF documents / amendments and present these to governance committee and development team meetings as required 5. Conduct literature review 6. Submit clinical documents to TMF 7. Develop site and CRA training materials and present these at SIVs and Investigator meetings 8. Review clinical narratives 9. Monitor clinical data for specific trends 10. Develop Data Review Plan in collaboration with Data Management 11. Ensure CRF design adequately supports data collection in alignment with the protocol in collaboration with Data Management/Programming 12. Submit clinical contributions to clinical study reports (CSRs) and clinical portions of Regulatory Documents (e.g., IB, DSUR, PSUR, Orphan Annual Reports, HA, EC, IRB responses and contribute to regulatory submission.) That seems correct. We'll output each as
    • . Now Requirements: we need to include Degree Requirements, Experience Requirements, Key Competency Requirements. Could combine into one section with subheadings? But we only allowed

      for section headings; we could have multiple <