Human Resource Generalist

We need to output HTML fragment with sections: About the role, Responsibilities (maybe "WHAT YOU’LL DO"), Qualifications (maybe "WHAT YOU’LL NEED"), Benefits (if present), maybe Work Environment (if present). 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. 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. First part: description about company (Cornerstone Building Brands) - that's boilerplate? It's company overview; maybe we can keep as part of About the role? Actually "About the role" is separate. The company description is not part of role; it's generic. The instruction says 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. The company overview may be considered substantive? It's not about the role but maybe we can keep as a short paragraph before sections? The instruction says 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. It doesn't forbid a company overview paragraph. However they said "Prefer a few substantive sections over many thin ones." We could include a

  with company overview before sections. But they said "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have sections for About the role, Responsibilities, Qualifications, Benefits, Work Environment maybe. The "Work Environment" is not in the list but could be considered a section heading? They gave examples but not exhaustive; we can still use

  for any section heading we deem appropriate. However they said "include a section ONLY when the posting has real, specific content for it". Work Environment section exists: they have details about environment. So we can include a Work Environment section. Now we need to extract content. Let's copy the posting and extract relevant parts. Company overview: "Cornerstone Building Brands is a leading manufacturer of exterior building products for residential and low-rise non-residential buildings in North America. Headquartered in Cary, N.C., we serve residential and commercial customers across the new construction and Repair & Remodel (R&R) markets. Our market-leading portfolio of products spans vinyl windows, vinyl siding, stone veneer, metal roofing, metal wall systems and metal accessories. Cornerstone Building Brands’ broad, multi-channel distribution platform and expansive national footprint includes more than 18,800 team members at manufacturing, distribution and office locations throughout North America. Corporate stewardship and Environmental, Social and Governance (ESG) responsibility are embedded in our culture. We are committed to contributing positively to the communities where we live, work and play. For more information, visit us at http://cornerstonebuildingbrands.com." That's substantive; we can keep as a

  before sections. Now "Job Description ABOUT THE ROLE" heading. Content after that: "Provides comprehensive Human Resources support to the Human Resources Manager, Plant Manager, leadership team, and employees. Serves as the primary on-site HR partner for designated facilities, supporting employee relations, talent acquisition, workforce engagement, retention strategies, compliance, HR systems, and people analytics. Utilizes data-driven insights to support business objectives, improve employee experience, and drive organizational effectiveness. This position supports operations across multiple sites and requires regular collaboration with site leadership and employees at multiple locations." That's prose for About the role. Next "WHAT YOU’LL DO" (Responsibilities). Content: bullet-like sentences each starting with a verb. We need to convert to

  • . Let's list them: - Partner with hiring managers and Talent Acquisition to identify workforce needs, develop recruiting strategies, and support initiatives that improve hiring outcomes, retention, and workforce stability. - Facilitate onboarding, orientation, and training activities. - Serve as a trusted HR resource to employees and leaders. - Assist with HR technology platforms including HRIS, payroll, learning management systems, and employee self-service tools. - Maintain attendance, workforce, and employee records while ensuring data integrity. - Develop, maintain, and distribute HR reports, dashboards, and KPIs. - Analyze workforce metrics including turnover, retention, attendance, staffing levels, and engagement trends. - Conduct regular audits of HR systems and employee data. - Support employee engagement initiatives. - Conduct or support employee relations investigations and corrective action processes. - Assist leaders with performance management processes. - Provide employees guidance regarding leave processes. - Ensure compliance with federal, state, and local employment laws. - Participate in continuous improvement initiatives. - Maintain confidentiality and professionalism. - Provide support and oversight for multiple company locations. - Build effective partnerships with leaders and employees across assigned sites. - Travel regularly to designated facilities to support business and workforce needs. - Ensure consistency in processes, compliance, and employee experience across all assigned locations. - Perform other duties as assigned. That's a list. Now "Qualifications" heading (maybe "WHAT YOU’LL NEED"). Content: "Education: Bachelor's degree in Human Resources, Business Administration, Organizational Development, or related field, or equivalent combination of education and experience. Experience: Minimum of three (3) years of progressive Human Resources experience required. Manufacturing experience preferred. Skills: Strong communication, organizational, employee relations, compliance, and analytical skills. Experience with HRIS systems and HR reporting. Technical Requirements: Intermediate Excel skills required including Pivot Tables, XLOOKUP/VLOOKUP, Conditional Formatting, IF Statements, Data Validation, and workforce data analysis. Experience creating HR reports and scorecards. Creating dashboards, Power BI or Tableau experience is preferred. Travel between facilities is required to ensure consistent implementation of company policies, programs, and initiatives. SHRM-CP, SHRM-SCP, PHR, or SPHR preferred." We need to format as maybe sections: Education, Experience, Skills, Technical Requirements, Certifications? But instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could have a Qualifications section with subheadings? But they only said use

    for section headings; we could have multiple

    sections like Education, Experience, Skills, Technical Requirements, Certifications. However they said "Prefer a few substantive sections over many thin ones." So maybe we keep Qualifications as one section with paragraphs and lists. We can break into

    for prose and

    • for lists where appropriate. Education: one sentence ->

      . Experience: one sentence ->

      . Skills: list of skills: "Strong communication, organizational, employee relations, compliance, and analytical skills." Could be a

      • each skill? Might be overkill. Could keep as

        . Technical Requirements: list of Excel skills etc. Could be

        . Travel requirement: sentence. Certifications: SHRM-CP etc. Could be

        or

        . We need to preserve all substantive info. Now "WORK ENVIRONMENT" section: content: "Primarily based in a manufacturing facility environment with exposure to noise, moving equipment, and varying temperaturesRegular walking of the production floor and interaction with operations teamsWill require use of personal protective equipment (PPE) such as safety glasses, ear protection, and steel-toe bootsTravel may be required for training, audits, or collaboration across sitesCombination of office and production floor work" Note there are missing spaces; we need to parse: "Primarily based in a manufacturing facility environment with exposure to noise, moving equipment, and varying temperaturesRegular walking of the production floor and interaction with operations teamsWill require use of personal protective equipment (PPE) such as safety glasses, ear protection, and steel-toe bootsTravel may be required for training, audits, or collaboration across sitesCombination of office and production floor work" We should add spaces: after temperatures, there should be a space before "Regular". After teams, space before "Will". After boots, space before "Travel". After sites, space before "Combination". We'll reconstruct. Thus we can make a

        with those sentences. Now "Additional Information" includes Address: "2405 Campbell Rd. Sidney, OH 45365". That's minor metadata; we can fold into a short

        maybe after sections or drop? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

        or drop it." Address is minor metadata; we can include a short

        maybe after sections. Then "Why work for Cornerstone Building Brands?" repeated twice with benefits. That's benefits section. We need to extract benefits: "Full-time* team members receive** medical, dental and vision benefits starting day 1. Other benefits include PTO, paid holidays, FSA, life insurance, LTD, STD, 401k, EAP, discount programs, tuition reimbursement, training, and professional development. *Full-time is defined as regularly working 30+ hours per week. **Union programs may vary depending on the collective bargaining agreement" We should create a Benefits section with

        Benefits

        and then a

        or

        • for list of benefits. We need to avoid duplication; the text appears twice; we only include once. Now we need to remove EEO boilerplate, scam warnings, etc. So we will omit all that after "Additional Information" etc. Now we need to ensure we don't create Pay or Schedule sections because not present. Now produce HTML fragment. Structure:

          Company overview...

          About the role

          ...

          Responsibilities

          • ...
          ...

          Qualifications

          Education: Bachelor's degree in Human Resources, Business Administration, Organizational Development, or related field, or equivalent combination of education and experience.

          Experience: Minimum of three (3) years of progressive Human Resources experience required. Manufacturing experience preferred.

          Skills: Strong communication, organizational, employee relations, compliance, and analytical skills. Experience with HRIS systems and HR reporting.

          Technical Requirements

          ? Actually we should not use

          unless we want subheading; but we can keep as

          with list. Maybe we can do

          Technical Requirements

          as a subsection? But they said use

          for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They didn't forbid other headings but we should stick to those. However we can embed technical requirements as a

          inside Qualifications. Better: Keep Qualifications as a section with

          for Education, Experience, Skills, then a

          for Technical Requirements, then a

          for Travel requirement, then a

          for