Jobs · Management · Wisconsin

Environmental Health & Safety ( EHS) Specialist

Pregis · Sussex, WI · 1 wk ago
ManagementFull-time
The user wants me to reformat a job posting into clean, well-structured semantic HTML. Let me analyze the content and apply the rules. Rules: - 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) - 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 - 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") - 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 Now, let's parse the job posting: 1. Company intro: "We're Not Just in the Packaging Business–We're in the 'Wow' Business Pregis is Hiring! Why Join Pregis? ..." This is company marketing. Could be an "About the Company" or "Why Join Us" section. But the rules say to use headings like "About the role", "Responsibilities", etc. There's no "About the role" heading in the posting, but there is a "Position Summary". I'll use "Position Summary" as a heading. 2. Job metadata: Location, Travel, Pay. Location: Sussex, WI (Supports Sussex and Elkhorn, WI Facilities). Travel: Up to 25% Local and Regional Travel. Pay: Competitive pay based on experience. These are metadata. The rules say not to put Job ID/requisition numbers as headings, but location, travel, pay are not headings. They can be folded into a short

    or dropped. Since they are substantive, I'll include them in a "Job Details" or "Overview" paragraph. But the rules say to use

    for section headings like "Pay", "Schedule". However, the pay is mentioned as "Competitive pay based on experience". That's not specific. The rules say never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting states "Pay: Competitive pay based on experience". That's a statement, but it's vague. The rules say "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". "Competitive pay based on experience" is similar to "commensurate with experience". So I should not create a Pay section. Similarly, Travel is mentioned, but not a schedule. Benefits are listed later under "Why Join Pregis?" with a list: Competitive Pay, Comprehensive Benefits Package, Career Growth..., etc. That's a benefits list. The rules say to include a section only when the posting has real, specific content. The benefits list is specific. So I can create a "Benefits" section. 3. Required Qualifications: list of bullet points. That's a "Requirements" or "Qualifications" section. 4. Preferred Qualifications: list. Could be part of Qualifications or separate "Preferred Qualifications". I'll include as a subsection or separate list. 5. Position Summary: prose. 6. Key Responsibilities: list of duties. That's "Responsibilities". 7. Physical Requirements: list. That's "Physical Requirements". 8. Why Join Pregis? (second occurrence): list of benefits. That's "Benefits". 9. Diversity and Inclusion, EEO statement: boilerplate, remove. 10. Visit us at www.pregis.com: application instruction, remove. Also, there is a "#AMB1" maybe a job code, drop. Now, structure: - Maybe start with a brief intro paragraph about the company? The posting has "Why Join Pregis?" at the top. That's marketing. Could be a "Company Overview" or "About Pregis". But the rules say to use headings like "About the role". However, the posting doesn't have an "About the role" section. It has "Position Summary". I'll use "Position Summary" as a heading. - Job details: location, travel. Could be a "Job Details" paragraph. - Required Qualifications: heading "Requirements" or "Qualifications". Use

    Qualifications

    then list required and preferred. - Position Summary: heading "Position Summary". - Key Responsibilities: heading "Responsibilities". - Physical Requirements: heading "Physical Requirements". - Benefits: heading "Benefits". - Remove EEO, diversity, etc. Now, ensure no duplicate headings. The posting has two "Why Join Pregis?" sections. The first is company intro, the second is benefits list. I'll combine the benefits list into a Benefits section. Also, the first "Why Join Pregis?" includes a paragraph about company mission. That could be a "Company Overview" paragraph. But the rules say to prefer a few substantive sections over many thin ones. I could include a brief "About Pregis" paragraph before the position summary. But the rules: "Do NOT repeat the job title as a heading (the page already shows it)". The job title is "Environmental Health & Safety Specialist". Not in the HTML. Now, write HTML. I'll create:

    Position Summary

    ...

    Job Details

    Location: Sussex, WI (supports Sussex and Elkhorn, WI facilities). Travel: Up to 25% local and regional travel.

    Qualifications

    Required

    • ...

    Preferred

    • ...
    But the rules say use

    for section headings. Should I use

    for subsections? The rules didn't forbid

    , but they said use

    for section headings. I think using

    for main sections and maybe

    for sub-sections is okay. However, to keep it simple, I could make "Required Qualifications" and "Preferred Qualifications" as separate

    headings. But that might be too many thin sections. The rules: "Prefer a few substantive sections over many thin ones." So I'll combine under one "Qualifications" heading with two lists labeled. But the HTML should be semantic. I'll use

    Qualifications

    then a paragraph "Required Qualifications:" then
      , then "Preferred Qualifications:" then
        . Or use

        for each. I think using

        is fine. Similarly, "Key Responsibilities" ->

        Responsibilities

        . "Physical Requirements" ->

        Physical Requirements

        . "Why Join Pregis?" benefits ->

        Benefits

        . Now, the company intro: "We're Not Just in the Packaging Business–We're in the 'Wow' Business ... Pregis is in the packaging business to protect what matters..." This is company description. Could be a

        About Pregis

        but the rules didn't list that as a standard heading. However, they said "e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". "About the role" is similar to "Position Summary". The company intro is not about the role. I could include it as a preamble paragraph before sections. But the output should be HTML fragment. I'll include a

        at the top with the company mission. But the rules: "Output ONLY the HTML fragment". So I can start with a

        then sections. Let's draft. First, company intro paragraph:

        Pregis is in the packaging business to protect what matters. We are committed to providing our customers and employees sustainable growth through purpose-driven innovation and customer-centric packaging solutions. We thrive across various high-growth industries and are innovative, customer-focused, high-integrity, and believe in strong teamwork and collaboration.

        Then Job Details:

        Job Details

        Location: Sussex, WI (supports Sussex and Elkhorn, WI facilities). Travel: Up to 25% local and regional travel.

        Then Position Summary:

        Position Summary

        We are seeking an experienced Environmental Health & Safety Specialist to lead safety, health, and environmental programs supporting our Sussex and Elkhorn facilities. This role is responsible for driving a Safety-First culture, ensuring regulatory compliance, reducing workplace risk, supporting employee well-being, and partnering with site leadership to continuously improve EHS performance.

        Then Qualifications:

        Qualifications

        Required

        • Minimum 3 years of Environmental, Health & Safety (EHS) experience in a manufacturing or industrial environment
        • Strong knowledge of OSHA, EPA, NFPA, PSM, and RMP regulations
        • Experience developing, implementing, and managing EHS programs and compliance initiatives
        • Strong written and verbal communication skills with the ability to influence at all levels of the organization
        • Proficiency in Microsoft Office Suite (Word, Excel, Outlook, PowerPoint)
        • Ability to maintain confidentiality regarding employee matters, investigations, and company processes
        • Self-motivated with the ability to work independently and manage multiple priorities
        • Ability to travel locally and regionally as needed

        Preferred

        • Bachelor's degree in Occupational Health & Safety, Environmental Science, Industrial Hygiene, or a related field
        • Experience managing workers' compensation programs and safety compliance systems
        • Experience leading safety audits, risk assessments, and incident investigations
        • Manufacturing industry experience preferred
        Then Responsibilities:

        Responsibilities

        • Promote a Safety-First culture through employee engagement, accountability, and continuous safety improvement initiatives
        • Partner with site leadership, managers, and supervisors to support safety programs and ensure compliance across operations
        • Develop, implement, and maintain EHS programs, policies, procedures, and training programs
        • Lead new employee safety orientation and onboarding activities
        • Conduct and maintain Job Safety Analyses (JSAs) and Job Hazard Analyses (JHAs)
        • Manage workers’ compensation claims and safety compliance programs
        • Lead incident reporting, investigations, root cause analysis, and corrective action implementation
        • Maintain EHS records, logs, permits, and regulatory documentation
        • Manage hazardous waste handling, storage, disposal, and regulatory reporting requirements
        • Ensure Safety Data Sheets (SDS) are maintained and review new materials for compliance and safety risks
        • Conduct safety audits, inspections, and compliance assessments while driving continuous improvement initiatives
        • Support emergency response activities and provide first aid guidance when necessary
        • Utilize safety metrics and audit findings to identify trends and implement preventative measures
        • Collaborate with leadership to monitor EHS performance and support organizational safety goals
        Then Physical Requirements:

        Physical Requirements

        • Frequent walking throughout manufacturing and warehouse environments
        • Ability to stand, bend, reach, and climb stairs

Similar jobs