Environmental Compliance & Policy Specialist

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. No Job ID. Remove boilerplate, navigation, EEO, etc. Preserve all substantive info. We need to parse the posting. First paragraph: Seneca Global Services, LLC is part of Seneca Nation Group... includes description of company, benefits, etc. That's about the company and benefits. Could be "About the role"? Actually "About the role" is about the position. The posting includes description of company and benefits before the role. We could treat that as "About the company" but not requested. The headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content. We have a description of the role: "Seneca Global Services, LLC is seeking a full-time Environmental Compliance & Policy Specialist to support the Army environmental portfolio for the Office of the Deputy Assistant Secretary of the Army for Environment, Safety and Occupational Health (ODASA(ESOH)). ..." That is about the role. So we can put that under

About the role

with a paragraph. Then responsibilities list: bullet points after "Responsibilities include, but are not limited to:" We'll put under

Responsibilities

with

• each. Then Basic Qualifications: list of qualifications. Could be under

  Requirements

  or

  Qualifications

  . The posting has "Basic Qualifications:" and then list. Also "Desired Skills:" list. So we can separate: Requirements = Basic Qualifications (mandatory). Qualifications maybe also Basic? Actually they ask for both Requirements and Qualifications sections. We could put Requirements = Basic Qualifications, Qualifications = maybe also Basic? But we need to avoid duplication. Perhaps we treat Requirements as the basic qualifications (must-have) and Qualifications as desired skills? But they also have Skills section. Let's map: - Requirements: Basic Qualifications (education, experience, knowledge, etc.) - Qualifications: maybe also Basic? But we could treat Qualifications as also Basic? Might be redundant. Better: Requirements = Basic Qualifications (mandatory). Qualifications = maybe also Basic? Actually they said "Prefer a few substantive sections over many thin ones." So we could combine Basic Qualifications and Desired Skills into Requirements and Qualifications? Let's think. The headings list includes both Requirements and Qualifications. Usually Requirements = mandatory, Qualifications = preferred or additional. Skills = desired skills. But we have Desired Skills list. So we can assign: - Requirements: Basic Qualifications (education, experience, knowledge, etc.) - Qualifications: maybe also Basic? Hmm. Alternatively, we could treat Requirements as the bullet list under Basic Qualifications, Qualifications as the bullet list under Desired Skills, and Skills as maybe also Desired Skills? But we need Skills section too. Could treat Skills as the Desired Skills list (tools, software). But Desired Skills includes both experience and tools. Could split: Qualifications = Desired Skills (experience), Skills = technical tools (Microsoft Teams, SharePoint, etc.). However the instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should include those headings only if we have content. We have content for About the role, Responsibilities, Basic Qualifications (mandatory), Desired Skills (preferred), Benefits (mentioned earlier), Pay (not specified), Schedule (not specified). Benefits: they mention benefits package earlier in company description: "We offer a comprehensive benefits package that includes medical, dental, vision, life, and disability, voluntary benefit programs (critical illness, hospital, and accident), health savings and flexible spending accounts, and retirement 401K plan." Also mention competitive pay, flexible work-life balance, etc. So we have Benefits content. Pay: they mention "competitive pay" but no specific numbers. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. They do state benefits, so we can include Benefits. Pay: they mention "competitive pay" but that's vague; is that considered stating pay? It says "competitive pay" but no specifics. The instruction says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "competitive pay" is somewhat vague but still a statement. Might be considered filler? It's not a specific number or range. Safer to omit Pay section because it's not specific. Similarly Schedule: they mention full-time, at least 30 hours a week, but not specific schedule. Could be considered schedule info: "Full-time employees working at least 30 hours a week on a regular basis are eligible..." That's about eligibility, not schedule. No explicit schedule like "Monday-Friday, 9-5". So omit Schedule. Thus sections: About the role, Responsibilities, Requirements (Basic Qualifications), Qualifications (Desired Skills?), Skills (maybe technical tools?), Benefits. We need to avoid duplication. Let's extract content. About the role: The paragraph describing the role and its purpose. Responsibilities: list of duties. Basic Qualifications: list: - Bachelor’s degree in environmental science, environmental policy, environmental or civil engineering, natural resources, public policy/administration, or a related field; master’s preferred. - 8–10 years of professional experience in environmental compliance, environmental policy, or federal/DoD environmental program support. - Working knowledge of major environmental programs applicable to DoD installations, including CAA, CWA, RCRA, and TSCA. - Experience developing or substantially revising policy, guidance, SOPs, or comparable official issuances, including comment resolution. - Experience supporting regulatory compliance activities such as reporting, monitoring, inspection/NOV response, or implementation guidance. - Strong written and verbal communication skills; ability to write for senior Army audiences and run working-group discussions. - Proficiency with Microsoft Excel, PowerPoint, and Word. - Ability to obtain a Secret clearance. - Ability to travel as required. Desired Skills: list: - Direct Army or DoW headquarters / command-level environmental policy experience (e.g., AR 200-1 or similar issuances). - Experience with ETMS2 or equivalent HQ tasking systems. - Familiarity with the Army PPBE process and environmental program resourcing. - Experience with underground/aboveground storage tanks, solid waste, or hazardous-waste compliance programs. - Experience tracking or analyzing Notices of Violation, enforcement actions, or enterprise compliance metrics. - Experience with Microsoft Teams, SharePoint, Approvals, Power BI, Visio, and related collaboration tools. We could split Qualifications = Desired Skills (experience) and Skills = technical tools (Microsoft Teams, SharePoint, etc.) but the desired skills list includes both experience and tools. Could separate: Qualifications = experience items (first five bullets), Skills = technical tools (last bullet). However the desired skills list includes "Experience with Microsoft Teams, SharePoint, Approvals, Power BI, Visio, and related collaboration tools." That's a tool experience. Could treat that as Skills. Thus: Qualifications (Desired experience): - Direct Army or DoW headquarters / command-level environmental policy experience (e.g., AR 200-1 or similar issuances). - Experience with ETMS2 or equivalent HQ tasking systems. - Familiarity with the Army PPBE process and environmental program resourcing. - Experience with underground/aboveground storage tanks, solid waste, or hazardous-waste compliance programs. - Experience tracking or analyzing Notices of Violation, enforcement actions, or enterprise compliance metrics. Skills (Technical/tools): - Experience with Microsoft Teams, SharePoint, Approvals, Power BI, Visio, and related collaboration tools. But also Basic Qualifications includes proficiency with Microsoft Excel, PowerPoint, Word. Those could be considered Skills as well. However we already have Skills section for tools; we could include those there too. But to avoid duplication, maybe we keep Skills as the technical tools from both Basic and Desired. But the instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine all skills into one Skills section. But we already have Requirements and Qualifications sections. Could we omit Skills and put tools under Qualifications? But they asked for Skills heading as example; we can include if we have content. Let's see if we have enough content for Skills: we have proficiency with Microsoft Excel, PowerPoint, Word (Basic) and experience with Teams, SharePoint, Approvals, Power BI, Visio (Desired). That's substantive. Thus we can have Skills section covering both. Then Qualifications could be the Desired Skills experience items (excluding tools). Requirements = Basic Qualifications. Thus we have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. Now we need to extract Benefits content: from earlier paragraph: "We offer a comprehensive benefits package that includes medical, dental, vision, life, and disability, voluntary benefit programs (critical illness, hospital, and accident), health savings and flexible spending accounts, and retirement 401K plan." Also earlier: "Your total rewards package includes competitive pay, benefits, and perks, flexible work-life balance, professional development opportunities, and performance and recognition programs." Also "Full-time employees working at least 30 hours a week on a regular basis are eligible to participate in our benefits and paid leave programs." Also "We pride ourselves on our collaborative work environment and culture..." but that's not benefits. We should preserve all substantive info about benefits. So we can combine into a Benefits section with a paragraph listing those. We must not include boilerplate like EEO statement. Remove that. Now produce HTML fragment. Structure:

  About the role

  ...

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...

  Qualifications

  • ...
  ...

  Skills

  • ...
  ...

  Benefits

  ...

  Make sure no extra whitespace? It's fine. Now craft the paragraphs. About the role paragraph: Combine the description: "Seneca Global Services, LLC is seeking a full-time Environmental Compliance & Policy Specialist to support the Army environmental portfolio for the Office of the Deputy Assistant Secretary of the Army for Environment, Safety and Occupational Health (ODASA(ESOH)). The Army issues and maintains environmental policy that installations and commands must implement under statutes such as the Clean Air Act, Clean Water Act, Toxic Substances Control Act, and Resource Conservation and Recovery Act, as well as tank, solid-waste, and related compliance programs. This position provides regulatory research, policy-product development, comment adjudication, tasker management, and coordination so those issuances stay current, consistent, and usable." That's good. Responsibilities list: copy each bullet. Responsibilities include, but are not limited to: then list. We'll produce each as
• . List: - Research and consolidate environmental statutes, regulations, DoD/Army policy, and guidance relevant to the assigned portfolio. - Develop recommendations to update, revise, or rescind Army environmental issuances. - Advise government personnel on structure, format, and staffing of environmental policy products. - Collect, analyze, and adjudicate stakeholder comments on draft policies and guidance; maintain comment matrices and decision records. - Work with Army subject-matter experts through structured comment-resolution processes and incorporate approved changes. - Develop, route, and track ETMS2 tasking packages and related staffing actions. - Prepare working-group agendas and minutes, research summaries, draft guidance, executive briefings, white papers, newsletters, and training materials. - Support annual compliance reporting, Notices of Violation tracking/analysis,