Senior Director, Global Market Access

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. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the posting. Sections present: - Who We Are (company description) – could be "About the role"? Actually "Who We Are" is about company, not role. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have: - The Role description (paragraph about role). That could go under "About the role". Should include description of role, reporting line, remit, etc. - Responsibilities: bullet list under "Responsibilities". The posting has sections: Global Market Access & Value Strategy, Evidence, HEOR & Oncology Value Strategy, Pricing & Reimbursement, Launch Readiness. Those are subheadings but we can treat them as list items under Responsibilities. - Qualifications: bullet list under "Qualifications". The posting has a list of qualifications. - Skills: maybe not explicitly separate; but qualifications include skills. Could we create a Skills section? The posting does not have a separate skills list; but we could extract skills from qualifications: strong analytical, strategic planning, project management, communication skills. Could put under Skills. - Benefits: The posting has "Our Offer To You" describing benefits: competitive salary, bonus, stock awards, benefits package, 100% medical/dental/vision premiums, funding up to 75% of in-network deductibles, 401(k) match, generous PTO, 12 weeks paid parental leave, paid family and medical leave, company-paid short-term disability up to 20 weeks, wellness programs, tuition reimbursement, inclusive family-forming support. Also mention locations (Waltham, MA; Boulder, CO) with amenities. Should we include location info under Benefits? Possibly as part of Benefits or separate? The instruction only allows those headings; we could include location details under Benefits or maybe under About the role? Better to put location info under Benefits as part of offer. - Pay: Salary Range $260,000 to $305,000 USD Target Bonus: 25% Exact compensation will vary based on skills, experience, and location. That's pay info. - Schedule: Not mentioned. No schedule info (e.g., full-time, remote). So we should not create Schedule section. - Requirements: Might be similar to Qualifications. The instruction includes Requirements heading separate from Qualifications. The posting has "Qualifications" section; we could treat that as Qualifications. Requirements could be maybe the same? But we should not create empty sections. If we have Qualifications, we could omit Requirements or combine? The instruction says include a section ONLY when posting has real, specific content for it. So we need to decide if we have content for Requirements separate from Qualifications. The posting does not have a separate "Requirements" heading; it's all under Qualifications. So we should not create a Requirements section. - Skills: we have some skills mentioned; we could create Skills section. - Benefits: we have content. - Pay: we have content. - Schedule: none -> omit. - About the role: we have content. Thus sections: About the role, Responsibilities, Qualifications, Skills, Benefits, Pay. We need to use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format them. We must not repeat job title as heading. The job title is "Senior Director, Global Market Access". Not to be used as heading. We must not put Job ID/requisition numbers as headings; none present. We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The posting includes an EEO statement at end: "We are proud to be an Equal Opportunity Employer...". That's boilerplate; we should remove it. Also remove duplicated lines? Not seeing duplicates. We need to preserve all substantive info: company description, role description, responsibilities sub-sections, qualifications, skills, benefits, pay, location details. We must not invent or summarize away detail; we must keep specifics like numbers, percentages, etc. Let's extract. Company description (Who We Are): "Cogent Biosciences is a publicly traded biotechnology company focused on developing novel precision therapies to treat a broad range of patients with unmet medical needs. Cogent’s lead program, bezuclastinib, is designed to selectively and potently inhibit exon 17 mutations found within the KIT receptor tyrosine kinase, including KIT D816V. KIT D816V is responsible for driving a rare and serious condition called Systemic Mastocytosis, and exon 17 mutations are also found in patients with gastrointestinal stromal tumors (GIST), a type of cancer with strong dependence on oncogenic KIT signaling. Bezuclastinib has exhibited promising initial data across all three trials: APEX in AdvSM, SUMMIT in NonAdvSM and PEAK in GIST, including an encouraging safety profile across 600+ patients in single agent and combination dosing." That's all. Role description (The Role): "Cogent Biosciences is seeking an entrepreneurial and strategic Senior Director, Global Market Access to develop and execute market access strategies that enable patients with cancer to access innovative therapies. Reporting to the Vice President, Value & Access Strategy, this role will have a global remit with some responsibility for the US market. The Sr. Director will work across the organization to translate clinical and economic value into compelling market access strategies across key markets. The role will partner closely with Commercial, Medical Affairs, Clinical Development, Regulatory, Finance, and other cross-functional teams, while working closely with the company's HEOR capabilities within the Value & Access organization to develop evidence and value strategies that support payer and HTA decision-making. The ideal candidate brings strong oncology market access experience, a solid understanding of payer and reimbursement dynamics, and experience developing access strategies across international markets. This is a highly visible, hands-on role in a growing biotech environment, requiring both strategic thinking and the ability to drive execution with lean internal resources and external partners." We need to keep all that. Responsibilities: The posting has headings: - Global Market Access & Value Strategy - Develop and execute global market access strategies for oncology pipeline and commercial products across the product lifecycle. - Identify market access opportunities, risks, and potential barriers across the US and priority international markets. - Develop market-specific strategies informed by payer dynamics, reimbursement and HTA requirements, clinical practice, treatment pathways, and competitive landscapes. - Integrate market access, pricing, reimbursement, HEOR, and value considerations into broader product, development, and commercialization strategies. - Monitor changes in oncology treatment, reimbursement, and health-system environments and assess implications for the portfolio. - Evidence, HEOR & Oncology Value Strategy - Lead the integration of market access and HEOR perspectives into the overall value strategy for oncology assets. - Translate the clinical profile, unmet need, and treatment landscape into differentiated payer and HTA value propositions. - Partner closely with HEOR and Medical Affairs to define evidence requirements and develop evidence-generation strategies across key markets. - Provide market access input into clinical development plans, endpoints, comparators, patient populations, and evidence-generation priorities. - Identify evidence gaps that may create future access barriers and work with HEOR and cross-functional teams to address them. - Guide development of value dossiers, economic models, budget impact analyses, and other market access tools in partnership with HEOR. - Ensure HEOR outputs are effectively translated into payer, HTA, and broader market access strategies. - Pricing & Reimbursement - Develop and support global pricing and reimbursement strategies in partnership with the VP, Value & Access Strategy and cross-functional stakeholders. - Conduct pricing and reimbursement assessments across priority markets, considering clinical value, treatment alternatives, healthcare-system dynamics, and market access requirements. - Develop pricing scenarios and assumptions to support business planning, forecasting, and strategic decision-making. - Ensure pricing considerations are appropriately integrated with the overall value and access strategy throughout the product lifecycle. - Launch Readiness - Serve as a core market access leader within cross-functional launch teams. - Develop market access launch plans, milestones, risks, and mitigation strategies. - Incorporate payer, reimbursement, pricing, HTA, and evidence considerations into launch sequencing and commercialization planning. - Support development of payer-facing materials and value communication tools. - Help establish appropriate access metrics and readiness assessments. - Ensure the organization is prepared to address market access considerations in key launch markets. We need to put these as list items under Responsibilities. Could we keep subheadings? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid additional headings inside, but we should follow the instruction: only those headings. However we could still include the responsibility subheadings as

  or ? But to preserve structure, we could keep them as

  with bold? But we must not invent new headings beyond those listed? The instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other headings, but to be safe, we can keep the responsibility subheadings as

  maybe with . However the instruction says "Use

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

    for prose." So we can treat each bullet as

  • . The subheadings could be

    with bold text. That's acceptable. Thus Responsibilities section:

    Responsibilities

    then maybe

    Global Market Access & Value Strategy

    then
    with the bullets. Similarly for other subheadings. Qualifications: The posting has: "Bachelor’s degree in a relevant discipline; advanced degree preferred (e.g., MBA, MPH, PharmD, MS). 10+ years of experience in pharmaceutical or biotechnology market access, pricing, reimbursement, HEOR, or a related discipline. Demonstrated experience developing market access strategies in the US and international markets. Experience in oncology, specialty pharmaceuticals, or other complex therapeutic areas. Experience supporting products through development and/or commercialization, ideally including a launch. Experience translating clinical evidence and product value into payer and HTA strategies. Understanding of global pricing, reimbursement, and HTA environments. Strong analytical, strategic planning, project management, and communication skills." We need to put as list under Qualifications. Skills: We could extract skills from qualifications: Strong analytical, strategic planning, project management, and communication skills. Also maybe "entrepreneurial and strategic". But we already have those in qualifications. Could we create a Skills section with those skills? The instruction says we can have Skills section. We'll include the skills mentioned: Strong analytical, strategic planning, project management, and communication skills. Also maybe "entrepreneurial and strategic". But to avoid duplication, we could just list the skills from qualifications. However we must preserve ALL substantive information; if we put skills only in Skills section and not also in Qualifications, we might lose the qualification statements. Better to keep qualifications as is, and Skills section could be empty? But we cannot create empty section. So maybe we should not create a Skills section if it would duplicate content. The instruction says prefer a few substantive sections over many thin ones. So we could omit Skills section and keep skills within Qualifications. However the instruction list includes Skills as a possible heading; but we are not required to include it if no