EH&S Manager
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use - for lists
- Use
for prose
- Do NOT repeat job title as heading (page already shows it)
- Do NOT put Job ID/requisition numbers as headings
- Preserve ALL substantive information
- Remove boilerplate (EEO, equal opportunity, scam warning, application instructions, cookie/navigation/legal)
- Include section ONLY when real specific content exists
- Never emit heading followed by filler/placeholder text
- Never create Pay/Schedule/Benefits sections unless posting actually states them
- Output ONLY HTML fragment, no html/body, no markdown fences
Let me structure:
1. About the role / About the company? The posting has "About Phoenix Tailings", "Why Phoenix Tailings", "Our Values", "Who We Are Looking For". These are company background and role context. I could combine into an "About the role" or "About the company" section. But the rule says "About the role" as heading example. Since the job title is not to be repeated, I'll create an "About the role" section with the descriptive paragraphs.
2. Responsibilities - "Key Responsibilities" list
3. Qualifications - "Qualifications" list
4. Benefits - "What We Offer" includes pay range, healthcare, stock options, time off, learning. This is a Benefits section. Pay is part of it. Should I separate Pay? The rule says "Pay" as possible heading. But the posting includes pay range in What We Offer. I could make a "Benefits" section with all, or separate Pay and Benefits. The rule says "include a section ONLY when the posting has real, specific content for it". The posting has specific pay range, healthcare, stock options, time off, learning. So I'll create a "Benefits" section that includes all. Or maybe "Compensation and Benefits". The example headings include "Pay" and "Benefits" separately. But the posting groups them. I'll do a "Benefits" section with sub-items. Since the rule says use
- for lists, I'll list each benefit.
5. Schedule - not mentioned, so omit.
6. Remove EEO statement, AI hiring note, "Please note" paragraph about future opportunities, etc.
Now, let's write HTML.
First, "About the role" section: combine "About Phoenix Tailings", "Why Phoenix Tailings", "Our Values", "Who We Are Looking For" into prose paragraphs. But "Our Values" is a list of values. Could be a list. However, the rule says use
- for any list of duties/requirements/benefits. Values are not duties/requirements/benefits, but they are a list. I'll include as a list under a subheading? But we only have h3 headings. Could include values as a list within the About section. I'll do a paragraph for each major block, and for values, a list.
But the rule: "Use
- for any list of duties/requirements/benefits". It doesn't forbid using for other lists. But to be safe, I'll keep values as a list.
Let's structure:
About the role
About Phoenix Tailings... (first paragraph)
Rare earths are essential... (second paragraph)
The Freedom Facility will be designed... (third paragraph)
Why Phoenix Tailings
? But the rule says use h3 for section headings like "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". It doesn't say we must use exactly those, but those are examples. The user said "e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". So we can use other headings if needed. But we should prefer those. However, "Why Phoenix Tailings" is company pitch. Could be part of About the role. I'll merge.
Better: Use "About the company" or "About the role". Since the role is EHS Manager, the "Who We Are Looking For" describes the role. I'll create an "About the role" section with the company context and role summary.
Let's write:
About the role
Phoenix Tailings is a rapidly growing clean mining and metals production startup focused on building a domestic supply of critical materials. Our Freedom Facility in Rochester, New York will be a commercial-scale rare earth separation facility designed to expand U.S. capacity to process and separate rare earth materials.
Rare earths are essential inputs for many of the technologies that power modern life. They are used in high-performance permanent magnets found in electric vehicles, wind turbines, robotics, advanced electronics, aerospace systems, and defense applications. Today, much of the world's rare earth processing and separation capacity is concentrated overseas. Building more of this capability in the United States is important for strengthening domestic supply chains, reducing reliance on foreign processing, and supporting the advanced manufacturing, energy, technology, and national-security industries that depend on these materials.
The Freedom Facility will be designed to produce thousands of tons of separated rare earth oxides annually, making Rochester an important part of Phoenix Tailings' expansion of domestic rare earth processing capacity.
At Phoenix, we believe that nothing great is ever accomplished alone or without the passion of people who push and motivate one another. If you are someone who shares our relentless pursuit of a better future, passion for innovation, and are excited about working with some of the top innovators in the world, then this is the place for you.
Our values
- You are only crazy if you are wrong, it's ok to be wrong - Say what you think even when it’s uncomfortable
- Lead with Compassion - Show up for your teammates, make the people around you better.
- Be Resourceful - Find a way with what you have, don't wait for more.
- Listen - Understand before you act, ask good questions before deciding.
- Hustle - Put your heart into every interaction, no matter how small.
As we build toward operations in 2027 and 2028, we are beginning to meet with individuals who may be interested in joining Phoenix Tailings. We encourage interested candidates to apply, learn more about what we are building, and stay connected as we develop our facility. Phoenix Tailings is looking for an experienced environmental health and safety leader interested in a future EHS Manager opportunity at our Rochester Freedom Facility. The EHS Manager will build and lead the site's environmental health and safety systems for chemical processing hazards, fire risk, gases, and permit-controlled work. This person will manage hot-work and safety permits, lead training and inspections, and coordinate incident prevention and response. This is an opportunity to help establish EHS practices at a new facility and prepare its workforce to recognize hazards and carry out work safely.
But the "Our values" heading is not in the example list. However, it's a substantive list. The rule says "include a section ONLY when the posting has real, specific content for it". It does. But the example headings are just examples. I think it's okay to have "Our values" as h3. But the user said "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". This suggests we should use those standard headings. "Our values" might be considered part of "About the role". I'll keep it as a subsection? But we only have h3. Could make it a list within the About section without a heading. But the values are distinct. I'll include as a list under "About the role" without a separate heading, maybe introduce with a sentence.
Let's adjust: In "About the role" section, after the why paragraph, add a sentence "Our values:" then list.
But the rule: "Use - for any list of duties/requirements/benefits". Values are not those, but it's a list. I think it's fine.
Now Responsibilities:
Responsibilities
- Build site safety and environmental programs for construction and operations, establishing the procedures, permits, training, and inspections needed for startup
- Manage contractor safety, hot work, chemical hazards, gases, and fire risk, assessing work conditions and ensuring required safeguards are in place
- Develop practical EHS training and inspection programs, documenting findings and working with site leaders to complete corrective actions
- Prepare environmental compliance, permitting, and reporting processes for operations, integrating EHS requirements into facility readiness and process planning
- Lead incident investigations and prevention efforts and coordinate emergency preparedness and response as the site transitions from construction into production
Qualifications:
Qualifications
- Bachelor's degree in Environmental Health and Safety, Occupational Health, Environmental Engineering, Chemical Engineering, or a related technical field
- Experience managing EHS programs in industrial construction, chemical processing, metals, or manufacturing, including building programs for a growing or new site
- Working knowledge of industrial safety and environmental requirements, chemical and fire hazards, contractor safety, and permit-controlled work
- Demonstrated ability to assess risks, lead training and inspections, investigate incidents, and establish corrective-action and emergency-preparedness processes
Benefits:
Benefits
- Pay range: $118,000–$175,000 per year (total cash compensation including salary + discretionary bonus)
- Healthcare: 100% medical, dental, and vision coverage for employee
- Stock options: Ownership in a fast-growing venture-backed company
- Time off: Unlimited PTO
- Learning: Learning and development opportunities to grow your skills and career
Note: The pay range is included as a benefit item. The rule says never create Pay section unless posting actually states them. The posting states pay range. Could create separate Pay section. But the example includes both Pay and Benefits. However, the posting groups them under "What We Offer". I'll keep as Benefits with pay as one item. That's fine.
Now remove boilerplate: EEO statement, AI hiring note, "Please note" paragraph about future opportunities, "Phoenix Tailings, Inc. is an Equal Opportunity Employer..." etc. Also remove "This pay range reflects best estimate..." but that's part of pay description. I'll keep the pay range but not the "best estimate" sentence? The rule says preserve ALL substantive information. The "best estimate" is part of the pay description. I'll include it in the pay bullet.
Also remove "At Phoenix Tailings, we have an open culture that values learning, and we are looking to grow the team with enthusiastic individuals who share our vision of sustainable mining." That's fluff.
Now output only HTML fragment.
Let's write final
for prose - Do NOT repeat job title as heading (page already shows it) - Do NOT put Job ID/requisition numbers as headings - Preserve ALL substantive information - Remove boilerplate (EEO, equal opportunity, scam warning, application instructions, cookie/navigation/legal) - Include section ONLY when real specific content exists - Never emit heading followed by filler/placeholder text - Never create Pay/Schedule/Benefits sections unless posting actually states them - Output ONLY HTML fragment, no html/body, no markdown fences Let me structure: 1. About the role / About the company? The posting has "About Phoenix Tailings", "Why Phoenix Tailings", "Our Values", "Who We Are Looking For". These are company background and role context. I could combine into an "About the role" or "About the company" section. But the rule says "About the role" as heading example. Since the job title is not to be repeated, I'll create an "About the role" section with the descriptive paragraphs. 2. Responsibilities - "Key Responsibilities" list 3. Qualifications - "Qualifications" list 4. Benefits - "What We Offer" includes pay range, healthcare, stock options, time off, learning. This is a Benefits section. Pay is part of it. Should I separate Pay? The rule says "Pay" as possible heading. But the posting includes pay range in What We Offer. I could make a "Benefits" section with all, or separate Pay and Benefits. The rule says "include a section ONLY when the posting has real, specific content for it". The posting has specific pay range, healthcare, stock options, time off, learning. So I'll create a "Benefits" section that includes all. Or maybe "Compensation and Benefits". The example headings include "Pay" and "Benefits" separately. But the posting groups them. I'll do a "Benefits" section with sub-items. Since the rule says use
- for lists, I'll list each benefit.
5. Schedule - not mentioned, so omit.
6. Remove EEO statement, AI hiring note, "Please note" paragraph about future opportunities, etc.
Now, let's write HTML.
First, "About the role" section: combine "About Phoenix Tailings", "Why Phoenix Tailings", "Our Values", "Who We Are Looking For" into prose paragraphs. But "Our Values" is a list of values. Could be a list. However, the rule says use
- for any list of duties/requirements/benefits. Values are not duties/requirements/benefits, but they are a list. I'll include as a list under a subheading? But we only have h3 headings. Could include values as a list within the About section. I'll do a paragraph for each major block, and for values, a list.
But the rule: "Use
- for any list of duties/requirements/benefits". It doesn't forbid using for other lists. But to be safe, I'll keep values as a list.
Let's structure:
About the role
About Phoenix Tailings... (first paragraph)
Rare earths are essential... (second paragraph)
The Freedom Facility will be designed... (third paragraph)
Why Phoenix Tailings
? But the rule says use h3 for section headings like "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". It doesn't say we must use exactly those, but those are examples. The user said "e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". So we can use other headings if needed. But we should prefer those. However, "Why Phoenix Tailings" is company pitch. Could be part of About the role. I'll merge. Better: Use "About the company" or "About the role". Since the role is EHS Manager, the "Who We Are Looking For" describes the role. I'll create an "About the role" section with the company context and role summary. Let's write:About the role
Phoenix Tailings is a rapidly growing clean mining and metals production startup focused on building a domestic supply of critical materials. Our Freedom Facility in Rochester, New York will be a commercial-scale rare earth separation facility designed to expand U.S. capacity to process and separate rare earth materials.
Rare earths are essential inputs for many of the technologies that power modern life. They are used in high-performance permanent magnets found in electric vehicles, wind turbines, robotics, advanced electronics, aerospace systems, and defense applications. Today, much of the world's rare earth processing and separation capacity is concentrated overseas. Building more of this capability in the United States is important for strengthening domestic supply chains, reducing reliance on foreign processing, and supporting the advanced manufacturing, energy, technology, and national-security industries that depend on these materials.
The Freedom Facility will be designed to produce thousands of tons of separated rare earth oxides annually, making Rochester an important part of Phoenix Tailings' expansion of domestic rare earth processing capacity.
At Phoenix, we believe that nothing great is ever accomplished alone or without the passion of people who push and motivate one another. If you are someone who shares our relentless pursuit of a better future, passion for innovation, and are excited about working with some of the top innovators in the world, then this is the place for you.
Our values
- You are only crazy if you are wrong, it's ok to be wrong - Say what you think even when it’s uncomfortable
- Lead with Compassion - Show up for your teammates, make the people around you better.
- Be Resourceful - Find a way with what you have, don't wait for more.
- Listen - Understand before you act, ask good questions before deciding.
- Hustle - Put your heart into every interaction, no matter how small.
As we build toward operations in 2027 and 2028, we are beginning to meet with individuals who may be interested in joining Phoenix Tailings. We encourage interested candidates to apply, learn more about what we are building, and stay connected as we develop our facility. Phoenix Tailings is looking for an experienced environmental health and safety leader interested in a future EHS Manager opportunity at our Rochester Freedom Facility. The EHS Manager will build and lead the site's environmental health and safety systems for chemical processing hazards, fire risk, gases, and permit-controlled work. This person will manage hot-work and safety permits, lead training and inspections, and coordinate incident prevention and response. This is an opportunity to help establish EHS practices at a new facility and prepare its workforce to recognize hazards and carry out work safely.
But the "Our values" heading is not in the example list. However, it's a substantive list. The rule says "include a section ONLY when the posting has real, specific content for it". It does. But the example headings are just examples. I think it's okay to have "Our values" as h3. But the user said "usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". This suggests we should use those standard headings. "Our values" might be considered part of "About the role". I'll keep it as a subsection? But we only have h3. Could make it a list within the About section without a heading. But the values are distinct. I'll include as a list under "About the role" without a separate heading, maybe introduce with a sentence. Let's adjust: In "About the role" section, after the why paragraph, add a sentence "Our values:" then list. But the rule: "Use
- for any list of duties/requirements/benefits". Values are not those, but it's a list. I think it's fine.
Now Responsibilities:
Responsibilities
- Build site safety and environmental programs for construction and operations, establishing the procedures, permits, training, and inspections needed for startup
- Manage contractor safety, hot work, chemical hazards, gases, and fire risk, assessing work conditions and ensuring required safeguards are in place
- Develop practical EHS training and inspection programs, documenting findings and working with site leaders to complete corrective actions
- Prepare environmental compliance, permitting, and reporting processes for operations, integrating EHS requirements into facility readiness and process planning
- Lead incident investigations and prevention efforts and coordinate emergency preparedness and response as the site transitions from construction into production
Qualifications
- Bachelor's degree in Environmental Health and Safety, Occupational Health, Environmental Engineering, Chemical Engineering, or a related technical field
- Experience managing EHS programs in industrial construction, chemical processing, metals, or manufacturing, including building programs for a growing or new site
- Working knowledge of industrial safety and environmental requirements, chemical and fire hazards, contractor safety, and permit-controlled work
- Demonstrated ability to assess risks, lead training and inspections, investigate incidents, and establish corrective-action and emergency-preparedness processes
Benefits
- Pay range: $118,000–$175,000 per year (total cash compensation including salary + discretionary bonus)
- Healthcare: 100% medical, dental, and vision coverage for employee
- Stock options: Ownership in a fast-growing venture-backed company
- Time off: Unlimited PTO
- Learning: Learning and development opportunities to grow your skills and career
- for any list of duties/requirements/benefits". It doesn't forbid using for other lists. But to be safe, I'll keep values as a list.
Let's structure:
- for any list of duties/requirements/benefits. Values are not duties/requirements/benefits, but they are a list. I'll include as a list under a subheading? But we only have h3 headings. Could include values as a list within the About section. I'll do a paragraph for each major block, and for values, a list.
But the rule: "Use