Project Manager, Master Data

We need to output HTML fragment with sections: About the role? The description includes description paragraph. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We have description (maybe About the role). Then Responsibilities: there is a "Key Responsibilities" block. Then Qualifications & Experience: that's qualifications. Also there is "Success Measures" maybe could be part of Responsibilities? But we can treat as part of Responsibilities or maybe separate? The instruction: prefer few substantive sections over many thin ones. So we can combine Success Measures into Responsibilities or Qualifications? Probably Responsibilities includes monitoring & auditing etc. Success Measures could be part of Responsibilities as outcomes. We'll include Responsibilities section covering both Key Responsibilities and Success Measures. We have Salary Description: $100,000 - $135,000. That's Pay. So include Pay section. We have no explicit Benefits or Schedule. So omit those sections. We need to not repeat job title as heading. The job title is "Project Manager, Master Data". Not to be used as heading. We need to include minor metadata like Job ID? Not present. So ignore. We need to remove boilerplate etc. Not present. We need to use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve all substantive information. Let's extract content. Description paragraph: "The Project Manager, Master Data leads the strategy, governance, and end-to-end development of product and enterprise master data across planning, merchandising, pricing, and compliance systems. This is a hands-on, high-visibility role: you will own the accuracy, integrity, and timeliness of product data that Planning, Merchandising, and Operations rely on daily, and you will lead the projects, system enhancements, and process improvements to create & maintain data integrity that scales with the business will partner directly with Sales, Planning, Merchandising, IT, and Operations leadership to translate business requirements into data standards, system capabilities, and measurable quality outcomes." There's a slight grammar issue but we keep as is. Now Responsibilities: Under "Key Responsibilities" there are bullet-like sentences but not formatted as list. We need to turn into

  • . Let's list each responsibility: - End-to-End Stewardship: Manage the execution of product data across planning, merchandising, pricing, and compliance systems driving accurate, consistent, secure, accessible data and usage. - Standards & Integrity: Enforce strict data standards, governance rules, and naming conventions to maintain a "single source of truth." - Readiness: Ensure data completeness and accuracy to support critical functions such as forecasting, assortment planning, and replenishment. - Project Leadership: Plan and lead master data projects and system enhancements from scope planning through go-live, coordinating timelines, stakeholders, and user acceptance testing. - Data Roadmap: Contribute to a multi-quarter master data roadmap, prioritizing initiatives against Planning, Merchandising, and compliance needs. - Quality Control & Optimization Monitoring & Auditing: Track data quality KPIs and perform regular audits, validations, and data cleansing to mitigate risks. - Process Improvement: Develop automation solutions to enhance the speed, accuracy, and reliability of data entry and maintenance. - KPI Ownership: Define and report data quality KPIs (e.g., item-setup accuracy, on-time attribute completion, audit error rate) to leadership on a recurring cadence. - Root-Cause Resolution: Investigate recurring data errors to their source and implement permanent fixes rather than one-off corrections. - Systems & Collaboration Functional Expertise: Act as the lead data expert for ERP/NetSuite and , PLM/WFX platforms. (Note there is a stray comma after NetSuite and before PLM/WFX; we keep as is.) - Technical Support: Support system upgrades, User Acceptance Testing (UAT), and defect resolution. - Cross-Functional Partnership: Collaborate closely with Sales, Planning, Merchandising, IT, and Operations to streamline data workflows. - Compliance: Maintain product safety and compliance records while supporting internal and external audits. - Systems Roadmap: Partner with IT on the long-term systems roadmap for NetSuite, PLM/ WFX, and adjacent data platforms (e.g., PIM/DAM), advocating for master data requirements. Success Measures: Could be separate bullet list but we can incorporate as part of Responsibilities or separate? Since we want few sections, we can add as part of Responsibilities as additional bullet points. Success Measures bullet points: - Data accuracy and completeness rates trend upward quarter over quarter across NetSuite and PLM/WFX. - New items and attribute changes are set up correctly and on time, minimizing downstream rework for Planning and Merchandising. - Audit findings related to product data decline year over year. - Manual data-entry effort decreases as automation and process improvements are implemented take hold. Now Qualifications & Experience: We need to list qualifications. We have: Experience: 4+ years of dedicated experience in product/master data management or enterprise retail systems; experience in home textiles, flooring, apparel or consumer goods is a plus. Education: Bachelor’s degree in Business, Information Systems, Supply Chain Management, or a related field, or equivalent practical experience. Technical Proficiency: Strong hands-on experience with ERP and product management systems (NetSuite, PLM/WFX, or similar). Advanced Excel skills (VLOOKUPs, Pivot Tables, Macros, etc.) are required. Reporting & Analytics: Experience with SQL, Power BI, Tableau, or similar reporting/data-visualization tools is a plus. Project Management: Demonstrated project management experience; PMP, Agile/Scrum, or Lean Six Sigma certification is a plus. Competencies: Proven ability to operate independently in high-pressure, deadline-driven environments. Exceptional attention to detail and a proactive approach to problem-solving. Strong communication skills to bridge the gap between technical and business stakeholders. We can turn each into
  • under a
    for Requirements? Actually we have a section "Requirements" maybe we should use that heading for qualifications? The instruction says use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide where to put each piece. We have description (About the role). Responsibilities we have. Qualifications & Experience could go under Qualifications. Requirements maybe could be split? But we have both Requirements and Qualifications headings. The posting has a "Requirements" section (the heading "Requirements") then under that there are bullet points: Key Responsibilities etc. Actually the posting shows: Description ... Requirements Key Responsibilities ... Qualifications & Experience ... Thus the "Requirements" section includes the Key Responsibilities. Then "Qualifications & Experience" includes qualifications. Thus we should map: - About the role: description paragraph. - Responsibilities: maybe not needed because we have Requirements heading for responsibilities. But we need to follow instruction: Use headings as listed. We can put responsibilities under "Requirements" heading (since that's what the posting labels). Or we could put responsibilities under "Responsibilities" heading and ignore "Requirements". The instruction: "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples; we should use those headings when appropriate. The posting has a "Requirements" section containing responsibilities. So we should use

    Requirements

    for that content. Then we can also have

    Qualifications

    for qualifications. We may not need a separate Responsibilities heading if we already used Requirements. But we could also include both if we split responsibilities and requirements? However the posting does not have a separate "Responsibilities" heading; it's under Requirements. So we should not create a Responsibilities heading with no content. So we will use Requirements for the responsibilities list. Qualifications for qualifications list. We also have Pay section from Salary Description. Thus final sections: About the role, Requirements, Qualifications, Pay. We need to ensure we don't include empty sections. Now format:

    About the role

    The Project Manager, Master Data leads the strategy, governance, and end-to-end development of product and enterprise master data across planning, merchandising, pricing, and compliance systems. This is a hands-on, high-visibility role: you will own the accuracy, integrity, and timeliness of product data that Planning, Merchandising, and Operations rely on daily, and you will lead the projects, system enhancements, and process improvements to create & maintain data integrity that scales with the business will partner directly with Sales, Planning, Merchandising, IT, and Operations leadership to translate business requirements into data standards, system capabilities, and measurable quality outcomes.

    Requirements

    • End-to-End Stewardship: Manage the execution of product data across planning, merchandising, pricing, and compliance systems driving accurate, consistent, secure, accessible data and usage.
    • Standards & Integrity: Enforce strict data standards, governance rules, and naming conventions to maintain a "single source of truth."
    • Readiness: Ensure data completeness and accuracy to support critical functions such as forecasting, assortment planning, and replenishment.
    • Project Leadership: Plan and lead master data projects and system enhancements from scope planning through go-live, coordinating timelines, stakeholders, and user acceptance testing.
    • Data Roadmap: Contribute to a multi-quarter master data roadmap, prioritizing initiatives against Planning, Merchandising, and compliance needs.
    • Quality Control & Optimization Monitoring & Auditing: Track data quality KPIs and perform regular audits, validations, and data cleansing to mitigate risks.
    • Process Improvement: Develop automation solutions to enhance the speed, accuracy, and reliability of data entry and maintenance.
    • KPI Ownership: Define and report data quality KPIs (e.g., item-setup accuracy, on-time attribute completion, audit error rate) to leadership on a recurring cadence.
    • Root-Cause Resolution: Investigate recurring data errors to their source and implement permanent fixes rather than one-off corrections.
    • Systems & Collaboration Functional Expertise: Act as the lead data expert for ERP/NetSuite and , PLM/WFX platforms.
    • Technical Support: Support system upgrades, User Acceptance Testing (UAT), and defect resolution.
    • Cross-Functional Partnership: Collaborate closely with Sales, Planning, Merchandising, IT, and Operations to streamline data workflows.
    • Compliance: Maintain product safety and compliance records while supporting internal and external audits.
    • Systems Roadmap: Partner with IT on the long-term systems roadmap for NetSuite, PLM/ WFX, and adjacent data platforms (e.g., PIM/DAM), advocating for master data requirements.
    • Success Measures: Data accuracy and completeness rates trend upward quarter over quarter across NetSuite and PLM/WFX.
    • Success Measures: New items and attribute changes are set up correctly and on time, minimizing downstream rework for Planning and Merchandising.
    • Success Measures: Audit findings related to product data decline year over year.
    • Success Measures: Manual data-entry effort decreases as automation and process improvements are implemented take hold.
    But note we duplicated "Success Measures:" as label inside li; maybe better to just list them as li without label. However we need to preserve the content. The success measures are statements; we can just put them as li. Thus we can have li for each success measure. Now Qualifications:

    Qualifications

    • Experience: 4+ years of dedicated experience in product/master data management or enterprise retail systems; experience in home textiles, flooring