Market Development Manager - Mississippi Delta
Astellas Pharma · Chicago, IL · 1 mo ago
Business Development$140k–$187k/yrFull-time
We need to output HTML fragment with sections: About the role? The posting includes description: "Do you want to be part of an inclusive team...". That's about the company. Could be "About the role" or "About the company". The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections are present.
We have:
- Intro paragraph about inclusive team, mission, etc. Could be "About the role" or maybe "About the company". Since they ask not to repeat job title as heading, but we can have About the role.
- Purpose paragraph: "The Market Development Manager (MDM) will serve as the primary lead..." That's essentially role purpose. Could be part of About the role.
- Essential Job Responsibilities: list of duties. Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections are present.
We have:
- Intro paragraph about inclusive team, mission, etc. Could be "About the role" or maybe "About the company". Since they ask not to repeat job title as heading, but we can have About the role.
- Purpose paragraph: "The Market Development Manager (MDM) will serve as the primary lead..." That's essentially role purpose. Could be part of About the role.
- Essential Job Responsibilities: list of duties. Use - .
- Qualifications: Required and Preferred. Could be under Requirements or Qualifications. The instruction includes Requirements and Qualifications as possible headings. We have both Required and Preferred. Could combine into Qualifications section.
- Working Environment: description about field-based, travel. Could be under Schedule? Not exactly schedule. Could be a separate section like "Working Environment" but not in allowed headings list. The allowed headings list is examples, not exhaustive? It says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should stick to those headings. Working Environment could be part of Responsibilities or maybe Schedule? Not schedule. Could be omitted? But we need to preserve ALL substantive information. We could incorporate working environment details into Responsibilities or maybe a separate "Schedule" if travel schedule? Not exactly schedule. Could treat as "Responsibilities" includes travel requirement. Or we could add a "Working Environment" heading though not in list; but instruction says use those as examples, not strict? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we can use those headings; but we could also use other headings if needed? Safer to stick to those. We can put travel info under Responsibilities as a bullet.
- Compensation Range: $140,000 - $187,000. That's Pay. So we need a Pay section.
- Benefits: list of benefits. So Benefits section.
- Schedule: not explicitly given. There's mention of field-based, travel, remote work from certain states may be permitted, hybrid work encouraged. That's about work arrangement, could be Schedule? Might be considered Schedule (remote/hybrid). We could include a Schedule section with that info.
- Skills: not explicitly listed; we have communication, presentation, organizational skills etc. Those could go under Skills.
- Requirements: maybe we separate Required qualifications under Requirements, and Preferred under Qualifications? But we have both Required and Preferred. Could do Requirements for Required, Qualifications for Preferred. Or combine.
We need to avoid boilerplate: EEO line, etc. Remove that.
We must not repeat job title as heading. So no heading for "Market Development Manager". Good.
We must not include Job ID/requisition numbers.
We must preserve all substantive information.
Let's extract substantive content:
Intro: "Do you want to be part of an inclusive team that works to develop innovative therapies for patients? Every day, we are driven to develop and deliver innovative and effective new medicines to patients and physicians. If you want to be part of this exciting work, you belong at Astellas! Astellas Pharma Inc. is a pharmaceutical company conducting business in more than 70 countries around the world. We are committed to turning innovative science into medical solutions that bring value and hope to patients and their families. Keeping our focus on addressing unmet medical needs and conducting our business with ethics and integrity enables us to improve the health of people throughout the world. For more information on Astellas, please visit our website at www.astellas.com . This position is field based in the Mississippi Delta. 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."
Essential Job Responsibilities (list):
- 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, to keep a pulse on their organization and opportunities for Iveric Bio partnership.
- Maintain highest integrity by ensuring compliance with all regulations and policies.
Qualifications Required:
- Bachelor’s Degree in science or business-related discipline.
- 8+ years of experience within the pharmaceutical or biotechnology industries.
- Strong clinical acumen with specialty pharmaceutical/biopharmaceutical experience.
- Broad range of leadership competencies and ability to work in cross-functional role.
- Excellent communication, presentation, and organizational skills.
- Ability to travel extensively within the U.S.
Preferred:
- Prior first- or second-line team leadership experience.
- Prior experience working in Ophthalmology marketing, operations, or patient services.
- Experience in buy-and-bill environments.
- Direct experience with customers in the Retina, Comprehensive Ophthalmology or Optometry customer segments, ideally with a strong base of existing thought leader relationships.
Working Environment:
- This position is a field-based role and will require regular travel within the defined geography and may require travel throughout the US.
Compensation Range: $140,000 - $187,000 (NOTE: Final Salary could be more or less, based on experience Flexible grade level based on candidate background and skillset)
Benefits:
- Medical, Dental and Vision Insurance
- Generous Paid Time Off options, including Vacation and Sick time, plus national holidays including year-end shut down
- 401(k) match and annual company contribution
- Company paid life insurance
- Annual Corporate Bonus and Quarterly Sales Incentive for eligible positions
- Long Term Incentive Plan for eligible positions
- Referral bonus program
Category IZERVAY Brand (maybe not needed). Also there is a line: "Category IZERVAY Brand". Might be metadata; we can drop.
EEO line: remove.
Now we need to map to sections.
Possible sections:
- About the role (intro + purpose)
- Responsibilities (essential job responsibilities)
- Requirements (required qualifications)
- Qualifications (preferred qualifications) maybe combine? But we have both Required and Preferred; we could put Required under Requirements, Preferred under Qualifications. Or we could have a single Qualifications section with both required and preferred, but instruction says we can use Requirements and Qualifications as headings. Let's do:
Requirements
for required qualifications.
Qualifications
for preferred qualifications.
- Skills: we have communication, presentation, organizational skills etc. Those are already in Required qualifications. Could also be a Skills section but we already have them. Might be redundant. Could omit Skills section to avoid thin sections. The instruction: "Prefer a few substantive sections over many thin ones." So we can incorporate skills into Requirements.
- Benefits: Benefits section.
- Pay: Pay section.
- Schedule: we have info about field-based, remote work, hybrid work, travel. Could be Schedule section.
We also have Working Environment: field-based, travel. Could be part of Schedule.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule.
Check each for substantive content.
About the role: combine intro and purpose.
Responsibilities: list of duties.
Requirements: required qualifications list.
Qualifications: preferred qualifications list.
Benefits: list.
Pay: compensation range.
Schedule: field-based, remote work, hybrid, travel.
Now ensure we don't include filler like "commensurate with experience". The Pay section includes note: "NOTE: Final Salary could be more or less, based on experience Flexible grade level based on candidate background and skillset". That's somewhat filler but it's part of the posting. It's not placeholder like "N/A". It's actual info about flexibility. We can keep it.
We must not include boilerplate like EEO, etc.
Now produce HTML fragment: only the HTML, no markdown fences.
We'll output:
About the role
...
Then Responsibilities
- ...
etc.
Make sure to preserve all substantive information exactly as given, but we can rephrase? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should not change meaning, but we can keep the sentences as is. Slight editing for clarity maybe okay but better to keep original phrasing.
Let's copy the intro paragraph exactly:
"Do you want to be part of an inclusive team that works to develop innovative therapies for patients? Every day, we are driven to develop and deliver innovative and effective new medicines to patients and physicians. If you want to be part of this exciting work, you belong at Astellas! Astellas Pharma Inc. is a pharmaceutical company conducting business in more than 70 countries around the world. We are committed to turning innovative science into medical solutions that bring value and hope to patients and their families. Keeping our focus on addressing unmet medical needs and conducting our business with ethics and integrity enables us to improve the health of people throughout the world. For more information on Astellas, please visit our website at www.astellas.com . This position is field based in the Mississippi Delta. Remote work from certain states may be permitted in accordance with Astellas’ Responsible Flexibility Guidelines. Candidates interested in hybrid work are encouraged to apply."
Note there is a space before period? We'll keep as is.
Purpose paragraph:
"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'll combine intro and purpose into About the role paragraph(s). Could be
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should stick to those headings. Working Environment could be part of Responsibilities or maybe Schedule? Not schedule. Could be omitted? But we need to preserve ALL substantive information. We could incorporate working environment details into Responsibilities or maybe a separate "Schedule" if travel schedule? Not exactly schedule. Could treat as "Responsibilities" includes travel requirement. Or we could add a "Working Environment" heading though not in list; but instruction says use those as examples, not strict? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we can use those headings; but we could also use other headings if needed? Safer to stick to those. We can put travel info under Responsibilities as a bullet.
- Compensation Range: $140,000 - $187,000. That's Pay. So we need a Pay section.
- Benefits: list of benefits. So Benefits section.
- Schedule: not explicitly given. There's mention of field-based, travel, remote work from certain states may be permitted, hybrid work encouraged. That's about work arrangement, could be Schedule? Might be considered Schedule (remote/hybrid). We could include a Schedule section with that info.
- Skills: not explicitly listed; we have communication, presentation, organizational skills etc. Those could go under Skills.
- Requirements: maybe we separate Required qualifications under Requirements, and Preferred under Qualifications? But we have both Required and Preferred. Could do Requirements for Required, Qualifications for Preferred. Or combine.
We need to avoid boilerplate: EEO line, etc. Remove that.
We must not repeat job title as heading. So no heading for "Market Development Manager". Good.
We must not include Job ID/requisition numbers.
We must preserve all substantive information.
Let's extract substantive content:
Intro: "Do you want to be part of an inclusive team that works to develop innovative therapies for patients? Every day, we are driven to develop and deliver innovative and effective new medicines to patients and physicians. If you want to be part of this exciting work, you belong at Astellas! Astellas Pharma Inc. is a pharmaceutical company conducting business in more than 70 countries around the world. We are committed to turning innovative science into medical solutions that bring value and hope to patients and their families. Keeping our focus on addressing unmet medical needs and conducting our business with ethics and integrity enables us to improve the health of people throughout the world. For more information on Astellas, please visit our website at www.astellas.com . This position is field based in the Mississippi Delta. 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."
Essential Job Responsibilities (list):
- 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, to keep a pulse on their organization and opportunities for Iveric Bio partnership.
- Maintain highest integrity by ensuring compliance with all regulations and policies.
Qualifications Required:
- Bachelor’s Degree in science or business-related discipline.
- 8+ years of experience within the pharmaceutical or biotechnology industries.
- Strong clinical acumen with specialty pharmaceutical/biopharmaceutical experience.
- Broad range of leadership competencies and ability to work in cross-functional role.
- Excellent communication, presentation, and organizational skills.
- Ability to travel extensively within the U.S.
Preferred:
- Prior first- or second-line team leadership experience.
- Prior experience working in Ophthalmology marketing, operations, or patient services.
- Experience in buy-and-bill environments.
- Direct experience with customers in the Retina, Comprehensive Ophthalmology or Optometry customer segments, ideally with a strong base of existing thought leader relationships.
Working Environment:
- This position is a field-based role and will require regular travel within the defined geography and may require travel throughout the US.
Compensation Range: $140,000 - $187,000 (NOTE: Final Salary could be more or less, based on experience Flexible grade level based on candidate background and skillset)
Benefits:
- Medical, Dental and Vision Insurance
- Generous Paid Time Off options, including Vacation and Sick time, plus national holidays including year-end shut down
- 401(k) match and annual company contribution
- Company paid life insurance
- Annual Corporate Bonus and Quarterly Sales Incentive for eligible positions
- Long Term Incentive Plan for eligible positions
- Referral bonus program
Category IZERVAY Brand (maybe not needed). Also there is a line: "Category IZERVAY Brand". Might be metadata; we can drop.
EEO line: remove.
Now we need to map to sections.
Possible sections:
- About the role (intro + purpose)
- Responsibilities (essential job responsibilities)
- Requirements (required qualifications)
- Qualifications (preferred qualifications) maybe combine? But we have both Required and Preferred; we could put Required under Requirements, Preferred under Qualifications. Or we could have a single Qualifications section with both required and preferred, but instruction says we can use Requirements and Qualifications as headings. Let's do:
Requirements
for required qualifications.
Qualifications
for preferred qualifications.
- Skills: we have communication, presentation, organizational skills etc. Those are already in Required qualifications. Could also be a Skills section but we already have them. Might be redundant. Could omit Skills section to avoid thin sections. The instruction: "Prefer a few substantive sections over many thin ones." So we can incorporate skills into Requirements.
- Benefits: Benefits section.
- Pay: Pay section.
- Schedule: we have info about field-based, remote work, hybrid work, travel. Could be Schedule section.
We also have Working Environment: field-based, travel. Could be part of Schedule.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule.
Check each for substantive content.
About the role: combine intro and purpose.
Responsibilities: list of duties.
Requirements: required qualifications list.
Qualifications: preferred qualifications list.
Benefits: list.
Pay: compensation range.
Schedule: field-based, remote work, hybrid, travel.
Now ensure we don't include filler like "commensurate with experience". The Pay section includes note: "NOTE: Final Salary could be more or less, based on experience Flexible grade level based on candidate background and skillset". That's somewhat filler but it's part of the posting. It's not placeholder like "N/A". It's actual info about flexibility. We can keep it.
We must not include boilerplate like EEO, etc.
Now produce HTML fragment: only the HTML, no markdown fences.
We'll output:
About the role
Requirements
for required qualifications.Qualifications
for preferred qualifications. - Skills: we have communication, presentation, organizational skills etc. Those are already in Required qualifications. Could also be a Skills section but we already have them. Might be redundant. Could omit Skills section to avoid thin sections. The instruction: "Prefer a few substantive sections over many thin ones." So we can incorporate skills into Requirements. - Benefits: Benefits section. - Pay: Pay section. - Schedule: we have info about field-based, remote work, hybrid work, travel. Could be Schedule section. We also have Working Environment: field-based, travel. Could be part of Schedule. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. Check each for substantive content. About the role: combine intro and purpose. Responsibilities: list of duties. Requirements: required qualifications list. Qualifications: preferred qualifications list. Benefits: list. Pay: compensation range. Schedule: field-based, remote work, hybrid, travel. Now ensure we don't include filler like "commensurate with experience". The Pay section includes note: "NOTE: Final Salary could be more or less, based on experience Flexible grade level based on candidate background and skillset". That's somewhat filler but it's part of the posting. It's not placeholder like "N/A". It's actual info about flexibility. We can keep it. We must not include boilerplate like EEO, etc. Now produce HTML fragment: only the HTML, no markdown fences. We'll output:About the role
...
ThenResponsibilities
- ...