Dir/Sr. Director of Business Intelligence and Analytics
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.
We need to decide which sections to include based on content.
The posting includes:
- Intro about company mission (maybe "About the role"? Actually that's about company. Could be "About the role" or "About the company". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map content accordingly.
We have:
- Summary: description of role (Dir/Sr. Director of Business Intelligence and Analytics) – could be "About the role".
- Essential Functions: broken into Data Analytics and Insights, Reporting, Forecasting and Modeling, Leadership. Those are responsibilities/duties. So we can have a "Responsibilities" section with list items.
- Required Education and Experience: qualifications. Could be "Qualifications" or "Requirements". The instruction includes both Requirements and Qualifications headings. We need to decide which to use. Probably "Qualifications" for education/experience, and maybe "Skills" for technical skills. But we can combine.
- Preferred Experience: maybe also part of qualifications.
- Work Environment/Location: could be "Schedule"? Actually schedule is about remote/hybrid, travel. Could be "Schedule" or maybe we omit if not specific schedule. The instruction says only create Schedule section if posting actually states them. It does mention hybrid (2 days/week in Secaucus office), up to 30% domestic travel, occasional international travel, remote candidates, regular overnight travel to headquarters if remote. That's schedule/location info. Could be placed under a "Schedule" section or maybe "Work Environment". Since only allowed headings are those listed, we could use "Schedule" for hybrid/remote/travel details.
- Compensation and Benefits: includes Salary Range, bonus, benefits package. So we need both Pay and Benefits sections. The instruction says never create Pay/Schedule/Benefits sections unless posting actually states them. It does state salary range and benefits, so we can include Pay and Benefits sections.
We must not include boilerplate like EEO, visa sponsorship note (though that is substantive? It's about authorization to work; maybe we can keep as a short paragraph? It's not a heading; we can fold minor metadata into a short
or drop it. The note about applicants must be authorized to work for any employer in the U.S., as this position is not eligible for sponsorship or transfer of visa. That's substantive but could be placed in a short p under maybe "About the role" or separate? The instruction says fold minor metadata into a short
or drop it. This is not minor? It's a requirement. Could be included in Requirements? Might be considered a requirement. But we can include as a short p under Requirements.
We must remove duplicated lines, cookie/navigation/legal/EEO etc. At the end there is EEO statement and link; we should remove that.
Also remove "Pierre FabrePierre Fabre has been recognized..." duplicate? Actually there is a line: "Pierre FabrePierre Fabre has been recognized by Forbes as one of the "World's Best Employers" for the 3rd year running. https://www.pierrefabrepharmaceuticals.com/" That's boilerplate; remove.
Also remove "Pierre Fabre is an equal employment opportunity employer..." etc.
Now we need to output only HTML fragment, no /, no markdown.
We'll structure:
About the role
... summary paragraph ...
Maybe also include the mission statement? That's about company, not role. Could be part of About the role? The instruction says use headings like About the role, Responsibilities, etc. The mission statement is about company; maybe we can include it in About the role as context. But we must preserve all substantive information. The mission statement is substantive. Could be placed in About the role section as a paragraph.
We also have note about visa sponsorship; we can include as a short p under About the role or Requirements.
Let's extract the summary text:
"SUMMARY:The Dir/Sr. Director of Business Intelligence and Analytics will play a pivotal and highly visible role shaping commercial strategy and company evolution and will build and lead the Business Intelligence and Analytics function for Pierre Fabre Pharmaceuticals US, serving as a strategic partner to the US Commercial Leadership Team. This role will be responsible for developing the Analytics Function at PFP, including partnership with outside vendors and internal resources to expand analytic capabilities and operationalize analytics solutions. The Dir/Sr. Director of Business Intelligence and Analytics is responsible for evaluating and analyzing data sources to generate actionable insights that inform business decisions enterprise wide. The ideal candidate thrives in an entrepreneurial environment, is resourceful, collaborative and brings a strong background in pharmaceutical analytics, insights, forecasting methodologies and optimally leveraging AI to demonstrate business impact. This role will report to the Chief Commercial Officer and be a core member of the US Commercial Leadership Team. The individual will partner closely with internal stakeholders, omnichannel teams, and agency partners to design and implement robust measurement frameworks, leveraging advanced analytics, forecasts, statistical methodologies, and machine learning techniques."
We'll put that in About the role.
Now Responsibilities: we need to list duties from Essential Functions.
Essential Functions broken into sections:
Data Analytics and Insights:
- Partner with the company's Leadership Team and commercial cross-functional leaders to define the data and insights strategy and roadmap and align analytics priorities with business objectives
- Manage and own the data and insights foundation, including the systems, data integration, and processes required to monitor business performance efficiently and accurately.
- Manage the collection, analysis, and interpretation of patient finding, promotional execution (including omnichannel) and sales data, leveraging latest available technologies and approaches (including AI) to identify trends, opportunities, and areas for improvement providing insightful recommendations leading to improved organizational execution
- Utilize data sources and innovative approaches to optimize patient identification at different stages of their journey developing recommended next steps guidance to optimize patient access to treatment.
- Lead the design, execution, and analysis of primary and secondary market research to provide differentiated insights and subsequent recommendations for brand strategy and customer segmentation, ie; look beyond the data and generate meaningful business insights based on understanding of PFP business
- Establish and execute a vision to optimally integrate available data sources to optimize organizational execution facilitating appropriate patient access to treatment
- Partner collaboratively with other commercial stakeholders to define KPIs and effectively implement data and insights recommendations leading to measurable business impact
Reporting, Forecasting and Modeling:
- Establish a robust, compliant data strategy and accessible, interpretable business performance reporting systems and processes
- Create, codify and present regular, comprehensive, intuitive, insight driven reports and dashboards to communicate business critical insights and recommendations to stakeholders.
- Set reliable processes to collect dispensing data (when applicable) and purchasing data from all class of trades and ensure consolidation of this data for analytical and forecasting purposes
- Develop and own forecasting models for in-line products and pipeline
- Support enablement of innovative, efficient patient finding and omnichannel deployment, defining and tracking KPIs for effectiveness
- Establish and execute a vision to optimally integrate available data sources to optimize organizational execution facilitating appropriate patient access to treatment (duplicate? appears again)
- Establish field force performance reporting platforms and processes including activity and Field Forve Incentive Compensation
- Serve as key contributor to Business Development commercial assessments
- Establish accessible, reliable, and compliant business-performance reporting — the systems and processes that make performance data trustworthy and easy to interpret across the organization.
Leadership:
- Lead cross-functional initiatives and influence key business decisions through data-driven insights.
- Develop strong partnerships across Commercial, Market Access, Medical, Finance, and external vendors
- Be seen as a trusted, collaborative, valued member of the commercial leadership team
- Other duties and responsibilities may be assigned as required based on evolving business needs.
We need to deduplicate duplicate lines: "Establish and execute a vision to optimally integrate available data sources to optimize organizational execution facilitating appropriate patient access to treatment" appears twice (once in Data Analytics and Insights, once in Reporting, Forecasting and Modeling). We should keep only one instance.
Also "Establish accessible, reliable, and compliant business-performance reporting — the systems and processes that make performance data trustworthy and easy to interpret across the organization." appears maybe twice? Actually appears in Reporting, Forecasting and Modeling as last bullet and also maybe earlier? We'll keep one.
Now we need to output as - for any list of duties/requirements/benefits. So we can have a single
with all responsibilities items. Or we could break into subheadings? Not allowed; only headings are those specific. So we can just have one Responsibilities section with a containing all duty items.
Now Requirements/Qualifications: We have Required Education and Experience, plus Preferred Experience, plus maybe the visa note.
We need to decide which heading to use: Requirements or Qualifications. The instruction includes both. We could use "Qualifications" for education/experience and "Skills" for technical skills. But we also have "Preferred Experience". Could be part of Qualifications.
Better to have a single "Qualifications" section containing both required and preferred. Or we could have "Requirements" for required, and "Skills" for technical skills, and maybe "Preferred Experience" as part of Requirements? But we must not create thin sections. Prefer few substantive sections.
Thus we can have:
Qualifications
- Bachelor’s degree in business, Economics, Data Science, Computer Science or related field such as Marketing; Master’s or MBA preferred.
- Minimum 10+ years in data analytics, forecasting or commercial strategy within the pharmaceutical or life sciences industry.
- Expert-level, hands-on command of SQL Server and advanced Excel, the technologies used day to day to build and deliver the data models, dashboards, and forecasts this role owns such as Tableau or Power BI. This is a build role, the successful candidate must work directly in these tools, not solely direct others who do.
- Fluency with various industry data sources, such as patient claims data, patient longitudinal data, RWD, etc
- Experience utilizing complex data to drive business decisions, hands on experience in data science methodologies (predictive analytics, machine learning, patient level data triggers)
- Demonstrated Experience in rare disease analytics or patient-finding programs
- Demonstrated expertise in developing forecasts, such as assumption development, scenario analysis, model validation, variance analysis, and communication of uncertainty.
- A bias toward action and outcomes and ability to thrive in a dynamic, fast paced, high-growth environment.
- Strong communication skills (written and verbal) to effectively present complex analytical findings to non-technical stakeholders.
- Strong team player, with low ego, high emotional intelligence and demonstrated ability to work productively with diverse, cross organizational teams
- Preferred Experience: Experience with commercial build or scaling of Analytics function strongly preferred
- Applicants must be
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. We need to decide which sections to include based on content. The posting includes: - Intro about company mission (maybe "About the role"? Actually that's about company. Could be "About the role" or "About the company". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map content accordingly. We have: - Summary: description of role (Dir/Sr. Director of Business Intelligence and Analytics) – could be "About the role". - Essential Functions: broken into Data Analytics and Insights, Reporting, Forecasting and Modeling, Leadership. Those are responsibilities/duties. So we can have a "Responsibilities" section with list items. - Required Education and Experience: qualifications. Could be "Qualifications" or "Requirements". The instruction includes both Requirements and Qualifications headings. We need to decide which to use. Probably "Qualifications" for education/experience, and maybe "Skills" for technical skills. But we can combine. - Preferred Experience: maybe also part of qualifications. - Work Environment/Location: could be "Schedule"? Actually schedule is about remote/hybrid, travel. Could be "Schedule" or maybe we omit if not specific schedule. The instruction says only create Schedule section if posting actually states them. It does mention hybrid (2 days/week in Secaucus office), up to 30% domestic travel, occasional international travel, remote candidates, regular overnight travel to headquarters if remote. That's schedule/location info. Could be placed under a "Schedule" section or maybe "Work Environment". Since only allowed headings are those listed, we could use "Schedule" for hybrid/remote/travel details. - Compensation and Benefits: includes Salary Range, bonus, benefits package. So we need both Pay and Benefits sections. The instruction says never create Pay/Schedule/Benefits sections unless posting actually states them. It does state salary range and benefits, so we can include Pay and Benefits sections. We must not include boilerplate like EEO, visa sponsorship note (though that is substantive? It's about authorization to work; maybe we can keep as a short paragraph? It's not a heading; we can fold minor metadata into a short
or drop it. The note about applicants must be authorized to work for any employer in the U.S., as this position is not eligible for sponsorship or transfer of visa. That's substantive but could be placed in a short p under maybe "About the role" or separate? The instruction says fold minor metadata into a short
or drop it. This is not minor? It's a requirement. Could be included in Requirements? Might be considered a requirement. But we can include as a short p under Requirements. We must remove duplicated lines, cookie/navigation/legal/EEO etc. At the end there is EEO statement and link; we should remove that. Also remove "Pierre FabrePierre Fabre has been recognized..." duplicate? Actually there is a line: "Pierre FabrePierre Fabre has been recognized by Forbes as one of the "World's Best Employers" for the 3rd year running. https://www.pierrefabrepharmaceuticals.com/" That's boilerplate; remove. Also remove "Pierre Fabre is an equal employment opportunity employer..." etc. Now we need to output only HTML fragment, no /, no markdown. We'll structure:
About the role
... summary paragraph ...
Maybe also include the mission statement? That's about company, not role. Could be part of About the role? The instruction says use headings like About the role, Responsibilities, etc. The mission statement is about company; maybe we can include it in About the role as context. But we must preserve all substantive information. The mission statement is substantive. Could be placed in About the role section as a paragraph. We also have note about visa sponsorship; we can include as a short p under About the role or Requirements. Let's extract the summary text: "SUMMARY:The Dir/Sr. Director of Business Intelligence and Analytics will play a pivotal and highly visible role shaping commercial strategy and company evolution and will build and lead the Business Intelligence and Analytics function for Pierre Fabre Pharmaceuticals US, serving as a strategic partner to the US Commercial Leadership Team. This role will be responsible for developing the Analytics Function at PFP, including partnership with outside vendors and internal resources to expand analytic capabilities and operationalize analytics solutions. The Dir/Sr. Director of Business Intelligence and Analytics is responsible for evaluating and analyzing data sources to generate actionable insights that inform business decisions enterprise wide. The ideal candidate thrives in an entrepreneurial environment, is resourceful, collaborative and brings a strong background in pharmaceutical analytics, insights, forecasting methodologies and optimally leveraging AI to demonstrate business impact. This role will report to the Chief Commercial Officer and be a core member of the US Commercial Leadership Team. The individual will partner closely with internal stakeholders, omnichannel teams, and agency partners to design and implement robust measurement frameworks, leveraging advanced analytics, forecasts, statistical methodologies, and machine learning techniques." We'll put that in About the role. Now Responsibilities: we need to list duties from Essential Functions. Essential Functions broken into sections: Data Analytics and Insights: - Partner with the company's Leadership Team and commercial cross-functional leaders to define the data and insights strategy and roadmap and align analytics priorities with business objectives - Manage and own the data and insights foundation, including the systems, data integration, and processes required to monitor business performance efficiently and accurately. - Manage the collection, analysis, and interpretation of patient finding, promotional execution (including omnichannel) and sales data, leveraging latest available technologies and approaches (including AI) to identify trends, opportunities, and areas for improvement providing insightful recommendations leading to improved organizational execution - Utilize data sources and innovative approaches to optimize patient identification at different stages of their journey developing recommended next steps guidance to optimize patient access to treatment. - Lead the design, execution, and analysis of primary and secondary market research to provide differentiated insights and subsequent recommendations for brand strategy and customer segmentation, ie; look beyond the data and generate meaningful business insights based on understanding of PFP business - Establish and execute a vision to optimally integrate available data sources to optimize organizational execution facilitating appropriate patient access to treatment - Partner collaboratively with other commercial stakeholders to define KPIs and effectively implement data and insights recommendations leading to measurable business impact Reporting, Forecasting and Modeling: - Establish a robust, compliant data strategy and accessible, interpretable business performance reporting systems and processes - Create, codify and present regular, comprehensive, intuitive, insight driven reports and dashboards to communicate business critical insights and recommendations to stakeholders. - Set reliable processes to collect dispensing data (when applicable) and purchasing data from all class of trades and ensure consolidation of this data for analytical and forecasting purposes - Develop and own forecasting models for in-line products and pipeline - Support enablement of innovative, efficient patient finding and omnichannel deployment, defining and tracking KPIs for effectiveness - Establish and execute a vision to optimally integrate available data sources to optimize organizational execution facilitating appropriate patient access to treatment (duplicate? appears again) - Establish field force performance reporting platforms and processes including activity and Field Forve Incentive Compensation - Serve as key contributor to Business Development commercial assessments - Establish accessible, reliable, and compliant business-performance reporting — the systems and processes that make performance data trustworthy and easy to interpret across the organization. Leadership: - Lead cross-functional initiatives and influence key business decisions through data-driven insights. - Develop strong partnerships across Commercial, Market Access, Medical, Finance, and external vendors - Be seen as a trusted, collaborative, valued member of the commercial leadership team - Other duties and responsibilities may be assigned as required based on evolving business needs. We need to deduplicate duplicate lines: "Establish and execute a vision to optimally integrate available data sources to optimize organizational execution facilitating appropriate patient access to treatment" appears twice (once in Data Analytics and Insights, once in Reporting, Forecasting and Modeling). We should keep only one instance. Also "Establish accessible, reliable, and compliant business-performance reporting — the systems and processes that make performance data trustworthy and easy to interpret across the organization." appears maybe twice? Actually appears in Reporting, Forecasting and Modeling as last bullet and also maybe earlier? We'll keep one. Now we need to output as- for any list of duties/requirements/benefits. So we can have a single
- with all responsibilities items. Or we could break into subheadings? Not allowed; only headings are those specific. So we can just have one Responsibilities section with a
- Bachelor’s degree in business, Economics, Data Science, Computer Science or related field such as Marketing; Master’s or MBA preferred.
- Minimum 10+ years in data analytics, forecasting or commercial strategy within the pharmaceutical or life sciences industry.
- Expert-level, hands-on command of SQL Server and advanced Excel, the technologies used day to day to build and deliver the data models, dashboards, and forecasts this role owns such as Tableau or Power BI. This is a build role, the successful candidate must work directly in these tools, not solely direct others who do.
- Fluency with various industry data sources, such as patient claims data, patient longitudinal data, RWD, etc
- Experience utilizing complex data to drive business decisions, hands on experience in data science methodologies (predictive analytics, machine learning, patient level data triggers)
- Demonstrated Experience in rare disease analytics or patient-finding programs
- Demonstrated expertise in developing forecasts, such as assumption development, scenario analysis, model validation, variance analysis, and communication of uncertainty.
- A bias toward action and outcomes and ability to thrive in a dynamic, fast paced, high-growth environment.
- Strong communication skills (written and verbal) to effectively present complex analytical findings to non-technical stakeholders.
- Strong team player, with low ego, high emotional intelligence and demonstrated ability to work productively with diverse, cross organizational teams
- Preferred Experience: Experience with commercial build or scaling of Analytics function strongly preferred
- Applicants must be
- containing all duty items.
Now Requirements/Qualifications: We have Required Education and Experience, plus Preferred Experience, plus maybe the visa note.
We need to decide which heading to use: Requirements or Qualifications. The instruction includes both. We could use "Qualifications" for education/experience and "Skills" for technical skills. But we also have "Preferred Experience". Could be part of Qualifications.
Better to have a single "Qualifications" section containing both required and preferred. Or we could have "Requirements" for required, and "Skills" for technical skills, and maybe "Preferred Experience" as part of Requirements? But we must not create thin sections. Prefer few substantive sections.
Thus we can have:
Qualifications