Senior Director: Global Patient Safety Solutions Partner
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 (the page already shows it) and 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.
We need to parse the posting.
Key parts:
- Intro paragraph(s): "The Senior Director, GPS Business Solution Lead will serve as the key interface between GPS business leadership and Digital & Technology, orchestrating D&T capabilities to deliver on Regeneron's Global Patient Safety (GPS) objectives and priorities across platforms, including Argus (safety), PIVIT, Signal Management, aRMM/ARMM, and SRP. This role owns the platform strategy and roadmap, prioritizing investment in partnership with the business, and will lead a team of Directors delivering delivery governance and regulatory-compliant operations across the safety technology portfolio. The Business Solution Lead will partner closely with GPS business leadership, Enterprise IT, and Information Security to ensure safety systems support Regeneron's Global Patient Safety obligations and global regulatory commitments. This role reports to the Executive Director, Global Development IT and will collaborate closely with GPS business leadership and Enterprise IT partners to shape the safety technology roadmap and ensure delivery excellence across the platform portfolio. Where and When This is an on-site position 4 days/week, primarily based at our Sleepy Hollow, NY or Warren, NJ office. If eligible, we can offer relocation benefits; we cannot offer a fully remote option."
- Then "Key Responsibilities" heading (but we should not repeat heading? Actually we can use
Responsibilities
and list bullet points.
- Then bullet list under Key Responsibilities: multiple sub-sections: GPS Platform Strategy & Ownership, Delivery Oversight & Team Leadership, Data Governance & Regulatory Compliance, Cross-Functional & Vendor Partnership, Executive & Stakeholder Engagement. Each has bullet points.
- Then "Qualifications And Requirements" heading: includes Education & Experience, Technical Expertise, Skills & Competencies, Certifications (Preferred). Should we treat as Requirements? The instruction says we can have sections like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content.
We have qualifications and requirements content: Education & Experience, Technical Expertise, Skills & Competencies, Certifications (Preferred). Also there is a paragraph about "Does this sound like you? Apply now..." which is application instruction - should be removed. Also EEO boilerplate etc - remove.
We also have salary range: "Salary Range (annually) $216,100.00 - $360,200.00". That's Pay info, so we should include a Pay section with that range.
We have schedule: "This is an on-site position 4 days/week, primarily based at our Sleepy Hollow, NY or Warren, NJ office. If eligible, we can offer relocation benefits; we cannot offer a fully remote option." That's schedule/location info. Should we include a Schedule section? The instruction says include Schedule section only if posting actually states them. It does state on-site 4 days/week, location. So we can include Schedule.
Benefits: There's a paragraph about benefits: "Regeneron offers a competitive and comprehensive total rewards package which may include, depending on country and role: annual bonuses or other incentive plans, equity awards, pension or retirement benefits, 401(k) company match, health and wellness programs, fitness centers, insurance benefits (e.g. medical, dental, vision, life and disability), paid time off, and family support benefits." Also earlier: "If eligible, we can offer relocation benefits". So we have benefits info. Should include Benefits section.
We need to avoid duplication and boilerplate. Remove EEO etc.
We need to preserve all substantive info.
We need to format using for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
We need to decide which sections to include: About the role (intro), Responsibilities, Requirements (maybe combine Qualifications And Requirements?), Skills (maybe separate Skills & Competencies?), Benefits, Pay, Schedule.
But we must not create thin sections. Perhaps combine Qualifications and Skills into one Requirements section? However instruction gives examples: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It seems they allow multiple sections but we should prefer few substantive sections over many thin ones. So we need to decide which headings actually have substantive content.
We have:
- About the role: intro paragraphs (substantive).
- Responsibilities: detailed bullet points (substantive).
- Requirements: Education & Experience, Technical Expertise (substantive).
- Skills: Skills & Competencies, Certifications (Preferred) (substantive).
- Benefits: benefits paragraph + relocation benefits (substantive).
- Pay: salary range (substantive).
- Schedule: on-site 4 days/week, location (substantive).
Thus we could include all these sections. That's many but each is substantive. The instruction says prefer a few substantive sections over many thin ones, but these are not thin; they have content. So we can include all.
We must not include headings with filler like "commensurate with experience". Not present.
We need to remove duplicated lines, application instructions, EEO boilerplate, etc.
Let's extract content.
Intro paragraphs (About the role):
"The Senior Director, GPS Business Solution Lead will serve as the key interface between GPS business leadership and Digital & Technology, orchestrating D&T capabilities to deliver on Regeneron's Global Patient Safety (GPS) objectives and priorities across platforms, including Argus (safety), PIVIT, Signal Management, aRMM/ARMM, and SRP. This role owns the platform strategy and roadmap, prioritizing investment in partnership with the business, and will lead a team of Directors delivering delivery governance and regulatory-compliant operations across the safety technology portfolio. The Business Solution Lead will partner closely with GPS business leadership, Enterprise IT, and Information Security to ensure safety systems support Regeneron's Global Patient Safety obligations and global regulatory commitments. This role reports to the Executive Director, Global Development IT and will collaborate closely with GPS business leadership and Enterprise IT partners to shape the safety technology roadmap and ensure delivery excellence across the platform portfolio. Where and When This is an on-site position 4 days/week, primarily based at our Sleepy Hollow, NY or Warren, NJ office. If eligible, we can offer relocation benefits; we cannot offer a fully remote option."
Note: The "Where and When" sentence is part of intro but we might move schedule info to Schedule section. However we can keep it in About the role but then we would duplicate schedule info. Better to extract schedule info to Schedule section and keep About the role without schedule. Let's separate.
Thus About the role: everything up to "This role reports to the Executive Director, Global Development IT and will collaborate closely with GPS business leadership and Enterprise IT partners to shape the safety technology roadmap and ensure delivery excellence across the platform portfolio." Then we have schedule sentence separate.
Now Responsibilities: The bullet points under "Key Responsibilities". We need to convert each bullet into
- . The bullet points include subheadings like "GPS Platform Strategy & Ownership" etc. Should we treat those as subheadings? The instruction says use
for section headings, and - for any list of duties/requirements/benefits. So we could keep the subheadings as plain text inside
- or maybe as ? Not specified. Probably just include them as part of the
- text.
Thus we need to list each duty as a
- . The bullet points are:
Under GPS Platform Strategy & Ownership:
- Partner with senior GPS leadership, to align technology and capabilities to deliver on Global Patient Safety objectives and enterprise priorities.
- Own and prioritize, in partnership with the business, the multi-year platform strategy and roadmap for Argus (safety), PIVIT, Signal Management, aRMM/ARMM, and SRP, translating Global Patient Safety and regulatory priorities into a funded, prioritized delivery plan.
- Own the organizational design of the GPS Business Solution function, including structure, role allocation, and resourcing across Directors and Managers assigned to the domain.
- Establish governance frameworks, standards, and validation practices for GPS platform delivery, ensuring consistency across teams and vendor engagements.
- Own budget, forecast, and vendor contract accountability for the GPS platform portfolio, including software licensing and services agreements.
Under Delivery Oversight & Team Leadership:
- Serve as the escalation and quality-assurance point for planning, prioritization, and execution of safety platform initiatives led by direct reports.
- Oversee product backlog, incident management, and release governance across the GPS platform portfolio, ensuring consistent reporting of value delivered against plan.
- Coach and develop Directors and Managers, ensuring delivery commitments are met and domain capabilities continue to mature.
- Manage steering committee meetings, working groups, and issue/release management for upgrades to existing safety platforms.
Under Data Governance & Regulatory Compliance:
- Partner with GPS business leadership, Regulatory Affairs, and Quality organizations to ensure safety platforms meet GxP validation, data integrity, and audit-readiness standards.
- Own data classification, access, and quality standards for safety-related data, ensuring compliance with global safety reporting obligations (e.g., FDA, EMA).
- Maintain oversight of case processing, signal detection, and risk management workflows to ensure platforms support timely and accurate regulatory reporting.
Under Cross-Functional & Vendor Partnership:
- Partner with Enterprise IT, Enterprise Architecture, and Information Security to align safety platform investments with enterprise standards and security requirements.
- Build and maintain relationships with key platform vendors to clarify demands, resolve conflicts, and align technology roadmaps to business needs.
- Represent GPS technology priorities in enterprise architecture and governance forums, ensuring alignment with enterprise-wide standards.
Under Executive & Stakeholder Engagement:
- Serve as the primary point of contact for senior GPS and IT leadership on matters requiring negotiation of complex or ambiguous issues.
- Build relationships with key GPS business leaders to clarify demands, resolve conflicts, and align technology roadmaps with pharmacovigilance priorities.
- Monitor industry trends in drug safety technology and regulatory reporting, bringing forward innovative approaches to senior leadership.
- Prepare and deliver executive-level materials on the health and roadmap of the GPS platform portfolio for governance forums and senior leadership.
Now Qualifications And Requirements: We need to split into Requirements (Education & Experience, Technical Expertise) and Skills (Skills & Competencies, Certifications). Let's extract.
Education & Experience:
"Bachelor’s degree in Computer Science, Information Systems, Business Administration, or a related field (Master’s degree preferred).
15+ years of progressive industry/relevant professional experience, including significant experience managing enterprise-scale Global Patient Safety, drug safety, or regulatory technology platforms.
Experience in the biotech, pharma, or life sciences industry strongly preferred.
Proven experience leading a multi-disciplinary team of Directors and Managers, including budget and vendor contract accountability for a major function."
Technical Expertise:
"Deep expertise in patient safety and drug safety systems (e.g
for prose. 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. 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. We need to parse the posting. Key parts: - Intro paragraph(s): "The Senior Director, GPS Business Solution Lead will serve as the key interface between GPS business leadership and Digital & Technology, orchestrating D&T capabilities to deliver on Regeneron's Global Patient Safety (GPS) objectives and priorities across platforms, including Argus (safety), PIVIT, Signal Management, aRMM/ARMM, and SRP. This role owns the platform strategy and roadmap, prioritizing investment in partnership with the business, and will lead a team of Directors delivering delivery governance and regulatory-compliant operations across the safety technology portfolio. The Business Solution Lead will partner closely with GPS business leadership, Enterprise IT, and Information Security to ensure safety systems support Regeneron's Global Patient Safety obligations and global regulatory commitments. This role reports to the Executive Director, Global Development IT and will collaborate closely with GPS business leadership and Enterprise IT partners to shape the safety technology roadmap and ensure delivery excellence across the platform portfolio. Where and When This is an on-site position 4 days/week, primarily based at our Sleepy Hollow, NY or Warren, NJ office. If eligible, we can offer relocation benefits; we cannot offer a fully remote option." - Then "Key Responsibilities" heading (but we should not repeat heading? Actually we can use
Responsibilities
and list bullet points. - Then bullet list under Key Responsibilities: multiple sub-sections: GPS Platform Strategy & Ownership, Delivery Oversight & Team Leadership, Data Governance & Regulatory Compliance, Cross-Functional & Vendor Partnership, Executive & Stakeholder Engagement. Each has bullet points. - Then "Qualifications And Requirements" heading: includes Education & Experience, Technical Expertise, Skills & Competencies, Certifications (Preferred). Should we treat as Requirements? The instruction says we can have sections like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content. We have qualifications and requirements content: Education & Experience, Technical Expertise, Skills & Competencies, Certifications (Preferred). Also there is a paragraph about "Does this sound like you? Apply now..." which is application instruction - should be removed. Also EEO boilerplate etc - remove. We also have salary range: "Salary Range (annually) $216,100.00 - $360,200.00". That's Pay info, so we should include a Pay section with that range. We have schedule: "This is an on-site position 4 days/week, primarily based at our Sleepy Hollow, NY or Warren, NJ office. If eligible, we can offer relocation benefits; we cannot offer a fully remote option." That's schedule/location info. Should we include a Schedule section? The instruction says include Schedule section only if posting actually states them. It does state on-site 4 days/week, location. So we can include Schedule. Benefits: There's a paragraph about benefits: "Regeneron offers a competitive and comprehensive total rewards package which may include, depending on country and role: annual bonuses or other incentive plans, equity awards, pension or retirement benefits, 401(k) company match, health and wellness programs, fitness centers, insurance benefits (e.g. medical, dental, vision, life and disability), paid time off, and family support benefits." Also earlier: "If eligible, we can offer relocation benefits". So we have benefits info. Should include Benefits section. We need to avoid duplication and boilerplate. Remove EEO etc. We need to preserve all substantive info. We need to format using for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
We need to decide which sections to include: About the role (intro), Responsibilities, Requirements (maybe combine Qualifications And Requirements?), Skills (maybe separate Skills & Competencies?), Benefits, Pay, Schedule.
But we must not create thin sections. Perhaps combine Qualifications and Skills into one Requirements section? However instruction gives examples: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It seems they allow multiple sections but we should prefer few substantive sections over many thin ones. So we need to decide which headings actually have substantive content.
We have:
- About the role: intro paragraphs (substantive).
- Responsibilities: detailed bullet points (substantive).
- Requirements: Education & Experience, Technical Expertise (substantive).
- Skills: Skills & Competencies, Certifications (Preferred) (substantive).
- Benefits: benefits paragraph + relocation benefits (substantive).
- Pay: salary range (substantive).
- Schedule: on-site 4 days/week, location (substantive).
Thus we could include all these sections. That's many but each is substantive. The instruction says prefer a few substantive sections over many thin ones, but these are not thin; they have content. So we can include all.
We must not include headings with filler like "commensurate with experience". Not present.
We need to remove duplicated lines, application instructions, EEO boilerplate, etc.
Let's extract content.
Intro paragraphs (About the role):
"The Senior Director, GPS Business Solution Lead will serve as the key interface between GPS business leadership and Digital & Technology, orchestrating D&T capabilities to deliver on Regeneron's Global Patient Safety (GPS) objectives and priorities across platforms, including Argus (safety), PIVIT, Signal Management, aRMM/ARMM, and SRP. This role owns the platform strategy and roadmap, prioritizing investment in partnership with the business, and will lead a team of Directors delivering delivery governance and regulatory-compliant operations across the safety technology portfolio. The Business Solution Lead will partner closely with GPS business leadership, Enterprise IT, and Information Security to ensure safety systems support Regeneron's Global Patient Safety obligations and global regulatory commitments. This role reports to the Executive Director, Global Development IT and will collaborate closely with GPS business leadership and Enterprise IT partners to shape the safety technology roadmap and ensure delivery excellence across the platform portfolio. Where and When This is an on-site position 4 days/week, primarily based at our Sleepy Hollow, NY or Warren, NJ office. If eligible, we can offer relocation benefits; we cannot offer a fully remote option."
Note: The "Where and When" sentence is part of intro but we might move schedule info to Schedule section. However we can keep it in About the role but then we would duplicate schedule info. Better to extract schedule info to Schedule section and keep About the role without schedule. Let's separate.
Thus About the role: everything up to "This role reports to the Executive Director, Global Development IT and will collaborate closely with GPS business leadership and Enterprise IT partners to shape the safety technology roadmap and ensure delivery excellence across the platform portfolio." Then we have schedule sentence separate.
Now Responsibilities: The bullet points under "Key Responsibilities". We need to convert each bullet into
- . The bullet points include subheadings like "GPS Platform Strategy & Ownership" etc. Should we treat those as subheadings? The instruction says use
for section headings, and - for any list of duties/requirements/benefits. So we could keep the subheadings as plain text inside
- or maybe as ? Not specified. Probably just include them as part of the
- text.
Thus we need to list each duty as a
- . The bullet points are:
Under GPS Platform Strategy & Ownership:
- Partner with senior GPS leadership, to align technology and capabilities to deliver on Global Patient Safety objectives and enterprise priorities.
- Own and prioritize, in partnership with the business, the multi-year platform strategy and roadmap for Argus (safety), PIVIT, Signal Management, aRMM/ARMM, and SRP, translating Global Patient Safety and regulatory priorities into a funded, prioritized delivery plan.
- Own the organizational design of the GPS Business Solution function, including structure, role allocation, and resourcing across Directors and Managers assigned to the domain.
- Establish governance frameworks, standards, and validation practices for GPS platform delivery, ensuring consistency across teams and vendor engagements.
- Own budget, forecast, and vendor contract accountability for the GPS platform portfolio, including software licensing and services agreements.
Under Delivery Oversight & Team Leadership:
- Serve as the escalation and quality-assurance point for planning, prioritization, and execution of safety platform initiatives led by direct reports.
- Oversee product backlog, incident management, and release governance across the GPS platform portfolio, ensuring consistent reporting of value delivered against plan.
- Coach and develop Directors and Managers, ensuring delivery commitments are met and domain capabilities continue to mature.
- Manage steering committee meetings, working groups, and issue/release management for upgrades to existing safety platforms.
Under Data Governance & Regulatory Compliance:
- Partner with GPS business leadership, Regulatory Affairs, and Quality organizations to ensure safety platforms meet GxP validation, data integrity, and audit-readiness standards.
- Own data classification, access, and quality standards for safety-related data, ensuring compliance with global safety reporting obligations (e.g., FDA, EMA).
- Maintain oversight of case processing, signal detection, and risk management workflows to ensure platforms support timely and accurate regulatory reporting.
Under Cross-Functional & Vendor Partnership:
- Partner with Enterprise IT, Enterprise Architecture, and Information Security to align safety platform investments with enterprise standards and security requirements.
- Build and maintain relationships with key platform vendors to clarify demands, resolve conflicts, and align technology roadmaps to business needs.
- Represent GPS technology priorities in enterprise architecture and governance forums, ensuring alignment with enterprise-wide standards.
Under Executive & Stakeholder Engagement:
- Serve as the primary point of contact for senior GPS and IT leadership on matters requiring negotiation of complex or ambiguous issues.
- Build relationships with key GPS business leaders to clarify demands, resolve conflicts, and align technology roadmaps with pharmacovigilance priorities.
- Monitor industry trends in drug safety technology and regulatory reporting, bringing forward innovative approaches to senior leadership.
- Prepare and deliver executive-level materials on the health and roadmap of the GPS platform portfolio for governance forums and senior leadership.
Now Qualifications And Requirements: We need to split into Requirements (Education & Experience, Technical Expertise) and Skills (Skills & Competencies, Certifications). Let's extract.
Education & Experience:
"Bachelor’s degree in Computer Science, Information Systems, Business Administration, or a related field (Master’s degree preferred).
15+ years of progressive industry/relevant professional experience, including significant experience managing enterprise-scale Global Patient Safety, drug safety, or regulatory technology platforms.
Experience in the biotech, pharma, or life sciences industry strongly preferred.
Proven experience leading a multi-disciplinary team of Directors and Managers, including budget and vendor contract accountability for a major function."
Technical Expertise:
"Deep expertise in patient safety and drug safety systems (e.g
for prose. We need to decide which sections to include: About the role (intro), Responsibilities, Requirements (maybe combine Qualifications And Requirements?), Skills (maybe separate Skills & Competencies?), Benefits, Pay, Schedule. But we must not create thin sections. Perhaps combine Qualifications and Skills into one Requirements section? However instruction gives examples: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It seems they allow multiple sections but we should prefer few substantive sections over many thin ones. So we need to decide which headings actually have substantive content. We have: - About the role: intro paragraphs (substantive). - Responsibilities: detailed bullet points (substantive). - Requirements: Education & Experience, Technical Expertise (substantive). - Skills: Skills & Competencies, Certifications (Preferred) (substantive). - Benefits: benefits paragraph + relocation benefits (substantive). - Pay: salary range (substantive). - Schedule: on-site 4 days/week, location (substantive). Thus we could include all these sections. That's many but each is substantive. The instruction says prefer a few substantive sections over many thin ones, but these are not thin; they have content. So we can include all. We must not include headings with filler like "commensurate with experience". Not present. We need to remove duplicated lines, application instructions, EEO boilerplate, etc. Let's extract content. Intro paragraphs (About the role): "The Senior Director, GPS Business Solution Lead will serve as the key interface between GPS business leadership and Digital & Technology, orchestrating D&T capabilities to deliver on Regeneron's Global Patient Safety (GPS) objectives and priorities across platforms, including Argus (safety), PIVIT, Signal Management, aRMM/ARMM, and SRP. This role owns the platform strategy and roadmap, prioritizing investment in partnership with the business, and will lead a team of Directors delivering delivery governance and regulatory-compliant operations across the safety technology portfolio. The Business Solution Lead will partner closely with GPS business leadership, Enterprise IT, and Information Security to ensure safety systems support Regeneron's Global Patient Safety obligations and global regulatory commitments. This role reports to the Executive Director, Global Development IT and will collaborate closely with GPS business leadership and Enterprise IT partners to shape the safety technology roadmap and ensure delivery excellence across the platform portfolio. Where and When This is an on-site position 4 days/week, primarily based at our Sleepy Hollow, NY or Warren, NJ office. If eligible, we can offer relocation benefits; we cannot offer a fully remote option." Note: The "Where and When" sentence is part of intro but we might move schedule info to Schedule section. However we can keep it in About the role but then we would duplicate schedule info. Better to extract schedule info to Schedule section and keep About the role without schedule. Let's separate. Thus About the role: everything up to "This role reports to the Executive Director, Global Development IT and will collaborate closely with GPS business leadership and Enterprise IT partners to shape the safety technology roadmap and ensure delivery excellence across the platform portfolio." Then we have schedule sentence separate. Now Responsibilities: The bullet points under "Key Responsibilities". We need to convert each bullet into