Product Owner

We need to output HTML fragment with sections: maybe About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. The posting includes description of role, responsibilities, requirements, qualifications, skills, maybe benefits not mentioned, pay not mentioned, schedule not mentioned (though hybrid location). There's mention of "Hybrid / Onsite Several Days Per Week" which is schedule info. Could include Schedule section. Benefits not mentioned. Pay not mentioned. So we include sections: About the role (maybe summary), Responsibilities, Requirements, Qualifications, Skills, Schedule. Also maybe "Work Authorization" but that's minor metadata; we can fold into a short p. We must not repeat job title as heading. Use

for each section heading. We need to preserve all substantive info, not invent. Remove boilerplate like "SEND RESUME Rachael rachael@sidramtech.com Please Share Updated Resume Work Authorization Current Location Availability Contact Details LinkedIn Profile Follow SidRam Technologies..." etc. Also remove hashtags. We need to extract content. Let's parse: Job posting: NOW HIRING: SENIOR PRODUCT OWNER FINANCE ERP TRANSFORMATION Client: Altimetrik Industry: Insurance Location: Cary, NC Hybrid / Onsite Several Days Per Week Employment: Full-Time Experience: 12+ Years Work Authorization: No H1B ERP Finance Experience: MUST HAVE ROLE: SENIOR PRODUCT OWNER Workday Finance Transformation | Enterprise Data Hub on Azure A leading insurance carrier is modernizing its ERP landscape from PeopleSoft to Workday, supported by an enterprise Data Hub built on Azure Databricks, Azure Data Factory, and ADLS Gen2. We are seeking a senior Product Owner with deep ERP Finance functional experience to own the Finance data, integration, and reporting backlog across Workday and the Azure Data Hub. Must-have Skills Strong ERP Finance functional experience PeopleSoft / Workday / SAP / Oracle / Microsoft Dynamics GL, AP, AR, Fixed Assets, Financial Close Intercompany, Reconciliation & Financial Controls Finance ERP implementation / modernization / migration Product Ownership / Functional Lead experience Requirements, Epics, User Stories & Acceptance Criteria UAT, Data Validation & Reconciliation Finance Data & Integration Agile / Scrum Jira or Azure DevOps Strong Finance & Technical Stakeholder Management Ability to work Hybrid from Cary, NC Preferred Insurance / Financial Services experience PeopleSoft Financials / Workday Financial Management Workday EIB, Core Connectors, Prism / FDM Azure Databricks / ADF / ADLS Gen2 Synapse / Fabric / Snowflake Finance Data Migration & Data Warehousing Power BI / Adaptive / Anaplan / OneStream Actuarial / Investment / Reinsurance / Risk exposure CSPO / PSPO / CPA / CMA Then after that: "SEND RESUME Rachael rachael@sidramtech.com Please Share Updated Resume Work Authorization Current Location Availability Contact Details LinkedIn Profile Follow SidRam Technologies for daily US IT jobs, Full-Time & Contract opportunities, interview tips, and hiring updates. #SeniorProductOwner ..." We need to drop application instructions and boilerplate. Thus we need to produce sections: About the role: maybe the paragraph describing role: "A leading insurance carrier is modernizing its ERP landscape from PeopleSoft to Workday, supported by an enterprise Data Hub built on Azure Databricks, Azure Data Factory, and ADLS Gen2. We are seeking a senior Product Owner with deep ERP Finance functional experience to own the Finance data, integration, and reporting backlog across Workday and the Azure Data Hub." Responsibilities: Could list items from "Must-have Skills" that are responsibilities? Actually those are skills/experience. But we can treat them as responsibilities: owning finance data, integration, reporting backlog; managing stakeholders; agile/scrum; Jira/Azure DevOps; UAT, data validation; etc. However we need to not invent. We can extract responsibilities from the description: "own the Finance data, integration, and reporting backlog across Workday and the Azure Data Hub." Also "Strong Finance & Technical Stakeholder Management". Also "Ability to work Hybrid from Cary, NC". Also maybe "Product Ownership / Functional Lead experience". Also "Requirements, Epics, User Stories & Acceptance Criteria". Also "UAT, Data Validation & Reconciliation". Also "Finance Data & Integration". Also "Agile / Scrum". Also "Jira or Azure DevOps". We'll put these as bullet list. Requirements: maybe "12+ Years experience", "No H1B", "ERP Finance Experience: MUST HAVE". Also "Strong ERP Finance functional experience". Also "PeopleSoft / Workday / SAP / Oracle / Microsoft Dynamics GL, AP, AR, Fixed Assets, Financial Close Intercompany, Reconciliation & Financial Controls". Also "Finance ERP implementation / modernization / migration". Also "Product Ownership / Functional Lead experience". Also "Requirements, Epics, User Stories & Acceptance Criteria". Also "UAT, Data Validation & Reconciliation". Also "Finance Data & Integration". Also "Agile / Scrum". Also "Jira or Azure DevOps". Also "Strong Finance & Technical Stakeholder Management". Also "Ability to work Hybrid from Cary, NC". Also "Preferred Insurance / Financial Services experience". Also "PeopleSoft Financials / Workday Financial Management". Also "Workday EIB, Core Connectors, Prism / FDM". Also "Azure Databricks / ADF / ADLS Gen2". Also "Synapse / Fabric / Snowflake". Also "Finance Data Migration & Data Warehousing". Also "Power BI / Adaptive / Anaplan / OneStream". Also "Actuarial / Investment / Reinsurance / Risk exposure". Also "CSPO / PSPO / CPA / CMA". That's a lot; many are preferred skills. We need to separate Requirements vs Qualifications vs Skills. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills). So we need to decide what goes where. Usually Requirements are mandatory, Qualifications are preferred, Skills are specific abilities. But we can just follow the posting: "Must-have Skills" list is under that heading. Then "Preferred" list after. So we can treat "Must-have Skills" as Skills section. Then "Preferred" as Qualifications (or maybe Requirements). But we also have experience 12+ years, work authorization, etc. Those could be Requirements. Thus: - About the role: description paragraph. - Responsibilities: maybe bullet list of core duties: owning finance data, integration, reporting backlog; managing stakeholders; agile/scrum; Jira/Azure DevOps; UAT, data validation; etc. - Requirements: 12+ years experience, No H1B, ERP Finance experience mandatory, ability to work hybrid Cary NC, etc. - Qualifications: Preferred insurance/financial services experience, PeopleSoft Financials/Workday Financial Management, Workday EIB etc., Azure Databricks/ADF/ADLS Gen2, Synapse/Fabric/Snowflake, Finance Data Migration & Data Warehousing, Power BI/Adaptive/Anaplan/OneStream, Actuarial/Investment/Reinsurance/Risk exposure, CSPO/PSPO/CPA/CMA. - Skills: Must-have Skills list (the bullet list under "Must-have Skills"). But there is overlap; we need to avoid duplication. However instruction says preserve ALL substantive information; do not invent or summarize away detail. So we need to include all info, but we can organize without duplication? If we duplicate, that's okay as long as we preserve. But better to avoid duplication but still include all. Could split: Must-have Skills list as Skills; Preferred list as Qualifications; Experience and work auth as Requirements; Responsibilities separate. Let's extract Must-have Skills list exactly: Strong ERP Finance functional experience PeopleSoft / Workday / SAP / Oracle / Microsoft Dynamics GL, AP, AR, Fixed Assets, Financial Close Intercompany, Reconciliation & Financial Controls Finance ERP implementation / modernization / migration Product Ownership / Functional Lead experience Requirements, Epics, User Stories & Acceptance Criteria UAT, Data Validation & Reconciliation Finance Data & Integration Agile / Scrum Jira or Azure DevOps Strong Finance & Technical Stakeholder Management Ability to work Hybrid from Cary, NC Note: Ability to work Hybrid from Cary, NC appears also in Must-have Skills. That could be a requirement. Now Preferred list: Insurance / Financial Services experience PeopleSoft Financials / Workday Financial Management Workday EIB, Core Connectors, Prism / FDM Azure Databricks / ADF / ADLS Gen2 Synapse / Fabric / Snowflake Finance Data Migration & Data Warehousing Power BI / Adaptive / Anaplan / OneStream Actuarial / Investment / Reinsurance / Risk exposure CSPO / PSPO / CPA / CMA Now Responsibilities: maybe we can derive from role description: own the Finance data, integration, and reporting backlog across Workday and the Azure Data Hub. Also maybe "Strong Finance & Technical Stakeholder Management". Also "Ability to work Hybrid from Cary, NC". Also "Product Ownership / Functional Lead experience". Also "Requirements, Epics, User Stories & Acceptance Criteria". Also "UAT, Data Validation & Reconciliation". Also "Finance Data & Integration". Also "Agile / Scrum". Also "Jira or Azure DevOps". But many of those overlap with skills. However we can still list responsibilities as bullet points derived from the description: owning finance data, integration, reporting backlog; managing stakeholders; working hybrid; agile/scrum; using Jira/Azure DevOps; conducting UAT, data validation; defining requirements, epics, user stories; ensuring finance ERP implementation/migration; etc. We need to be careful not to invent. Let's stick to explicit statements: - Own the Finance data, integration, and reporting backlog across Workday and the Azure Data Hub. - Strong Finance & Technical Stakeholder Management. - Ability to work Hybrid from Cary, NC. - Product Ownership / Functional Lead experience. - Define Requirements, Epics, User Stories & Acceptance Criteria. - Conduct UAT, Data Validation & Reconciliation. - Manage Finance Data & Integration. - Apply Agile / Scrum methodologies. - Use Jira or Azure DevOps. - Ensure Finance ERP implementation / modernization / migration. These are all present in the text. Now Requirements: 12+ Years experience, No H1B, ERP Finance Experience MUST HAVE, Ability to work Hybrid from Cary, NC (already in responsibilities but okay). Also maybe "Strong ERP Finance functional experience" is a skill not requirement. But we can include as requirement. Qualifications: Preferred list. Skills: Must-have Skills list (maybe we can keep as is). However we already used many of those in responsibilities; but okay. We need to ensure we don't create sections with filler like "commensurate with experience". Not present. Now produce HTML:

About the role

A leading insurance carrier is modernizing its ERP landscape from PeopleSoft to Workday, supported by an enterprise Data Hub built on Azure Databricks, Azure Data Factory, and ADLS Gen2. We are seeking a senior Product Owner with deep ERP Finance functional experience to own the Finance data, integration, and reporting backlog across Workday and the Azure Data Hub.

Responsibilities

• Own the Finance data, integration, and reporting backlog across Workday and the Azure Data Hub.
• Provide strong Finance & Technical Stakeholder Management.
• Ability to work Hybrid from Cary, NC.
• Apply Product Ownership / Functional Lead experience.
• Define Requirements,