EHS System Lead
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. We need to preserve all substantive info, remove boilerplate. We have company description, job description, position summary, key responsibilities, key competencies, success measures, qualifications, additional information (benefits, pay range note). We need to extract relevant content. We need to decide sections: About the role (maybe position summary). Responsibilities (key responsibilities). Requirements (maybe qualifications). Qualifications (maybe separate? but we can combine? The instruction says use headings for those categories; we can have both Requirements and Qualifications if distinct. But we can also just have Qualifications. However we need to avoid thin sections. Let's see content: Qualifications section includes Bachelors Degree... plus experience, certification preferred, etc. Also there is "Key Competencies" which could be Skills. So we can have Skills section for key competencies. Benefits: mention comprehensive package of benefits including paid time off, medical/dental/vision insurance and 401(k). Also short-term incentive programs. Pay: there is a note about compensation range but not actual numbers; they say "Applicable only to applicants applying to a position in any location with pay disclosure requirements under state or local law: The compensation range described below is the range of possible base pay compensation..." but they didn't actually give numbers. So we should not create Pay section because no specific numbers. Schedule: not mentioned. So we omit Pay and Schedule. We need About the role: maybe position summary. Provide that. Responsibilities: key responsibilities bullet list. Requirements: maybe qualifications? But we have Qualifications separate. Could treat Requirements as the qualifications (education/experience). But we already have Qualifications heading. To avoid duplication, we could have Requirements as the qualifications and skip Qualifications heading. However instruction says use headings for those categories; we can include both if content distinct. But we have qualifications and also key competencies (skills). So we can have Requirements (education/experience) and Qualifications (maybe certifications?) but they overlap. Better to have Requirements for education/experience, Skills for key competencies, and maybe Qualifications for certifications? But they said "Qualifications" heading. Let's interpret: Requirements = mandatory qualifications (education/experience). Qualifications = preferred or additional qualifications (certifications). However the posting lumps certification as preferred but not required under Qualifications. So we can split: Requirements: Bachelors Degree... plus 5+ years... or Masters plus 3 years. Qualifications: EHS or Engineering professional certification preferred, but not required. Also maybe "Working experience in implementing EHS regulations..." etc could be part of Requirements? Those are abilities. Might be better to put them under Requirements as well. But we need to avoid thin sections. Let's think: We could have sections: About the role (position summary), Responsibilities (key responsibilities), Requirements (education/experience + abilities), Skills (key competencies), Benefits (benefits description). That seems reasonable. We must not repeat job title as heading. No Job ID. We must preserve all substantive information. Let's extract. Company description: Not needed for job posting? Might be considered boilerplate? It's about AbbVie mission. Could be considered part of About the company, but not required sections. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Company description might be considered not boilerplate but could be kept? It's not a standard section heading; we could include it as a
before sections? The instruction says output only HTML fragment; we can include any content as
not under headings. But we should preserve all substantive information. The company description is substantive about AbbVie. We could include it as a
before sections. However they said "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." They didn't forbid other
content. So we can include a brief intro paragraph about AbbVie. But we must remove duplicated lines. There's duplication of "Follow @abbvie onLinkedIn,Facebook,Instagram,XandYouTube." That's social media; maybe considered boilerplate? It's not legal/EEO but could be considered navigation? Might be considered boilerplate; safer to remove. Also "For more information about AbbVie, please visit us atwww.abbvie.com." That's also maybe boilerplate. We'll keep mission statement? Might be okay. But to be safe, we can keep the mission sentence: "AbbVie's mission is to discover and deliver innovative medicines and solutions that solve serious health issues today and address the medical challenges of tomorrow. We strive to have a remarkable impact on people's lives across several key therapeutic areas including immunology, oncology and neuroscience - and products and services in our Allergan Aesthetics portfolio." That's substantive. Now position summary: The paragraph after "Position Summary". We'll put that as
under About the role heading? Actually About the role heading could contain that summary. We'll do
About the role
...position summary...
. Responsibilities: list of key responsibilities. We'll extract each bullet. Key Responsibilities list includes several paragraphs each starting with a bold heading? Actually they are headings: EHS Management System Leadership, Program Ownership Network Leadership, Coaching and Capability Development, Program Maturity and Strategic Improvement, Stakeholder Engagement and Influence, Assurance, Audit and Compliance Support. Each has multiple sentences. We'll turn each into- .
Requirements: education/experience plus abilities. We'll combine: Bachelors Degree (EHS related, Engineering) plus 5+ years of EHS related experience or Masters Degree (EHS related, Engineering) plus 3 years of EHS related experience. EHS or Engineering professional certification is preferred, but not required. (But we may put certification under Qualifications). Also abilities: Working experience in implementing EHS regulations, conducting incident investigations, interacting with regulatory agencies and external organizations and managing cross functional teams; Ability to establish measurable project goals and implementation plans, balance conflicting work demands, and develop action plans including the identification of resource requirements.; Ability to develop standards and/or policies that meet business objectives.; Ability to actively listen, build and maintain effective working relationships with internal/ external colleagues and stakeholders, and resolve conflict constructively.; Ability to successfully manage project and programs.
We'll put those as
- . Skills: Key Competencies list: Strategic EHS Leadership, Change Management, Influencing Without Direct Authority, Program and Project Management, Coaching and Talent Development, Systems Thinking, Stakeholder Engagement, Continuous Improvement, Organizational Capability Building, Data-Driven Decision Making, Communication and Facilitation Skills. We'll list as
- .
Benefits: "We offer a comprehensive package of benefits including paid time off (vacation, holidays, sick), medical/dental/vision insurance and 401(k) to eligible employees. This job is eligible to participate in our short-term incentive programs." We'll put as
under Benefits heading. We must not include Pay section because no specific numbers. We must not include Schedule. We must not include EEO boilerplate etc. Now ensure we don't repeat content. Also remove duplicated lines like "Note: No amount of pay is considered to be wages..." that's legal boilerplate; remove. Also remove "Applicable only to applicants applying to a position in any location with pay disclosure requirements under state or local law: ..." That's pay disclosure note; we might keep as part of Benefits? It's about pay but no numbers; we decided not to include Pay section. Could we include a short
about pay disclosure? The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state compensation range described below is the range of possible base pay compensation... but no actual numbers. It's still pay info but vague. The instruction says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state something about compensation range, but it's not a specific range; it's a description that there is a range but not given. That could be considered placeholder? It says "The compensation range described below is the range of possible base pay compensation that the Company believes in good faith it will pay for this role at the time of this posting based on the job grade for this position." No actual numbers. That's essentially placeholder. So we should not create Pay section. Thus we omit Pay. Now produce HTML. We'll start with a
for company mission maybe. Then
About the role
position summary
. ThenResponsibilities
- ...
Requirements
- ...
Skills
- ...
Benefits
...
Make sure to close tags. Let's craft the position summary text exactly: "The EHS System Lead is responsible for leading the deployment, maturity, integration, and continuous improvement of the North Chicago Manufacturing (NCM) EHS Management System. The role provides governance and oversight for EHS programs aligned to Global EHS Management and Technical Standards while developing a network of EHS Program Leads embedded across the site. Working collaboratively with business leaders, functional experts, and operational teams, the EHS System Lead drives a structured and sustainable approach to EHS program ownership, ensuring clear accountability, effective implementation, and continual advancement of site EHS performance. The role serves as a coach, facilitator, and strategic partner to strengthen EHS capabilities throughout the organization and enable long-term readiness for internal and external assurance activities." Now responsibilities bullets: We'll extract each heading and its sentences. 1. EHS Management System Leadership: "Lead the ongoing development, deployment, and continuous improvement of the NCM EHS Management System. Ensure EHS programs are aligned with applicable Global EHS Management Standards, Technical Standards, corporate requirements, and regulatory expectations. Establish and maintain a structured governance framework for monitoring program health, maturity, effectiveness, and performance. Promote a systems-based approach to EHS program ownership across the organization." 2. Program Ownership Network Leadership: "Lead and coordinate a network of EHS Program Leads from multiple departments and operational functions across the site. Define and communicate roles, responsibilities, and accountability expectations for EHS program owners and process owners. Facilitate cross-functional collaboration to drive consistent implementation and sustainment of EHS programs. Establish communities of practice that encourage shared learning, standardization, and continuous improvement." 3. Coaching and Capability Development: "Coach EHS Program Leads, managers, supervisors, and functional leaders on their responsibilities within the EHS Management System. Translate corporate EHS standards into practical operational expectations that can be effectively implemented in day-to-day activities. Build organizational capability through mentoring, training, workshops, and structured development plans. Support leaders in integrating EHS requirements into business processes, decision-making, and operational routines." 4. Program Maturity and Strategic Improvement: "Develop and maintain the site EHS Program Maturity Roadmap. Manage and coordinate project plans associated with closing gaps against Global EHS Standards and audit findings. Track program maturity, key milestones, actions, and performance indicators to ensure sustained progress. Identify improvement opportunities and implement systematic solutions that strengthen EHS performance and resilience." 5. Stakeholder Engagement and Influence: "Partner with operational leaders to embed EHS ownership into daily management systems. Facilitate leadership reviews and governance forums to communicate program status, risks, priorities, and resource needs. Maintain strong working relationships across all levels of the organization to drive engagement, ownership, and accountability. Influence positive organizational change through collaboration, leadership, and effective communication." 6. Assurance, Audit and Compliance Support: "Support site readiness