Substation Project Manager (Northwest Region)

We need to output only HTML fragment, using

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where posting has real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. We need to parse the posting. First paragraph: "At HDR, our employee-owners are fully engaged..." This is about company culture. Could be "About the role"? Actually "About the role" is generic; but we have content about HDR culture, mission, etc. Could be "About the role" or maybe "About HDR". The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those headings if content matches. We have content about HDR's culture and mission; could go under "About the role". We'll include that. Then "HDR Engineering is currently seeking a Substation Project Manager to join our growing and nationally ranked team of Power Delivery professionals. Opportunities are available in these preferred locations: Anchorage, Boise, Billings, Missoula, Portland Seattle, Spokane." This is location info; could be part of "About the role" or maybe separate but we don't have a heading for Locations. We'll embed in About the role. Then "Primary Responsibilities" heading in source. We'll map to

Responsibilities

and list duties. List of duties: "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. The primary duties of a Substation Project Manager include executing and managing all aspects of substation engineering projects, including scope and/or proposal development, project team development and assignment, project execution, quality control, scope, schedule, and budget management, and project closeout. As a Substation Project Manager, your role will encompass the following: 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." We need to turn these into

• items. The text includes sentences separated by periods. We'll split into logical items. Potential items: - Manage Substation projects of all sizes and complexities, domestically and potentially abroad. - Work with design teams to help execute projects. - Execute and manage all aspects of substation engineering projects, including scope and/or proposal development, project team development and assignment, project execution, quality control, scope, schedule, and budget management, and project closeout. - Manage and lead projects and programs throughout the entire life cycle. - Work independently and/or direct, mentor, train, and/or supervise Project Engineers, EITs, Coordinators, Designers, CADD Technicians, and administrative staff. - Provide team member oversight over workload, schedule, quality, utilization, morale, and performance. - Oversee non-engineering components such as public engagement, County/State/Federal agency engagement, permitting, right of way acquisition, and construction management (as applicable). - Lead the QA/QC process per HDR’s Quality Management Systems (QMS) requirements, committing to deliver services and work products that exceed client quality expectations. - Support client management and engage in broader business development activities with existing and target clients in the region and beyond. - Coordinate with Area and Regional leadership and HDR’s Talent Acquisition team to develop a hiring plan to build and grow a group of professionals to meet program and practice needs. - Workshare with staff in multiple offices to execute projects. - Represent HDR to support marketing and proposal development for new opportunities. We'll keep them as list items. Next: "Preferred Qualifications" heading. We'll map to

  Qualifications

  maybe? But we have both Required Qualifications and Preferred Qualifications. The instruction says use headings like Qualifications, Skills, etc. We could combine Required and Preferred under Qualifications, or separate into Requirements and Qualifications? The list includes: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide where to put Required Qualifications vs Preferred Qualifications. Possibly "Requirements" for required qualifications, and "Qualifications" for preferred? Or "Skills" for skills. Let's map: - Required Qualifications ->

  Requirements

  - Preferred Qualifications ->

  Qualifications

  (or maybe Skills). But we also have a list of skills: "Must have the ability to interact with various design teams and have excellent organizational, project management and communication (both written and verbal) skills." That's a skill. Could go under Skills. We also have "Preferred Qualifications" includes: Bachelor’s degree in electrical engineering, related field or equivalent experience. 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. 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 Note: There's some duplication: both required and preferred mention ability to interact etc. We'll keep as is. We need to preserve all substantive info, not invent. We'll create

  Requirements

  with list items for required qualifications. List: - Bachelor's degree in related field - 7 years related experience - Minimum of 2 years project management experience - Ability to interact with various design teams - Excellent organizational, project management and communication (both written and verbal) skills - Attitude and commitment to being an active participant of our employee-owned culture is a must Now

  Qualifications

  for preferred qualifications list: - Bachelor’s degree in electrical engineering, related field or equivalent experience - 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 - Experience with public involvement, environmental permitting, and real estate acquisition (added benefit) - Ability to interact with various design teams and have excellent organizational, project management and communication (both written and verbal) skills Note: Some overlap with required; but we keep. Now Skills: maybe we can extract skills from the text: "excellent organizational, project management and communication (both written and verbal) skills". Also "ability to interact with various design teams". Could be under Skills. But we already have those in qualifications. However we could still create a Skills section if there is distinct skill content not covered elsewhere. The instruction says prefer a few substantive sections over many thin ones. Might be better to combine skills into Qualifications or Requirements. But we have headings list includes Skills; we could include if there is specific skill content. The posting mentions "excellent organizational, project management and communication (both written and verbal) skills" and "ability to interact with various design teams". That's skill-like. We could put under Skills. But we already have those in Requirements and Qualifications; duplication may be okay but we risk thin sections. Perhaps we can omit Skills section and put those under Requirements/Qualifications. The instruction: "Prefer a few substantive sections over many thin ones." So better to not create a Skills section if it would be thin. We'll incorporate skill statements into Requirements and Qualifications. Now Benefits: The posting includes a paragraph: "What We Believe ... Our Commitment ... 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. 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 Benefits and Pay sections. Benefits: list of benefits. Pay: compensation ranges per location. We should not include placeholder like "varies". We have actual numbers. Thus:

  Benefits

  • medical
  • dental
  • vision
  • short and long-term disability
  • life insurance
  • employee assistance program
  • paid time away
  • parental leave
  • paid holidays
  • retirement savings plan with employer match
  • employee referral bonus
  • tuition reimbursement
  Pay: we have multiple location ranges. We'll list each as
• Location: $low - $high
. Locations given: Montana, Spokane, WA, Seattle/Bellevue/Everett, WA, Olympia, WA, Gig Harbor, WA, Vancouver, WA. We'll output each. Schedule: The posting includes "Schedule:Full-time". So we have schedule info. We'll create

Schedule

with

Full-time

or maybe
• Full-time
. Use

for prose. Now About the role: We'll include the initial paragraphs about HDR culture, mission, locations, etc. We need to avoid duplication: The location list appears also later in "Primary Location:United States-Idaho-Boise Other Locations:...". We'll include location info in About the role maybe. We must not include boilerplate like "At HDR, we are committed to the principles of employment equity..." etc. That's EEO; remove. Also remove duplicated lines, navigation, cookie, legal, scam-warning, application instructions. Now we need to ensure we preserve all substantive information. Let's extract all substantive pieces: - Intro about HDR employee-owners, welcoming environment,