Environmental Health & Safety Engineer, Contractor Management
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. No Job ID etc. Remove boilerplate: EEO, ITAR, etc. Also remove duplicated lines like "Additional Requirements" repeated. We need to preserve substantive info.
Let's parse content:
First paragraph: "SpaceX was founded under the belief that a future where humanity is out exploring the stars is fundamentally more exciting than one where we are not. Today SpaceX is actively developing the technologies to make this possible, with the ultimate goal of enabling human life on Mars." This is about company, maybe "About the role"? Actually "About the role" heading is for description of role. The first paragraph is more about company mission. Could be placed under "About the role" as description. We'll treat as About the role.
Then: "ENVIRONMENTAL HEALTH & SAFETY ENGINEER, CONTRACTOR MANAGEMENT" is job title, we ignore as heading.
Then: "We are seeking a highly capable and self-motivated EHS professional to join our Business Operations team. This role is critical in delivering proactive environmental, health, and safety support across a dynamic and fast-paced organization. The ideal candidate is a confident, autonomous operator who thrives while working with minimal supervision and possesses a strong customer service mindset. This position requires a proactive safety leader who can effectively support field teams, leadership, and operational stakeholders both domestically and internationally." This is also about role description. Could be part of About the role.
Then "Responsibilities" heading with bullet list.
List items:
- Develop and implement contractor management safety programs across the organization
- Collaborate with supply, legal and operational partners to drive program success
- Provide expert EHS support to the Business Operations team, acting as a trusted advisor and safety partner
- Travel as needed to engage and coordinate with suppliers, contractors and internal teams as needed.
- Conduct site assessments, audits, hazard analyses, and safety inspections with minimal oversight
- Develop and implement safety programs, training, and risk mitigation strategies tailored to operational needs
- Respond to urgent safety concerns and support incident investigations across multiple locations
- Champion a strong safety culture while balancing operational demands and timelines
- Collaborate with cross-functional teams to ensure regulatory compliance and continuous improvement
Then "Basic Qualifications" heading with bullet list? Actually it's a paragraph: "Bachelor’s degree 3+ years of experience in the design, development and operational oversight of environmental, health and safety disciplines". Could be list.
Then "Preferred Skills And Experience" heading with bullet list:
- Bachelor’s degree in Occupational Safety, Environmental Science, Engineering, or related field (or equivalent experience)
- Demonstrated experience in managing contractor safety management programs
- 5+ years of progressive EHS experience in high-risk or industrial environments
- Demonstrated ability to work autonomously with minimal direction and make sound decisions in the field
- Strong customer service orientation with excellent interpersonal and communication skills
- Proven experience supporting business operations or field-based teams
- Deep knowledge of OSHA, EPA, and international EHS regulations
- Professional certifications (CSP, CIH, CHMM, or equivalent) strongly preferred
- Excellent organizational, presentation, training and communication skills
- Experience with interpreting, applying, and documenting federal, state, and local safety regulations
- Experience with emergency response communication and incident management
- Intermediate Microsoft Office Suite (Excel, PowerPoint, Word, and Outlook)
Then "Additional Requirements" heading with bullet list? Actually lines:
- Position occasionally requires the ability to work extended hours and weekends when needed
- If not local to a SpaceX site relocation will be necessary
- Willingness and ability to travel 50%+ domestically and internationally
Note "Additional Requirements" appears twice (duplicate). We'll include once.
Then "Compensation And Benefits" heading with paragraphs:
- Pay Range: Level 1: $95,000.00 - $125,000.00 Level 2: $110,000.00 - $150,000.00
- Your actual level and base salary will be determined on a case-by-case basis and may vary based on the following considerations: job-related knowledge and skills, education, and experience.
- Base salary is just one part of your total rewards package at SpaceX. You may also be eligible for long-term incentives, in the form of company stock or long-term cash awards, as well as potential discretionary bonuses and the ability to purchase additional stock at a discount through an Employee Stock Purchase Plan.
- You will also receive access to comprehensive medical, vision, and dental coverage, access to a 401(k) retirement plan, short and long-term disability insurance, life insurance, paid parental leave, and various other discounts and perks.
- You may also accrue 3 weeks of paid vacation and will be eligible for 10 or more paid holidays per year.
- Employees accrue paid sick leave pursuant to Company policy which satisfies or exceeds the accrual, carryover, and use requirements of the law.
Then "ITAR Requirements" heading with paragraph about citizenship etc. This is likely boilerplate legal; we should remove as per instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. ITAR is legal requirement; likely remove. Also EEO statement remove.
Thus we keep sections: About the role, Responsibilities, Basic Qualifications, Preferred Skills And Experience, Additional Requirements, Compensation And Benefits (including Pay and Benefits). However we have headings for Pay and Benefits separately per instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They want separate Pay and Benefits sections if content exists. We have Pay range info and Benefits info. Could split: Pay section with pay range details; Benefits section with benefits description. Also we have Schedule? Not present; no schedule info besides travel and extended hours; but schedule not given. So we omit Schedule.
We also have Requirements vs Qualifications vs Skills. The instruction says use headings like Requirements, Qualifications, Skills. We have Basic Qualifications (maybe Requirements), Preferred Skills And Experience (maybe Skills). We could map: Basic Qualifications -> Requirements (or Qualifications). Preferred Skills And Experience -> Skills. We'll follow the headings exactly as they appear in posting? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should use those exact headings if we have content. So we need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Possibly also Schedule if present (not). We'll not include Qualifications if we already have Requirements? But we have both Basic Qualifications and Preferred Skills And Experience. Could treat Basic Qualifications as Requirements, and Preferred Skills And Experience as Skills. Qualifications heading maybe not needed if we don't have separate qualifications beyond requirements. But we could also put Basic Qualifications under Qualifications. However we need to preserve all substantive info; we can put Basic Qualifications under Requirements (or Qualifications). Let's decide: Use Requirements for Basic Qualifications (since they are basic qualifications). Use Skills for Preferred Skills And Experience. We'll not use Qualifications heading (to avoid thin section). Or we could use Qualifications for Basic Qualifications and Skills for Preferred Skills And Experience, and omit Requirements. But we have both basic and preferred; maybe better to have Requirements (basic) and Skills (preferred). We'll omit Qualifications.
Thus sections:
- About the role (company mission + role description)
- Responsibilities (list)
- Requirements (basic qualifications bullet list)
- Skills (preferred skills bullet list)
- Additional Requirements (maybe could be part of Requirements? but it's separate; we could treat as Requirements as well? But it's about travel, relocation, extended hours. Could be part of Requirements. However we already have Requirements for basic qualifications; we could add these as additional bullet points under Requirements. But instruction: "Prefer a few substantive sections over many thin ones." Could combine Additional Requirements into Requirements. However they are not qualifications but job requirements. Might be okay to keep separate section? There's no heading for Additional Requirements in the list of allowed headings; but we could still use for any heading? 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. Safer to stick to those headings. So we can incorporate Additional Requirements into Requirements or maybe into Responsibilities? It's about travel, relocation, extended hours - could be part of Responsibilities? Not exactly. Could be part of Requirements (job requirements). We'll add them under Requirements as extra bullet points.
- Benefits (benefits description)
- Pay (pay range and details)
We must not include Schedule.
Now we need to output HTML fragment only, no markdown fences.
We'll produce:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should use those exact headings if we have content. So we need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Possibly also Schedule if present (not). We'll not include Qualifications if we already have Requirements? But we have both Basic Qualifications and Preferred Skills And Experience. Could treat Basic Qualifications as Requirements, and Preferred Skills And Experience as Skills. Qualifications heading maybe not needed if we don't have separate qualifications beyond requirements. But we could also put Basic Qualifications under Qualifications. However we need to preserve all substantive info; we can put Basic Qualifications under Requirements (or Qualifications). Let's decide: Use Requirements for Basic Qualifications (since they are basic qualifications). Use Skills for Preferred Skills And Experience. We'll not use Qualifications heading (to avoid thin section). Or we could use Qualifications for Basic Qualifications and Skills for Preferred Skills And Experience, and omit Requirements. But we have both basic and preferred; maybe better to have Requirements (basic) and Skills (preferred). We'll omit Qualifications.
Thus sections:
- About the role (company mission + role description)
- Responsibilities (list)
- Requirements (basic qualifications bullet list)
- Skills (preferred skills bullet list)
- Additional Requirements (maybe could be part of Requirements? but it's separate; we could treat as Requirements as well? But it's about travel, relocation, extended hours. Could be part of Requirements. However we already have Requirements for basic qualifications; we could add these as additional bullet points under Requirements. But instruction: "Prefer a few substantive sections over many thin ones." Could combine Additional Requirements into Requirements. However they are not qualifications but job requirements. Might be okay to keep separate section? There's no heading for Additional Requirements in the list of allowed headings; but we could still use for any heading? 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. Safer to stick to those headings. So we can incorporate Additional Requirements into Requirements or maybe into Responsibilities? It's about travel, relocation, extended hours - could be part of Responsibilities? Not exactly. Could be part of Requirements (job requirements). We'll add them under Requirements as extra bullet points.
- Benefits (benefits description)
- Pay (pay range and details)
We must not include Schedule.
Now we need to output HTML fragment only, no markdown fences.
We'll produce:
About the role
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. Safer to stick to those headings. So we can incorporate Additional Requirements into Requirements or maybe into Responsibilities? It's about travel, relocation, extended hours - could be part of Responsibilities? Not exactly. Could be part of Requirements (job requirements). We'll add them under Requirements as extra bullet points.
- Benefits (benefits description)
- Pay (pay range and details)
We must not include Schedule.
Now we need to output HTML fragment only, no markdown fences.
We'll produce:
About the role
SpaceX was founded under the belief that a future where humanity is out exploring the stars is fundamentally more exciting than one where we are not. Today SpaceX is actively developing the technologies to make this possible, with the ultimate goal of enabling human life on Mars. We are seeking a highly capable and self-motivated EHS professional to join our Business Operations team. This role is critical in delivering proactive environmental, health, and safety support across a dynamic and fast-paced organization. The ideal candidate is a confident, autonomous operator who thrives while working with minimal supervision and possesses a strong customer service mindset. This position requires a proactive safety leader who can effectively support field teams, leadership, and operational stakeholders both domestically and internationally.
Responsibilities
- Develop and implement contractor management safety programs across the organization
- Collaborate with supply, legal and operational partners to drive program success
- Provide expert EHS support to the Business Operations team, acting as a trusted advisor and safety partner
- Travel as needed to engage and coordinate with suppliers, contractors and internal teams as needed.
- Conduct site assessments, audits, hazard analyses, and safety inspections with minimal oversight
- Develop and implement safety programs, training, and risk mitigation strategies tailored to operational needs
- Respond to urgent safety concerns and support incident investigations across multiple locations
- Champion a strong safety culture while balancing operational demands and timelines
- Collaborate with cross-functional teams to ensure regulatory compliance and continuous improvement
Requirements
- Bachelor’s degree
- 3+ years of experience in the design, development and operational oversight of environmental, health and safety disciplines
- Position occasionally requires the ability to work extended hours and weekends when needed
- If not local to a SpaceX site relocation will be necessary
- Willingness and ability to travel 50%+ domestically and internationally
Skills
- Bachelor’s degree in Occupational Safety, Environmental Science, Engineering, or related field (or equivalent experience)
- Demonstrated experience in managing contractor safety management programs
- 5+ years of progressive EHS experience in high-risk or industrial environments
- Demonstrated ability to work autonomously with minimal direction and make sound decisions in the field
- Strong customer service orientation with excellent interpersonal and communication skills
- Proven experience supporting business operations or field-based teams
- Deep knowledge of OSHA, EPA, and international EHS regulations
- Professional certifications (CSP, CIH, CHMM, or equivalent) strongly preferred
- Excellent organizational, presentation