Senior Master Data Steward - Master Data Mgmt - 5020
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.
We have:
- Position Summary (some prose about role location, etc.)
- Key Responsibilities (list)
- Required Qualifications (list)
- Preferred Qualifications (list)
- Skills & Competencies (list)
- Benefits: The posting includes "Why you’ll love it here! Benefits include Medical, Dental, Vision, Tuition Reimbursement, Pet, and Legal Insurance 401k Community Service Day Spotlight Awards National Sales Excellence Awards CFSP Prep Certification Program". So there is benefits content. Also later: "In addition to base salary, this role will be eligible for participation in TriMark’s’ benefits programs, including medical, dental, vision, 401K (with employer match), etc." So benefits are present.
- Compensation: There's a paragraph about compensation includes posted base salary range and does not reflect potential commission, incentive, bonus, etc. Also mentions leadership positions may also qualify for participation in bonus programs commensurate with role and scope of responsibility. This is somewhat vague but includes mention of compensation details. However we should not create Pay section unless posting actually states them. It does mention base salary range (though not given numbers) and bonus programs commensurate with role. This is somewhat vague but still mentions compensation. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state compensation includes posted base salary range and bonus programs. So we could include a Pay section? But they said prefer a few substantive sections over many thin ones. Could combine Compensation into Benefits? Probably better to have a Benefits section and maybe a Compensation section if there is specific info. However the compensation paragraph is somewhat generic but still mentions base salary range and bonus programs. It's not placeholder like "commensurate with experience" but it's still vague. The instruction says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). The compensation paragraph includes "commensurate with role and scope of responsibility." That's similar to placeholder. Might be considered filler. Safer to omit Pay section.
Schedule: Not mentioned (Hybrid is mentioned in Position Summary: "Located in Mansfield, MA Full-Time Hybrid". That's schedule info: Full-Time Hybrid. Could we create a Schedule section? The posting states Full-Time Hybrid. That's specific. So we could include a Schedule section with that info. However they said prefer a few substantive sections over many thin ones. Could incorporate schedule into Position Summary or maybe a separate Schedule section. Since schedule is specific, we could include a Schedule section.
But we need to decide sections: About the role (maybe Position Summary), Responsibilities (Key Responsibilities), Requirements (maybe combine Required and Preferred Qualifications?), Qualifications (maybe separate?), Skills (Skills & Competencies), Benefits, Schedule.
We need to avoid duplication. Let's extract substantive content.
First, we need to strip boilerplate: The initial paragraph about TriMark USA description, "Why you’ll love it here! Benefits include..." we need to keep benefits but remove fluff? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we keep the benefits list as is.
We also need to remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, application instructions. So we need to cut out the EEO paragraph, scam alert, accommodation request, etc.
Also remove the initial fluff about TriMark USA? That is substantive? It's company description; maybe not needed for job posting but could be considered background. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. The company description is substantive but maybe not required for job posting? However they said we should not repeat job title as heading; but we can include a short paragraph about company? The initial paragraph is about TriMark USA; it's not directly about the role but could be considered background. The instruction didn't say to remove company description. It said remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we keep the company description.
But we need to format into sections with headings.
Let's parse the posting:
TriMark USA is the country’s largest provider... (company description)
Why you’ll love it here! Benefits include Medical, Dental, Vision, Tuition Reimbursement, Pet, and Legal Insurance401kCommunity Service DaySpotlight AwardsNational Sales Excellence AwardsCFSP Prep Certification Program
Position Summary The Senior Master Data Steward reports to the Master Data Steward ManagerLocated in Mansfield, MAFull-TimeHybrid TriMark USA is seeking a Senior Master Data Steward, an experienced ERP professional who will own the accuracy, consistency, and integrity of master data across all three core domains: Product/Item, Customer, and Vendor/Supplier. The ideal candidate brings strong, broad-based ERP expertise together with working knowledge of Infor M3 and JD Edwards (JDE), and sets the standards, controls, and processes that keep master data reliable across a multi-ERP environment, including system integrations, acquisitions, and data conversions. This is a lead-level individual contributor role that also guides and mentors other data stewards and partners closely with Sales, Procurement, Finance, Supply Chain, and IT.
Key Responsibilities ERP Master Data Ownership, serve as the organization's ERP master data expert across all three core domains, Item/Product, Customer, and Vendor/Supplier, working primarily within Infor M3 and JD Edwards (JDE). Data Governance, lead governance, standardization, and lifecycle management for master data creation, maintenance, enrichment, and retirement across ERP systems, ensuring one consistent source of truth. Standards & Controls, define, document, and enforce data quality standards, naming conventions, field-level definitions, and validation rules across product, customer, and vendor master files. Cross-Functional Partnership, partner with Sales, Procurement, Finance, and Supply Chain to gather requirements and ensure master data supports downstream transactions, including pricing, order management, procurement, and invoicing. Data Quality, lead root-cause analysis and remediation of data quality issues; define and monitor KPIs for data accuracy, completeness, and timeliness. Migrations & Integrations, support ERP data migrations, conversions, and system integrations, including mapping and validating data moving between platforms such as Infor M3 and JD Edwards. Documentation & Enablement, develop and maintain governance documentation, SOPs, data dictionaries, field-level standards, stewardship policies and lead training for business users and junior stewards on ERP master data standards. Systems Collaboration, collaborate with IT and functional teams on system enhancements, user acceptance testing (UAT), and change management related to master data structures and workflows. M&A / Multi-ERP Support, assess legacy or newly-acquired company ERP data during mergers, acquisitions, or system consolidations, and lead mapping/conversion of records into standardized formats across Infor M3, JD Edwards, or other systems as needed. Continuous Improvement, identify and drive automation and process improvement opportunities within master data maintenance and governance workflows.
Required Qualifications Bachelor's degree in Business, Information Systems, Supply Chain Management, or a related field, or an equivalent combination of education and experience. 5+ years of experience in master data management, data stewardship, or ERP data administration. Demonstrated expertise in ERP master data management and governance, with hands-on experience across Item/Product, Customer, and Vendor/Supplier domains; working knowledge of Infor M3 and/or JD Edwards (JDE) is required, with proficiency in both strongly preferred. Strong understanding of how ERP master data supports core business processes, including order-to-cash, procure-to-pay, and item lifecycle management. Prior experience leading, mentoring, or providing functional direction to other data stewards or analysts. Excellent analytical and problem-solving skills, with the ability to translate business requirements into clear data standards and governance controls. Advanced proficiency in Excel and other data analysis/reporting tools for data auditing and quality reporting.
Preferred Qualifications Hands-on experience with both Infor M3 and JD Edwards (JDE) EnterpriseOne, including item, customer, and vendor master structures. Experience supporting ERP consolidations, migrations, or M&A integration projects spanning multiple ERP platforms. Familiarity with Infor ION, Infor Data Lake, BODs, or other ERP integration/middleware tools. Industry experience in distribution, manufacturing, or foodservice equipment and supplies. Knowledge of formal data governance frameworks or master data management (MDM) tools and methodologies.
Skills & Competencies Exceptional attention to detail and an unwavering commitment to data accuracy and integrity. Strong stakeholder management skills across both business and technical audiences. Ability to lead and influence cross-functional teams without direct authority. Solid organizational and project management skills, with the ability to manage multiple priorities. Comfortable operating across multiple ERP environments and adapting to evolving system landscapes. Ability to successfully pass a background check post offer acceptance.
Compensation includes the posted base salary range and does not reflect potential commission, incentive, bonus, or other additional compensation opportunities, where applicable. Total compensation is determined based on experience, skills, internal equity, geographic location, and other job-related compensatory factors. In addition to base salary, this role will be eligible for participation in TriMark’s’ benefits programs, including medical, dental, vision, 401K (with employer match), etc. Leadership positions may also qualify for participation in bonus programs commensurate with role and scope of responsibility.
Then EEO etc.
We need to output HTML fragment with sections.
We need to decide which headings to use: About the role (maybe Position Summary), Responsibilities, Requirements (maybe combine Required and Preferred?), Qualifications (maybe separate?), Skills, Benefits, Schedule.
But we need to avoid thin sections. Could combine Required and Preferred Qualifications into a single "Qualifications" section with subheadings? But we only allowed h3 for section headings; we could have multiple h3 sections: Required Qualifications, Preferred Qualifications. That's okay if they have substantive content. They do.
Skills & Competencies also substantive.
Benefits: we have benefits list.
Schedule: we have Full-Time Hybrid.
We could also include a short paragraph about location (Mansfield, MA) maybe in Position Summary.
Let's craft sections:
- About the role (maybe "Position Summary") as h3.
- Responsibilities (Key Responsibilities) as h3.
- Required Qualifications as h3.
- Preferred Qualifications as h3.
- Skills & Competencies as h3.
- Benefits as h3.
- Schedule as h3 (Full-Time Hybrid).
We need to ensure we don't include filler like "commensurate with experience". The Benefits section includes specific items: Medical, Dental, Vision, Tuition Reimbursement, Pet, and Legal Insurance, 401k, Community Service Day, Spotlight Awards, National Sales Excellence Awards, CFSP Prep Certification Program. That's specific.
Schedule: Full-Time
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. We have: - Position Summary (some prose about role location, etc.) - Key Responsibilities (list) - Required Qualifications (list) - Preferred Qualifications (list) - Skills & Competencies (list) - Benefits: The posting includes "Why you’ll love it here! Benefits include Medical, Dental, Vision, Tuition Reimbursement, Pet, and Legal Insurance 401k Community Service Day Spotlight Awards National Sales Excellence Awards CFSP Prep Certification Program". So there is benefits content. Also later: "In addition to base salary, this role will be eligible for participation in TriMark’s’ benefits programs, including medical, dental, vision, 401K (with employer match), etc." So benefits are present. - Compensation: There's a paragraph about compensation includes posted base salary range and does not reflect potential commission, incentive, bonus, etc. Also mentions leadership positions may also qualify for participation in bonus programs commensurate with role and scope of responsibility. This is somewhat vague but includes mention of compensation details. However we should not create Pay section unless posting actually states them. It does mention base salary range (though not given numbers) and bonus programs commensurate with role. This is somewhat vague but still mentions compensation. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state compensation includes posted base salary range and bonus programs. So we could include a Pay section? But they said prefer a few substantive sections over many thin ones. Could combine Compensation into Benefits? Probably better to have a Benefits section and maybe a Compensation section if there is specific info. However the compensation paragraph is somewhat generic but still mentions base salary range and bonus programs. It's not placeholder like "commensurate with experience" but it's still vague. The instruction says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). The compensation paragraph includes "commensurate with role and scope of responsibility." That's similar to placeholder. Might be considered filler. Safer to omit Pay section. Schedule: Not mentioned (Hybrid is mentioned in Position Summary: "Located in Mansfield, MA Full-Time Hybrid". That's schedule info: Full-Time Hybrid. Could we create a Schedule section? The posting states Full-Time Hybrid. That's specific. So we could include a Schedule section with that info. However they said prefer a few substantive sections over many thin ones. Could incorporate schedule into Position Summary or maybe a separate Schedule section. Since schedule is specific, we could include a Schedule section. But we need to decide sections: About the role (maybe Position Summary), Responsibilities (Key Responsibilities), Requirements (maybe combine Required and Preferred Qualifications?), Qualifications (maybe separate?), Skills (Skills & Competencies), Benefits, Schedule. We need to avoid duplication. Let's extract substantive content. First, we need to strip boilerplate: The initial paragraph about TriMark USA description, "Why you’ll love it here! Benefits include..." we need to keep benefits but remove fluff? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we keep the benefits list as is. We also need to remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, application instructions. So we need to cut out the EEO paragraph, scam alert, accommodation request, etc. Also remove the initial fluff about TriMark USA? That is substantive? It's company description; maybe not needed for job posting but could be considered background. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. The company description is substantive but maybe not required for job posting? However they said we should not repeat job title as heading; but we can include a short paragraph about company? The initial paragraph is about TriMark USA; it's not directly about the role but could be considered background. The instruction didn't say to remove company description. It said remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we keep the company description. But we need to format into sections with headings. Let's parse the posting: TriMark USA is the country’s largest provider... (company description) Why you’ll love it here! Benefits include Medical, Dental, Vision, Tuition Reimbursement, Pet, and Legal Insurance401kCommunity Service DaySpotlight AwardsNational Sales Excellence AwardsCFSP Prep Certification Program Position Summary The Senior Master Data Steward reports to the Master Data Steward ManagerLocated in Mansfield, MAFull-TimeHybrid TriMark USA is seeking a Senior Master Data Steward, an experienced ERP professional who will own the accuracy, consistency, and integrity of master data across all three core domains: Product/Item, Customer, and Vendor/Supplier. The ideal candidate brings strong, broad-based ERP expertise together with working knowledge of Infor M3 and JD Edwards (JDE), and sets the standards, controls, and processes that keep master data reliable across a multi-ERP environment, including system integrations, acquisitions, and data conversions. This is a lead-level individual contributor role that also guides and mentors other data stewards and partners closely with Sales, Procurement, Finance, Supply Chain, and IT. Key Responsibilities ERP Master Data Ownership, serve as the organization's ERP master data expert across all three core domains, Item/Product, Customer, and Vendor/Supplier, working primarily within Infor M3 and JD Edwards (JDE). Data Governance, lead governance, standardization, and lifecycle management for master data creation, maintenance, enrichment, and retirement across ERP systems, ensuring one consistent source of truth. Standards & Controls, define, document, and enforce data quality standards, naming conventions, field-level definitions, and validation rules across product, customer, and vendor master files. Cross-Functional Partnership, partner with Sales, Procurement, Finance, and Supply Chain to gather requirements and ensure master data supports downstream transactions, including pricing, order management, procurement, and invoicing. Data Quality, lead root-cause analysis and remediation of data quality issues; define and monitor KPIs for data accuracy, completeness, and timeliness. Migrations & Integrations, support ERP data migrations, conversions, and system integrations, including mapping and validating data moving between platforms such as Infor M3 and JD Edwards. Documentation & Enablement, develop and maintain governance documentation, SOPs, data dictionaries, field-level standards, stewardship policies and lead training for business users and junior stewards on ERP master data standards. Systems Collaboration, collaborate with IT and functional teams on system enhancements, user acceptance testing (UAT), and change management related to master data structures and workflows. M&A / Multi-ERP Support, assess legacy or newly-acquired company ERP data during mergers, acquisitions, or system consolidations, and lead mapping/conversion of records into standardized formats across Infor M3, JD Edwards, or other systems as needed. Continuous Improvement, identify and drive automation and process improvement opportunities within master data maintenance and governance workflows. Required Qualifications Bachelor's degree in Business, Information Systems, Supply Chain Management, or a related field, or an equivalent combination of education and experience. 5+ years of experience in master data management, data stewardship, or ERP data administration. Demonstrated expertise in ERP master data management and governance, with hands-on experience across Item/Product, Customer, and Vendor/Supplier domains; working knowledge of Infor M3 and/or JD Edwards (JDE) is required, with proficiency in both strongly preferred. Strong understanding of how ERP master data supports core business processes, including order-to-cash, procure-to-pay, and item lifecycle management. Prior experience leading, mentoring, or providing functional direction to other data stewards or analysts. Excellent analytical and problem-solving skills, with the ability to translate business requirements into clear data standards and governance controls. Advanced proficiency in Excel and other data analysis/reporting tools for data auditing and quality reporting. Preferred Qualifications Hands-on experience with both Infor M3 and JD Edwards (JDE) EnterpriseOne, including item, customer, and vendor master structures. Experience supporting ERP consolidations, migrations, or M&A integration projects spanning multiple ERP platforms. Familiarity with Infor ION, Infor Data Lake, BODs, or other ERP integration/middleware tools. Industry experience in distribution, manufacturing, or foodservice equipment and supplies. Knowledge of formal data governance frameworks or master data management (MDM) tools and methodologies. Skills & Competencies Exceptional attention to detail and an unwavering commitment to data accuracy and integrity. Strong stakeholder management skills across both business and technical audiences. Ability to lead and influence cross-functional teams without direct authority. Solid organizational and project management skills, with the ability to manage multiple priorities. Comfortable operating across multiple ERP environments and adapting to evolving system landscapes. Ability to successfully pass a background check post offer acceptance. Compensation includes the posted base salary range and does not reflect potential commission, incentive, bonus, or other additional compensation opportunities, where applicable. Total compensation is determined based on experience, skills, internal equity, geographic location, and other job-related compensatory factors. In addition to base salary, this role will be eligible for participation in TriMark’s’ benefits programs, including medical, dental, vision, 401K (with employer match), etc. Leadership positions may also qualify for participation in bonus programs commensurate with role and scope of responsibility. Then EEO etc. We need to output HTML fragment with sections. We need to decide which headings to use: About the role (maybe Position Summary), Responsibilities, Requirements (maybe combine Required and Preferred?), Qualifications (maybe separate?), Skills, Benefits, Schedule. But we need to avoid thin sections. Could combine Required and Preferred Qualifications into a single "Qualifications" section with subheadings? But we only allowed h3 for section headings; we could have multiple h3 sections: Required Qualifications, Preferred Qualifications. That's okay if they have substantive content. They do. Skills & Competencies also substantive. Benefits: we have benefits list. Schedule: we have Full-Time Hybrid. We could also include a short paragraph about location (Mansfield, MA) maybe in Position Summary. Let's craft sections: - About the role (maybe "Position Summary") as h3. - Responsibilities (Key Responsibilities) as h3. - Required Qualifications as h3. - Preferred Qualifications as h3. - Skills & Competencies as h3. - Benefits as h3. - Schedule as h3 (Full-Time Hybrid). We need to ensure we don't include filler like "commensurate with experience". The Benefits section includes specific items: Medical, Dental, Vision, Tuition Reimbursement, Pet, and Legal Insurance, 401k, Community Service Day, Spotlight Awards, National Sales Excellence Awards, CFSP Prep Certification Program. That's specific. Schedule: Full-Time