Senior Project Manager - Electrical Utilities

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must remove boilerplate, navigation, EEO, etc. Must preserve all substantive info. We need to parse the posting. Content: - Intro: "The Senior Project Manager is responsible for the end-to-end execution of capital projects within electric utility systems, including transmission, distribution, and substation assets. This role leads delivery from project initiation through commissioning, with a strong emphasis on technical execution, constructability, cost and schedule control, and risk management. This is a hybrid role. As a Senior Project Manager, you will be at the center of electric utility project delivery, developing and executing comprehensive project plans that define scope, objectives, deliverables, milestones, and timelines. You will translate engineering design into safe, efficient, and executable field work, coordinating engineers, technicians, contractors, equipment, and materials to ensure construction readiness and seamless project progression. You will provide technical guidance throughout the project lifecycle, driving alignment between engineering, procurement, and construction to ensure high-quality outcomes. A key focus of this role is maintaining strict control over budget and schedule, including monitoring expenditures, forecasting performance, and proactively addressing risks or deviations. Strong client engagement is essential, you will establish clear communication channels, understand client requirements, provide transparent updates, and resolve issues quickly and effectively. The ideal candidate brings deep utility project experience and a proven ability to deliver technically complex projects safely, on time, within budget, and in compliance with regulatory requirements." That's about role and responsibilities. Then "Qualifications" list: - Bachelor’s degree from an accredited college or university - Previous experience in electrical engineering, project management, or a related role - 10 years experience or greater - Transmission line and/or Substation experience needed - Experience with electrical utilities, electrical system design, installation, and maintenance projects - Proven experience managing capital projects, programs, or portfolios - Strong understanding of utility project lifecycle (stage gate processes, planning, engineering, construction, commissioning) - Experience with project controls (cost, schedule, reporting) - Demonstrated ability to manage cross-functional teams and multiple stakeholders - PMP certification is a plus, but not required Then "Execution Focus: ..." bullet list of competencies (maybe Skills). Those are: - Execution Focus: Drives projects forward with urgency, accountability, and disciplined follow-through - Problem Solving: Anticipates challenges and resolves issues before they impact delivery - Field Orientation: Comfortable operating in both office and construction environments - Communication: Clear, direct communicator with the ability to engage technical and non-technical stakeholders - Curious and active listener: You have a deep hunger to learn, coupled with a willingness to think outside the box. You ask a lot of questions. You recognize there is a difference between “hearing” and “listening. - Resilient and self-motivated: You are always striving to build upon previous successes - Detail oriented: The little things matter! - Collaborative: When we all succeed, we’re better for it! Then "Not quite right for you? For a full listing of all our openings, please visit us at: https://entrustsol.com/careers/" - that's navigation, remove. Then "Why Join Us?" paragraph about company, maybe not needed? It's generic but could be considered "About the company". Not requested sections; we can ignore or maybe include as part of About the role? Probably not needed; we can drop as it's fluff but still substantive? It's about company culture; but we are told to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Why Join Us?" is not boilerplate but maybe considered marketing fluff. The instruction: "Prefer a few substantive sections over many thin ones." We could include a section "About the company" but not in list of allowed headings. Allowed headings are limited to those listed. So we should not add extra headings. So we can incorporate that info into maybe "About the role"? But it's not about role. Might be better to omit because not requested. The instruction: "include a section ONLY when the posting has real, specific content for it". So we can decide to not include sections that aren't clearly mapped. The "Why Join Us?" is not about role, responsibilities, qualifications, skills, benefits, pay, schedule. So we can omit. Then "What We Offer" paragraph: supportive environment, opportunities for growth, competitive salary and comprehensive benefits package, etc. Then "Benefits & Salary" section with pay range and benefits details. We need to extract Benefits and Pay. Pay: "$120,000 and $150,000 annually". Benefits: list: company sponsored medical, dental, vision, 401(k) with match, tuition reimbursement, voluntary life, disability, critical illness, accident and hospitalization plans. HSA or FSA medical accounts and FSA dependent care and transportation/parking accounts also available. Full time employees eligible to earn PTO hours. May be eligible for discretionary bonus. Schedule: Not explicitly mentioned except "hybrid role". That's schedule info: hybrid (some remote, some onsite). Could be considered schedule. The posting says "This is a hybrid role." That's schedule info. So we can include Schedule section with that. Also "Full time employees" indicates full-time. Thus we have sections: - About the role (maybe combine intro and responsibilities) - Responsibilities (maybe separate) - Qualifications (list) - Skills (the Execution Focus bullet list) - Benefits - Pay - Schedule We must not repeat job title as heading. Use

for each section heading. We need to use

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

  for prose. We must preserve all substantive information; do not invent or summarize away detail. We need to ensure we don't include filler like "commensurate with experience". Not present. We need to remove duplicated lines. Let's craft. First, About the role: maybe a paragraph summarizing role: "The Senior Project Manager is responsible for the end-to-end execution of capital projects within electric utility systems, including transmission, distribution, and substation assets. This role leads delivery from project initiation through commissioning, with a strong emphasis on technical execution, constructability, cost and schedule control, and risk management. This is a hybrid role." That's prose. Responsibilities: list of duties: developing and executing comprehensive project plans that define scope, objectives, deliverables, milestones, and timelines; translating engineering design into safe, efficient, and executable field work, coordinating engineers, technicians, contractors, equipment, and materials to ensure construction readiness and seamless project progression; providing technical guidance throughout the project lifecycle, driving alignment between engineering, procurement, and construction to ensure high-quality outcomes; maintaining strict control over budget and schedule, including monitoring expenditures, forecasting performance, and proactively addressing risks or deviations; establishing clear communication channels, understanding client requirements, providing transparent updates, and resolving issues quickly and effectively. We can put as

  • . Qualifications: list as above. Skills: list the Execution Focus items. Benefits: list as above. Pay: maybe a

    stating salary range. Schedule: mention hybrid role and full-time. We must not include headings for empty sections. Let's produce HTML. Check for any boilerplate: remove "Not quite right for you? For a full listing of all our openings, please visit us at: https://entrustsol.com/careers/" remove. Remove "Why Join Us?" and "What We Offer" paragraphs (they are somewhat generic but contain some info about benefits etc. However we already captured benefits and pay from "Benefits & Salary". The "What We Offer" includes supportive environment, opportunities for growth, competitive salary and comprehensive benefits package. Some of that is already covered; but we might lose "supportive and inclusive work environment that values diversity and encourages innovation. Opportunities for professional growth and career development." That's substantive but not covered elsewhere. Should we include? Could be part of Benefits? Not exactly benefits but company culture. There's no section for culture. Could we incorporate into About the role? Might be okay to add a short paragraph under About the role? But that would be mixing. The instruction: "Prefer a few substantive sections over many thin ones." We could add a section "About the company" but not allowed headings. So maybe we can incorporate that into Benefits? Not ideal. However the instruction says "include a section ONLY when the posting has real, specific content for it". It doesn't forbid adding extra sections beyond the listed headings? It says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies we should use those headings if we have content. It doesn't explicitly forbid other headings, but likely they want only those. Safer to stick to those. Thus we may lose some culture info. But maybe it's considered boilerplate? It's not boilerplate but still generic. However it's substantive. The instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." So we must preserve that info. If we cannot add a section for it, we need to incorporate it into existing sections without losing info. Could add a paragraph under Benefits about "supportive and inclusive work environment..." but that's not a benefit per se. Could add under About the role? Might be okay to add a short paragraph about company culture under About the role? That might be stretching. Alternatively, we could create a section "About the company" but not in the list; risk of being marked wrong. The instruction says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exhaustive. So we could add other headings if needed. But they also say "Prefer a few substantive sections over many thin ones." So we could add a section "Company Overview" if needed. However they'd likely expect us to stick to the given headings. The safest is to incorporate culture into Benefits or About the role as a prose paragraph. Let's add a paragraph under Benefits about "We foster a culture where innovation, collaboration, and continuous improvement are expected..." Actually that's from "Why Join Us?" paragraph. We'll incorporate that into Benefits as a prose paragraph before the list. Similarly "Opportunities for professional growth and career development." could be under Benefits as well. Thus Benefits section will have prose describing culture and growth, then a list of specific benefits. Pay section: just salary range. Schedule section: mention hybrid role and full-time. Now ensure we don't repeat any info. Let's craft. HTML:

    About the role

    The Senior Project Manager is responsible for the end-to-end execution of capital projects within electric utility systems, including transmission, distribution, and substation assets. This role leads delivery from project initiation through commissioning, with a strong emphasis on technical execution, constructability, cost and schedule control, and risk management. This is a hybrid role.

    Responsibilities

    • Develop and execute comprehensive project plans that define scope, objectives, deliverables, milestones, and timelines.
    • Translate engineering design into safe, efficient, and executable field work, coordinating engineers, technicians, contractors, equipment, and materials to ensure construction readiness and seamless project progression.
    • Provide technical guidance throughout the project lifecycle, driving alignment between engineering, procurement, and construction to ensure high-quality outcomes.
    • Maintain strict control over budget and schedule, including monitoring expenditures, forecasting performance, and proactively addressing risks or deviations.
    • Establish clear communication channels, understand client requirements, provide transparent updates, and resolve issues quickly and effectively.

    Qualifications

    • Bachelor’s degree