Senior EHS Program Manager
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content accordingly.
We have sections: About The Team (maybe we can treat as "About the role"? Actually there is "About The Team" then "About The Role" then "About You". Also there is compensation and benefits.
We need to include sections only when posting has real specific content. So we need:
- About The Team: content describing team role.
- About The Role: responsibilities.
- About You: qualifications/requirements.
- Benefits: they mention "competitive salary and equity, a generous PTO and sick leave policy, parental leave, an annual learning and development stipend, and more!" Also "To see some of the benefits & perks we offer, please visit here." So we have some benefits content.
- Pay: they have "Hiring Range $114,000—$170,000 USD". So we can include Pay section.
- Schedule: not mentioned, so omit.
- Skills: maybe not separate; we can incorporate into About You.
We must not repeat job title as heading. No Job ID.
We must remove boilerplate: EEO, equal opportunity, accommodation, unsolicited resumes note, etc. Also remove "To see some of the benefits & perks we offer, please visit here." maybe keep as part of benefits? It's a link placeholder; but we can keep the sentence? It's not substantive; maybe we can drop it as it's just a link instruction. Better to keep only substantive benefits: competitive salary and equity, generous PTO and sick leave policy, parental leave, annual learning and development stipend.
We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep the bullet points of responsibilities etc.
We need to use - for any list of duties/requirements/benefits.
We need to use
for prose.
We need to output only HTML fragment.
Let's structure:
About The Team
As a Senior EHS Program Manager, you will be instrumental in building and scaling Relativity's Environmental Health and Safety management systems across all sites and programs. This role requires a unique blend of strategic program development and technical systems expertise. You will lead the development of enterprise-wide EHS standards, policies, and procedures while simultaneously building and managing data systems that drive EHS insights and performance. Working cross-functionally with site EHS teams, Enterprise Applications, engineering, and operations, you will establish the infrastructure and systems that enable a world-class safety culture. This is a strategic role that combines deep EHS technical knowledge with modern data analytics and program management capabilities.
About The Role
- Further the development and implementation of Relativity's EHS Management System aligned with ISO 45001 and ISO 14001 standards, including health and safety minimum standards, SOPs, specifications, and policies that apply across all sites and programs
- Design, build, and manage EHS data systems and analytics platforms in coordination with the Enterprise Applications team
- Lead requirements definition and implementation of EHS data infrastructure using BigQuery, Confluence, Jira, Power BI, and other data warehouse systems
- Develop dashboards, metrics, and reporting systems that provide actionable insights on EHS performance, trends, and risks
- Leverage modern tools (including AI/ML capabilities) to enhance EHS data analysis and decision-making
- Serve as the strategic lead for enterprise EHS program development, driving continuous improvement initiatives and ensuring alignment with regulatory requirements and industry best practices
- Partner cross-functionally with site EHS teams, engineering, operations, and IT to implement scalable EHS programs, ensuring consistency while accommodating site-specific needs
But note: we cannot nest inside - ? Actually we can but better to keep flat list. Could break into separate items.
Simplify: list each bullet as separate
- . For the subpoints we can incorporate into the main bullet using commas or semicolons.
Let's produce:
About The Role
- Further the development and implementation of Relativity's EHS Management System aligned with ISO 45001 and ISO 14001 standards, including health and safety minimum standards, SOPs, specifications, and policies that apply across all sites and programs
- Design, build, and manage EHS data systems and analytics platforms in coordination with the Enterprise Applications team: lead requirements definition and implementation of EHS data infrastructure using BigQuery, Confluence, Jira, Power BI, and other data warehouse systems; develop dashboards, metrics, and reporting systems that provide actionable insights on EHS performance, trends, and risks; leverage modern tools (including AI/ML capabilities) to enhance EHS data analysis and decision-making
- Serve as the strategic lead for enterprise EHS program development, driving continuous improvement initiatives and ensuring alignment with regulatory requirements and industry best practices
- Partner cross-functionally with site EHS teams, engineering, operations, and IT to implement scalable EHS programs, ensuring consistency while accommodating site-specific needs
About You
- Bachelor's degree in Environmental Health and Safety, Occupational Safety, Environmental Science, Engineering, or related technical field
- 5+ years of progressive EHS experience with demonstrated expertise in developing and implementing ISO 45001 and ISO 14001 management systems
- Experience with data analysis and business intelligence tools (SQL, BigQuery, Power BI, or similar platforms)
- Proven experience developing enterprise-wide EHS policies, standards, and procedures in manufacturing or aerospace environments
- Strong technical writing and program management skills with ability to influence across all organizational levels
- Experience conducting risk assessments, audits, and managing complex EHS compliance requirements across multiple sites
We could also include Nice To Have as optional but not required; we could omit or include as part of About You? The instruction: include a section ONLY when posting has real, specific content. Nice To Have is specific content; we could include as a subsection maybe under "Preferred Qualifications". But we only have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could treat Nice To Have as part of Qualifications or Skills. But we already have About You covering requirements; we could add another Preferred Qualifications
but not in list. Better to incorporate into About You as additional bullets maybe under a separate heading "Preferred Qualifications". However the instruction says use those example headings; but not strictly limited to them? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings where appropriate. So we could have a section "Qualifications" for About You, and maybe "Skills" for Nice To Have. But we already have About You containing both required and nice-to-have; we could split.
Let's do:
Qualifications
Bachelor's degree in Environmental Health and Safety, Occupational Safety, Environmental Science, Engineering, or related technical field; 5+ years of progressive EHS experience with demonstrated expertise in developing and implementing ISO 45001 and ISO 14001 management systems; experience with data analysis and business intelligence tools (SQL, BigQuery, Power BI, or similar platforms); proven experience developing enterprise-wide EHS policies, standards, and procedures in manufacturing or aerospace environments; strong technical writing and program management skills with ability to influence across all organizational levels; experience conducting risk assessments, audits, and managing complex EHS compliance requirements across multiple sites.
Preferred Qualifications
- Experience with modern data tools including AI/ML applications, data warehouses, and cloud analytics platforms
- Professional certifications: CSP, CIH, CHMM, or ISO 45001/14001 Lead Auditor
- Aerospace, defense, or advanced manufacturing experience
- Experience implementing EHS management software or enterprise applications
But the instruction says use headings like Qualifications, Skills. Preferred Qualifications not in list but could be considered under Qualifications. Might be okay to keep as Qualifications and include both required and preferred within same section? Might be mixing.
Better to follow the examples: we have About The Team, About The Role, About You (maybe treat as Qualifications). Then Benefits, Pay.
Thus we can have:
About The Team
...
About The Role
...
Qualifications
...
(including required and nice-to-have? Could separate but we can include all.)
But we need to preserve all info; we can include nice-to-have as part of Qualifications but maybe label as "Nice to have" inside . However we should not invent headings not in list? The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says use those for those sections. It's ambiguous. Safer to stick to those headings.
Thus we can map:
- About The Team -> maybe "About the role"? Actually About The Team is not exactly About the role. Could treat as "About the role"? But we also have About The Role separate. Could combine? But we have both sections; we could treat About The Team as "About the role" and About The Role as "Responsibilities". However the instruction says use those headings for section headings; we can use them as we see fit.
Let's decide:
About the role
-> combine About The Team and About The Role? Might be too much.
Better to keep both: use About The Team
and About The Role
. The instruction didn't forbid using other headings; it just gave examples. So it's okay.
Thus final HTML:
About The Team
As a Senior EHS Program Manager, you will be instrumental in building and scaling Relativity's Environmental Health and Safety management systems across all sites and programs. This role requires a unique blend of strategic program development and technical systems expertise. You will lead the development of enterprise-wide EHS standards, policies, and procedures while simultaneously building and managing data systems that drive EHS insights and performance. Working cross-functionally with site EHS teams, Enterprise Applications, engineering, and operations, you will establish the infrastructure and systems that enable a world-class safety culture. This is a strategic role that combines deep EHS technical knowledge with modern data analytics and program management capabilities.
About The Role
- Further the development and implementation of Relativity's EHS Management System aligned with ISO 45001 and ISO 14001 standards, including health and safety minimum standards, SOPs, specifications, and policies that apply across all sites and programs
- Design, build, and manage EHS data systems and analytics platforms in coordination with the Enterprise Applications team: lead requirements definition and implementation of EHS data infrastructure using BigQuery, Confluence, Jira, Power BI, and other data warehouse systems; develop dashboards, metrics, and reporting systems that provide actionable insights on EHS performance, trends, and risks; leverage modern tools (including AI/ML capabilities) to enhance EHS
for prose. We need to output only HTML fragment. Let's structure:
About The Team
As a Senior EHS Program Manager, you will be instrumental in building and scaling Relativity's Environmental Health and Safety management systems across all sites and programs. This role requires a unique blend of strategic program development and technical systems expertise. You will lead the development of enterprise-wide EHS standards, policies, and procedures while simultaneously building and managing data systems that drive EHS insights and performance. Working cross-functionally with site EHS teams, Enterprise Applications, engineering, and operations, you will establish the infrastructure and systems that enable a world-class safety culture. This is a strategic role that combines deep EHS technical knowledge with modern data analytics and program management capabilities.
About The Role
- Further the development and implementation of Relativity's EHS Management System aligned with ISO 45001 and ISO 14001 standards, including health and safety minimum standards, SOPs, specifications, and policies that apply across all sites and programs
- Design, build, and manage EHS data systems and analytics platforms in coordination with the Enterprise Applications team
- Lead requirements definition and implementation of EHS data infrastructure using BigQuery, Confluence, Jira, Power BI, and other data warehouse systems
- Develop dashboards, metrics, and reporting systems that provide actionable insights on EHS performance, trends, and risks
- Leverage modern tools (including AI/ML capabilities) to enhance EHS data analysis and decision-making
- Serve as the strategic lead for enterprise EHS program development, driving continuous improvement initiatives and ensuring alignment with regulatory requirements and industry best practices
- Partner cross-functionally with site EHS teams, engineering, operations, and IT to implement scalable EHS programs, ensuring consistency while accommodating site-specific needs
- inside
- ? Actually we can but better to keep flat list. Could break into separate items. Simplify: list each bullet as separate
- . For the subpoints we can incorporate into the main bullet using commas or semicolons.
Let's produce:
About The Role
- Further the development and implementation of Relativity's EHS Management System aligned with ISO 45001 and ISO 14001 standards, including health and safety minimum standards, SOPs, specifications, and policies that apply across all sites and programs
- Design, build, and manage EHS data systems and analytics platforms in coordination with the Enterprise Applications team: lead requirements definition and implementation of EHS data infrastructure using BigQuery, Confluence, Jira, Power BI, and other data warehouse systems; develop dashboards, metrics, and reporting systems that provide actionable insights on EHS performance, trends, and risks; leverage modern tools (including AI/ML capabilities) to enhance EHS data analysis and decision-making
- Serve as the strategic lead for enterprise EHS program development, driving continuous improvement initiatives and ensuring alignment with regulatory requirements and industry best practices
- Partner cross-functionally with site EHS teams, engineering, operations, and IT to implement scalable EHS programs, ensuring consistency while accommodating site-specific needs
About You
- Bachelor's degree in Environmental Health and Safety, Occupational Safety, Environmental Science, Engineering, or related technical field
- 5+ years of progressive EHS experience with demonstrated expertise in developing and implementing ISO 45001 and ISO 14001 management systems
- Experience with data analysis and business intelligence tools (SQL, BigQuery, Power BI, or similar platforms)
- Proven experience developing enterprise-wide EHS policies, standards, and procedures in manufacturing or aerospace environments
- Strong technical writing and program management skills with ability to influence across all organizational levels
- Experience conducting risk assessments, audits, and managing complex EHS compliance requirements across multiple sites
Preferred Qualifications
but not in list. Better to incorporate into About You as additional bullets maybe under a separate heading "Preferred Qualifications". However the instruction says use those example headings; but not strictly limited to them? It says usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings where appropriate. So we could have a section "Qualifications" for About You, and maybe "Skills" for Nice To Have. But we already have About You containing both required and nice-to-have; we could split. Let's do:
Qualifications
Bachelor's degree in Environmental Health and Safety, Occupational Safety, Environmental Science, Engineering, or related technical field; 5+ years of progressive EHS experience with demonstrated expertise in developing and implementing ISO 45001 and ISO 14001 management systems; experience with data analysis and business intelligence tools (SQL, BigQuery, Power BI, or similar platforms); proven experience developing enterprise-wide EHS policies, standards, and procedures in manufacturing or aerospace environments; strong technical writing and program management skills with ability to influence across all organizational levels; experience conducting risk assessments, audits, and managing complex EHS compliance requirements across multiple sites.
Preferred Qualifications
- Experience with modern data tools including AI/ML applications, data warehouses, and cloud analytics platforms
- Professional certifications: CSP, CIH, CHMM, or ISO 45001/14001 Lead Auditor
- Aerospace, defense, or advanced manufacturing experience
- Experience implementing EHS management software or enterprise applications
About The Team
...
About The Role
- ...
Qualifications
- ...
. However we should not invent headings not in list? The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says use those for those sections. It's ambiguous. Safer to stick to those headings. Thus we can map: - About The Team -> maybe "About the role"? Actually About The Team is not exactly About the role. Could treat as "About the role"? But we also have About The Role separate. Could combine? But we have both sections; we could treat About The Team as "About the role" and About The Role as "Responsibilities". However the instruction says use those headings for section headings; we can use them as we see fit. Let's decide:
About the role
-> combine About The Team and About The Role? Might be too much. Better to keep both: useAbout The Team
andAbout The Role
. The instruction didn't forbid using other headings; it just gave examples. So it's okay. Thus final HTML:About The Team
As a Senior EHS Program Manager, you will be instrumental in building and scaling Relativity's Environmental Health and Safety management systems across all sites and programs. This role requires a unique blend of strategic program development and technical systems expertise. You will lead the development of enterprise-wide EHS standards, policies, and procedures while simultaneously building and managing data systems that drive EHS insights and performance. Working cross-functionally with site EHS teams, Enterprise Applications, engineering, and operations, you will establish the infrastructure and systems that enable a world-class safety culture. This is a strategic role that combines deep EHS technical knowledge with modern data analytics and program management capabilities.
About The Role
- Further the development and implementation of Relativity's EHS Management System aligned with ISO 45001 and ISO 14001 standards, including health and safety minimum standards, SOPs, specifications, and policies that apply across all sites and programs
- Design, build, and manage EHS data systems and analytics platforms in coordination with the Enterprise Applications team: lead requirements definition and implementation of EHS data infrastructure using BigQuery, Confluence, Jira, Power BI, and other data warehouse systems; develop dashboards, metrics, and reporting systems that provide actionable insights on EHS performance, trends, and risks; leverage modern tools (including AI/ML capabilities) to enhance EHS