Environmental Health & Safety Engineering Intern

We need to output HTML fragment with sections: Responsibilities, Who You Are (maybe "Qualifications"? Actually they have "Who You Are" and "For This Role, You Will Need:" and "Preferred Qualifications That Set You Apart:" and "Our Culture & Commitment to You:" and "About Us" etc. We need to use headings

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we must only include sections when posting has real specific content. We need to map content to these headings appropriately. We have responsibilities list: training content development, inspection/audit template review & development, Digital Environmental Compliance Calendar Project, Work Comp Scorecard development, Sustainability/Green Team project partnership. So we can have

Responsibilities

with

• items. We have "Who You Are": description of traits. Could map to "Qualifications"? Actually "Who You Are" is more like personal attributes/skills. Could be "Skills" or "Qualifications". The headings list includes Qualifications, Skills. We need to decide. Probably "Qualifications" for required qualifications (education, experience, etc.) and "Skills" for preferred qualifications and personal traits. However we also have "For This Role, You Will Need:" which lists: pursuing a bachelor’s in engineering, zero years of related experience, ability to work full-time in-person at Twin Cities location, legal authorization to work in US. Those are requirements. So we can put those under

  Requirements

  . Then "Preferred Qualifications That Set You Apart:" includes GPA 3.0+, prior internship experience, strong written and verbal communication skills. Those could go under

  Qualifications

  (preferred) or maybe "Skills". Since they are qualifications, we can put under Qualifications. Then "Our Culture & Commitment to You:" includes description of culture, benefits: flexible time off plans, monthly housing allowance, paid holidays, employee choice hours, paid sick time, paid volunteer time, hands-on experience, professional development, networking opportunities, on-site cafeterias, fitness facilities, employee resource groups, recognition, etc. Also mentions competitive compensation, integrated benefits offerings. Also mentions hourly pay $24-$28, commensurate with year in school and experience. So we have Pay info: hourly pay $24-$28. So we need a Pay section. Also we have benefits: monthly housing allowance, paid holidays, employee choice hours, paid sick time, paid volunteer time, on-site cafeterias, fitness facilities, employee resource groups, recognition, etc. Also mention flexible time off plans. So we can have Benefits section. Schedule: they mention ability to work full-time (40 hours per week) in-person. That's schedule info: full-time 40 hrs/week, in-person. So we can have Schedule section. About the role: maybe we could have a brief summary? The posting didn't have an explicit "About the role" paragraph besides the responsibilities. But we could include a short paragraph summarizing role? The instruction: "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." Also "Prefer a few substantive sections over many thin ones." We need to include sections only when posting has real specific content. We have content for Responsibilities, Requirements, Qualifications (preferred), Benefits, Pay, Schedule. Also maybe "About the role" could be a brief summary from the first sentence? The posting starts: "Job Description In This Role, Your Responsibilities Will Be:" then list. There's no separate "About the role" paragraph besides that. Could we treat the introductory sentence as About the role? It says "Job Description In This Role, Your Responsibilities Will Be:" That's basically heading to responsibilities. Might be okay to not have About the role section if no separate content. But we could include a short paragraph summarizing the role: maybe combine responsibilities? But that would duplicate. Better to omit About the role if no distinct content. We must not include sections with filler like "commensurate with experience" etc. Pay section: we have actual pay range $24-$28, so we can include Pay section with that info. Should we include "commensurate with year in school and experience"? That's descriptive but still specific. It's okay. We must not include boilerplate like EEO, legal, etc. Remove those. We must preserve all substantive information. So we need to include all bullet points from responsibilities, requirements, preferred qualifications, culture/benefits, pay, schedule. We need to format as HTML fragment: use

  for headings,

  • for lists,

    for prose. We must not include markdown code fences. Let's craft:

    Responsibilities

    • Training content development (e.g. Cority training modules, energy-based safety training modules, EHS training templates, etc.)
    • Inspection/audit template review & development (e.g. creation of inspection & audit templates in Cority after reviewing and updating content)
    • Digital Environmental Compliance Calendar Project (e.g. work with Global Sustainability Leader to set up compliance requirements in EHS Management system & assist sites with building their calendars)
    • Work Comp Scorecard development (e.g. work with US Work Comp Program Leader to understand and/or develop a working dynamic scorecard using PowerBI)
    • Sustainability/Green Team project partnership (e.g. join team in waste walk or energy treasure hunt, etc.)

    Requirements

    • Pursuing a bachelor’s in engineering
    • Zero (0) years of related experience
    • Ability to work full-time (40 hours per week) in-person at a Twin Cities Location (Shakopee, Chanhassen, or Eden Prairie, MN)
    • Legal authorization to work in the United States

    Qualifications

    • GPA of 3.0 or above
    • Prior internship experience
    • Strong written and verbal communication skills
    Maybe also include "Who You Are" traits as Skills? Could add a Skills section: but we already used Qualifications for preferred qualifications. The "Who You Are" describes personal attributes: balancing planning with actions, staying aligned with goals, productive, asking questions, defining problem, learning priority, trying different solutions, learning from results, making new connections, building relationships, focusing on creating effective collaborative style. Those are skills/attributes. Could put under

    Skills

    . Since we have a Skills heading available, we should use it for those traits. Then Qualifications could be just the preferred qualifications (GPA, internship, communication). But communication is also a skill. However we can split: Qualifications: GPA, prior internship experience. Skills: strong written and verbal communication skills + the personal attributes list. But we need to avoid duplication. Let's decide: Use Qualifications for GPA and prior internship experience. Use Skills for strong written and verbal communication skills plus the personal attributes list (the "Who You Are" paragraph). That seems reasonable. Thus:

    Skills

    • Strong written and verbal communication skills
    • Balances planning with actions
    • Stays aligned with goals and stays productive
    • Takes time to ask questions and define the problem
    • Makes learning a priority and a goal
    • Tries different solutions for problems and learns from the results
    • Makes new connections and builds relationships in other areas and teams
    • Focuses on creating an effective collaborative style
    Now Benefits section: from "Our Culture & Commitment to You:" we have: flexible time off plans, monthly housing allowance, paid holidays, employee choice hours, paid sick time, paid volunteer time, hands-on experience, professional development, networking opportunities, on-site cafeterias, fitness facilities, employee resource groups, recognition, etc. Also mention "competitive compensation, integrated benefits offerings". We'll list the concrete benefits. Thus:

    Benefits

    • Flexible time off plans
    • Monthly housing allowance
    • Paid holidays
    • Employee choice hours
    • Paid sick time
    • Paid volunteer time
    • Hands-on experience
    • Professional development
    • Networking opportunities
    • On-site cafeterias
    • Fitness facilities
    • Employee resource groups
    • Recognition programs
    Pay section: hourly pay $24-$28, commensurate with year in school and experience. Thus:

    Pay

    The hourly pay for this role is $24–$28, commensurate with the year in school and experience each candidate brings to the role.

    Schedule section: ability to work full-time (40 hours per week) in-person at Twin Cities location. Thus:

    Schedule

    Full‑time, 40 hours per week, in‑person at a Twin Cities location (Shakopee, Chanhassen, or Eden Prairie, MN).

    We might also include a short paragraph about the role under "About the role"? Not needed. Check for any other substantive info: "About Us" section includes description of Emerson, but that's boilerplate about company; might be considered not required? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The "About Us" description of Emerson's mission might be considered boilerplate? It's not strictly legal/EEO, but it's generic company description. Might be considered not substantive to the job. However the instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." The "About Us" is substantive about the company but not about the role. Usually we might keep it? But the instruction says to prefer few substantive sections over many thin ones. The "About Us" is not a required heading; we could include it as a

    without heading? But we only have headings list; we could add a

    after responsibilities maybe. However the instruction says "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests using those for sections. It says "include a section ONLY when the posting has real, specific content for it". So we could add an "About the company" paragraph without heading? But they'd likely expect only those headings. Safer to omit the generic Emerson description as it's not specific to the role. However we might lose some substantive info about the company's mission, but it's not required for the job. The instruction says preserve ALL substantive information; but maybe they consider that as boilerplate? Not sure. The "About Us" includes details about Emerson being a global leader in automation technology, etc. That's somewhat generic but could be considered substantive. However many job postings include such fluff; the instruction to remove boilerplate might include that. The "About Us" is not legal/EEO but still could be considered boilerplate. I'd lean to omit it to keep to the required sections. Also there is "Work Authorization" and "Equal Opportunity Employer" etc - remove. Also "No calls or agencies please." - remove. Thus final HTML fragment includes the sections we made. Check for any missing info: responsibilities list includes "Digital Environmental Compliance Calendar Project (e.g. work with Global Sustainability Leader to set up compliance requirements in EHS Management system & assist sites with building their calendars". Note there is a missing closing parenthesis? We'll