Market Development Manager, Northeast

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Astellas" and "Purpose". The instructions: 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 decide which sections to include based on content. We have: - About Astellas (company description) – could be "About the role"? Actually "About the role" is a typical heading but we have "About Astellas". The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings? It says use

  for section headings (e.g. About the role, Responsibilities...). Likely they expect we use those standard headings if applicable. But we can also use other headings? The instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are examples; we can use other headings if needed but they gave examples. Probably we should stick to those headings where applicable. The posting includes "About Astellas" (company overview) and "Purpose" (role purpose). Could map "About the role" to purpose? Or we could have "About the role" as a section describing the role purpose. The "About Astellas" could be considered company overview, maybe not needed as a separate section? But we need to preserve ALL substantive information. So we need to include that info somewhere. Could put it under a heading like "About Astellas" using

  . The instruction didn't forbid other headings; it just gave examples. So we can include "About Astellas" as a heading. Similarly we have "Purpose" which could be under "About the role". But we also have "Essential Job Responsibilities" (list). That maps to Responsibilities. We have "Required Qualifications" and "Preferred Qualifications". Those map to Requirements/Qualifications. Could combine into Qualifications section with required and preferred subpoints? But we need to preserve all info. Could have a "Qualifications" section with required and preferred bullet lists. We have "Location and Working Environment" – includes location, travel, hybrid work. Could be under "Schedule"? Not exactly. Could be under "Schedule" if they mention schedule/hybrid. But we have no explicit schedule. Could create a "Schedule" section if they mention hybrid work and travel. The instruction says never create Pay/Schedule/Benefits sections unless posting actually states them. They do mention hybrid work and travel, which is about schedule/working environment. So we could include a "Schedule" section describing location, travel, hybrid. We have "What awaits you at Astellas?" – that's like benefits/culture. Could be under "Benefits"? They list benefits later. The "What awaits you..." includes bullet points: Global collaboration, Real-world patient impact, Relentless Innovation, A Culture of Growth. Those are more like culture/benefits. Could be under "Benefits" or maybe a separate "Benefits" section for tangible benefits (medical, dental, etc). The instruction says include a section ONLY when posting has real, specific content for it. So we can have Benefits section with the listed benefits (medical, dental, vision, PTO, 401k, life insurance, bonus, LTIP, company fleet vehicle, referral bonus). Also we have the "What awaits you..." which is more like value proposition; could be under "Benefits" as well or maybe under a "Culture" section but not in examples. Safer to include under Benefits as additional bullet points. We have Salary Range – that's Pay. So we need a Pay section with the salary range. We have "Our Organizational Values and Behaviors" – could be under something like "Skills"? Not exactly. Could be under "About the role"? Might be considered part of company culture. Could be omitted? But we need to preserve ALL substantive information. So we need to include that info somewhere. Could be under a "Skills" section? Not really. Could be under "About the role" as a paragraph. Or we could create a separate section like "Values" but not in examples. However instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings but suggests we use those. To be safe, we could incorporate the values into the "About the role" section or maybe a "Skills" section (though it's not skills). But we could still put it under "About the role" as prose. We also have "Category IZERVAY Brand" and EEO statement – we need to remove EEO/equal-opportunity boilerplate. So drop that line. We also have "Learn more at Astellas.com." – that's part of About Astellas; we can keep. We need to remove duplicated lines, cookie/navigation/legal/EEO/scams, application instructions. There's no explicit application instructions besides maybe "Candidates interested in hybrid work are encouraged to apply." That's near the territory line. That's basically an encouragement to apply; could be considered application instruction? It's not explicit instruction like "apply via". Might be okay to keep as part of description. But we can keep. We need to preserve ALL substantive information. So we need to include territory, remote work possibility, etc. Let's outline sections: - About Astellas (company overview) –

  About Astellas

  with paragraph(s). - About the role / Purpose – maybe combine purpose and role description. Could have

  About the role

  with paragraph describing purpose and role. - Responsibilities –

  Responsibilities

  with
  • for each essential job responsibility. - Qualifications –

    Qualifications

    with two sub-sections? Could have

    Required Qualifications

    ? But instruction only mentions

    for section headings. Could still use

    but not specified. Safer to keep everything under

    Qualifications

    and separate required and preferred using or separate paragraphs. But we need to preserve all info. Could do

    Required Qualifications

    and

    Preferred Qualifications

    . Those are examples given (Requirements, Qualifications). Actually they listed Requirements and Qualifications as examples. So we could have

    Required Qualifications

    and

    Preferred Qualifications

    . That seems okay. - Skills – maybe not needed separately; we could put communication etc under Qualifications. But we have a separate "Excellent communication, presentation, and organizational skills." That's part of required qualifications. So we can include under Required Qualifications. - Benefits –

    Benefits

    with
    • for each benefit listed. - Pay –

      Pay

      with paragraph containing salary range. - Schedule –

      Schedule

      with paragraph about location, travel, hybrid work. We also have "What awaits you at Astellas?" – could be included under Benefits as additional bullet points (like "Global collaboration", etc.) Or we could create a separate section like "Culture" but not in examples. Safer to add under Benefits. We also have "Our Organizational Values and Behaviors" – could be added under Benefits as well or under About the role. Perhaps under About the role as a paragraph. We need to avoid filler/placeholder text. All content we have is specific. Now we need to ensure we don't repeat job title as heading. The job title is "Market Development Manager - Northeast". We'll not use that as heading. We need to not put Job ID/requisition numbers as headings – none present. We need to output only HTML fragment. Let's extract content precisely. About Astellas paragraph: "Astellas is a global life sciences company committed to turning innovative science into VALUE for patients. We provide transformative therapies in disease areas that include oncology, ophthalmology, urology, immunology and women's health. Through our research and development programs, we are pioneering new healthcare solutions for diseases with high unmet medical need. Learn more at Astellas.com. Are you driven to make a real difference in the lives of patients? We're seeking passionate individuals who thrive in dynamic environments, embrace new ideas, and aren't afraid to take intelligent risks. People who act with unwavering integrity and are deeply committed to making a tangible impact." That's a mix of company description and call to action. We'll keep as paragraph(s). Could split into two paragraphs: first about company, second about seeking individuals. Purpose paragraph: "This position is field based in the Northeast Region. Territory includes New York, Vermont, New Hampshire, New Jersey and Maine. Remote work from certain states may be permitted in accordance with Astellas’ Responsible Flexibility Guidelines. Candidates interested in hybrid work are encouraged to apply. Purpose The Market Development Manager (MDM) will serve as the primary lead for interactions with key thought leaders and influencers in Retina, Comprehensive Ophthalmology, and Optometry. MDM will collaborate closely with these key customers to build advocacy for the treatment of GA and for Izervay. They will collaborate effectively with the Sales, Field Medical, Field Reimbursement, and Marketing teams to support peer-to-peer education efforts, share customer insights and provide customer feedback that can be used to shape brand strategy and drive adoption. In addition, they will lead the planning for customer engagements with key company personnel as needed and build a plan for customer interactions at key congresses and meetings throughout the year." We need to preserve that. Could combine territory and purpose under About the role. Responsibilities list (Essential Job Responsibilities): - Create and execute a plan of action to increase advocacy with key thought leaders and influencers in Retina, Comprehensive Ophthalmology, and Optometry for the treatment of GA and for Izervay. - Represent the company in customer engagements and ophthalmology conferences, demonstrating in-depth knowledge of customer needs and how our product and programs can support their patients. - Collect and share customer insights and provide customer feedback that can be used to matrix team and brand strategy. - Demonstrate strong disease state and product based clinical acumen in interactions with businesses in Retina, Comprehensive Ophthalmology and Optometry. - Collaborate closely with Sales, Field Medical, and Field Reimbursement to develop strategic plans to strengthen relationships with national and regional key thought leaders. - Facilitate collaboration and insight sharing with the aligned Sales, Field Medical and Reimbursement teams to maximize opportunities with shared customers and accounts. - Support the Marketing team in identifying and training thought leaders for the speaker’s bureau and facilitating the execution of peer-to-peer education efforts. - Establish connections with the leadership of regional retina, ophthalmic and optometric societies