Senior Air Quality Specialist

We need to output HTML fragment with sections: About the role? The posting includes narrative about HDR, role description, responsibilities, qualifications, benefits, pay, schedule, etc. Must not repeat job title as heading. Use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. Must not include filler like "commensurate with experience". Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate, navigation, legal, EEO, scam-warning, duplicated lines, application instructions. We need to parse the posting. Let's extract content: First paragraph: "At HDR, our employee-owners are fully engaged in creating a welcoming environment where each of us is valued and respected, a place where everyone is empowered to bring their authentic selves and novel ideas to work every day. As we foster a culture of inclusion throughout our company and within our communities, we constantly ask ourselves: What is our impact on the world? Watch Our Story:' https://www.hdrinc.com/our-story' Each and every role throughout our organization makes a difference in our ability to change the world for the better. Read further to learn how you could help make great things possible not only in your community, but around the world. We believe industry drives progress. As part of our Industrial sector, you’ll help shape efficient, advanced infrastructure and environmental stewardship. We partner with clients across industries to responsibly optimize processes, modernize facilities and solve complex challenges. Our work spans the full project life cycle, from up-front evaluation and planning studies through design and into construction monitoring and operations. You can help clients push boundaries and meet evolving industrial demands while supporting resilient infrastructure and responsible growth. This isn’t just a job, it’s a chance to engineer smarter solutions, drive industrial innovation and make a lasting impact." That's about the role/company. Could be "About the role" or "About HDR". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can use "About the role" for that introductory narrative. Next: "In the role of Senior Air Quality Specialist, we'll count on you to:" then list bullet points: - Serve as a technical expert with recognized authority in an area of specialization that resolves problems of greater scope and complexity - Plan and manage all aspects of air quality projects - Work on projects that include PSD, Title V and minor source permitting; air quality modeling; and compliance assistance projects - Develop new clients and expand work with existing clients - Track the financial aspects of projects, and coordinate and adjust the work effort with the team to ensure that the work is completed within the parameters of the agreed-upon schedule - Serve as Project Manager or client manager, establish client relations, and work on marketing and contract solidification as needed - Work with the Business/Accounting Manager or Project Controller and the Department Manager for project reviews, and with company management as needed - Perform other duties as needed These are responsibilities. So we can put under

Responsibilities

with

• each. Next: "Preferred Qualifications" then list: - Master's degree preferred, or PhD in Environmental Sciences, Engineering, or Meteorology or related field of study - Dispersion modeling experience and/or stack testing a plus but not required These are preferred qualifications. Could go under "Qualifications" or "Preferred Qualifications". The headings list includes Qualifications, Skills. We could combine required and preferred under Qualifications? But we have separate Required Qualifications later. Might be better to have sections: Requirements (maybe required), Qualifications (preferred), Skills (maybe skills). However instruction: Use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide mapping. We have Required Qualifications: - Bachelor's degree in Environmental Sciences, Engineering, Meteorology or closely related field - A minimum of 10 years experience in environmental consulting with a successful track record of marketing, project management, staff management and client satisfaction, business development skills, familiarity of local clients and markets. - Advance degree may offset years of experience - Familiarity with air emission methodologies, construction and operating permits, with PSD, Title V, NSPS, MACT, and CAM programs - Proficiency with Microsoft Office programs - Highly motivated self-starter - Leadership skills and ability to manage in a team environment - Excellent communication skills - May require the ability to travel - An attitude and commitment to being an active participant of our employee-owned culture is a must These are requirements/qualifications. Could put under Requirements. Preferred Qualifications could go under Qualifications (or Skills). But we also have Skills heading; we could put specific skills like "Proficiency with Microsoft Office programs", "Leadership skills", "Excellent communication skills", etc. However those are already in Required Qualifications. Might be better to put Required Qualifications under Requirements, Preferred under Qualifications, and maybe Skills under Skills (like technical skills: dispersion modeling, stack testing, air emission methodologies, etc). But we need to avoid duplication. Let's parse: The posting includes "Preferred Qualifications" and "Required Qualifications". We'll create two sections: Requirements (for required) and Qualifications (for preferred). Then Skills maybe for specific technical skills like "Dispersion modeling experience and/or stack testing a plus but not required" (that's preferred). But we could also put that under Qualifications. However we need to avoid empty sections. We'll decide: - About the role: intro narrative. - Responsibilities: bullet list. - Requirements: required qualifications bullet list. - Qualifications: preferred qualifications bullet list. - Skills: maybe we can extract skills like "Proficiency with Microsoft Office programs", "Leadership skills", "Excellent communication skills", "Ability to travel". But those are already in Requirements. Could still list them under Skills but would duplicate. Better to not duplicate. Perhaps we can put Skills for technical skills like "Air emission methodologies, construction and operating permits, PSD, Title V, NSPS, MACT, CAM programs", "Dispersion modeling", "Stack testing". But those are also in qualifications. Might be okay to have Skills section with those specific technical skills, while Requirements covers education/experience/leadership etc. However we must not invent content; we must preserve all substantive info. If we split, we need to ensure we don't lose any info. Let's see if we can allocate: Required Qualifications list includes: - Bachelor's degree... - 10 years experience... - Advance degree may offset years... - Familiarity with air emission methodologies, construction and operating permits, with PSD, Title V, NSPS, MACT, and CAM programs - Proficiency with Microsoft Office programs - Highly motivated self-starter - Leadership skills and ability to manage in a team environment - Excellent communication skills - May require the ability to travel - Attitude/commitment to employee-owned culture Preferred Qualifications list: - Master's degree preferred, or PhD in Environmental Sciences, Engineering, or Meteorology or related field of study - Dispersion modeling experience and/or stack testing a plus but not required Thus we could have: Requirements: education/experience/leadership/communication/travel/culture. Qualifications: preferred education (Master's/PhD) and dispersion modeling/stack testing. Skills: maybe we could list "Proficiency with Microsoft Office programs", "Leadership skills", "Excellent communication skills", "Ability to travel". But those are already in Requirements. Could still list them under Skills but would be duplicate. The instruction says preserve ALL substantive information; does not forbid duplication? It says do not invent or summarize away detail. Duplication is not prohibited but might be considered redundant. Safer to avoid duplication. So we could put Skills as empty? But we must not emit a heading with filler/placeholder text. So we should omit Skills section if we have no unique content not already covered. Similarly Benefits: The posting includes benefits description: "We provide a comprehensive benefits package that promotes employee ownership, employee health, performance, and success, which includes medical, dental, vision, short and long-term disability, life insurance, an employee assistance program, paid time away, parental leave, paid holidays, a retirement savings plan with employer match, employee referral bonus and tuition reimbursement." Also note about temporary/part-time limited benefits. So we can include Benefits section. Pay: The posting includes: "The expected compensation range for this position depends upon skills, experience, education and geographical location. (Stated benefits are for full-time regular positions. Temporary and part-time roles eligible for limited benefits.) Minnesota: $102,606 - $146,580". So we have pay range for Minnesota. So we can include Pay section with that range. Schedule: The posting includes: "Schedule:Full-time Employee Status:Regular". So we have schedule: Full-time. Also Employee Status: Regular. So we can include Schedule section with Full-time. We also have Primary Location etc. That could be considered metadata; we could fold into a short

  or drop. The instruction says do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. So we can include a short paragraph for location maybe under About the role or separate? But we can just include a

  with location info. We must remove boilerplate: EEO, scam-warning, etc. Also remove duplicated lines, navigation, cookie, legal. The posting includes "At HDR, we are committed to the principles of employment equity. We are an Affirmative Action and Equal Opportunity Employer (https://www.hdrinc.com/equal-employment-opportunity-employer). We consider all qualified applicants, regardless of criminal histories, arrest and conviction records." That's EEO boilerplate; remove. Also remove "Watch Our Story:' https://www.hdrinc.com/our-story'" maybe keep as part of About the role? It's a link; we could keep as part of narrative but it's a URL. Might be considered not essential but it's part of the description. The instruction says preserve ALL substantive information; the link is substantive? It's a reference to story; could keep but it's not required. Might be okay to keep as part of About the role. We must not include application instructions. There's none explicit besides maybe "Read further to learn how you could help..." but that's part of narrative. Now construct HTML. We'll start with

  About the role

  then

  containing the introductory narrative (maybe multiple paragraphs). We'll need to preserve the content exactly? Not required to be exact wording but preserve all substantive info. We'll combine sentences. Let's craft:

  At HDR, our employee-owners are fully engaged in creating a welcoming environment where each of us is valued and respected, a place where everyone is empowered to bring their authentic selves and novel ideas to work every day. As we foster a culture of inclusion throughout our company and within our communities, we constantly ask ourselves: What is our impact on the world? Watch Our Story: https://www.hdrinc.com/our-story. Each and every role throughout our organization makes a difference in our ability to change the world for the better. Read further to learn how you could help make great things possible not only in your community, but around the world. We believe industry drives progress. As part of our Industrial sector, you’ll help shape efficient, advanced infrastructure and environmental stewardship. We partner with clients across industries to responsibly optimize processes, modernize facilities and solve complex challenges. Our work spans the full project life cycle, from up-front evaluation and planning studies through design and into construction monitoring and operations. You can help clients push boundaries and meet evolving industrial demands while supporting resilient infrastructure and responsible growth. This isn’t just a job, it’s a chance to engineer smarter solutions, drive industrial innovation and make a lasting impact.

  Then Responsibilities:

  Responsibilities

  • Serve as a technical expert with recognized authority in an area of