Medical Director - Heart Failure - US Central / West

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate like EEO etc. Also remove navigation, cookie, legal, duplicated lines, application instructions. Must not create sections with filler like "commensurate with experience". So we need to parse the posting. The posting includes: - About Us (company description) - but we need "About the role" heading? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings. The posting has "Job Purpose" which is about the role. That could go under About the role. Also "About Us" is company info, maybe not needed? The instruction says do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. It doesn't say we must include About Us; we can include it under About the role? Probably we should include relevant info about the role: Job Purpose, maybe also some company overview as context. But the heading "About the role" expects description of the role. We'll put Job Purpose content there. - Responsibilities: there is a "Job Responsibilities" section with two pillars and details. We'll put that under

Responsibilities

with

• items. - Requirements: there is "Education & Professional Background", "Required Experience and Capabilities", "GCP Requirement", "Additional Preferred Experience". These are requirements/qualifications. We'll split maybe into Requirements and Qualifications? The instruction lists both Requirements and Qualifications as possible headings. We need to decide what goes where. Typically Requirements = mandatory, Qualifications = preferred. We'll put mandatory under Requirements, preferred under Qualifications. Also "Education" could be under Requirements or Qualifications. We'll treat Education as part of Requirements (preferred but maybe required? It says "Advanced scientific or healthcare degree preferred". That's preferred, so maybe Qualifications. But we can put under Qualifications. Let's think: The posting says "Education & Professional Background Advanced scientific or healthcare degree preferred, e.g., MD, PharmD, PhD, NP, PA, MSc, or equivalent." That's a preference. Then "Required Experience and Capabilities Experience within cardiology is required; heart failure experience is preferred." etc. So we have required and preferred items. We'll create:

  Requirements

  for mandatory items: Experience within cardiology is required; Experience from clinical development, research and/or Medical Affairs; Demonstrated understanding of clinical trial conduct and investigator engagement; Experience collaborating with investigators, academic institutions, and cross-functional internal stakeholders; Ability to work effectively within cross-functional and matrix organizations; Strong scientific communication, relationship-building, and stakeholder-management skills; Ability to translate external insights into actionable recommendations for internal stakeholders; Basic GCP training or certification is preferred (but it's preferred, not required). Actually GCP is preferred. So maybe not required. We'll keep it under Qualifications. Also "Requires budgetary responsibilities and discretion with confidential data" and "Travelling – approximately 65% of the time" are additional info; could be under Requirements or maybe under Additional Information. We'll put them under Requirements as they are job demands. Qualifications: Preferred items: heart failure experience preferred; cardiovascular outcomes trial experience; launch or pre-launch experience; experience engaging US-based KOLs and national thought leaders; experience working across both clinical development and medical affairs environments; established KOL network within heart failure/cardiology; Advanced scientific or healthcare degree preferred; Basic GCP training or certification preferred. Also "Success Profile" and "Competencies" maybe could be under Skills? The instruction includes Skills heading. We could put competencies under Skills. Also "Attitude and Demeanor" list could be under Skills. Benefits, Pay, Schedule: The posting does not mention benefits, pay, or schedule specifics besides travel 65% (schedule?). It mentions travel approx 65% of the time, which is schedule-related. So we could include Schedule section with that detail. Benefits and Pay not mentioned, so we should not create those sections. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Schedule. We must not include empty sections. Now we need to preserve all substantive information; do not invent or summarize away detail. Must keep details. We need to format as HTML fragment: use

  for headings,

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

    for prose. We must not repeat job title. No markdown fences. We need to extract prose paragraphs for About the role: from "Job Purpose" paragraph(s). Also maybe include "About Us"? Not required but could be considered part of About the role? The instruction says About the role heading; we can include both company overview and job purpose as prose. But we must preserve all substantive information; if we omit About Us, we lose some info about company. However the instruction says we should include sections only when posting has real, specific content for it. The About Us is present; we could put it under About the role as prose. That seems okay. Thus About the role will contain paragraphs: first the About Us description, then Job Purpose. We need to ensure we don't include boilerplate like EEO etc. At the end there is a long EEO statement; we must remove that. Also remove duplicated lines, navigation, cookie, legal, scam-warning, application instructions. There's no explicit application instructions besides "To learn more visit www.pharmacosmos.us". That's maybe minor metadata; we could fold into a short

    or drop it. The instruction says fold minor metadata into a short

    or drop it. We could include that as a short p under About the role maybe. But it's not essential; we could drop it. Safer to drop it. Also "All job requirements listed indicate the minimum level..." etc is boilerplate; we should remove that. Also "This job description is not to be construed as an exhaustive statement..." etc remove. Also "Pharmacosmos Therapeutics Inc. is committed to equal opportunity..." remove. Now we need to list responsibilities as

    • . The responsibilities section has many sentences; we need to break into list items. We should preserve all substantive information; we can split each sentence or clause into separate
    • . Must not lose details. Let's extract responsibilities: Under "Job Responsibilities The responsibilities are structured in two complementary pillars" Then "Boundaries of the Role Trial Support ICONIC-HF Site Engagement and Enrollment Enablement The purpose of this pillar is to strengthen investigator engagement, facilitate communication, and generate insights that support successful trial execution." Then a list of bullet-like sentences (though not formatted as bullets). We'll convert each sentence to
    • . List: - Establish and maintain strong scientific relationships with investigators, study coordinators, and other site personnel involved in ICONIC-HF. - Conduct regular site engagements, virtually and in person where relevant, to understand local opportunities, challenges, operational barriers and operate within compliance, GCP, and trial governance frameworks. - Serve as a US-based scientific liaison between participating sites and the HQ R&D ICONIC-HF trial team in coordination with the US affiliate and the contracted CRO. - Identify, understand, and communicate barriers that may impact screening, enrollment, site engagement, or study execution, analyze potential root causes, and help defining mitigations activities with HQ R&D ICONIC-HF trial team and the CRO. - Facilitate appropriate cross-functional problem solving and escalation pathways when barriers are identified. - Support protocol understanding and scientific discussions within approved governance frameworks. - Gather and communicate investigator insights, competitive intelligence, protocol feedback, and study-related observations to internal stakeholders. - Organize and facilitate regional sponsor-investigator touchpoint meetings as appropriate. - Identify and share best practices from successful sites to support broader site engagement efforts, where appropriate and compliant. - Support site activation and engagement initiatives in partnership with HQ R&D ICONIC-HF trial team and the CRO. - Maintain a strong understanding of site experiences and investigator perspectives throughout the study lifecycle. - Does not function as a CRA. - Does not perform monitoring activities. - Does not conduct source data verification. - Does not own enrollment metrics or site performance targets. - Does not manage day-to-day clinical trial operations. These responsibilities remain with HQ Clinical Operations and the CRO. Then second pillar: "Strategic Heart Failure Insights, Advocacy Development and Launch Readiness The purpose of this pillar is to establish Pharmacosmos as a trusted scientific partner in heart failure while building the foundation for future adoption of IV iron in this therapeutic area." Then list: - Develop a deep understanding of the evolving US heart failure landscape, including treatment pathways, referral patterns, unmet needs, evidence gaps, barriers to adoption, and emerging trends relevant to IV iron. - Map, prioritize, and engage regional and national heart failure thought leaders. - Build and maintain scientific relationships with key experts beyond the ICONIC-HF investigator network. - Generate actionable insights that can support future evidence generation, publication planning, congress activities, scientific communication, advisory board strategy, and launch readiness. - Partner closely with HQ and the US affiliate to ensure field insights are translated into strategic recommendations. - Support identification and prioritization of investigator-sponsored research opportunities. - Contribute to long-term medical affairs strategy and launch-readiness planning for IV iron in heart failure. - Support future launch-readiness initiatives through close partnership with Medical Affairs, Strategy and Operations, Market Access, and Commercial colleagues while maintaining full compliance with applicable governance requirements. Then "Policies, Procedures & Compliance Stay current and in compliance both individually and as a department to align with industry best practices. This includes all Corporate Policies as well as mandated government Regulations. Ensure adherence to all relevant laws, regulations, and guidelines related to pharmaceutical operations, including FDA, EMA, and other global health authority regulations. Stay current with and adhere to all policies and procedures as outlined in the employee handbook." We could treat that as part of Responsibilities or maybe as a separate section like Compliance. But we only have allowed headings; we could include under Responsibilities as additional items. Or we could create a separate section like "Compliance" but not allowed. So we will include under Responsibilities as list items. Thus responsibilities list includes those compliance items. Now Requirements: mandatory items. From text: "Education & Professional Background Advanced scientific or healthcare degree preferred, e.g., MD, PharmD, PhD, NP, PA, MSc, or equivalent." That's preferred, not required. So maybe not in Requirements. "Required Experience and Capabilities Experience within cardiology is required; heart failure experience is preferred." "Experience from clinical development, research and/or Medical Affairs." "Demonstrated understanding of clinical trial conduct and investigator engagement." "Experience collaborating with investigators, academic institutions, and cross-functional internal stakeholders." "Ability to work effectively within cross-functional and matrix organizations." "Strong scientific communication, relationship-building, and stakeholder-management skills." "Ability to translate external insights into actionable recommendations for internal stakeholders." "GCP Requirement Basic GCP training or certification is preferred. Training can be provided for an otherwise qualified candidate." That's preferred. "Additional Preferred Experience Heart failure expertise. Cardiovascular outcomes trial experience. Launch or pre-launch experience. Experience engaging US-based KOLs and national thought leaders. Experience working across both clinical development and medical affairs environments. Established KOL network within heart failure/cardiology." Also "Requires budgetary responsibilities and discretion with confidential data" and "Travelling – approximately 65% of the time" are additional info. Thus for Requirements (mandatory) we include: - Experience within cardiology is required. - Experience from clinical development, research and/or Medical Affairs. - Demonstrated understanding of clinical trial conduct and investigator engagement. - Experience collaborating with investigators, academic institutions, and cross-functional internal stakeholders. - Ability to work