AVP, Business Intelligence Manager
for each section heading only if there is real content. We must not repeat job title. We must not include Job ID etc. Remove boilerplate like cookie/navigation/legal/EEO etc. Also remove duplicated lines. We need to preserve all substantive info.
We need to parse the posting.
Content:
- Who We Are SiriusPoint is a specialty underwriter... (company description). This could be "About the role"? Actually "Who We Are" is about company, not role. But we need sections: About the role (maybe we can put company description there? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to these headings. "About the role" could include description of role and maybe company overview? Usually "About the role" includes role summary. We have "Join Our Team You will be our AVP, Business Intelligence Manager, accountable for ...". That's role summary. So we can put that under About the role.
- Responsibilities: The bullet list under "Your Responsibilities Will Include" with subheadings: BI Strategy, Governance, and Operating Model; Team Leadership and Delivery; Business Partnership and Insight; Technology, Data Quality, and Controls. Each has paragraphs. We need to output as - for any list of duties/requirements/benefits. So we can treat each bullet as
- with the content. Should we preserve subheadings inside li? Probably we can keep them as part of li text.
- Requirements / Qualifications / Skills: The posting has "Your Skills And Abilities Should Include" list. That's skills. Also there may be qualifications like Bachelor's degree etc. We can put under Skills (or Requirements). The instruction: Use sections as needed. We have Skills section. Could also have Qualifications (education). We'll decide: We'll put education under Qualifications. Skills under Skills.
- Benefits: list of benefits after "Benefits". We'll output as
- .
- Pay: Salary range $150,000 - $170,000 USD. So we need Pay section.
- Schedule: Not mentioned. So we omit Schedule section.
- Also we have "Our CCPA Job Applicant Policy" etc - that's legal boilerplate, remove.
- Also "United behind common goals" etc - that's fluff but maybe part of company culture; could be considered part of About the role? Might be considered boilerplate but it's about culture. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The culture statements might be considered not boilerplate but could be considered fluff. However they are substantive? They are generic values. Might be considered boilerplate? The instruction says remove duplicated lines, but not necessarily remove values. However they say "Prefer a few substantive sections over many thin ones." Might be okay to include under About the role? But we already have About the role with role summary. Could add a short paragraph about company culture under About the role? Might be considered filler. Safer to omit unless it's specific. The values are generic but could be considered part of company description. However we already have Who We Are section describing company. That could be placed under About the role? Actually "Who We Are" is company overview. That is substantive. So we can include that as part of About the role (or maybe a separate section like "About the company" but not allowed headings). We'll put company overview in About the role before role summary.
Thus About the role will contain: company description (Who We Are) + role summary (Join Our Team ...). We'll combine into a
maybe multiple paragraphs.
Now Responsibilities: we need to extract each bullet.
Let's extract responsibilities sections:
**BI Strategy, Governance, and Operating Model**
- Define and maintain the BI roadmap, priorities, standards, and delivery approach in alignment with enterprise data and technology strategy.
- Establish consistent practices for dashboard design, KPI definitions, data lineage, documentation, testing, release management, and ongoing support.
- Embed AI across the BI delivery lifecycle, from requirements and data modeling through development, testing, documentation, and support, to increase speed, quality, and consistency.
- Partner with data governance, architecture, security, and business teams to improve the trust, accessibility, and appropriate use of information.
- Drive adoption, data literacy, and a self-service analytics culture while maintaining appropriate controls and stewardship.
**Team Leadership and Delivery**
- Lead, coach, and develop BI engineers and analysts, setting clear objectives, accountabilities, and development plans.
- Build AI fluency across the team and embed AI-driven ways of working into everyday BI delivery.
- Own demand intake, prioritization, capacity planning, and delivery commitments for the BI portfolio.
- Create a transparent delivery cadence with clear plans, risks, dependencies, decisions, and stakeholder communications.
- Balance strategic platform improvements with business reporting needs, production support, and technical debt reduction.
**Business Partnership and Insight**
- Build trusted relationships with senior stakeholders to understand business outcomes, define meaningful measures, and translate needs into scalable BI solutions.
- Oversee the development and maintenance of executive dashboards, operational reporting, and analytical products across insurance and corporate functions.
- Ensure insights are communicated clearly, with appropriate context, to support decisions, identify trends, and highlight opportunities and risks.
- Evolve the practice from static report production toward AI-augmented insight, such as automated anomaly detection, forecasting, and plain-language explanation of results.
- Partner with business teams to rationalize reports, strengthen KPI ownership, and reduce duplicative or inconsistent reporting.
- Lead a community of practice to strengthen collaboration, standards, and adoption.
**Technology, Data Quality, and Controls**
- Provide technical leadership across Power BI, SQL, AWS Redshift, semantic models, ETL processes, and related cloud technologies.
- Ensure solutions meet expectations for performance, scalability, usability, resilience, security, and maintainability.
- Implement quality controls for data validation, reconciliation, access, change management, and production monitoring.
- Set review and validation standards for AI-assisted development and AI-generated insights so that outputs remain accurate, explainable, and auditable.
- Partner with data engineering and architecture teams on source integration, platform enhancements, and reusable data products.
Now Skills: "Your Skills And Abilities Should Include" list:
- Progressive experience in business intelligence, reporting, analytics, or data engineering, including leadership of teams and complex delivery portfolios.
- Demonstrated ability to lead managers, engineers, or analysts and to build a high-performing, service-oriented team.
- Strong hands-on knowledge of Power BI, SQL, and modern data platforms; experience with AWS Redshift and cloud-based data ecosystems is strongly preferred.
- Experience defining BI standards, governance, operating practices, and scalable reporting architectures.
- Strong understanding of data modeling, semantic layers, ETL or ELT, data quality, security, and performance optimization.
- Understanding of semantic layers and knowledge graphs/ontologies as the foundation for AI.
- Insurance or reinsurance experience is preferred, including familiarity with policy, claims, underwriting, finance, or actuarial data.
- Experience applying AI to modernize how BI is designed, delivered, and consumed, with sound judgment on quality, risk, and governance.
- Excellent executive communication, stakeholder management, facilitation, and presentation skills.
- Demonstrated ability to influence across a global organization, manage competing priorities, and make pragmatic, risk-informed decisions.
- Bachelor’s degree in computer science, information systems, data analytics, engineering, or a related field, or equivalent professional experience.
We could split: Education under Qualifications, rest under Skills. But we can also put all under Skills. The instruction: Use headings for Skills, Benefits, Pay, Schedule, etc. It didn't forbid mixing qualifications under Skills. But we have a Qualifications heading available; we could put education there. Let's do:
- Qualifications: Bachelor’s degree ... or equivalent professional experience.
- Skills: the rest.
Now Benefits list: after "Benefits We aim to retain..." list:
Medical
Dental
Vision
FSA Medical and Dependent care
Health Savings Account (HSA)
EAP
Basic Life and AD&D (company paid)
Basic Long-Term Disability (employer) paid-Taxable income
Employee paid Long Term Disability(voluntary)
Company Medical Leave, Parental leave- 8 weeks full pay after 6 months of service
Voluntary benefits: short term disability, Critical illness, Hospital Indemnity, Accident
Travel assistance programs Company paid
401(k) 6 % safe harbor match, fully vested after two years, pre- and post-tax contributions allowed
Gym reimbursement
Legal plan
Pet Insurance
Tuition reimbursement
Generous PTO
Flexible work arrangement
Fully stacked pantry on-site
Team outings
ERG Groups
We need to output as
- each item. Some items have colons etc. Keep as is.
Pay: Salary range $150,000 - $170,000 USD.
Schedule: none.
Now we need to output only HTML fragment, no /, no markdown fences.
We'll produce something like:
About the role
SiriusPoint is a specialty underwriter providing solutions to clients and brokers around the world. Bermuda-headquartered with offices in New York, London, Stockholm and other locations, we are listed on the New York Stock Exchange (SPNT). We have licenses to write Property & Casualty and Accident & Health insurance and reinsurance globally. Our offering and distribution capabilities are strengthened by a portfolio of strategic partnerships with Managing General Agents and program managers. With over $3.0 billion total capital, SiriusPoint’s operating companies have a financial strength rating of A from AM Best, Fitch and S&P, and A3 from Moody’s.
Join Our Team You will be our AVP, Business Intelligence Manager, accountable for the strategy, delivery, adoption, and governance of enterprise reporting, dashboards, and analytics. You will lead and develop the BI team, partner with business and technology leaders, and ensure that trusted data is translated into actionable insights that support decision-making across SiriusPoint. You will be instrumental in evolving SiriusPoint's BI practice from traditional reporting to AI-driven decision intelligence, guiding the team and stakeholders in designing and delivering enterprise analytical datasets, semantic models, and business ontologies that enable trusted, scalable self-service analytics. The role will use Microsoft Fabric, Power BI, and emerging AI technologies to transform governed enterprise data into business-ready data products. This role combines people leadership, stakeholder management, delivery accountability, and hands-on BI expertise. You will help mature our cloud-based reporting capabilities across AWS Redshift, Microsoft Fabric, Power BI, and other scalable data solutions.
Responsibilities
- Define and maintain the BI roadmap, priorities, standards, and delivery approach in alignment with enterprise data and technology strategy.
- Establish consistent practices for dashboard design, KPI definitions, data lineage, documentation, testing, release management, and ongoing support.
- Embed AI across the BI delivery lifecycle, from requirements and data modeling through development, testing, documentation, and support, to increase speed, quality, and consistency.
- Partner with data governance, architecture, security, and business teams to improve the trust, accessibility, and appropriate use of information.
- Drive adoption, data literacy, and a self-service analytics culture while maintaining appropriate controls and stewardship.
- Lead, coach, and develop BI engineers and analysts, setting clear objectives, accountabilities, and development plans.
- Build AI fluency across the team and embed AI-driven ways of working into everyday BI delivery.
- Own demand intake, prioritization, capacity planning, and delivery commitments
- for any list of duties/requirements/benefits. So we can treat each bullet as
- with the content. Should we preserve subheadings inside li? Probably we can keep them as part of li text.
- Requirements / Qualifications / Skills: The posting has "Your Skills And Abilities Should Include" list. That's skills. Also there may be qualifications like Bachelor's degree etc. We can put under Skills (or Requirements). The instruction: Use sections as needed. We have Skills section. Could also have Qualifications (education). We'll decide: We'll put education under Qualifications. Skills under Skills.
- Benefits: list of benefits after "Benefits". We'll output as
- .
- Pay: Salary range $150,000 - $170,000 USD. So we need Pay section.
- Schedule: Not mentioned. So we omit Schedule section.
- Also we have "Our CCPA Job Applicant Policy" etc - that's legal boilerplate, remove.
- Also "United behind common goals" etc - that's fluff but maybe part of company culture; could be considered part of About the role? Might be considered boilerplate but it's about culture. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The culture statements might be considered not boilerplate but could be considered fluff. However they are substantive? They are generic values. Might be considered boilerplate? The instruction says remove duplicated lines, but not necessarily remove values. However they say "Prefer a few substantive sections over many thin ones." Might be okay to include under About the role? But we already have About the role with role summary. Could add a short paragraph about company culture under About the role? Might be considered filler. Safer to omit unless it's specific. The values are generic but could be considered part of company description. However we already have Who We Are section describing company. That could be placed under About the role? Actually "Who We Are" is company overview. That is substantive. So we can include that as part of About the role (or maybe a separate section like "About the company" but not allowed headings). We'll put company overview in About the role before role summary.
Thus About the role will contain: company description (Who We Are) + role summary (Join Our Team ...). We'll combine into a
maybe multiple paragraphs. Now Responsibilities: we need to extract each bullet. Let's extract responsibilities sections: **BI Strategy, Governance, and Operating Model** - Define and maintain the BI roadmap, priorities, standards, and delivery approach in alignment with enterprise data and technology strategy. - Establish consistent practices for dashboard design, KPI definitions, data lineage, documentation, testing, release management, and ongoing support. - Embed AI across the BI delivery lifecycle, from requirements and data modeling through development, testing, documentation, and support, to increase speed, quality, and consistency. - Partner with data governance, architecture, security, and business teams to improve the trust, accessibility, and appropriate use of information. - Drive adoption, data literacy, and a self-service analytics culture while maintaining appropriate controls and stewardship. **Team Leadership and Delivery** - Lead, coach, and develop BI engineers and analysts, setting clear objectives, accountabilities, and development plans. - Build AI fluency across the team and embed AI-driven ways of working into everyday BI delivery. - Own demand intake, prioritization, capacity planning, and delivery commitments for the BI portfolio. - Create a transparent delivery cadence with clear plans, risks, dependencies, decisions, and stakeholder communications. - Balance strategic platform improvements with business reporting needs, production support, and technical debt reduction. **Business Partnership and Insight** - Build trusted relationships with senior stakeholders to understand business outcomes, define meaningful measures, and translate needs into scalable BI solutions. - Oversee the development and maintenance of executive dashboards, operational reporting, and analytical products across insurance and corporate functions. - Ensure insights are communicated clearly, with appropriate context, to support decisions, identify trends, and highlight opportunities and risks. - Evolve the practice from static report production toward AI-augmented insight, such as automated anomaly detection, forecasting, and plain-language explanation of results. - Partner with business teams to rationalize reports, strengthen KPI ownership, and reduce duplicative or inconsistent reporting. - Lead a community of practice to strengthen collaboration, standards, and adoption. **Technology, Data Quality, and Controls** - Provide technical leadership across Power BI, SQL, AWS Redshift, semantic models, ETL processes, and related cloud technologies. - Ensure solutions meet expectations for performance, scalability, usability, resilience, security, and maintainability. - Implement quality controls for data validation, reconciliation, access, change management, and production monitoring. - Set review and validation standards for AI-assisted development and AI-generated insights so that outputs remain accurate, explainable, and auditable. - Partner with data engineering and architecture teams on source integration, platform enhancements, and reusable data products. Now Skills: "Your Skills And Abilities Should Include" list: - Progressive experience in business intelligence, reporting, analytics, or data engineering, including leadership of teams and complex delivery portfolios. - Demonstrated ability to lead managers, engineers, or analysts and to build a high-performing, service-oriented team. - Strong hands-on knowledge of Power BI, SQL, and modern data platforms; experience with AWS Redshift and cloud-based data ecosystems is strongly preferred. - Experience defining BI standards, governance, operating practices, and scalable reporting architectures. - Strong understanding of data modeling, semantic layers, ETL or ELT, data quality, security, and performance optimization. - Understanding of semantic layers and knowledge graphs/ontologies as the foundation for AI. - Insurance or reinsurance experience is preferred, including familiarity with policy, claims, underwriting, finance, or actuarial data. - Experience applying AI to modernize how BI is designed, delivered, and consumed, with sound judgment on quality, risk, and governance. - Excellent executive communication, stakeholder management, facilitation, and presentation skills. - Demonstrated ability to influence across a global organization, manage competing priorities, and make pragmatic, risk-informed decisions. - Bachelor’s degree in computer science, information systems, data analytics, engineering, or a related field, or equivalent professional experience. We could split: Education under Qualifications, rest under Skills. But we can also put all under Skills. The instruction: Use headings for Skills, Benefits, Pay, Schedule, etc. It didn't forbid mixing qualifications under Skills. But we have a Qualifications heading available; we could put education there. Let's do: - Qualifications: Bachelor’s degree ... or equivalent professional experience. - Skills: the rest. Now Benefits list: after "Benefits We aim to retain..." list: Medical Dental Vision FSA Medical and Dependent care Health Savings Account (HSA) EAP Basic Life and AD&D (company paid) Basic Long-Term Disability (employer) paid-Taxable income Employee paid Long Term Disability(voluntary) Company Medical Leave, Parental leave- 8 weeks full pay after 6 months of service Voluntary benefits: short term disability, Critical illness, Hospital Indemnity, Accident Travel assistance programs Company paid 401(k) 6 % safe harbor match, fully vested after two years, pre- and post-tax contributions allowed Gym reimbursement Legal plan Pet Insurance Tuition reimbursement Generous PTO Flexible work arrangement Fully stacked pantry on-site Team outings ERG Groups We need to output as
- each item. Some items have colons etc. Keep as is.
Pay: Salary range $150,000 - $170,000 USD.
Schedule: none.
Now we need to output only HTML fragment, no /, no markdown fences.
We'll produce something like:
About the role
SiriusPoint is a specialty underwriter providing solutions to clients and brokers around the world. Bermuda-headquartered with offices in New York, London, Stockholm and other locations, we are listed on the New York Stock Exchange (SPNT). We have licenses to write Property & Casualty and Accident & Health insurance and reinsurance globally. Our offering and distribution capabilities are strengthened by a portfolio of strategic partnerships with Managing General Agents and program managers. With over $3.0 billion total capital, SiriusPoint’s operating companies have a financial strength rating of A from AM Best, Fitch and S&P, and A3 from Moody’s.
Join Our Team You will be our AVP, Business Intelligence Manager, accountable for the strategy, delivery, adoption, and governance of enterprise reporting, dashboards, and analytics. You will lead and develop the BI team, partner with business and technology leaders, and ensure that trusted data is translated into actionable insights that support decision-making across SiriusPoint. You will be instrumental in evolving SiriusPoint's BI practice from traditional reporting to AI-driven decision intelligence, guiding the team and stakeholders in designing and delivering enterprise analytical datasets, semantic models, and business ontologies that enable trusted, scalable self-service analytics. The role will use Microsoft Fabric, Power BI, and emerging AI technologies to transform governed enterprise data into business-ready data products. This role combines people leadership, stakeholder management, delivery accountability, and hands-on BI expertise. You will help mature our cloud-based reporting capabilities across AWS Redshift, Microsoft Fabric, Power BI, and other scalable data solutions.
Responsibilities
- Define and maintain the BI roadmap, priorities, standards, and delivery approach in alignment with enterprise data and technology strategy.
- Establish consistent practices for dashboard design, KPI definitions, data lineage, documentation, testing, release management, and ongoing support.
- Embed AI across the BI delivery lifecycle, from requirements and data modeling through development, testing, documentation, and support, to increase speed, quality, and consistency.
- Partner with data governance, architecture, security, and business teams to improve the trust, accessibility, and appropriate use of information.
- Drive adoption, data literacy, and a self-service analytics culture while maintaining appropriate controls and stewardship.
- Lead, coach, and develop BI engineers and analysts, setting clear objectives, accountabilities, and development plans.
- Build AI fluency across the team and embed AI-driven ways of working into everyday BI delivery.
- Own demand intake, prioritization, capacity planning, and delivery commitments
- each item. Some items have colons etc. Keep as is.
Pay: Salary range $150,000 - $170,000 USD.
Schedule: none.
Now we need to output only HTML fragment, no /, no markdown fences.
We'll produce something like:
- .
- Pay: Salary range $150,000 - $170,000 USD. So we need Pay section.
- Schedule: Not mentioned. So we omit Schedule section.
- Also we have "Our CCPA Job Applicant Policy" etc - that's legal boilerplate, remove.
- Also "United behind common goals" etc - that's fluff but maybe part of company culture; could be considered part of About the role? Might be considered boilerplate but it's about culture. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The culture statements might be considered not boilerplate but could be considered fluff. However they are substantive? They are generic values. Might be considered boilerplate? The instruction says remove duplicated lines, but not necessarily remove values. However they say "Prefer a few substantive sections over many thin ones." Might be okay to include under About the role? But we already have About the role with role summary. Could add a short paragraph about company culture under About the role? Might be considered filler. Safer to omit unless it's specific. The values are generic but could be considered part of company description. However we already have Who We Are section describing company. That could be placed under About the role? Actually "Who We Are" is company overview. That is substantive. So we can include that as part of About the role (or maybe a separate section like "About the company" but not allowed headings). We'll put company overview in About the role before role summary.
Thus About the role will contain: company description (Who We Are) + role summary (Join Our Team ...). We'll combine into a