Site EHS Manager
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.
We need to decide which sections to include. The posting includes:
- About Heraeus (company description)
- About Heraeus Precious Metals (more detail)
- The EHS Site Manager role description (responsibilities)
- Total Rewards That Support You & Your Family (benefits)
- Grow Your Career & Your Earnings (career development)
- Why Heraeus? (company culture)
- Application instructions (apply now, reference code, email, etc.) which we need to remove as per instruction: remove application instructions.
We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have content that fits:
- About the role: could be a brief description of the role (the EHS Site Manager serves as senior site authority...). That is substantive.
- Responsibilities: we have bullet-like sentences describing responsibilities: developing and executing site-wide EHS strategy, ensuring compliance, protecting employees and assets, enabling operational excellence, serving as primary advisor, exercising independent judgment, etc. Could be list.
- Requirements/Qualifications/Skills: Not explicitly listed; the posting does not give specific qualifications or requirements. It says "even if you don't meet all the requirements, but have good reasons why you are still the right fit". No explicit list. So we should not create those sections if no specific content.
- Benefits: we have "Total Rewards That Support You & Your Family" with list: Medical, Dental & Vision coverage; Flexible Spending Accounts (FSA) and Health Savings Accounts (HSA); Employee Assistance Program (EAP); Paid Family Leave benefits; 401(k) with a 5% company match (fully vested at hire); Company-paid life and disability insurance. That's benefits.
- Pay: Not specified. No salary info. So we should not create Pay section.
- Schedule: Not specified. No schedule info. So we should not create Schedule.
- Also we have "Grow Your Career & Your Earnings" which could be considered as "Career Development" but not in allowed headings. Could we map to "Skills"? Not really. Could we treat as "Qualifications"? Not exactly. The instruction says prefer a few substantive sections over many thin ones. We could include a section like "Career Development" but not allowed headings. The allowed headings list is examples; maybe we can use other headings if they match content? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we could use other headings if appropriate? However they say "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't restrict to only those headings, but they gave examples. Safer to stick to those headings. So we can have About the role, Responsibilities, Benefits. Possibly also "Why Heraeus?" could be considered as "About the company" but not in list. Could we incorporate that into About the role? Might be redundant. But we could include a section "About Heraeus" as a heading? Not in examples but maybe allowed. However instruction says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are typical but not exhaustive. However to be safe, we could create sections for About the role, Responsibilities, Benefits, and maybe "Career Development" if we treat as Skills? Not exactly.
Better to include About the role (company + role overview), Responsibilities (duties), Benefits (total rewards). Possibly also "Why Heraeus?" as a separate section but we could incorporate into About the role or Benefits? It's more about culture. Could be a section "Why Heraeus?" but not in examples. Might be okay but risk.
Given instruction to prefer few substantive sections over many thin ones, we could combine "Why Heraeus?" and "Grow Your Career & Your Earnings" into a section like "Career & Culture" but not in examples. Might be better to just include About the role, Responsibilities, Benefits. That covers substantive info.
We need to preserve all substantive information. If we omit "Grow Your Career & Your Earnings" and "Why Heraeus?" we lose some info. But maybe we can incorporate that info into About the role or Benefits? The "Grow Your Career & Your Earnings" includes: Paid training and tuition reimbursement, Clear pathways for career advancement, Opportunities to increase earnings as you build skills, certifications, and experience, Build a long-term career in a stable, growing industry focused on sustainability and the circular economy, Work with advanced precious metals refining and recycling technologies that support industries around the world. That's substantive. Could be placed under a section "Skills" or "Qualifications"? Not exactly. Could be under "Benefits"? It's more career development. Could be under "Responsibilities"? No.
We could create a section "Skills" and list those as items? But they are not skills; they are career development opportunities. However the heading "Skills" could be used for list of skills/abilities required or offered. The posting does not list required skills. But we could list offered skills development as part of "Skills"? Might be a stretch.
Alternatively, we could create a section "Qualifications" and list the career development opportunities? Not appropriate.
Given the instruction to not create sections with filler, but we have real content for career development. So we should include a section for it. Since the allowed headings are examples, we can use a heading like "Career Development". The instruction didn't forbid other headings; it just gave examples. So we can use Career Development
and list items.
Similarly, "Why Heraeus?" could be a section "Company Culture" or "Why Join Heraeus?" but we could incorporate into About the role? Might be okay to have a section "Why Heraeus?" as heading.
But to keep few sections, we could merge "Why Heraeus?" and "Grow Your Career & Your Earnings" into a section "Why Join Heraeus?" with bullet points covering both culture and career growth. That would be substantive.
Thus sections:
- About the role (company overview + role description)
- Responsibilities (list of duties)
- Benefits (total rewards)
- Why Join Heraeus? (career development + culture)
We need to avoid repeating job title as heading. Not using Job ID.
We need to remove application instructions: "Curious? Apply now! We look forward to receiving your documents by reference code 60044 via our online application portal - even if you don't meet all the requirements, but have good reasons why you are still the right fit for this role! Any further questions? Our Recruiting Team, Heraeus Precious Metals, is happy to assist you by email: [[cust_RecTeam]]. Or visit us at jobs.heraeus.com. ReqID: 60044" Remove all that.
Also remove duplicated lines? Not seeing duplicates.
Now craft HTML.
We'll start with About the role
then
containing company description and role overview.
Company description: "Permanent About Heraeus Making displays foldable? Helping hearts beat with medical innovations? Or breathing new life into precious metals? As a family-owned global technology group we help our customers to always being one step ahead. About Heraeus Precious Metals With more than 350 years of experience in precious metal processing, Heraeus Precious Metals is one of the world’s leading provider of innovative products and services, such as precious metal trading and recycling. Our products are used in a wide range of industries, for example to reduce climate-damaging gases such as nitrous oxide and methane, or in the form of active pharmaceutical ingredients for the treatment of cancer. The driving force behind our innovation is our workforce with about 2,500 employees at 11 locations worldwide, who work passionately alongside our partners to develop groundbreaking and sustainable solutions. Our vision: We create innovative precious metal products and services – leading the way to a sustainable future. To this end, we have set ambitious goals."
That's a bit messy due to the initial "Permanent About Heraeus Making displays foldable? Helping hearts beat with medical innovations? Or breathing new life into precious metals?" That seems like a garbled intro maybe from some other content. But we must preserve all substantive information. That line seems like a fragment maybe from a different posting. It's part of the posting; we should keep it. It says: "Permanent About Heraeus Making displays foldable? Helping hearts beat with medical innovations? Or breathing new life into precious metals? As a family-owned global technology group we help our customers to always being one step ahead." That's weird but we keep.
Then "About Heraeus Precious Metals With more than 350 years of experience..." etc.
Then role description: "The EHS Site Manager serves as the senior site authority for Environmental, Health, Safety, Process Safety, Regulatory Compliance, Sustainability, Emergency Preparedness, and Operational Risk Management. The position is responsible for developing and executing site-wide EHS strategy, ensuring compliance with all applicable federal, state, local, and corporate requirements, protecting employees and company assets, and enabling operational excellence through proactive risk management and continuous improvement initiatives. The role serves as the primary advisor to site leadership and exercises significant independent judgment in matters affecting regulatory compliance, business continuity, environmental stewardship, workforce safety, and organizational risk."
We'll combine into a paragraph.
Next section: Responsibilities. We can list bullet points from the responsibilities sentences. Let's extract:
- Developing and executing site-wide EHS strategy
- Ensuring compliance with all applicable federal, state, local, and corporate requirements
- Protecting employees and company assets
- Enabling operational excellence through proactive risk management and continuous improvement initiatives
- Serving as the primary advisor to site leadership
- Exercising significant independent judgment in matters affecting regulatory compliance, business continuity, environmental stewardship, workforce safety, and organizational risk
We'll put each as
- .
Next section: Benefits. List from Total Rewards:
- Medical, Dental & Vision coverage
- Flexible Spending Accounts (FSA) and Health Savings Accounts (HSA)
- Employee Assistance Program (EAP)
- Paid Family Leave benefits
- 401(k) with a 5% company match (
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 decide which sections to include. The posting includes: - About Heraeus (company description) - About Heraeus Precious Metals (more detail) - The EHS Site Manager role description (responsibilities) - Total Rewards That Support You & Your Family (benefits) - Grow Your Career & Your Earnings (career development) - Why Heraeus? (company culture) - Application instructions (apply now, reference code, email, etc.) which we need to remove as per instruction: remove application instructions. We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content that fits: - About the role: could be a brief description of the role (the EHS Site Manager serves as senior site authority...). That is substantive. - Responsibilities: we have bullet-like sentences describing responsibilities: developing and executing site-wide EHS strategy, ensuring compliance, protecting employees and assets, enabling operational excellence, serving as primary advisor, exercising independent judgment, etc. Could be list. - Requirements/Qualifications/Skills: Not explicitly listed; the posting does not give specific qualifications or requirements. It says "even if you don't meet all the requirements, but have good reasons why you are still the right fit". No explicit list. So we should not create those sections if no specific content. - Benefits: we have "Total Rewards That Support You & Your Family" with list: Medical, Dental & Vision coverage; Flexible Spending Accounts (FSA) and Health Savings Accounts (HSA); Employee Assistance Program (EAP); Paid Family Leave benefits; 401(k) with a 5% company match (fully vested at hire); Company-paid life and disability insurance. That's benefits. - Pay: Not specified. No salary info. So we should not create Pay section. - Schedule: Not specified. No schedule info. So we should not create Schedule. - Also we have "Grow Your Career & Your Earnings" which could be considered as "Career Development" but not in allowed headings. Could we map to "Skills"? Not really. Could we treat as "Qualifications"? Not exactly. The instruction says prefer a few substantive sections over many thin ones. We could include a section like "Career Development" but not allowed headings. The allowed headings list is examples; maybe we can use other headings if they match content? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we could use other headings if appropriate? However they say "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't restrict to only those headings, but they gave examples. Safer to stick to those headings. So we can have About the role, Responsibilities, Benefits. Possibly also "Why Heraeus?" could be considered as "About the company" but not in list. Could we incorporate that into About the role? Might be redundant. But we could include a section "About Heraeus" as a heading? Not in examples but maybe allowed. However instruction says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are typical but not exhaustive. However to be safe, we could create sections for About the role, Responsibilities, Benefits, and maybe "Career Development" if we treat as Skills? Not exactly.
Better to include About the role (company + role overview), Responsibilities (duties), Benefits (total rewards). Possibly also "Why Heraeus?" as a separate section but we could incorporate into About the role or Benefits? It's more about culture. Could be a section "Why Heraeus?" but not in examples. Might be okay but risk.
Given instruction to prefer few substantive sections over many thin ones, we could combine "Why Heraeus?" and "Grow Your Career & Your Earnings" into a section like "Career & Culture" but not in examples. Might be better to just include About the role, Responsibilities, Benefits. That covers substantive info.
We need to preserve all substantive information. If we omit "Grow Your Career & Your Earnings" and "Why Heraeus?" we lose some info. But maybe we can incorporate that info into About the role or Benefits? The "Grow Your Career & Your Earnings" includes: Paid training and tuition reimbursement, Clear pathways for career advancement, Opportunities to increase earnings as you build skills, certifications, and experience, Build a long-term career in a stable, growing industry focused on sustainability and the circular economy, Work with advanced precious metals refining and recycling technologies that support industries around the world. That's substantive. Could be placed under a section "Skills" or "Qualifications"? Not exactly. Could be under "Benefits"? It's more career development. Could be under "Responsibilities"? No.
We could create a section "Skills" and list those as items? But they are not skills; they are career development opportunities. However the heading "Skills" could be used for list of skills/abilities required or offered. The posting does not list required skills. But we could list offered skills development as part of "Skills"? Might be a stretch.
Alternatively, we could create a section "Qualifications" and list the career development opportunities? Not appropriate.
Given the instruction to not create sections with filler, but we have real content for career development. So we should include a section for it. Since the allowed headings are examples, we can use a heading like "Career Development". The instruction didn't forbid other headings; it just gave examples. So we can use Career Development
and list items.
Similarly, "Why Heraeus?" could be a section "Company Culture" or "Why Join Heraeus?" but we could incorporate into About the role? Might be okay to have a section "Why Heraeus?" as heading.
But to keep few sections, we could merge "Why Heraeus?" and "Grow Your Career & Your Earnings" into a section "Why Join Heraeus?" with bullet points covering both culture and career growth. That would be substantive.
Thus sections:
- About the role (company overview + role description)
- Responsibilities (list of duties)
- Benefits (total rewards)
- Why Join Heraeus? (career development + culture)
We need to avoid repeating job title as heading. Not using Job ID.
We need to remove application instructions: "Curious? Apply now! We look forward to receiving your documents by reference code 60044 via our online application portal - even if you don't meet all the requirements, but have good reasons why you are still the right fit for this role! Any further questions? Our Recruiting Team, Heraeus Precious Metals, is happy to assist you by email: [[cust_RecTeam]]. Or visit us at jobs.heraeus.com. ReqID: 60044" Remove all that.
Also remove duplicated lines? Not seeing duplicates.
Now craft HTML.
We'll start with About the role
then
Career Development
and list items. Similarly, "Why Heraeus?" could be a section "Company Culture" or "Why Join Heraeus?" but we could incorporate into About the role? Might be okay to have a section "Why Heraeus?" as heading. But to keep few sections, we could merge "Why Heraeus?" and "Grow Your Career & Your Earnings" into a section "Why Join Heraeus?" with bullet points covering both culture and career growth. That would be substantive. Thus sections: - About the role (company overview + role description) - Responsibilities (list of duties) - Benefits (total rewards) - Why Join Heraeus? (career development + culture) We need to avoid repeating job title as heading. Not using Job ID. We need to remove application instructions: "Curious? Apply now! We look forward to receiving your documents by reference code 60044 via our online application portal - even if you don't meet all the requirements, but have good reasons why you are still the right fit for this role! Any further questions? Our Recruiting Team, Heraeus Precious Metals, is happy to assist you by email: [[cust_RecTeam]]. Or visit us at jobs.heraeus.com. ReqID: 60044" Remove all that. Also remove duplicated lines? Not seeing duplicates. Now craft HTML. We'll start withAbout the role
thencontaining company description and role overview. Company description: "Permanent About Heraeus Making displays foldable? Helping hearts beat with medical innovations? Or breathing new life into precious metals? As a family-owned global technology group we help our customers to always being one step ahead. About Heraeus Precious Metals With more than 350 years of experience in precious metal processing, Heraeus Precious Metals is one of the world’s leading provider of innovative products and services, such as precious metal trading and recycling. Our products are used in a wide range of industries, for example to reduce climate-damaging gases such as nitrous oxide and methane, or in the form of active pharmaceutical ingredients for the treatment of cancer. The driving force behind our innovation is our workforce with about 2,500 employees at 11 locations worldwide, who work passionately alongside our partners to develop groundbreaking and sustainable solutions. Our vision: We create innovative precious metal products and services – leading the way to a sustainable future. To this end, we have set ambitious goals." That's a bit messy due to the initial "Permanent About Heraeus Making displays foldable? Helping hearts beat with medical innovations? Or breathing new life into precious metals?" That seems like a garbled intro maybe from some other content. But we must preserve all substantive information. That line seems like a fragment maybe from a different posting. It's part of the posting; we should keep it. It says: "Permanent About Heraeus Making displays foldable? Helping hearts beat with medical innovations? Or breathing new life into precious metals? As a family-owned global technology group we help our customers to always being one step ahead." That's weird but we keep. Then "About Heraeus Precious Metals With more than 350 years of experience..." etc. Then role description: "The EHS Site Manager serves as the senior site authority for Environmental, Health, Safety, Process Safety, Regulatory Compliance, Sustainability, Emergency Preparedness, and Operational Risk Management. The position is responsible for developing and executing site-wide EHS strategy, ensuring compliance with all applicable federal, state, local, and corporate requirements, protecting employees and company assets, and enabling operational excellence through proactive risk management and continuous improvement initiatives. The role serves as the primary advisor to site leadership and exercises significant independent judgment in matters affecting regulatory compliance, business continuity, environmental stewardship, workforce safety, and organizational risk." We'll combine into a paragraph. Next section: Responsibilities. We can list bullet points from the responsibilities sentences. Let's extract: - Developing and executing site-wide EHS strategy - Ensuring compliance with all applicable federal, state, local, and corporate requirements - Protecting employees and company assets - Enabling operational excellence through proactive risk management and continuous improvement initiatives - Serving as the primary advisor to site leadership - Exercising significant independent judgment in matters affecting regulatory compliance, business continuity, environmental stewardship, workforce safety, and organizational risk We'll put each as