Air Quality Engineer, AWS Environmental

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the job description. First, description: "As an Air Quality Engineer you will play a key role..." etc. That's the overview. Could be "About the role" section. Then "Key job responsibilities" list bullet points. That's responsibilities. Then "A day in the life" maybe part of responsibilities or separate? Could be "About the role" again? Might be considered part of description. But we can treat as part of responsibilities or maybe "About the role". The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content. We have "Basic Qualifications" and "Preferred Qualifications". Those map to Requirements and Qualifications? Usually Basic Qualifications = Requirements, Preferred Qualifications = Qualifications or Skills. But we have separate headings: Requirements, Qualifications, Skills. We need to decide. We have "Basic Qualifications" with bullet points: 5+ years of increasing responsibilities in EHS or environmental programs in manufacturing, production, or service operations experience, or Bachelor's degree - 5+ years with air permitting at local, state (e.g., minor source/synthetic minor source), and federal (e.g. Title V, NSR, PSD) levels That's requirements. "Preferred Qualifications": list bullet points: Experience managing multiple projects and priorities across teams in a fast-paced, deadline-driven environment; Experience that includes strong analytical skills, attention to detail, and effective communication abilities; Experience developing and implementing environmental compliance programs including regulated waste, water, and air regulations in accordance with applicable laws - 3+ years with engine specific regulations including 40 CFR 63 Subpart ZZZZ and 40 CFR 60 Subpart IIII These could be Qualifications or Skills. We could put them under Qualifications. Skills maybe not explicitly listed; but we could combine preferred qualifications into Skills. However we need to avoid thin sections. Perhaps we can have Requirements (Basic Qualifications) and Qualifications (Preferred Qualifications). No separate Skills unless we have explicit skills list. There's no explicit skills list besides those in preferred qualifications. Could treat them as Skills. But we have both Qualifications and Skills headings available; we need to decide which to use. We also have Pay: The posting includes salary ranges for multiple locations: "USA, OH, COLUMBUS - 127,100.00 - 171,900.00 USD annually" etc. That's pay info. So we should include a Pay section with those ranges. Benefits: The posting mentions benefits: "Amazon also offers comprehensive benefits including health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance and option for Supplemental life plans, EAP, Mental Health Support, Medical Advice Line, Flexible Spending Accounts, Adoption and Surrogacy Reimbursement coverage), 401(k) matching, paid time off, and parental leave." Also earlier: "Your Amazon package will include sign-on payments and restricted stock units (RSUs)." So we have benefits content. Schedule: Not mentioned. No schedule info. So we should not include Schedule section. We also have "About The Team" and "Why AWS" etc. Those could be part of About the role or maybe separate sections like "About the team". But only allowed headings are those listed. We could incorporate team info into About the role or maybe omit if not fitting. The instruction: "include a section ONLY when the posting has real, specific content for it". So we need to decide which sections to include: About the role, Responsibilities, Requirements (Basic Qualifications), Qualifications (Preferred Qualifications), Benefits, Pay. Possibly also Skills if we want to separate but we can merge preferred qualifications into Qualifications. We must not repeat job title as heading. Not include Job ID. We must remove boilerplate: EEO, accommodation links, etc. Also remove duplicated lines, navigation, cookie, legal, etc. Also remove application instructions. We need to preserve all substantive information. Thus produce HTML:

About the role

As an Air Quality Engineer you will play a key role in air permitting and air quality compliance for new and existing AWS facilities in the Americas (AMER) region. You will be the environmental representative on behalf of the AWS Environmental Team in AMER responsible for the successful delivery of air permitting projects. You will partner with stakeholders across AWS to develop standards and mechanisms that incorporate air quality permitting into the process of planning, building, and operating data centers. You will manage strategic air quality engineering and air permitting projects and provide regulatory compliance guidance for both design and operations teams. The Air Quality Engineer will also work with internal and external partners that include government entities, AWS regional environmental engineers, consultants, design, construction, operations and other key stakeholders. You will regularly engage with stakeholders; report to AWS Environmental leaders; and ensure risks to air permitting and compliance pathways are being appropriately identified, communicated, and managed. The successful candidate will have a strong track record of air quality engineering solutions and air permitting in North America, the demonstrated ability to deliver multiple high priority projects simultaneously, the ability to drive alignment across teams with competing priorities, and be a strong advocate for air quality compliance and sustainability.

Then responsibilities:

Responsibilities

• Function as a leader for air permitting work in AMER by managing the preparation of air permit applications for new construction, modifications, amendments, and renewals.
• Manage contracts and relationships with environmental consultants and testing firms to complete air permit applications and air dispersion modeling analyses.
• Manage regulatory agency interactions for permit evaluation and processing, and new process and technology introduction.
• Prioritize and manage multiple technically complex assignments concurrently.
• Represent Amazon at appropriate levels with governmental agencies and throughout the company.
• Review environmental permitting requirements for new power generation technologies, including both prime power generation and back up emergency power for data centers.
• Work collaboratively with energy, design engineering, public policy, capacity delivery, real estate, due diligence, and legal teams on large scale projects with undefined scope and drive towards sustainable long term energy supply solutions.

Maybe also include "A day in the life" content as part of responsibilities or as separate? Could add a paragraph under responsibilities summarizing day-to-day. But we already have responsibilities list; we could add a paragraph before list: "This role's primary focus is to function as an environmental air quality engineering leader and implement centralized management systems that support AWS growth and compliance in the Americas. You will work directly with partner teams throughout the data center development lifecycle to encourage sustainable air quality development and design and to ensure compliance with local, state and federal air regulations. Beyond the day-to-day responsibilities, you will monitor and review evolving and emerging air quality permitting/modeling regulations; you may be required to assess impact(s) of regulatory changes to AWS and propose course of action." That is substantive; we should include it. Could be a

after heading before

. Thus responsibilities section: heading

Responsibilities

then a

with day-in-life description, then

list. Now Requirements (Basic Qualifications):

Requirements

• 5+ years of increasing responsibilities in EHS or environmental programs in manufacturing, production, or service operations experience, or Bachelor's degree
• 5+ years with air permitting at local, state (e.g., minor source/synthetic minor source), and federal (e.g. Title V, NSR, PSD) levels
But note the original: "5+ years of increasing responsibilities in EHS or environmental programs in manufacturing, production, or service operations experience, or Bachelor's degree - 5+ years with air permitting at local, state (e.g., minor source/synthetic minor source), and federal (e.g. Title V, NSR, PSD) levels". It seems two bullet points combined with "or". We can split as two items. Now Qualifications (Preferred Qualifications):

Qualifications

• Experience managing multiple projects and priorities across teams in a fast-paced, deadline-driven environment
• Experience that includes strong analytical skills, attention to detail, and effective communication abilities
• Experience developing and implementing environmental compliance programs including regulated waste, water, and air regulations in accordance with applicable laws - 3+ years with engine specific regulations including 40 CFR 63 Subpart ZZZZ and 40 CFR 60 Subpart IIII
Now Benefits:

Benefits

• Health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance and option for Supplemental life plans, EAP, Mental Health Support, Medical Advice Line, Flexible Spending Accounts, Adoption and Surrogacy Reimbursement coverage)
• 401(k) matching
• Paid time off
• Parental leave
• Sign-on payments and restricted stock units (RSUs)
Now Pay:

Pay

• USA, OH, COLUMBUS - $127,100.00 - $171,900.00 USD annually
• USA, TX, Austin - $127,100.00 - $171,900.00 USD annually
• USA, VA, Herndon - $127,100.00 - $171,900.00 USD annually
• USA, WA, Seattle - $127,100.00 - $171,900.00 USD annually
We should preserve the exact numbers as given: "127,100.00 - 171,900.00 USD annually". Could keep as is. We must not include any extra sections like Schedule. We must output only HTML fragment, no markdown fences. Check for any leftover boilerplate: removed EEO, accommodation, etc. Check for duplicated lines: we have not duplicated. Check for any mention of "About The Team", "Why AWS", "Diverse Experiences", "Work/Life Balance", "Inclusive Team Culture", "Mentorship and Career Growth". Those are boilerplate-ish but could be considered substantive? They are generic AWS culture statements. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Those culture sections might be considered boilerplate but not explicitly listed. However they are generic and not specific to the role. The instruction: "Prefer a few substantive sections over many thin ones." Those sections are generic and could be considered thin. Safer to omit them. We already omitted them. Now ensure we didn't miss any substantive info: The description about "The AWS Environmental team is a dynamic team..." that's also generic but maybe substantive about team. Could be included under About the role? Might be considered part of About the role. But we already have About the role covering the role description. The paragraph about AWS Environmental team could be added to About the role as additional detail. Let's see if we should include it: It's about the team, not the role. But we have no "About the team" heading allowed. Could incorporate into About the role as extra context. However the instruction says "include a section ONLY when the posting has real, specific content for it". The content about the team is specific to AWS Environmental team. It's not generic boilerplate; it's describing the team. Could be included under About the role or maybe we could add a separate section "About the team" but not allowed headings. So we could add a paragraph under About the