Environmental Regulatory Specialist II
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate.
We need to parse the job posting.
Key content:
- Description/Job Summary: includes position description: environmental planning and permitting tasks, preparing NEPA docs, permit applications, agency coordination, coordination with tribes, technical support to public engagement, based in Seattle, WA, assignments nationwide, travel ~10% time.
- Responsibilities/Duties: bullet list (Document Preparation, Permit Application Preparation, Impact Analysis, Coordination with Design Teams, Client Interaction, Agency Coordination, Public Engagement). Each with description.
- Minimum Requirements: list: BA/BS in Environmental Science, Natural Resource Management, Biology, Environmental Planning, or related field. Minimum 4+ years of directly related professional experience. Experience preparing environmental planning documents for NEPA compliance for capital projects. Experience preparing permit applications for Clean Water Act Section 404 and 401 permits for capital projects. Knowledge of Endangered Species Act (ESA) and Migratory Bird Treaty Act and experience supporting ESA Section 7 consultation for capital projects. Expertise in a relevant technical discipline (e.g., ecology, wetlands, fisheries, environmental sciences). Wetlands expertise will be prioritized. Professional competence with Microsoft Office (e.g., Outlook, Word, PowerPoint, Excel, Teams) and SharePoint. Demonstrated ability to learn and adopt new technologies and digital tools to improve project delivery and operational efficiency.
- Desired Qualifications: Working knowledge of CERCLA (Superfund) regulations, environmental cleanup actions, and application of environmental regulations in that context. Experience with ARARs analysis and documentation for CERCLA remediation planning and design. Experience with mitigation planning and implementation for impacts to Waters of the United States (WOTUS). Experience performing field reconnaissance and field data collection. HAZWOPER 40-hour training/8-hour refresher. Experience using generative AI tools (e.g., Microsoft Copilot, ChatGPT, Claude, or similar) to improve technical writing, data analysis, research, visualization, or project delivery efficiency.
- Physical & Environmental Requirements: list: Ability to lift/move/relocate items up to 50 lbs. Repetitive hand motions (typing, tool use, etc.) Ability to see details at close range Ability to see details at a distance Viewing computer screen for extended periods Ability to interpret and analyze visual data (maps, graphs, warning indicators, etc.) Driving a company or personal vehicle Analyzing and synthesizing data Complex problem solving and decision making Reading and interpreting technical documents or regulations Writing reports, proposals, or technical documentation Leading a team or coordinating multiple priorities Communicating effectively with clients, team members, and stakeholders Managing competing deadlines and shifting priorities Work Environment Requirements: Must be able to travel up to 10% per year May work in environments with loud noises, dust, or hazardous materials Must wear appropriate personal protective equipment (PPE) Office and remote work environment.
- Details: Work Schedule: HGL office work is dictated by a 5-day work week; however, fieldwork schedules will deviate based on job requirements and may require longer hours and weekends. Office Type: In-office preferred, hybrid schedule available (3 days in office, 2 days remote) Travel: 10% A favorable pre-hire drug test is required. All positions are subject to a pre-hire education and driving record verification.
- More about HGL and the opportunity: paragraphs about mission, etc. Might be considered boilerplate? It's not strictly boilerplate but could be considered "About the company". The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "More about HGL and the opportunity" is not boilerplate but could be considered company description; we might keep as "About the role" or maybe "About HGL". However the instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. The "More about HGL and the opportunity" is substantive but not about the role. Could be placed under a heading like "About HGL" but we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we could put company info under "About the role"? That heading is for role description. The initial description could be considered "About the role". So we can put the position description under About the role
. Then responsibilities under Responsibilities
. Then requirements under Requirements
. Then desired qualifications under Qualifications
. Skills maybe we could combine some technical skills under Skills? But we have Microsoft Office etc. Could be under Skills. However we already have Requirements includes technical competence. Might be better to separate Skills: maybe list Microsoft Office, SharePoint, generative AI tools, etc. But we have to avoid duplication. Let's think.
We have sections: About the role (summary), Responsibilities (duties), Requirements (minimum), Qualifications (desired), Skills (maybe technical/proficiency), Pay (salary range), Schedule (work schedule, office type, travel). Benefits: not provided specific benefits; only mention "A full list of benefits is available at www.hgl.com/careers/." That's not specific, so we should not create Benefits section.
Pay: we have salary range $67,631 - $98,066. So we can include Pay section.
Schedule: we have work schedule details: 5-day work week, fieldwork may require longer hours and weekends; Office Type: In-office preferred, hybrid schedule available (3 days in office, 2 days remote); Travel: 10%. So we can include Schedule section.
Now we need to output HTML fragment only, no or . Use for headings, - for lists,
for prose.
We must preserve all substantive information, not invent or summarize away detail. Must not include filler like "commensurate with experience". We have none.
We need to ensure we don't repeat job title as heading. We'll not.
We need to remove boilerplate: EEO statements, etc. Remove lines about equal opportunity, accommodation, etc. Also remove "This description is not a comprehensive listing..." maybe that's boilerplate? It's a generic disclaimer; could be considered boilerplate. Might remove. Also remove "A favorable pre-hire drug test is required. All positions are subject to a pre-hire education and driving record verification." That's maybe not boilerplate but could be considered requirements? It's a condition; could be included under Requirements or maybe under Schedule? It's not about schedule. Could be under Requirements as a condition. But it's not a skill or qualification; it's a pre-employment requirement. Could be included under Requirements as a bullet. However the instruction says remove duplicated lines and boilerplate. This is not duplicated but it's a standard requirement; but it's substantive? Might keep.
We also need to remove "Digital & AI Proficiency : HGL encourages the responsible use of approved AI-enabled and digital technologies to improve productivity, technical quality, decision-making, and project delivery. Candidates who demonstrate curiosity, adaptability, and experience leveraging emerging technologies are highly valued." That's similar to desired qualifications about generative AI tools; we already have that. Might be considered boilerplate; but it's about AI proficiency. Could be merged into Qualifications.
We need to avoid duplication.
Let's extract content precisely.
**About the role (position description)**:
"Currently HGL has a position open for an Environmental Regulatory Specialist II to work on environmental planning and permitting tasks for capital development projects. The position will support assignments that involve preparing NEPA documents, preparing applications and supporting materials for federal, state, and local environmental permits, regulatory agency coordination, coordination with tribes, and technical support to public engagement. The position will be based in HGL’s Seattle, WA office, but assignments will span nationwide geographic range. Business travel will be episodically needed and make up approximately 10% of the time for this position. This exciting role will provide opportunities for meaningful involvement in navigating the environmental process for large scale capital projects. The successful candidate will thrive in the role based on their knowledge of the environmental planning process, strategic thinking, ability to innovate, and proven writing skills."
We'll put that as prose under About the role.
**Responsibilities/Duties**:
List items:
- Document Preparation : Write and review NEPA planning documents (e.g., Categorical Exemptions, Environmental Assessments (EAs), and Environmental Impact Statements (EISs), and supporting technical discipline reports (as technically qualified).
- Permit Application Preparation : Prepare environmental permit applications and supporting documents.
- Impact Analysis : Analyze how proposed actions affect the natural environment (e.g., natural resources, wildlife) and the built environment (e.g., infrastructure, communities, economics).
- Coordination with Design Teams : Interface with design engineers and technical specialists to align planning efforts and design efforts to obtain and incorporate information into environmental planning and permitting documents.
- Client Interaction : Participate in meetings with clients as needed to support preparation of environmental planning and permitting documents.
- Agency Coordination : Coordinate with federal, state, and local regulatory agencies and entities to secure environmental permits and approvals for proposed actions.
- Public Engagement : Provide technical support for public engagement actions (e.g., public meetings, public notices, preparing responses to public comments).
We'll make each as
- .
**Minimum Requirements (Requirements)**:
List:
- BA/BS in Environmental Science, Natural Resource Management, Biology, Environmental Planning, or related field.
- Minimum 4+ years of directly related professional experience.
- Experience preparing environmental planning documents for National Environmental Protection Act (NEPA) compliance for capital projects.
- Experience preparing permit applications for Clean Water Act Section 404 and 401 permits for capital projects.
- Knowledge of Endangered Species Act (ESA) and Migratory Bird Treaty Act and experience supporting ESA Section 7 consultation for capital projects.
- Expertise in a relevant technical discipline (e.g., ecology, wetlands, fisheries, environmental sciences). Wetlands expertise will be prioritized.
- Professional competence with Microsoft Office (e.g., Outlook, Word, PowerPoint, Excel, Teams) and SharePoint.
- Demonstrated ability to learn and adopt new technologies and digital tools to improve project delivery and operational efficiency.
- A favorable pre-hire drug test is required.
- All positions are subject to a pre-hire education and driving record verification.
We could also include physical & environmental requirements? Those are more about physical abilities; could be under Requirements or maybe under Skills? But they are not exactly qualifications; they are physical requirements. Could be under Requirements as well. However we have a separate section for Skills maybe. But we have no explicit Skills heading in the list; we could create Skills for things like Microsoft Office, SharePoint, generative AI tools, etc. But we already have those under Requirements. Might be better to keep Requirements as is and not create Skills.
But the instruction says we can use Skills heading if we have real specific content. We have technical skills like Microsoft Office, SharePoint, generative AI tools. However they are already in Requirements and Desired Qualifications. To avoid duplication, we could keep them under Requirements and Qualifications.
**Desired Qualifications (Qualifications)**:
List:
- Working knowledge of CERCLA (Superfund) regulations, environmental cleanup actions, and application of environmental regulations in that context.
- Experience with Applicable or Relevant and Appropriate Requirements (ARARs) analysis and documentation for CERCLA remediation planning and design.
- Experience with mitigation planning and implementation for impacts to Waters of the United States (WOTUS).
- Experience performing field reconnaissance and field data collection.
- HAZWOPER 40-hour training/8-hour refresher.
- Experience using generative AI tools (e.g., Microsoft Copilot, ChatGPT, Claude, or similar) to improve technical writing, data analysis, research,
- for lists,
for prose. We must preserve all substantive information, not invent or summarize away detail. Must not include filler like "commensurate with experience". We have none. We need to ensure we don't repeat job title as heading. We'll not. We need to remove boilerplate: EEO statements, etc. Remove lines about equal opportunity, accommodation, etc. Also remove "This description is not a comprehensive listing..." maybe that's boilerplate? It's a generic disclaimer; could be considered boilerplate. Might remove. Also remove "A favorable pre-hire drug test is required. All positions are subject to a pre-hire education and driving record verification." That's maybe not boilerplate but could be considered requirements? It's a condition; could be included under Requirements or maybe under Schedule? It's not about schedule. Could be under Requirements as a condition. But it's not a skill or qualification; it's a pre-employment requirement. Could be included under Requirements as a bullet. However the instruction says remove duplicated lines and boilerplate. This is not duplicated but it's a standard requirement; but it's substantive? Might keep. We also need to remove "Digital & AI Proficiency : HGL encourages the responsible use of approved AI-enabled and digital technologies to improve productivity, technical quality, decision-making, and project delivery. Candidates who demonstrate curiosity, adaptability, and experience leveraging emerging technologies are highly valued." That's similar to desired qualifications about generative AI tools; we already have that. Might be considered boilerplate; but it's about AI proficiency. Could be merged into Qualifications. We need to avoid duplication. Let's extract content precisely. **About the role (position description)**: "Currently HGL has a position open for an Environmental Regulatory Specialist II to work on environmental planning and permitting tasks for capital development projects. The position will support assignments that involve preparing NEPA documents, preparing applications and supporting materials for federal, state, and local environmental permits, regulatory agency coordination, coordination with tribes, and technical support to public engagement. The position will be based in HGL’s Seattle, WA office, but assignments will span nationwide geographic range. Business travel will be episodically needed and make up approximately 10% of the time for this position. This exciting role will provide opportunities for meaningful involvement in navigating the environmental process for large scale capital projects. The successful candidate will thrive in the role based on their knowledge of the environmental planning process, strategic thinking, ability to innovate, and proven writing skills." We'll put that as prose under About the role. **Responsibilities/Duties**: List items: - Document Preparation : Write and review NEPA planning documents (e.g., Categorical Exemptions, Environmental Assessments (EAs), and Environmental Impact Statements (EISs), and supporting technical discipline reports (as technically qualified). - Permit Application Preparation : Prepare environmental permit applications and supporting documents. - Impact Analysis : Analyze how proposed actions affect the natural environment (e.g., natural resources, wildlife) and the built environment (e.g., infrastructure, communities, economics). - Coordination with Design Teams : Interface with design engineers and technical specialists to align planning efforts and design efforts to obtain and incorporate information into environmental planning and permitting documents. - Client Interaction : Participate in meetings with clients as needed to support preparation of environmental planning and permitting documents. - Agency Coordination : Coordinate with federal, state, and local regulatory agencies and entities to secure environmental permits and approvals for proposed actions. - Public Engagement : Provide technical support for public engagement actions (e.g., public meetings, public notices, preparing responses to public comments). We'll make each as
- . **Minimum Requirements (Requirements)**: List: - BA/BS in Environmental Science, Natural Resource Management, Biology, Environmental Planning, or related field. - Minimum 4+ years of directly related professional experience. - Experience preparing environmental planning documents for National Environmental Protection Act (NEPA) compliance for capital projects. - Experience preparing permit applications for Clean Water Act Section 404 and 401 permits for capital projects. - Knowledge of Endangered Species Act (ESA) and Migratory Bird Treaty Act and experience supporting ESA Section 7 consultation for capital projects. - Expertise in a relevant technical discipline (e.g., ecology, wetlands, fisheries, environmental sciences). Wetlands expertise will be prioritized. - Professional competence with Microsoft Office (e.g., Outlook, Word, PowerPoint, Excel, Teams) and SharePoint. - Demonstrated ability to learn and adopt new technologies and digital tools to improve project delivery and operational efficiency. - A favorable pre-hire drug test is required. - All positions are subject to a pre-hire education and driving record verification. We could also include physical & environmental requirements? Those are more about physical abilities; could be under Requirements or maybe under Skills? But they are not exactly qualifications; they are physical requirements. Could be under Requirements as well. However we have a separate section for Skills maybe. But we have no explicit Skills heading in the list; we could create Skills for things like Microsoft Office, SharePoint, generative AI tools, etc. But we already have those under Requirements. Might be better to keep Requirements as is and not create Skills. But the instruction says we can use Skills heading if we have real specific content. We have technical skills like Microsoft Office, SharePoint, generative AI tools. However they are already in Requirements and Desired Qualifications. To avoid duplication, we could keep them under Requirements and Qualifications. **Desired Qualifications (Qualifications)**: List: - Working knowledge of CERCLA (Superfund) regulations, environmental cleanup actions, and application of environmental regulations in that context. - Experience with Applicable or Relevant and Appropriate Requirements (ARARs) analysis and documentation for CERCLA remediation planning and design. - Experience with mitigation planning and implementation for impacts to Waters of the United States (WOTUS). - Experience performing field reconnaissance and field data collection. - HAZWOPER 40-hour training/8-hour refresher. - Experience using generative AI tools (e.g., Microsoft Copilot, ChatGPT, Claude, or similar) to improve technical writing, data analysis, research,