Director, Program Lead – Women’s Health and Preeclampsia

We need to output HTML fragment with sections: h3 headings for sections present: About the role? Actually we have Company Summary, Position Summary, Key Responsibilities, Qualifications, Values and Behaviors, About Flagship Pioneering, Recruitment & Staffing Agencies, Salary range, Benefits, Privacy Notice. We must not repeat job title as heading. Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should map content to these headings where appropriate. We need to include sections only when posting has real, specific content. Avoid filler like "commensurate with experience". We have salary range: $179,000 - $236,500. So we can have Pay section with that. Benefits: they mention healthcare coverage, annual incentive program, retirement benefits and a broad range of other benefits. So Benefits section. Schedule: not mentioned, so omit. Skills: maybe not explicit; we could skip. Requirements: Qualifications section. Responsibilities: Key Responsibilities. About the role: Position Summary. Also maybe Company Summary as About the company? Not required but could be included as a section? The instruction: use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should stick to those. Could include About the company as maybe not needed. But we can include Company Summary as a paragraph before sections? Probably better to include as a

before sections. The instruction: 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. So we can keep Company Summary as a

before sections. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we must strip out the EEO statement, recruitment agency stuff, privacy notice, etc. Also remove the Flagship Pioneering description? That's not boilerplate but maybe considered company info; but it's not required. Might be okay to keep as part of Company Summary? It's separate. The instruction: Prefer a few substantive sections over many thin ones. So we could combine some. We need to preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep all substantive content from the posting, except boilerplate. That includes: Company Summary (first paragraph), Position Summary, Key Responsibilities (with sub-bullets), Qualifications (Required and Preferred), Values and Behaviors, About Flagship Pioneering (maybe considered substantive), Salary range, Benefits statement, maybe also the note about compensation depending on factors. Also the line about "ProFound Therapeutics, Inc. currently offers healthcare coverage, annual incentive program, retirement benefits and a broad range of other benefits." That's benefits. We must not include the recruitment agency stuff, privacy notice, EEO, etc. We need to format lists with

• . For responsibilities, we have bullet points under Program Leadership and Scientific and Discovery Leadership. We'll need to capture each bullet as
• . The responsibilities are nested; we can flatten. Similarly Qualifications: Required and Preferred each have bullet-like sentences separated by periods. We'll need to parse into list items. Values and Behaviors: paragraph. About Flagship Pioneering: paragraph. We'll need to decide headings: About the role (Position Summary), Responsibilities (Key Responsibilities), Requirements (Qualifications), Benefits, Pay. Possibly also About the company? Not required but could be included as a

  before sections. We must not create sections with filler. So we will include only those with content. Let's extract content. Company Summary paragraph: "ProFound™ Therapeutics is a biotechnology company discovering novel proteins across the expanded human proteome to unlock transformative drug targets and first-in-class medicines. The company’s proprietary ProFoundry™ Platform integrates state-of-the-art protein detection, validation, and computational technologies to systematically identify and characterize previously unknown proteins and validate their therapeutic potential. This approach has generated a rapidly expanding portfolio of novel targets and programs advancing toward the clinic, along with strategic collaborations with leading pharmaceutical partners. Together, these efforts support the development of breakthrough treatments across a broad range of disease areas. For more information, please visit www.profoundtx.com." We'll keep as

  . Position Summary paragraph: "ProFound Therapeutics is seeking a Director, Program Lead to lead our discovery program in Women’s Health, with an initial focus on preeclampsia and hypertensive disorders of pregnancy. The Program Lead is accountable for the Project Team (PT) and for the overall technical direction, execution, and success of the program, while providing direct scientific leadership to the team executing its laboratory work. The program is anchored by ProFound’s Gates Foundation–funded work and sits within the Cardiovascular, Metabolic, and Neuroscience therapeutic area, giving the Program Lead a funded mandate and defined collaboration goals from day one. The successful candidate brings a strong foundation in Women’s Health, vascular biology, hypertension, or a similar area of biology, as well as the scientific depth to direct and interpret mechanistic work spanning in vitro and in vivo models, and the ability to own program strategy end to end and represent it at the most senior levels of ProFound, Flagship, and partner organizations. The role is approximately 75% program leadership and external-facing work and 25% direct scientific leadership of the researchers executing the program’s laboratory work guiding experimental design, interpreting results, and translating them into program strategy." We'll put under

  About the role

  . Key Responsibilities: we have two main categories: Program Leadership and Scientific and Discovery Leadership, each with bullet points. Let's extract bullet points: Program Leadership: - Build, sustain, and develop a motivated, high-performing PT; leverage internal and external expertise, including advisory and counseling boards; collaborate closely with groups outside the PT. - Accountable for the PT, for the overall technical, development, and delivery success of the program, and for lean, fast execution of discovery and early development against defined milestones; able to speak to any program-related topic internally and externally. - Lead the PT to develop and drive program strategy that achieves collaboration goals and progresses novel protein targets through the defined pipeline stages; own and update the strategy and Target Product Profile (TPP), anticipating internal and external drivers. - Empowered to make program execution decisions; accountable for framing and recommending stage-gate and advancement options to relevant senior decision makers for continuous alignment on program vision and strategy. - Responsible for the financial steering of long-term program budgets as assigned by senior leadership, including forecasting, prioritization of spend, and accountability for delivery against budget. - Accountable to ProFound management and to relevant joint oversight committees with partners for all aspects of the PT’s activities. - Serve as a principal scientific and operational point of contact for the Gates Foundation collaboration, accountable for delivery against agreed goals, milestones, and reporting commitments. Scientific and Discovery Leadership: - Set the scientific direction for discovery research in preeclampsia and hypertension in pregnancy, and direct the design, execution, and interpretation of mechanistic studies using state-of-the-art models and technologies. - Provide day-to-day scientific leadership to the scientists and research associates executing the program’s laboratory work — experimental design, troubleshooting, data interpretation, and prioritization of effort. - Ensure timely creation and delivery of a Preeclampsia AI tool for evaluating and prioritizing novel preeclampsia biomarkers and drug targets. - Partner with computational biology and proteomics teams to apply AI and machine learning to large-scale datasets and prioritize targets with high translational potential. - Translate experimental output into program strategy — interrogating data, testing conclusions, and converting findings into decisions on target prioritization, study design, and pipeline direction. - Lead target validation informed by proteomic and computational insights, partnering with biology and proteomics teams and other in-house experts. - Design and oversee in vitro and in vivo models of disease to support target biology, biomarker development, and proof-of-concept studies. - Shape ProFound’s therapeutic strategy in Women’s Health, including assessment of new indications, and lead external academic and industry collaborations. We'll put under

  Responsibilities

  with a
  • for each bullet. Qualifications Required: list items: - M.D, Ph.D., or equivalent in Physiology, Cell Biology, Reproductive Biology, or a related discipline. - 12+ years of relevant postdoctoral and/or biotech or pharmaceutical industry experience, including a minimum of 4 years leading cross-functional project teams or programs with accountability for strategy, budget, and delivery. - Demonstrated ownership of a discovery or early development program, including advancement recommendations and defense of strategy to senior leadership or governance committees. - Experience building, leading, and developing scientific teams, through direct reporting relationships or a matrixed project team, including guiding the technical work of bench scientists. - Experience owning and steering multi-year program budgets, including forecasting and prioritization of spend. - Deep understanding of disease mechanisms and translational models for pharmaceutical development. - Deep technical command of cellular and molecular biology techniques (e.g., CRISPR, ELISA, qPCR, Western blotting, RNA-seq) and assay development, sufficient to direct experimental design, interpret primary data, and challenge conclusions; ability to integrate multi-omic or genetic data into experimental design. - Strong track record of scientific contributions (publications, patents, presentations), and excellent communication, collaboration, and organizational skills in a fast-paced, team-oriented environment. Preferred: - Experience in early-stage biotech or drug discovery from target identification through candidate selection or IND, and with stage-gate pipeline governance. - Experience with human tissue samples, iPSC-derived systems, or organoid models. - Experience representing a program to boards, joint steering committees, or pharmaceutical partners. - Experience within grant-funded, foundation-funded, or global health research collaborations and their reporting and governance expectations. We'll put under

    Requirements

    (or Qualifications). The instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use Requirements for the required qualifications, and maybe Qualifications for preferred? But they said Qualifications as a heading. Could combine required and preferred under Qualifications with subheadings? But we should avoid filler. Probably best to have a single Qualifications section with both required and preferred as lists, maybe with subheadings Required and Preferred inside. But we must not invent headings not listed? The instruction says use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should stick to those. Could have Qualifications h3 and inside we can have

    with required and preferred paragraphs. But we need to preserve list structure. Could do

    Qualifications

    then
    • for required, then another
      • for preferred with a note? Might be confusing. Better: Use

        Requirements

        for required, and

        Qualifications

        for preferred? But they listed both Requirements and Qualifications as examples. So we can have both sections. Thus:

        Requirements

        with ul list of required items.

        Qualifications

        with ul list of preferred items. Values and Behaviors: paragraph. We could put under

        Values and Behaviors

        but not in the list of examples. However we could include as a

        after Qualifications. The instruction: use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should prefer few substantive sections. Values and Behaviors is substantive; we could include as a section with h3 maybe "Values and Behaviors". It's not in the examples but likely acceptable. However to be safe,