Senior Master Data Specialist

We need to output HTML fragment with sections: headings using

for section headings like 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. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the posting and extract sections. The posting includes: - Our Mission and Purpose (maybe not needed as a section heading? The instructions say use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content to those headings if applicable. But we can also include other headings? The instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we should use those headings when appropriate. It doesn't forbid other headings, but likely we should stick to those standard headings. However, the posting includes sections like "Our Mission and Purpose", "Korpack’s Promise", "Culture", "About The Job", "THE JOURNEY" with subparts, "Required", "THE REQUIREMENTS", "Preferred", "This is a full-time, on-site position based in Bloomingdale, IL.", "THE CHALLENGES", "THE REWARD", "OUR CORE VALUES", "For Those Who Want More Than Just a Job", "Our Commitment to You". Many of these are not standard headings. The instruction says to use those headings for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It might be that we should map the content to those standard headings, ignoring other headings. But we must preserve ALL substantive information. So we need to include all info, but we can place it under appropriate standard headings. For example, "About the role" could contain the description of the job (About The Job, THE JOURNEY, etc). "Responsibilities" could contain duties (own the gate, own correctness, own replenishment signals, fix foundation, feed automations). "Requirements" could contain required qualifications. "Qualifications" could contain preferred qualifications. "Skills" could contain fluency with data tools, etc. "Benefits" could contain THE REWARD benefits. "Pay" could contain salary range. "Schedule" could contain full-time, on-site location. We must not create sections with filler. So we need to ensure each section has real content. Let's extract content. First, mission and purpose etc: This is company background, not directly about the role. Might be considered "About the role"? But maybe we can include under "About the role" a brief description of company mission? The instruction says preserve ALL substantive information. So we need to include that info somewhere. Could be under "About the role" as a paragraph describing the company. That seems okay. Now, "About The Job" section: It's a description of why master data matters. That's also about the role. "The Journey" with subheadings: Own the Gate, Own Correctness, Own the Replenishment Signals, Fix the Foundation, Feed the Automations, What Success Looks Like. Those are responsibilities/duties. "Required" then "THE REQUIREMENTS": list of required qualifications. "Preferred": list of preferred qualifications. "This is a full-time, on-site position based in Bloomingdale, IL.": schedule/location. "THE CHALLENGES": maybe part of responsibilities or notes. "THE REWARD": salary and benefits. "OUR CORE VALUES": maybe skills or attributes. "For Those Who Want More Than Just a Job": maybe mission again. "Our Commitment to You": maybe benefits. We need to avoid duplication. Let's structure:

  About the role

  ... company mission and purpose, Korpack's promise, culture, and overview of the role (why master data matters).

  Responsibilities

  • Own the Gate: sole authority for item and record creation in Acumatica (items, BOMs, routings, customers, vendors, units of measure); ensure nothing enters incomplete.
  • Own Correctness: understand downstream impact of each field (UoM conversions, item attributes, BOM accuracy); ensure fields are right, not just filled.
  • Own the Replenishment Signals: manage MRP and replenishment settings (lead times, safety stock, reorder points, min/max, vendor parameters) based on real demand and vendor performance.
  • Fix the Foundation: lead systematic data cleanup audit, prioritize by downstream damage, correct, and lock the gate.
  • Feed the Automations: partner with Business Analyst and Director of IS on data model for BI, customer feeds, automation; leverage AI and automate validation checks.
  • What Success Looks Like: ensure lines never stop for missing product; distribution customers get right product on time; automations stop breaking on data; new items launch-ready; trustworthy audit trail; shift company mindset from "is the data right?" to "what does the data say?".

  Requirements

  • 2+ years owning master data in a manufacturing ERP environment (items, BOMs, routings, UoM structures, replenishment parameters); Acumatica experience a plus.
  • Demonstrated understanding of downstream data dependency: able to cite a specific instance where bad master data caused a real breakdown, its cost, and how you fixed the system, not just the record.
  • MRP and replenishment parameter fluency: lead times, safety stock, reorder points, min/max; judgment to set them from real demand and vendor performance, not system defaults.
  • Gatekeeper temperament: process-driven, detail-obsessed, comfortable saying 'not yet' to people in a hurry.
  • Fluency with data tools (Excel at a power level; SQL a plus) and comfort with AI tools and automation.

  Qualifications

  • Preferred: Food, beverage, or CPG manufacturing experience.
  • Preferred: Catch-weight or weight-to-quantity conversion experience.
  • Preferred: Data governance or MDM program exposure.

  Skills

  • Strong process orientation and detail obsession.
  • Ability to explain data dependencies to stakeholders.
  • Proficiency in Excel (power user) and optionally SQL.
  • Comfort with AI tools and automation.
  • Alignment with core values: Determined, Innovative, Smile, Responsive, Understanding, Proactive, Teamwork (DISRUPT).

  Benefits

  • Comprehensive health, dental, vision, life, and LTD benefits.
  • 401(k) with company match.
  • Generous PTO.

  Pay

  $100,000–$115,000 salary.

  Schedule

  Full-time, on-site position based in Bloomingdale, IL.

  We need to ensure we didn't miss any substantive info: The mission and purpose, Korpack's Promise, Culture, etc. We included them in About the role paragraph. Let's craft that paragraph. About the role paragraph: Should include mission: "Our mission is clear: to be North America’s premier packaging solutions provider, simplifying client operations with innovative, technology-driven solutions. We are fueled by the values instilled by Nick Novy, aiming to not just meet but exceed industry benchmarks. Our purpose is to empower our customers with smarter business decisions through our expertise. Korpack’s Promise: FAST and Beyond – Fearless, Adaptable, Simplistic, and Technology-driven. Culture: agility, innovation, relentless pursuit of excellence; start‑up spirit combined with industry experience; close‑knit family team dedicated to client success via trust, integrity, mutual respect." Then mention the role: "This is not a data entry job. At Korpack, every automation runs off master data; incorrect data stops lines or ships wrong product. We are building a technology‑driven company that relies on correct master data. The Master Data Specialist will be the gatekeeper with sole authority to create items and records in Acumatica, understanding why each field matters, and ensuring data correctness to support MRP, replenishment, labeling, costing, and customer feeds." We need to ensure we don't repeat the job title as heading. We are not using job title heading. We must not include boilerplate like EEO, etc. Not present. We must not include duplicated lines. We'll avoid duplication. Now check each section for filler: All have real content. Check Benefits: we listed health, dental, vision, life, LTD; 401(k) match; generous PTO. That's from THE REWARD. Check Pay: salary range. Check Schedule: full-time on-site Bloomingdale, IL. Check Skills: we included core values etc. Might be okay. Check Qualifications: we listed preferred qualifications. Could also include "Preferred" as qualifications. Check Requirements: we listed required. Now ensure we didn't miss any required details: The "Required" section also had "THE REQUIREMENTS" heading with bullet points we captured. Also "Required" had a paragraph before THE REQUIREMENTS: "Required THE REQUIREMENTS". Actually the posting shows: Required THE REQUIREMENTS 2+ years owning master data in a manufacturing ERP environment — items, BOMs, routings, UoM structures, replenishment parameters (Acumatica a plus; we run it) Demonstrated understanding of downstream data dependency — you can walk us through a specific time bad master data broke something real, what it cost, and how you fixed the system, not just the record MRP and replenishment parameter fluency — lead times, safety stock, reorder points, min/max — and the judgment to set them from real demand and vendor performance, not system defaults The gatekeeper temperament: process-driven, detail-obsessed, and comfortable saying 'not yet' to people in a hurry Fluency with data tools (Excel at a power level; SQL a plus) and comfort with AI tools and automation We captured those. Preferred: "Preferred Food, beverage, or CPG manufacturing; catch-weight or weight-to-quantity conversion experience; data governance or MDM program exposure". We captured. Now "THE CHALLENGES" and "THE REWARD" and "OUR CORE VALUES" and "For Those Who Want More Than Just a Job" and "Our Commitment to You". Some of that content may be duplicate or not needed. Let's see if any substantive info not covered: THE CHALLENGES: describes pressure, cleanup, sole accountability. This is somewhat covered in responsibilities (Own the Gate, Fix the Foundation) and maybe we could add a responsibility about challenges. But we already