Environmental Health and Safety - Senior, EHS Specialist

The user wants me to reformat a job posting into clean, well-structured semantic HTML. I need to follow the rules: 1. Use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) 2. Use

• for any list of duties/requirements/benefits, and

  for prose 3. Do NOT repeat the job title as a heading (the page already shows it) 4. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it 5. Preserve ALL substantive information; do NOT invent or summarize away detail 6. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions 7. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text 8. Never create Pay/Schedule/Benefits sections unless the posting actually states them 9. Prefer a few substantive sections over many thin ones 10. Output ONLY the HTML fragment — no /, no markdown code fences Let me analyze the job posting content: - Company description: "Chromalloy is a global engineering & solutions company..." - this is company boilerplate, but it's substantive about the company. However, the instructions say to remove boilerplate. But this is company description, not legal boilerplate. I should include it as "About the company" or similar? The rules say use

  for section headings like "About the role". The posting doesn't have an explicit "About the company" section, but it starts with company description. I could include it as a section. - "Why work at Chromalloy?" - this is a section with benefits and culture info. - "Our Total Rewards Program..." - this is benefits. - "Job Summary" - this is the role summary. - "Work That Matters" - this is about the impact of the work. - "Location: San Diego, CA" and "Schedule: On-site, Monday-Friday..." - this is location and schedule. - "What You’ll Be Doing" - responsibilities. - "What We’re Looking For" - requirements/qualifications. - "Nice to Have" - preferred qualifications. - Then there are several paragraphs about work hours, salary range, US persons requirement, E-Verify, background check, drug screen, EEO statement, accommodation contact. I need to decide which sections to include. The rules: include a section ONLY when the posting has real, specific content for it. Never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does state schedule: "Schedule: On-site, Monday-Friday, with flexibility to respond during second and weekend shifts as needed." And later: "This position may require work hours outside of the regularly scheduled hours to meet operational needs. This may include work during evenings, weekends, and/or holidays. Additional work hours are assigned based on business requirements. Non-exempt employees will be paid overtime in accordance with applicable federal, state, and local laws." So schedule is stated. I should include a Schedule section. Benefits: "Our Total Rewards Program is designed to support you today and in the future. Comprehensive and flexible benefit options starting on day one, including medical, dental, vision, EAP, wellness incentives, and 401(k) with employer matching. Development & progression opportunities for every employee – regular performance conversations, training and development curriculum, and engineering fellowship programs. Paid time off, including vacation, sick time, paid holidays, and parental leave—all eligible on your first day of employment! Competitive pay, including eligibility for quarterly and annual bonuses, depending on role and site. Eligibility for individual benefit plans may vary based on employment status." That's specific benefits content. So include Benefits section. Pay: "The salary range for this position reflects a broad spectrum of experience levels. Individual compensation within the range is determined by multiple factors, including relevant experience, education, certifications, job related skills, internal equity, and market conditions. We evaluate each candidate individually to ensure fair and competitive pay decisions." This is a pay section, but it doesn't give a specific range. It's still substantive. The rule says never create Pay section unless the posting actually states them. It does state something about pay, but not a specific range. I think it's okay to include a Pay section with that prose. But the rule: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". This is not filler; it's a description of how pay is determined. So I can include it. Now, the EEO statement, E-Verify, background check, drug screen, US persons requirement, accommodation contact - these are legal boilerplate. The instructions say: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So I should remove those. Also, "Chromalloy is an equal opportunity employer - vets/disabled." That's EEO boilerplate. The accommodation contact: "In the United States, if you need a reasonable accommodation for the online application process due to a disability, please contact: https://www.chromalloy.com/contact-us/" - that's application instruction/boilerplate. So I'll omit those. Now, structure: I'll create sections: - About the company (or Company overview) - from the first paragraph(s) up to "Video: What We Do Why work at Chromalloy?" Actually, the first paragraph is company description. Then "Why work at Chromalloy?" is a heading in the posting. I could combine. But the rules: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So I should use those standard headings where appropriate. The posting has "Job Summary", "Work That Matters", "What You’ll Be Doing", "What We’re Looking For", "Nice to Have". I can map: - Job Summary -> About the role (or Summary) - Work That Matters -> maybe part of About the role or separate? It's about the impact. Could be a separate section "Impact" or "Work that matters". But the rules suggest standard headings. I'll use "About the role" for Job Summary and maybe include Work That Matters there or as a separate section. Since it's distinct, I'll make a section "Work that matters". - What You’ll Be Doing -> Responsibilities - What We’re Looking For -> Requirements (or Qualifications) - Nice to Have -> Preferred qualifications (or Skills) - Benefits -> Benefits - Schedule -> Schedule - Pay -> Pay Also, there is "Location: San Diego, CA" - that could be part of Schedule or a separate Location section. The rules don't mention Location heading, but Schedule is mentioned. I'll include location in Schedule section. Now, the company description and "Why work at Chromalloy?" and "Our Total Rewards Program" - the latter is benefits. The company description could be "About the company". But the rules say "About the role" not "About the company". However, the example headings include "About the role". The posting is for a job, so the company description is relevant but not the role. I think it's okay to include a "Company overview" section. But the rules say "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It says "e.g.", so other headings are allowed. But to be safe, I'll include a "Company overview" section. But the instructions: "Do NOT repeat the job title as a heading (the page already shows it)". The job title is "Senior Environment, Health & Safety (EHS) Specialist". Not in the text provided? Actually the user didn't provide the job title separately; the posting starts with company description. The job title might be in the original page but not in the text. The text says "We’re looking for a Senior Environment, Health & Safety (EHS) Specialist..." in Job Summary. So I should not repeat that as a heading. Now, let's draft HTML. I'll start with a

  Company overview

  and then

  for the company description. Then

  Why work at Chromalloy

  ? But that's similar to benefits. Actually "Why work at Chromalloy?" is a section with culture and values. Then "Our Total Rewards Program" is benefits. I could combine into a "Benefits" section. But the rules say Benefits section for benefits. The "Why work at Chromalloy?" includes "Chromalloy employees are proud, passionate problem-solvers..." and "Join our team...". That's more culture. I'll include a "Culture" section or "Why work here". But the rules prefer standard headings. I'll include a "Company culture" section. But the rules: "Prefer a few substantive sections over many thin ones." So maybe combine company overview and culture into one "About the company" section. Let's see: The first paragraph: "Chromalloy is a global engineering & solutions company... Video: What We Do Why work at Chromalloy? Chromalloy employees are proud, passionate problem-solvers who strive to live our values every day. A career with Chromalloy is an opportunity to learn from top industry experts, work with important technologies, and unlock a passion for innovation. Join our team of experts, innovators and problem-solvers delivering world-class solutions for our customers. As a global company, we are committed to creating an inclusive environment where all employees feel represented, heard, and able to bring their best selves to work every day. Be part of something bigger with Chromalloy!" Then "Our Total Rewards Program..." is separate. I'll create: -

  Company overview

  with the first paragraph (excluding "Video: What We Do" which is likely a video link, I'll drop that). -

  Benefits

  with the Total Rewards Program details. -

  About the role

  with Job Summary and Work That Matters. -

  Schedule

  with location and schedule details. -

  Responsibilities

  with What You’ll Be Doing. -

  Requirements

  with What We’re Looking For. -

  Preferred qualifications

  with Nice to Have. -

  Pay

  with the salary range paragraph. - Maybe

  Additional information

  for the work hours outside regular schedule, US persons requirement, etc. But those are legal/boilerplate? The work hours part is relevant to schedule. The US persons requirement is due to government regulation, maybe include in a "Requirements" or "Additional requirements". But the rules say remove legal boilerplate. The US persons requirement is a legal requirement for the role. It's substantive. I'll include it in a "Requirements" section or a separate "Eligibility" section. But the rules say never create a section unless real content. I'll include it in Requirements as a note. But the Requirements section already has a list. I can add a paragraph after the list. Similarly, the background check and drug screen are boilerplate. I'll include the work hours note in Schedule. Now, let's write the HTML. I need to output only the HTML fragment, no markdown fences. I'll write:

  Company overview

  Chromalloy is a global engineering & solutions company. We are a leading provider of aftermarket parts, repairs, and solutions that safely & reliably extend the life of aircraft engines and gas turbines. We develop, manufacture and repair critical turbine components for a range of engine platforms. Our solutions support the engines running the aerospace, energy and defense industries around the world