Product Data Steward - GCG Connectivity & Power Solutions - Collegeville, PA

We need to output HTML fragment with sections: About the role (maybe Overview?), Responsibilities (What You’ll Do), Requirements (What You’ll Bring), Benefits (What We Offer). Also maybe include hybrid work arrangement info? That's part of Overview. The instructions: Use

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. Output ONLY the HTML fragment — no /, no markdown code fences. Thus we need to extract sections: - Overview: description of role, hybrid work arrangement, reporting line, etc. Could be "About the role". Use

  About the role

  then paragraphs. - Responsibilities: "What You’ll Do" list of duties. Use

  Responsibilities

  then
  • each bullet. - Requirements: "What You’ll Bring" includes Required Qualifications and Preferred Qualifications. Could combine into Requirements section. Use

    Requirements

    then maybe separate sub-sections? But we can just list required and preferred as bullet points. - Benefits: "What We Offer" list of benefits. Use

    Benefits

    then
    • . We must not include Pay or Schedule sections unless explicitly stated. The posting mentions hybrid work arrangement, first three months primarily in office. That's schedule info but not explicit schedule like full-time/part-time. Should we include Schedule? The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does mention hybrid work arrangement and initial training period. That's schedule-ish but not explicit schedule like "Full-time". Might be considered schedule info. However they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state hybrid work arrangement and initial training period, which is schedule-related. Could we include a Schedule section? The example headings include Schedule. But we need to decide if we should include it. The posting says: "This position offers a hybrid work arrangement following an initial training period. The first three months are expected to be primarily in the office to support systems, product, and process training." That's schedule info. So we could include a Schedule section with that detail. However the instruction says "Prefer a few substantive sections over many thin ones." Might be better to fold schedule info into About the role paragraph. Since they said we can include Schedule only if posting actually states them. It does state hybrid work arrangement, but we could incorporate into About the role. Safer to not create a separate Schedule section to avoid thin section. We'll include schedule info in About the role. Similarly, Benefits: we have details. We'll create Benefits section. We must not include boilerplate like EEO, AI recruiting, etc. Remove those. We must preserve all substantive information. So we need to include all responsibilities bullets, all qualifications, all benefits. Let's extract responsibilities bullets from "What You’ll Do". They are sentences each starting with a verb. We'll convert each to
    • . List: - Maintain accurate and complete product master data across ERP, CRM, and related business systems, including part numbers, product categories, item descriptions, cross-references, approved vendors, units of measure, and other product attributes. - Create and maintain new product and part-number records, ensuring required information has been collected, reviewed, and accurately entered before products are made available for use across the business. - Review product information for accuracy and consistency, identify incomplete or incorrect records, and make appropriate corrections to improve overall data quality. - Perform regular data quality checks and audits to identify duplicate, outdated, inconsistent, or inaccurate information and trace data abnormalities back to their source. - Take ownership of day-to-day product data requests while helping ensure product information is categorized and structured correctly to make it easier for Sales and other teams to access reliable information. - Partner with Product Management to support larger new product introduction (NPI) initiatives, helping coordinate the collection, validation, setup, and implementation of product information across applicable systems. - Coordinate with cross-functional stakeholders to ensure product data updates are completed accurately, consistently, and on time, including situations where execution requires input or action from multiple teams. - Partner with IT and business teams to define and improve product data structures, attributes, and relationships so information remains consistent across systems and supports reliable reporting and analysis. - Support the implementation and ongoing use of product data governance policies, standards, and procedures designed to improve data integrity across the business. - Help establish consistent approaches to product categorization, naming conventions, attributes, units of measure, and other product-data standards. - Investigate product data issues and work with the appropriate business or technical teams to identify root causes, resolve discrepancies, and prevent recurring problems. - Participate in cross-functional projects to consolidate, clean, standardize, and optimize product master data across the business unit. - Work with Product Management, Marketing, IT, Purchasing, Sales, Finance, Operations, and other teams when product data changes affect multiple systems, processes, or customer-facing information. - Use Excel and other available tools to review large datasets, identify trends or abnormalities, validate information, and support product-data cleanup and reporting activities. - Contribute ideas and recommendations for improving product-data processes, system usability, data quality, and the overall efficiency of product data management. - Perform other duties as assigned. Now Requirements: Required Qualifications bullet list: - 1–2 years of experience working with data quality, master data, product information, data maintenance, or a related discipline. - Strong attention to detail and the ability to identify inconsistencies, errors, and gaps within large sets of product or business data. - Advanced Microsoft Excel skills and the ability to organize, analyze, compare, and validate data efficiently. - Foundational knowledge of SQL and Power BI. - Familiarity with AI-enabled tools and an interest in using technology to improve data management, analysis, or business processes. - Ability to investigate data abnormalities, identify their underlying cause, and work toward an effective resolution. - Ability to maintain accurate information across multiple interconnected business systems. - Strong organizational and prioritization skills, including the ability to balance routine data requests with larger projects and changing business priorities. - Strong written and verbal communication skills with the ability to work effectively with colleagues across technical and non-technical functions. - Ability to work independently, take initiative, develop practical solutions, and follow work through to completion. - Collaborative approach and demonstrated ability to build productive working relationships across multiple departments. - Comfort working in a fast-paced environment where processes, systems, and business needs may continue to evolve. Preferred Qualifications bullet list: - Experience working with product master data, product information management, ERP or CRM data, item setup, product categorization, or similar product-data processes. - Experience in a distribution environment. - Familiarity with the electrical components, wire and cable, connectivity, or related industrial markets. - Experience supporting data governance, data cleansing, new product introductions, or cross-functional data improvement initiatives. We could combine required and preferred under Requirements, maybe separate subheadings? But instruction says use

      for section headings, not subheadings. Could we include two

      sections: Required Qualifications and Preferred Qualifications? They said use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we could have Requirements and Qualifications separate. But we have both required and preferred; we could put required under Requirements and preferred under Qualifications. Or we could combine. The instruction: "Use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have sections for Requirements and Qualifications. Let's do: -

      Requirements

      for Required Qualifications. -

      Qualifications

      for Preferred Qualifications. But they said "Prefer a few substantive sections over many thin ones." Having both Requirements and Qualifications might be okay. However we could also combine into Requirements and note preferred within same list. But to follow the example, we can have Requirements and Qualifications. Now Benefits: list from "What We Offer". Bullets: - Competitive base salary and annual bonus based on company and individual performance - Comprehensive health coverage with multiple plan options (CDHP and PPO) - Company-paid life and disability insurance, 401(k) with company match, and supplemental insurance options - Generous time off including PTO, paid holidays, parental leave, and compassionate care leave - Wellness and support programs including EAP, wellness incentives, and telehealth - Additional benefits such as dental/vision plans, FSAs/HSAs with company contributions, pet insurance, legal services, and identity theft protection - A people-first culture that recognizes employees as our most important asset We should not include Pay section separately; benefits includes compensation. Now About the role: we need to capture overview paragraph(s). Let's combine: "GCG is currently seeking a Product Data Steward to join our Connectivity & Power solutions product management team and support efforts to ensure the product information our teams rely on is accurate, consistent, complete, and easy to use across our business systems. In this role, you will be responsible for maintaining and improving product master data across ERP, CRM, and related platforms. You’ll work hands-on with product records—including part numbers, product categories, descriptions, cross-references, approved vendors, units of measure, and other critical attributes—while partnering with Product Management and teams across the organization to resolve data issues and establish stronger standards for how product information is maintained. This is an opportunity for someone who enjoys digging into data, finding inconsistencies, understanding why they occurred, and putting practical solutions in place. You’ll balance day-to-day product setup and maintenance with larger initiatives involving new product introductions, data cleanup, governance, and continuous improvement. The role reports to the Director of Product Management and works closely with Product Management, Sales, IT, Marketing, Purchasing, Finance, Operations, and other business teams. This position offers a hybrid work arrangement following an initial training period. The first three months are expected to be primarily in the office to support systems, product, and process training." We can put that in

      maybe multiple paragraphs but we can keep as one. Now we must remove boilerplate: EEO, AI recruiting, equal opportunity, etc. Also remove "About Allied Wire & Cable (AWC)" and "About GCG" sections? Those are substantive? They describe company background. Might be considered substantive but not required for role. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The company overview might be considered substantive but not essential to role. However they said remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Allied Wire & Cable" and "About GCG" are not boilerplate; they are company description. Might be considered substantive. But we need to decide if we include them. The instruction says "Prefer a few substantive sections over many thin ones." Including company overview could be a section but not requested headings. Could we include as part of About the role? Might be okay to include a brief paragraph about company. However the overview already includes GCG description; the "About Allied Wire & Cable" and "About GCG" are extra.