Electrical Engineer Power & Renewables

We need to output HTML fragment with sections: About the role? The posting includes introductory paragraphs about HDR culture, mission, etc. That could be "About the role" or maybe "About HDR". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include sections only when posting has real specific content. We need to preserve all substantive information, remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. We need to include sections: maybe "About the role" (intro), "Responsibilities", "Qualifications" (maybe combine Preferred and Required?), "Skills"? The posting includes "Preferred Qualifications" and "Required Qualifications". Could treat as "Qualifications". Also "Benefits" (they list benefits). "Pay" (they give compensation range per location). "Schedule" (Full-time). Also maybe "Location"? Not in list of headings but we could include as part of About? The instruction only mentions those headings; we can add other headings if needed? 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 as examples. Safer to stick to those. We need to output only HTML fragment, no /, no markdown. We need to use

• for any list of duties/requirements/benefits, and

  for prose. We must not repeat job title as heading. No Job ID/requisition numbers as headings. We must not create sections with filler like "commensurate with experience". The posting includes compensation ranges, so we can create Pay section with those ranges. We need to preserve all substantive information: intro paragraphs about HDR culture, mission, Power sector description, responsibilities list, preferred qualifications, required qualifications, benefits, pay ranges, schedule (Full-time), location (maybe we can include in About? Not required but we could include location in a

  under About the role). The instruction says include a section ONLY when posting has real, specific content for it. So we can include About the role (intro), Responsibilities, Qualifications (maybe combine Preferred and Required), Benefits, Pay, Schedule. We need to avoid duplicating lines. Ensure we don't include EEO statement etc. Let's extract content. Intro paragraphs: "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 electricity powers modern life. As part of our Power sector, you’ll help shape how electricity is generated, transmitted and delivered as global energy demands grow. From massive data centers to modernizing transmission systems, our industry-recognized engineers and scientists have been at the forefront of grid transformation for more than a century. You’ll work side-by-side with these experts and contribute to reliable, resilient and sustainable power systems, helping communities thrive and industries expand. This isn’t just a job, it’s a chance to drive infrastructure forward, power innovation and leave your mark on our energy future." We can keep that as prose under About the role. Responsibilities: list under "Primary Responsibilities". Many bullet-like sentences. We'll convert each sentence starting with a verb into

• . Need to preserve all. Let's list responsibilities: - Lead, manage, and coordinate the work of design teams through the schematic design development and contract document phases of projects. - Lead, manage, mentor and develop less experienced electrical engineers and designers. - Coordinate workload to complete the deliverables on schedule. - Be a primary client contact for projects with significant electrical scope. - Conduct field visits at project sites in conjunction with the Project Manager and other disciplines. - Prepare detailed design packages for generation and storage facilities. - Prepare engineering calculations and reports such as load flow, short circuit, grounding and arc flash studies. - Lead and support modification projects include relay protection upgrades, inverter replacements, plant control system upgrades, excitation, governor, and power system upgrades. - Prepare major plant equipment specification for generators, oil-filled and dry-type transformers, medium and low voltage motors, switchgear, inverters, motor control centers, PLC and DCS control systems. - Coordinate power plant electrical engineering design effort with other HDR disciplines and project personnel. - Perform cable, raceway and equipment sizing calculations. - Prepare cable and conduit schedules and routing drawings. - Develop Input and Output (I/O) Lists and interface with the plant control system. - Testing and commissioning plans. - Review of engineering work deliverables following HDR Quality Process. - Lead project teams and provide internal and external technical status updates as needed. - Maintain good relationships with peers, client organizations, vendor representatives and sub-consultants. - Identify and develop new strategic relationships that will support winning and executing assignments for the Power Generation and Renewable team and other groups within HDR. - This position is subject to a preemployment drug test. (maybe include as a note; it's a responsibility? It's a condition. Could include as a
• or maybe in a note. We'll include as a
• .) Now Preferred Qualifications: list: - Master’s degree in Electrical Engineering or similar - Previous proposal development and client management experience - 6 years of related experience, local candidates are preferred - Engineering experience in the following areas: - Engineering design experience for simple/combined cycle gas turbines, renewables, coal and hydroelectric - Electrical powerhouse and balance of plant controls and power systems - Knowledge of large-scale power generation electrical and control systems (medium and low voltage switchgear and motor control centers, diesel generators, UPS systems, VFD’s, PLC’s, Excitation and Governor Systems) - Experience with detailed design for large power generation is highly desirable - Prior experience in a consulting engineering environment is highly desirable - Electrical System Design Software knowledge such as PVsys, PVcase, ETAP, SKM, and / or CDEGS is highly desired - Produce design drawings including one-lines, three-lines, schematics, general arrangements, connection diagrams, raceway drawings, and bill of materials - Experience developing proposals and estimates for Power Generation and Renewable projects - Preference is given to candidates who reside locally - Possess excellent written and verbal communication skills - Occasional travel is required We need to keep as list items. Required Qualifications: - Bachelor's degree in Engineering - Requires professional engineering license recognized by the licensing board for the location of the position offered. Example: Professional Engineer (PE or P.Eng) license. - Previous experience in project execution within the Power Market Sector. - Computer skills in Microsoft Office as well as standard Power Market Sector design software. (examples include PLS CAD, AutoCAD, Plant 3D, AutoPipe, and Revit) - An attitude and commitment to being an active participant of our employee-owned culture We could combine Preferred and Required under Qualifications, maybe separate subheadings? But instruction only allows those headings; we could have a Qualifications section with two sub-sections? Could use

  but not allowed? Probably better to have Qualifications section and within it separate

  for Required and

  for Preferred, each with

  . That's okay. Benefits: list: - medical, dental, vision - short and long-term disability - life insurance - employee assistance program - paid time away - parental leave - paid holidays - a retirement savings plan with employer match - employee referral bonus - tuition reimbursement Also note: "Stated benefits are for full-time regular positions. Temporary and part-time roles eligible for limited benefits." Could include as a

  . Pay: Provide ranges per location: - {Boston, MA}: $97,440 - $139,200 - {Bedford, NH}: $85,260 - $121,800 - {Portland, ME}: $77,140- $110,200 - {Providence, RI}: $85,260 - $121,800 - {Rocky Hill, CT}: $89,320 - $127,600 We should present as list. Schedule: Full-time. Location: Could be included in About the role or maybe not needed. The instruction didn't list Location as a heading; we could include location in a

  under About the role or maybe under a separate heading like "Location". But to be safe, we can include location in About the role paragraph. We must remove boilerplate: EEO statement, "At HDR, we are committed to the principles of employment equity..." etc. Also remove duplicated lines, navigation, cookie, legal, scam-warning, application instructions. Also remove the "Watch Our Story:' https://www.hdrinc.com/our-story'" maybe keep as part of intro? It's a link; we could keep as plain text but it's a URL. Might be considered navigation? It's a link to story; maybe keep as part of intro but it's not essential. 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; could be considered navigation. Safer to remove that line. Also remove "Read further to learn how you could help make great things possible not only in your community, but around the world." That's promotional but okay. We need to preserve all substantive information; the URL maybe not substantive. We'll drop it. Also remove "Primary Location:United States-New Hampshire-Bedford Other Locations:United States-Massachusetts-Boston, United States-Maine-Portland, United States-Connecticut-Rocky Hill, United States-Rhode Island-Providence". This is location info; we could incorporate into About the role as a short sentence: "Primary location: Bedford, NH; other locations: Boston, MA; Portland, ME; Rocky Hill, CT; Providence, RI." That's substantive. Also remove "Industry:Power Schedule:Full-time Employee Status:Regular BusinessClass:Power Generation Job Posting:Sep 17, 2026". That's metadata; we can drop Job Posting date maybe not needed. But schedule we already have; we can keep schedule. We need to ensure we don't repeat job title as heading. No job title appears. Now produce HTML. Structure:

  About the role

  ... intro paragraphs ... plus location sentence.

  Responsibilities

  • ...
  ...

  Qualifications

  Required Qualifications:

  ...

  Preferred Qualifications:

  ...
  Alternatively could have two subheadings but not allowed; we can use

  for headings inside Qualifications. But maybe better to have separate sections: Requirements and Qualifications? The list includes Requirements and Qualifications as examples. Could do Requirements for required, Qualifications for preferred. But we have both required and preferred. Could do Requirements for required, Qualifications for preferred. That matches examples. Let's do:

  Requirements

  (for required)

  Qualifications

  (for preferred) But the instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements