Sr. Manager, Environmental Health & Safety

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading only if there is real content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate (EEO, etc). Must not create sections with filler like "commensurate with experience". Must only include sections where posting has real specific content. Let's parse the posting. First paragraph: "SpaceX was founded under the belief..." That's about company mission. Could be "About the role"? Actually it's about SpaceX. Could be "About the role" maybe includes description of role and company. The posting includes a description: "We are building Terafab, a vertically integrated semiconductor factory...". That's about the role context. So we can put that under About the role. Then "This position requires a dedicated safety leader..." etc. That's also about role. Then "Responsibilities" heading appears in posting with bullet list. Then "Basic Requirements", "PREFERRED REQUIREMENTS:", "Additional Requirements", "ITAR Requirements". Those are qualifications/requirements. We need to map to sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for About the role, Responsibilities, Requirements (maybe combine basic and preferred and additional?), Qualifications (maybe same as Requirements?), Skills (maybe list of skills like knowledge of quality tools etc). Benefits, Pay, Schedule: not present except maybe travel up to 50% (that's schedule? Actually travel requirement). There's no explicit pay or benefits. So we should not create Pay/Benefits/Schedule sections unless posting actually states them. Travel is not schedule but maybe schedule? It says "This role may require up to 50% domestic travel." That's not schedule but could be under Schedule? The instruction: include a section ONLY when posting has real, specific content for it. Travel is not schedule but could be considered schedule? Probably not. Better to not create Schedule section unless there is explicit schedule like shift, hours. There's "Ability to work extended hours and weekends when needed". That's schedule info. So we could include Schedule section with that content. Also travel up to 50% could be under Schedule as well. So we can create Schedule section with those details. Benefits: none mentioned. Pay: none. So omit those. Qualifications: we could separate Requirements (basic) and Qualifications (preferred). Or combine. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Requirements and Qualifications separate. Skills: maybe list of skills like "knowledge of quality tools such as lean manufacturing principles, statistical process control, root cause analysis and corrective action, process failure mode and effects analysis (PFMEA), control plans, and various problem-solving approaches". Also "Strong command of federal and state EHS laws...". Could be under Skills. We need to preserve all substantive info, not invent or summarize away detail. Must not repeat job title as heading. Must not put Job ID/requisition numbers as headings (none). Must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip the EEO statement at end, also the ITAR requirements? ITAR is substantive? It's a requirement for eligibility. It's a requirement, so we should keep it under Requirements or Qualifications. It's not boilerplate; it's a specific requirement. So keep. Also remove "Learn more about the ITAR here." maybe that's a link; we can drop the link but keep the requirement text. Also remove "SpaceX is an Equal Opportunity Employer; employment with SpaceX is governed on the basis of merit..." etc. That's boilerplate EEO, remove. Also remove "Applicants wishing to view a copy of SpaceX’s Affirmative Action Plan..." etc. Remove. Now we need to output only HTML fragment, no /, no markdown fences. Let's craft sections. About the role: combine the introductory paragraphs about SpaceX mission and Terafab description and the role context. Content: "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 building Terafab, a vertically integrated semiconductor factory at an unprecedented scale. The facility houses logic, memory, packaging, test, and lithography mask production under one roof, optimized for rapid iteration and maximum compute density per square foot. Additionally, the campus will include power generation and compute testing facilities that will enable fully optimized development, operation, and testing of the fabrication facility and its products. This position requires a dedicated safety leader who will be able to use their skill, knowledge, and experience to further our Environmental Health and Safety programs within our fast-paced work environment that includes operations that have never been attempted before. You will bring deep experience in EHS risk assessment, industrial hygiene, environmental compliance, and equipment, process, and construction safety. You will have the opportunity to build and lead a talented team of EHS managers, specialists, and engineers. Success depends on clear communication, strong cross-functional influence, and the ability to operate in a fast-paced, high-change environment." That seems good. Responsibilities: list from posting. We need to preserve bullet points exactly as given (maybe slight formatting). Use

• . Responsibilities list: - Lead comprehensive EHS programs and operational plans across multiple teams, aligned to business goals and Tesla EHS standards - Set day-to-day priorities and long-range plans for the EHS organization, including EHS managers, specialists, and engineers - Lead EHS risk assessments and drive engineering controls and safeguards that mitigate or eliminate hazards - Coordinate with site leadership to ensure appropriate process safety involvement in department development/modification plans and procedure development - Represent the EHS department at site wide management meetings/briefings - Provide instructional guidance of job assignments, correct procedures and applicable techniques to perform specific skills; ensure accuracy and completion - Ensure mission and values are communicated to the team and are integrated within team goals, objectives, and work tasks - Implement all aspects of an occupational safety program, including processes, programs and documentation outlined by OSHA standards - Evaluate equipment overpressure/overtemperature scenarios and reaction hazards - Coordinate with and serve as the main point of contact for local resource agencies Note: The original had "Tesla EHS standards" maybe a mistake but we keep. Now Requirements: Basic Requirements plus maybe ITAR and Additional Requirements? Let's separate. Basic Requirements: - Bachelor’s degree - 10+ years of experience in the design, development, and general operational oversight of EHS disciplines - 5+ years of progressive EHS management experience Additional Requirements (non-preferred): - This is not a remote position and will require relocation if not already local to the Anderson / College Station, TX area - Position requires the ability to work extended hours and weekends when needed - Ability to travel up to 50% - Position is subject to pre-employment drug and random drug and alcohol testing - ITAR Requirements: To conform to U.S. Government export regulations, applicant must be a (i) U.S. citizen or national, (ii) U.S. lawful, permanent resident (aka green card holder), (iii) Refugee under 8 U.S.C.1157, or (iv) Asylee under 8 U.S.C.1158, or be eligible to obtain the required authorizations from the U.S. Department of State. We could keep ITAR as part of Requirements. Now Preferred Requirements: list. Preferred Requirements: - Bachelor's degree in engineering with an emphasis in process safety, chemical engineering, environmental engineering or systems safety engineering - Experience working in semiconductor industry - Experience with design and commissioning of process systems associated with or similar to those used in semiconductor manufacturing - Advanced understanding of industry codes, standards, and practices such as ASME, NFPA, ANSI, IBC/IFC, RAGAGEP, etc. - Strong command of federal and state EHS laws, regulations, and standards applicable to complex manufacturing; Texas experience preferred - Knowledge of quality tools such as lean manufacturing principles, statistical process control, root cause analysis and corrective action, process failure mode and effects analysis (PFMEA), control plans, and various problem-solving approaches Now Skills: maybe we can extract from Preferred and Additional that are skill-based: knowledge of quality tools, strong command of federal and state EHS laws, etc. But we already have those under Preferred. Could create Skills section for those skill items. However we must not duplicate content. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we create Skills section, we need to move some content there, but then we would be removing from Preferred Requirements? That would be summarizing away detail? Actually we could keep both sections; but we might duplicate content if we list same items in both. Better to keep Preferred Requirements as Qualifications, and Skills maybe separate for things like "clear communication, strong cross-functional influence, ability to operate in a fast-paced, high-change environment" which are more soft skills. Those appear in About the role paragraph. Could extract them to Skills. But we must not invent or summarize away detail; we can rephrase? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. That suggests we should not omit details, but we can rephrase? Probably we should keep the exact sentences. However we can move sentences to appropriate sections as long as we keep them verbatim. It's okay to reorganize. Thus we can have: About the role: includes mission, Terafab, role description. Responsibilities: list. Requirements: Basic Requirements + Additional Requirements (including ITAR). Qualifications: Preferred Requirements. Skills: maybe include "clear communication, strong cross-functional influence, and the ability to operate in a fast-paced, high-change environment." Also maybe "deep experience in EHS risk assessment, industrial hygiene, environmental compliance, and equipment, process, and construction safety." But that's already in About the role. Could still be there. But to avoid duplication, we could keep Skills empty? Better to not create Skills section if no specific skill list beyond what's already covered. However the instruction says prefer a few substantive sections over many thin ones. So we could omit Skills if not enough distinct content. But we have some skill statements: "clear communication, strong cross-functional influence, and the ability to operate in a fast-paced, high-change environment." That's a skill set. Also "deep experience in EHS risk assessment, industrial hygiene, environmental compliance, and equipment, process, and construction safety." That's also skill/experience. But those are already in About the role. If we move them to Skills, we would be removing from About the role, which might be okay as long as we keep the info somewhere. But we might lose the flow. However the instruction: "Prefer a few substantive sections over many thin ones." So maybe better to keep About the role with those details, and not create a Skills section unless there is a distinct list of skills separate from responsibilities/requirements. The posting does not have a separate "Skills" heading; the skill-like statements are embedded. So we could omit Skills section. Thus sections: About the role, Responsibilities, Requirements, Qualifications. Possibly Schedule (for travel and extended hours). But those are in Additional Requirements; we could keep them under Requirements. However we could also create Schedule section for those items. But then we would be moving content from Requirements to Schedule, which might be okay. However the instruction says include a section ONLY when posting has real, specific content for it. Travel up to 50% and ability to work extended hours and weekends when needed are specific content for schedule. So we could create Schedule section with those two bullets. Then we would remove them from Requirements (or keep them also? Better to avoid duplication). So we would have Requirements (basic +