Substation Project Manager (Northwest Region)

We need to output HTML fragment with sections: headings using

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real content. Remove boilerplate, navigation, EEO, etc. Also remove duplicated lines. Must preserve all substantive info. We need to parse the posting. Let's extract sections: - About the role: The opening paragraph about HDR employee-owners, welcoming environment, diversity, etc. Also the paragraph about each role making a difference, and the statement about HDR Engineering seeking Substation Project Manager. Could be considered "About the role". We'll include that as prose. - Responsibilities: The list under "Primary Responsibilities" and bullet points after "As a Substation Project Manager, your role will encompass the following:" We'll extract those. - Requirements/Qualifications: There's "Preferred Qualifications" and "Required Qualifications". Also "What We Believe", "Our Commitment", "performance, and success, which includes medical, dental..." That's benefits. Also compensation range. - Skills: Might be part of qualifications: ability to interact with design teams, excellent organizational, project management and communication skills. - Benefits: The paragraph about benefits: "Our eight Employee Network Groups..." Actually that's about employee network groups, not benefits. Then later: "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." That's benefits. - Pay: The compensation ranges for various locations. Also "The expected compensation range for this position depends upon skills, experience, education and geographical location." Then list of ranges per location. - Schedule: "Schedule:Full-time" appears near end. Also "Industry:Power Schedule:Full-time Employee Status:Regular". So schedule is Full-time. We need to avoid repeating job title as heading. Also not include Job ID etc. We must not include sections with placeholder text like "commensurate with experience". Not present. We need to output only HTML fragment, no /, no markdown fences. We'll structure:

About the role

... (combined paragraphs)

Responsibilities

• ...
...

Qualifications

maybe combine Required and Preferred? Could separate but we can have one Qualifications section with both required and preferred. But guidelines: use headings for section headings like Qualifications. We'll include Required Qualifications and Preferred Qualifications as subpoints? Could just list them in

. Might be okay. Alternatively separate:

Required Qualifications

and

Preferred Qualifications

. Both are allowed headings? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It lists Qualifications as an example, not Required/Preferred. But we can still use Qualifications heading and include both required and preferred inside. Safer. We'll also have Skills maybe as part of Qualifications; but we could also have a Skills section. However the instruction says prefer a few substantive sections over many thin ones. So we can combine Skills into Qualifications. Benefits: we have benefits paragraph. Pay: compensation ranges. Schedule: Full-time. We'll need to ensure we don't include boilerplate like "At HDR, our employee-owners are fully engaged..." That's about the role. Keep. We must remove duplicated lines: there are repeated sentences about diversity etc. We'll keep unique. Let's extract the About the role text: "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 work to weave diversity, equity, and inclusion into our work and foster a sense of belonging throughout the 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. HDR Engineering is currently seeking a Substation Project Manager to join our growing and nationally ranked team of Power Delivery professionals." We should remove the URL maybe? It's part of content but could be considered boilerplate? It's a link to Our Story. Might be considered navigation? It's a link but it's part of the description. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The URL is not navigation per se but it's a link. Might be okay to keep? Safer to remove the URL as it's like a navigation link. But the instruction says remove navigation boilerplate. The phrase "Watch Our Story:' https://www.hdrinc.com/our-story'" seems like a call to action. Might be considered navigation. I'd remove that sentence or at least the URL. Let's keep the sentence without URL: "Watch Our Story:" maybe still navigation. Better to remove the whole "Watch Our Story:' https://www.hdrinc.com/our-story'". We'll keep the rest. Thus About the role paragraph: combine the sentences before and after. 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 work to weave diversity, equity, and inclusion into our work and foster a sense of belonging throughout the company and within our communities, we constantly ask ourselves: What is our impact on the world? 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. HDR Engineering is currently seeking a Substation Project Manager to join our growing and nationally ranked team of Power Delivery professionals." Now Responsibilities: From "Primary Responsibilities As part of a well-established global Power Delivery practice, you will have the opportunity to manage Substation projects of all sizes and complexities, domestically and potentially abroad. Additionally, you will have the desire to roll up your sleeves and work with the design teams to help execute these projects." Then bullet list after "As a Substation Project Manager, your role will encompass the following:" Let's extract each bullet: - Managing and leading projects and programs throughout the entire life cycle. - Working independently and/or directing, mentoring, training, and/or supervising one or more Project Engineers, EITs, Coordinators, Designers, CADD Technicians, and administrative staff. - Providing team member oversight over workload, schedule, quality, utilization, morale, and performance. - As applicable, being responsible for overseeing non-engineering components of projects and programs, such as public engagement, County/State/Federal agency engagement, permitting, right of way acquisition, and construction management. - Leading the QA/QC process per HDR’s Quality Management Systems (QMS) requirements with a commitment to delivering services and work products that exceed client quality expectations. - Supporting client management and at times engaging in broader business development activities with existing and target clients in the region and beyond. - Coordinating with Area and Regional leadership and HDR’s Talent Acquisition team to develop a hiring plan to help build and grow a group of professionals to meet program and practice needs. - Ability to workshare with staff in multiple offices to execute projects. - Represents HDR to support marketing and proposal development for new opportunities. Note there is a typo "workshare". Keep as is. We'll put each as

. Now Qualifications: Required Qualifications: - Bachelor's degree in related field - 7 years related experience - A minimum of 2 years project management experience - Must have the ability to interact with various design teams, have excellent organizational, project management and communication (both written and verbal) skills - An attitude and commitment to being an active participant of our employee-owned culture is a must Preferred Qualifications: - Bachelor’s degree in electrical engineering, related field or equivalent experience. - A minimum of 2 years of project management experience. - FE, PE license preferred, PMP in lieu of PE. - Experience with or exposure to system projection and planning, communication, distribution, and transmission lines as well as public involvement, environmental permitting, and real estate acquisition are an added benefit. - Must have the ability to interact with various design teams and have excellent organizational, project management and communication (both written and verbal) skills. Note some overlap. We'll combine maybe deduplicate. We'll list required and preferred together maybe with note? But we can just list all items; duplication okay but we could deduplicate. Let's deduplicate: "Bachelor's degree in related field" vs "Bachelor’s degree in electrical engineering, related field or equivalent experience." We'll keep both as separate? Might be redundant. Better to keep both as they convey nuance. We'll keep both. "Minimum of 2 years project management experience" appears both required and preferred; we can keep one. "Must have the ability to interact with various design teams and have excellent organizational, project management and communication (both written and verbal) skills" appears both; keep one. We'll produce a list. Now Benefits: Paragraph: "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 earlier: "Our eight Employee Network Groups (Asian Pacific, Black, Hispanic/Latino(a), LGBTQ+, People with Disabilities, Veterans, Women, Young Professionals) help create a sense of belonging and foster a supportive environment where everyone is empowered to engage and contribute. Each group has an executive sponsor and is open to all employees." That's more about culture, not benefits but could be considered Benefits? Might be considered part of Benefits or Culture. The instruction says Benefits section only if posting actually states them. The network groups are more about culture/employee groups. Could be considered Benefits? Not typical benefits. Safer to not include as Benefits section unless clearly benefits. We'll keep the benefits paragraph only. Now Pay: "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.) {Montana}: $109,000 - $156,000 {Spokane, WA}: $109,000 - $156,000 {Seattle/Bellevue/Everett, WA}: $137,676 - $196,680 {Olympia, WA}: $114,730 - $163,900 {Gig Harbor, WA}: $126,203 - $180,290 {Vancouver, WA}: $120,467 - $172,095" We need to format as list maybe. We'll put in

• each location range. Now Schedule: "Schedule:Full-time" also "Industry:Power Schedule:Full-time Employee Status:Regular". So schedule is Full-time. We'll output a

  maybe under Schedule heading. Now we must not include sections with placeholder text. All good. Now produce HTML:

  About the role

  ...

  Responsibilities

  ...

  Qualifications

  ...

  Benefits

  ...

  Pay

  ...