Environmental Lawyer

We need to output only HTML fragment, no html/body tags, no markdown fences. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only if posting has real specific content. Let's parse. Job title: Environmental Lawyer at Axiom. Not to repeat as heading. Location: Remote. We need sections: - About the role: maybe a paragraph describing role. The posting includes description: "We are seeking a Environmental Lawyer to support our client, a large industrials company. In this role, you will support end-of-life asset portfolio matters, including environmental remediation, well abandonment, site cleanup, site restoration, and legacy environmental liabilities. The immediate focus will be on U.S. upstream and downstream matters, with the potential for the scope to expand to international matters. This role requires a remediation-focused environmental lawyer with significant hands-on experience who can provide effective counsel with little to no training. Direct environmental remediation and asset retirement experience is critical." That's about the role. So we can have

About the role

with

containing that. - Responsibilities: list bullet points. The posting lists responsibilities after "Responsibilities:" with bullet points (each line). We'll create

• for each. - Qualifications: after "Qualifications:" list bullet points. We'll create
  • . - Preferred Skills: after "Preferred Skills:" list bullet points. Could be Skills section. - Compensation: after "Compensation:" includes paragraph about estimated total compensation range and benefits. This is Pay and Benefits. We need separate sections for Pay and Benefits only if posting actually states them. It does state compensation range and mentions benefits. So we can have Pay section with the compensation range paragraph. Benefits section with benefits list. - About Axiom: maybe not required heading; but we could include About the company? Not in list of allowed headings. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About Axiom" is not allowed; we should not create a heading for it. However we could fold that info into About the role? But it's about company, not role. The instruction: "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples; we could also use other headings? Probably we should stick to those. The instruction: "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings when appropriate. It doesn't forbid other headings, but better to stick to those. The "About Axiom" could be considered "About the role"? Not exactly. Might be better to omit that section, as it's not required. However we must preserve ALL substantive information; do not invent or summarize away detail. If we omit About Axiom, we lose substantive info about the company. But maybe we can incorporate into About the role? The instruction says "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it." About Axiom is not minor metadata; it's substantive. But we don't have a heading for it in allowed list. Could we use "About the role" to also include company info? That might be stretching. 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". So we need to decide. Maybe we can treat "About Axiom" as "About the role" because it's about the role within the company? Not ideal. Alternatively, we could create a custom heading like "About Axiom" but the instruction says use

    for section headings (e.g. About the role, Responsibilities...). The "e.g." suggests those are examples, not exhaustive. So we could use other headings as needed, but we should follow the pattern. Safer to include "About Axiom" as a heading

    About Axiom

    . It's not prohibited. The instruction didn't forbid other headings; just gave examples. So we can include it. Similarly, we might need "Schedule" if posting mentions schedule? Not present. So we omit Schedule. We also need "Requirements" heading? The posting has Qualifications and Preferred Skills. Could treat Qualifications as Requirements? But we have both Qualifications and Skills headings allowed. We'll use Qualifications for the required qualifications, and Skills for preferred skills. We also need "Requirements" maybe not needed. We'll include:

    About the role

    ...

    Responsibilities

    ...

    Qualifications

    ...

    Skills

    ...
    (for Preferred Skills)

    Pay

    ... compensation range ...

    Benefits

    ...
    (list benefits: health, dental, vision insurance; paid holidays and PTO; flexible work arrangements; professional development opportunities and tools) We might also include "About Axiom" as separate heading. But we need to avoid duplication: The posting also includes "About Axiom:" paragraph. We'll include that. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The posting includes a lot of EEO statement at the end. We must remove that. Also remove "Learn more about life at Axiom." maybe considered boilerplate? It's promotional but maybe substantive? It's about Axiom; could be considered part of About Axiom. But the instruction says remove EEO/equal-opportunity/scam-warning boilerplate. The EEO statement is at the end: "Axiom ensures equal employment opportunity..." etc. We'll remove that entire block. Also remove "Upon request and consistent with applicable laws..." accommodation statement? That's also EEO-related? Might be considered boilerplate; but it's about accommodations. Might be considered legal boilerplate; but it's not EEO exactly. However it's still legal statement. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So legal boilerplate includes accommodation statement, privacy notice, background check, etc. We should remove those. Also remove "Learn more about life at Axiom." maybe not legal but promotional; could keep as part of About Axiom? Might be considered fluff but it's substantive about company. I'd keep it as part of About Axiom. We need to preserve all substantive information: role description, responsibilities, qualifications, preferred skills, compensation, benefits, and maybe company overview (About Axiom). We'll keep that. Now craft HTML. Let's extract details. About the role paragraph: We'll combine the sentences: "We are seeking a Environmental Lawyer to support our client, a large industrials company. In this role, you will support end-of-life asset portfolio matters, including environmental remediation, well abandonment, site cleanup, site restoration, and legacy environmental liabilities. The immediate focus will be on U.S. upstream and downstream matters, with the potential for the scope to expand to international matters. This role requires a remediation-focused environmental lawyer with significant hands-on experience who can provide effective counsel with little to no training. Direct environmental remediation and asset retirement experience is critical." That's the about role. Responsibilities list: - Advising internal site-management teams and outside counsel on environmental liability, cleanup strategy, remediation actions, and responses to environmental agencies. - Providing legal guidance on asset retirement and environmental remediation matters involving CERCLA, RCRA, and applicable state cleanup requirements. - Supporting end-of-life portfolio matters, including wells, site cleanup, site restoration, and legacy environmental liabilities. - Engaging with environmental regulatory agencies and advising on agency responses and remediation requirements. - Managing environmental legal issues related to U.S. upstream and downstream assets. Qualifications list: - 8+ years of experience practicing environmental law, with a focus on remediation and asset retirement. - Hands-on remediation experience and the ability to handle matters with little to no training. - Strong knowledge of CERCLA, RCRA, and state cleanup requirements. - Proven experience advising on environmental liability, cleanup strategy, and remediation actions. - Juris Doctor degree or equivalent and licensed to practice law in an applicable jurisdiction. Preferred Skills list: - Experience with underground storage tanks and gas-station cleanups. - Experience with well abandonment and site restoration. - Experience handling environmental matters in California, New Mexico, Texas, and/or Washington. Pay paragraph: "The estimated total compensation for full-time Axiom attorney roles is $104,500-325,000 per year and for non-attorney roles is $71,250-309,750 per year. Compensation decisions are based on various factors, including, but not limited to, experience, skills, certifications, location, and business needs." We could keep that as is. Benefits list: - health, dental, and vision insurance - paid holidays and PTO - flexible work arrangements - professional development opportunities and tools We could phrase as list items. About Axiom paragraph: We'll include the descriptive paragraph about Axiom (the long one) but we need to remove EEO boilerplate etc. The About Axiom section includes: "For over 25 years, Axiom has pioneered the alternative legal services industry, now serving more than 1,500 legal departments globally with our unique blend of world-class legal talent and advanced AI tools, delivering innovative solutions ranging from that combine top-tier talent with cutting-edge technology. We tackle complex legal matters across 12 practice areas for clients ranging from Fortune 100 to SMBs, empowering our legal professionals to engage in meaningful work that advances their careers. Our Talent NPS score of +71% and our Client NPS score of +64% highlight our commitment to excellence (Reported scores were Axiom’s average for 2025 – the legal industry average NPS score is +35%). Join our forward-thinking community where you’ll keep your career dynamic and multi-faceted, be part of a company that values agility, collaboration, and excellence, and love both the law and your life.Learn more about life at Axiom. Axiom is the global leader in high-caliber, on-demand legal talent. Covering North America, the UK, Europe, and APAC, we enable legal departments to drive efficiency and growth and meet the demands of today’s business landscape with best in class alterative legal services. Diversity is core to our values and we are proud to be an equal opportunity employer." We need to remove the EEO statement at the end? Actually the sentence "Diversity is core to our values and we are proud to be an equal opportunity employer." is EEO-related but maybe considered part of About Axiom. The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. That sentence is EEO boilerplate. So we should remove it. Also remove the later EEO block after that (the long list). So we will keep the About Axiom description up to before the EEO statement. Also remove "Learn more about life at Axiom." maybe keep? It's not EEO. It's a call to action; maybe considered promotional but not boilerplate. We'll keep it. Thus About Axiom paragraph: "For over 25 years, Axiom has pioneered the alternative legal services industry, now serving more than 1,500 legal departments globally with our unique blend of world-class legal