Risk Assessor II
HydroGeoLogic, Inc. · Overland Park, KS · 3 wk ago
Hybrid$84k–$126k/yrFull-time
We need to output only HTML fragment, no /, no markdown fences. Use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content. Let's parse.
Job Title line is not needed as heading.
We need to include sections:
- About the role: from Description/Job Summary (POSITION DESCRIPTION). That's prose.
- Responsibilities: from Responsibilities/Duties (WHAT YOU'LL BE DOING). List items.
- Requirements: from Minimum Requirements (WHAT YOU NEED TO BE SUCCESSFUL). Likely list.
- Qualifications: from Desired Qualifications (WHAT YOU NEED TO STAND OUT – Preferred, not required). List.
- Skills: maybe from abilities? Could combine but we can create Skills section if there is specific skill content. The posting includes abilities like presenting technical information, ability to succeed fast-paced, ability to learn new tech, etc. Could be considered Skills. We'll include Skills.
- Benefits: The posting mentions "A full list of benefits is available at www.hgl.com/careers/." No specific benefits listed. So we should NOT create Benefits section because no specific content. Also "HGL - WE INVEST IN YOU" mentions career growth opportunities via mentoring, training, education, support for certifications and licenses. That could be considered benefits? It's more about career development. Might be considered Benefits? The instruction: only include section when posting has real, specific content for it. The text mentions career growth opportunities, mentoring, training, education, support for certifications and licenses. That's specific enough? It's not a list of benefits like health insurance, 401k, etc. But it's still specific content about benefits. However the instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state career growth opportunities etc. So we could include Benefits with that content. But we need to decide if it's sufficiently specific. The phrase "A full list of benefits is available at www.hgl.com/careers/" is a reference but not listing. The "HGL - WE INVEST IN YOU" paragraph describes career growth opportunities etc. That could be considered benefits. I'd include Benefits section with that paragraph.
- Pay: The posting includes salary range: "The annual salary for this position ranges from $83,895.00 - $125,843.00." That's specific. So include Pay section with that sentence.
- Schedule: The posting includes "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: Hybrid (3 days in office) Travel: Minimal but as needed to client facilities; percentage varies by project assignment." That's specific. So include Schedule section.
We must not repeat job title as heading. Also not include Job ID etc.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should omit the EEO notices, equal opportunity statements, etc. Also omit "A favorable pre-hire drug test is required..." maybe that's not boilerplate? It's a requirement but could be considered part of Requirements? It's a condition. Might be included in Requirements? But it's not a typical qualification. Could be included as a separate bullet under Requirements? The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we should keep that line somewhere. Where? Could be under Requirements as a bullet? It's not a qualification but a condition. Could be under Requirements as a bullet: "A favorable pre-hire drug test is required." Also "All positions are subject to a pre-hire education and driving record verification." That's also a condition. We'll include those under Requirements.
Also "Digital & AI Proficiency: ..." is a paragraph about encouraging AI use. Could be under Skills or Qualifications? It's more about desired skill/experience. Could be under Qualifications as bullet: "Experience using generative AI tools ...". Already there is a bullet about generative AI in Desired Qualifications. So we can keep that.
We need to avoid duplication: The Desired Qualifications already includes "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." So we keep that.
Now we need to format.
Sections:
inside
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content. Let's parse.
Job Title line is not needed as heading.
We need to include sections:
- About the role: from Description/Job Summary (POSITION DESCRIPTION). That's prose.
- Responsibilities: from Responsibilities/Duties (WHAT YOU'LL BE DOING). List items.
- Requirements: from Minimum Requirements (WHAT YOU NEED TO BE SUCCESSFUL). Likely list.
- Qualifications: from Desired Qualifications (WHAT YOU NEED TO STAND OUT – Preferred, not required). List.
- Skills: maybe from abilities? Could combine but we can create Skills section if there is specific skill content. The posting includes abilities like presenting technical information, ability to succeed fast-paced, ability to learn new tech, etc. Could be considered Skills. We'll include Skills.
- Benefits: The posting mentions "A full list of benefits is available at www.hgl.com/careers/." No specific benefits listed. So we should NOT create Benefits section because no specific content. Also "HGL - WE INVEST IN YOU" mentions career growth opportunities via mentoring, training, education, support for certifications and licenses. That could be considered benefits? It's more about career development. Might be considered Benefits? The instruction: only include section when posting has real, specific content for it. The text mentions career growth opportunities, mentoring, training, education, support for certifications and licenses. That's specific enough? It's not a list of benefits like health insurance, 401k, etc. But it's still specific content about benefits. However the instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state career growth opportunities etc. So we could include Benefits with that content. But we need to decide if it's sufficiently specific. The phrase "A full list of benefits is available at www.hgl.com/careers/" is a reference but not listing. The "HGL - WE INVEST IN YOU" paragraph describes career growth opportunities etc. That could be considered benefits. I'd include Benefits section with that paragraph.
- Pay: The posting includes salary range: "The annual salary for this position ranges from $83,895.00 - $125,843.00." That's specific. So include Pay section with that sentence.
- Schedule: The posting includes "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: Hybrid (3 days in office) Travel: Minimal but as needed to client facilities; percentage varies by project assignment." That's specific. So include Schedule section.
We must not repeat job title as heading. Also not include Job ID etc.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should omit the EEO notices, equal opportunity statements, etc. Also omit "A favorable pre-hire drug test is required..." maybe that's not boilerplate? It's a requirement but could be considered part of Requirements? It's a condition. Might be included in Requirements? But it's not a typical qualification. Could be included as a separate bullet under Requirements? The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we should keep that line somewhere. Where? Could be under Requirements as a bullet? It's not a qualification but a condition. Could be under Requirements as a bullet: "A favorable pre-hire drug test is required." Also "All positions are subject to a pre-hire education and driving record verification." That's also a condition. We'll include those under Requirements.
Also "Digital & AI Proficiency: ..." is a paragraph about encouraging AI use. Could be under Skills or Qualifications? It's more about desired skill/experience. Could be under Qualifications as bullet: "Experience using generative AI tools ...". Already there is a bullet about generative AI in Desired Qualifications. So we can keep that.
We need to avoid duplication: The Desired Qualifications already includes "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." So we keep that.
Now we need to format.
Sections:
About the role
... prose from POSITION DESCRIPTION ...
We need to preserve all substantive information from that paragraph. Let's extract: "HGL is seeking a Risk Assessor II to support environmental projects, including hazardous, toxic, and radioactive waste; PFAS; mining; and military munitions response program projects nationwide. The Risk Assessor II will prepare human health risk assessments and/or ecological risk assessments in accordance with CERCLA, RCRA, and applicable state guidance, with support from HGL’s risk assessment team, including senior- and principal-level staff. The ideal candidate can lead both human health and ecological risk assessments; candidates with strong experience in either discipline will also be considered. This role is well suited for a self-directed individual who enjoys integrating complex environmental data, technical analysis, and regulatory requirements to support sound project and remedial decisions. HGL is seeking to fill one hybrid position based out of one of the following HGL office locations: Phoenix, AZ; Merritt Island, FL; Overland Park, KS; Billings, MT; or Ballston Lake, NY." We should keep that as a single. Now Responsibilities: list items from "WHAT YOU'LL BE DOING". Let's extract each bullet: - Manage and analyze large environmental datasets. - Prepare tables, figures, and other data exhibits. - Author risk assessments, risk assessment work plans, and other technical deliverables. - Review and interpret environmental and toxicological studies and reports. - Support remedial strategy design, including development of risk-based cleanup levels. - Conduct statistical analyses, including statistical comparisons of background data to site data. - Serve as the project risk assessor in project meetings and technical discussions with clients, regulatory agencies, and stakeholders. - Lead and provide technical direction to junior-level staff. We'll put each as
- .
Now Requirements (Minimum Requirements): list items from "WHAT YOU NEED TO BE SUCCESSFUL". Let's extract:
- Bachelor’s degree in toxicology, environmental science, public health, engineering, or a related health or environmental science discipline.
- At least 6 years of work experience in an environmental consulting or regulatory environment on DoD or EPA projects, with a focus on site investigation and human health or ecological risk assessment; or an equivalent combination of education and experience.
- Experience implementing EPA’s Risk Assessment Guidance for Superfund and/or EPA’s Ecological Risk Assessment Guidance for Superfund.
- Working knowledge of relevant federal regulations, especially CERCLA and RCRA, and the ability to integrate federal requirements with varying state regulations.
- Ability to present technical information effectively to scientific, regulatory, and public audiences.
- Ability to succeed in a fast-paced consulting environment, manage multiple project assignments, meet strict deadlines, travel to client facilities as needed, and work independently as a self-starter.
- 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'll include those as list items.
Now Qualifications (Desired Qualifications): list items from "WHAT YOU NEED TO STAND OUT – Preferred, not required". Extract:
- Advanced degree (MS, MPH, or PhD) in toxicology, environmental science, public health, engineering, or a related health or environmental science discipline.
- Experience completing statistical comparisons of site data to background data and geochemical evaluations to distinguish site-related contaminants from background constituents.
- Experience in technical areas beyond risk assessment—such as contaminant fate and transport, analytical chemistry, characterization of the nature and extent of contamination, or development of remediation strategies—to support integration across project teams.
- Experience designing and leading baseline ecological risk assessments that include collection of site-specific data, such as biota tissue, toxicity testing, bioaccumulation studies, or habitat and/or species surveys.
- Experience in blood lead modeling to support human health risk assessments.
- Familiarity with environmental databases, primarily LOCUS, and statistical software.
- 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.
Now Skills: we could extract abilities like presenting technical information (already in Requirements), ability to succeed fast-paced (also in Requirements), ability to learn new tech (also in Requirements). Might be redundant. Perhaps we can combine those into Skills section but we already have them in Requirements. To avoid duplication, maybe we don't need a separate Skills section; we can omit if content overlaps. The instruction: prefer a few substantive sections over many thin ones. So we could omit Skills if its content is covered elsewhere. However the instruction says to use section headings for Skills if there is real specific content. Since we already have those abilities in Requirements, we could still include Skills but risk duplication. Better to omit Skills section.
Now Benefits: we have "HGL - WE INVEST IN YOU" paragraph: "It’s not just a job, it’s your career. HGL provides career growth opportunities via mentoring, training, education, and support for your certifications and licenses. Achieve your career goals and help HGL achieve its mission of restoring the environment to beneficial use for our clients and communities." Also "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 could be considered benefits? It's more about culture and AI encouragement. Might be considered Benefits? The instruction: only include section when posting has real, specific content for it. This is specific enough. We'll include Benefits section with those two paragraphs combined maybe as
- ... ...
- ... ...
- ... ...
. But we must ensure we don't include boilerplate like EEO etc. We'll omit those. Now Pay: include the salary range sentence. Now Schedule: include the work schedule, office type, travel. Let's extract schedule 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: Hybrid (3 days in office) Travel: Minimal but as needed to client facilities; percentage varies by project assignment." We'll put that as a
. Now ensure we don't include any navigation/footer etc. Now produce HTML fragment:
About the role
...
Responsibilities
Requirements
Qualifications
Benefits
...
Pay
The annual salary for this position ranges from $83,895.00 - $125,843.00.
Schedule
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: Hybrid (3 days in office) Travel: Minimal but as needed to client facilities; percentage varies by project assignment.
Check for any duplicated content: Ensure we didn't include the location list in About the role? Already there. Good. Now ensure we didn't include any EEO etc. We removed. Now output only HTML fragment.