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 if posting has real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. We need to preserve all substantive info. Let's parse the posting. Key sections: - Description (intro) – could be "About the role" maybe. - Key job responsibilities – list. - A day in the life – maybe part of responsibilities. - The AWS Environmental team ... – could be "About the team" but there is also "About The Team" later. - About The Team (AWS Infrastructure Services) – separate. - Why Amazon – maybe not needed? It's generic but could be considered "About the role"? Might be considered filler? It's about AWS, not specific to role. Might be considered boilerplate? It's generic marketing. Probably we should omit as it's not specific to role? The instruction: "Prefer a few substantive sections over many thin ones." We can include "About the role" summarizing description. But we must not invent or summarize away detail. We can keep the description paragraphs as

under About the role. - Basic Qualifications – list. - Preferred Qualifications – list. - Benefits – there is a paragraph about benefits: "Amazon also offers comprehensive benefits including health insurance ...". Also mention sign-on payments and RSUs. So we can include Benefits section. - Pay – there is salary ranges listed for multiple locations. So we can include Pay section with those ranges. - Schedule – not mentioned. So omit. - Skills – not explicitly listed; maybe we can infer from qualifications but better not to create unless explicit. The posting does not have a "Skills" heading. So omit. - Requirements – could be combined with Qualifications? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We have Basic Qualifications and Preferred Qualifications. Could map to Requirements (basic) and Qualifications (preferred). Or we could have Requirements (basic) and Qualifications (preferred). Let's do that. Thus sections:

About the role

– include description paragraphs (first paragraph(s) up to "Key job responsibilities").

Responsibilities

– list of responsibilities (the bullet list after "Key job responsibilities"). Maybe also include "A day in the life" as part of responsibilities? Could be separate but it's more description. Could include under Responsibilities as extra paragraphs. But we should not duplicate. We'll include responsibilities list and then maybe a paragraph about day in the life.

Requirements

– Basic Qualifications.

Qualifications

– Preferred Qualifications.

Benefits

– benefits paragraph.

Pay

– salary ranges. We must not include schedule. We must not include boilerplate like EEO, accommodation, etc. We must not include "About The Team" (AWS Infrastructure Services) maybe could be included under About the role? But it's a separate section about team. Could be considered "About the team". However we already have About the role; we could add another section "About the team". The instruction allows any of those headings. It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings but suggests those. Safer to stick to those. The "About The Team" could be considered "About the role"? Might be redundant. But we could include as part of About the role description. We need to preserve all substantive information. The "About The Team" section includes details about AWS Infrastructure Services. That's substantive about the team. If we omit it, we lose info. So we should include it. Perhaps we can include a section "About the team". The instruction didn't forbid other headings, just gave examples. So we can add

About the team

. That seems okay. Similarly "Why AWS" etc maybe not needed. We also have "Diverse Experiences", "Work/Life Balance", "Inclusive Team Culture", "Mentorship and Career Growth". Those are generic Amazon culture sections; could be considered boilerplate? They are not specific to role but still part of posting. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Those sections are not boilerplate per se but are generic Amazon marketing. Might be considered filler but they are substantive? They are not specific to role but still part of posting. The instruction says "Prefer a few substantive sections over many thin ones." So we could omit those generic culture sections to keep sections thin. They are not essential to role. I'd omit them. Thus final sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, About the team. Check if any other substantive content: "The AWS Environmental team is a dynamic team..." that's under "A day in the life" paragraph after responsibilities. That is about the Environmental team. Could be included under About the role or About the team? Actually it's about the Environmental team, not AWS Infrastructure Services. Could be part of About the role. We'll incorporate that paragraph under About the role after the initial description. Now craft HTML. We need to wrap content in appropriate tags:

then

or

• . We must not include or . Let's extract text. About the role: The first paragraph(s) before "Key job responsibilities": "Description 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 after that there is "A day in the life 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. The AWS Environmental team is a dynamic team that is critical to enabling AWS’s growth around the world, as well as ensuring compliance of AWS’s global operations, including physical data centers, as well as other AWS facilities, customer-facing enterprises and products. The Environmental team has responsibility for architecting and implementing AWS’s global environmental programs. This includes defining and implementing risk management and compliance systems and driving their continuous improvement; setting and refining global policies and procedures; overseeing the development of standards, tools, auditing and metrics, and employee training; ensuring effective engagement by environmental teams on global initiatives, including those that are part of Amazon’s ambitious sustainability goals; providing specialist expertise; and engaging with all AWS business units to provide scalable and effective compliance strategies that support current and future business objectives while ensuring compliance with environmental regulations." We can combine these into About the role section as paragraphs. Now Responsibilities: list after "Key job responsibilities". The list: - 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. We'll put each as
• . Now Requirements (Basic Qualifications): - 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 Note: The text: "Basic Qualifications 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 without punctuation. We'll split into two items. Now Qualifications (Preferred 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: paragraph: "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. Learn more about our benefits at https://amazon.jobs/en/benefits." Also earlier: "Your Amazon package will include sign-on payments and restricted stock units (RSUs)." So include that. Now Pay: The salary ranges listed for multiple locations: - 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 can present as list. Now About the team: The section "About The Team About the team AWS Infrastructure Services (AIS) owns the design, planning, delivery, and operation of all AWS global infrastructure. In other words, we’re the people who keep the cloud running. We support all AWS data centers and all of the servers, storage, networking, power, and cooling equipment that ensure our customers have continual access to the innovation they rely on. We work on the most challenging problems, with thousands of variables impacting the supply chain — and we’re looking for talented people who