Senior Program Manager

We need to output HTML fragment with sections: About the role? Actually the posting includes "About NAES" (company description) then "Opportunity Summary", then "In This Role, You Will" (responsibilities), then "Why you're the perfect addition to our Team (about you):" (requirements/qualifications), then "Working Relationships", then "Compensation", then "Physical Requirements & Working Conditions", then "Fit for Duty", then "NAES Safe", then diversity statement (EEO). We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove EEO statement (the diversity statement). Also remove "Fit for Duty", "NAES Safe", maybe those are boilerplate safety statements; they might be considered boilerplate? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Safety statements maybe not required to keep? They are not EEO but could be considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Safety statements are not explicitly listed, but they might be considered boilerplate? However they are substantive? They talk about safety being core value, etc. Might be considered boilerplate but not explicitly prohibited. However we can keep if it's substantive? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So safety statements are not in that list, so we can keep them. However they might be considered legal? Not sure. Safer to keep them? The instruction says "Prefer a few substantive sections over many thin ones." So we might combine some. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we should only include sections when posting has real specific content. The posting includes: About NAES (company overview) maybe "About the role"? Not exactly. There's "Opportunity Summary" which is like role summary. Could map to "About the role". Then responsibilities: "In This Role, You Will" list. Then qualifications: "Why you're the perfect addition to our Team (about you):" includes experience, education, etc. Could be Requirements/Qualifications/Skills. Then compensation: "Compensation" includes salary range. Then schedule: "Physical Requirements & Working Conditions" includes full-time 40 hours per week, travel up to 30%, etc. That's schedule/working conditions. Benefits: not explicitly listed besides maybe none. There's no benefits section. So we should not create Benefits unless present. Pay: we have compensation range, so we can include Pay section. Schedule: we have full-time 40 hours per week, travel up to 30% etc. So we can include Schedule section. We need to avoid repeating job title as heading. Not needed. We need to output only HTML fragment, no /, no markdown fences. We'll structure:

About the role

... (Opportunity Summary + maybe About NAES? The About NAES is company description; could be part of About the role? Might be separate but we can include as part of About the role.) Better: About the role includes Opportunity Summary and maybe company description. Then

Responsibilities

with

• list of responsibilities from "In This Role, You Will". Then

  Requirements

  maybe combine qualifications and skills. Could split into Requirements and Skills but we prefer few substantive sections. Could have Requirements (education, experience) and Skills (technical). But we can combine into one Requirements section. But instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says use those headings when appropriate. We can include multiple if we have content. We have content for Requirements, Qualifications, Skills maybe overlapping. Could separate: Requirements (education, experience), Qualifications (certifications?), Skills (technical). But we have limited distinct sections. Let's parse the "Why you're the perfect addition to our Team (about you):" bullet list: - Proven experience leading technology programs with sustained business results in a fast-paced environment. - Bachelor's degree in engineering, computer science, information systems, or business. Relevant experience may substitute year-for-year. - 7+ years in program, product, or project management, including 3+ years running multiple concurrent products. - Track record of shipping to short, fixed windows, ideally an MVP in production within 90 days. - Fluent in agile delivery and framework agnostic: incremental release, backlog management, prioritization by outcome over output. - Able to manage dependencies and sequencing across applications delivered by different teams. - Experience managing vendor delivered implementations, with sound judgement on internal development versus vendor delivery. - Experience with IT technical implementations. - Modern delivery tooling such as Azure DevOps or Jira. MS Project Online is a plus. - Power generation, utilities, or heavy industrial operations experience is a plus, as is CMMS (Maximo preferred) or operational data platforms. - Able to read code and data schemas well enough to hold technical conversations with developers and vendors. - Able to operate with limited direction in an ambiguous problem space. - Strong interpersonal and customer service skills, effective with internal customers at every level. - PMP, PSM, CSM, or SAFe certification is a plus but is not required. We can split: Requirements: education, years experience, track record. Skills: agile, dependencies, vendor management, IT implementations, tooling, domain experience, code reading, ambiguity, interpersonal, certifications. Qualifications maybe similar to requirements. But we can just have one Requirements section covering all. Then Pay: compensation range. Schedule: full-time 40 hours per week, additional time may be required during heavy workloads or to meet deadlines. Ability to sit or stand..., travel up to 30%, site work requires protective equipment etc. That's schedule/working conditions. We also have Physical Requirements & Working Conditions section; we can put that under Schedule. We should remove duplicated lines: there may be duplicates like "Ability to sit or stand for long periods, communicate verbally and in writing, and handle long periods of screen time." appears maybe only once. We need to remove boilerplate: EEO statement (the diversity and inclusion paragraph). Also remove "Fit for Duty", "NAES Safe", maybe those are safety boilerplate but not explicitly prohibited. However they are somewhat repetitive safety statements; could be considered boilerplate. Safer to remove them? The instruction only mentions EEO/equal-opportunity/scam-warning boilerplate. Safety not mentioned. But they are also somewhat generic. I'd keep them? Might be considered legal? Not sure. I'd keep them as they are substantive about safety expectations. However they'd create extra sections; we could incorporate them into Schedule or maybe a separate Safety section but we don't have heading for Safety. Could omit to keep fewer sections. Given "Prefer a few substantive sections over many thin ones." So we should avoid creating many thin sections. So we can combine safety into Schedule or maybe not include at all if it's thin. The safety paragraphs are somewhat generic but still specific to NAES. Might be considered boilerplate but not prohibited. I'd include them under Schedule as part of working conditions. Thus Schedule section will include: full-time 40 hours per week, additional time may be required during heavy workloads or to meet deadlines. Ability to sit or stand for long periods, communicate verbally and in writing, and handle long periods of screen time. Travel to operating facilities up to 30%. Site work requires protective equipment and mobility to traverse stairways, ladders, and uneven terrain. Fit for Duty ... NAES Safe ... (maybe we can keep short). But we need to avoid filler like "commensurate with experience". Not present. Now About the role: combine About NAES description and Opportunity Summary. About NAES: "At NAES, you’ll find engaging and challenging career opportunities in the power generation, renewable energy and industrial construction industry. At every level of the company, we share a common goal: To instill confidence in our clients through our steadfast commitment to safety, integrity and quality of work. NAES is largest independent operator of power facilities in the industry, operating more than 190 power plants throughout the United States, Canada, Mexico and the UK that span all technologies and provide over 49 GW of capacity. With the strength of 4000 people, our growing family of companies now addresses the entire life cycle of power generation and other industrial plants." Opportunity Summary: "The Senior Program Manager will deliver the NAES technology roadmap, which produces multiple applications on a common plan, run as one program rather than separate projects. Working with Business Process Owners and SBU leaders, you will decide what gets built and whether each product is delivered internally, by a vendor, or by configuring an existing platform, owning the outcome either way. The program runs to a quarterly cadence under a 90-day mandate: every product reaches a minimum viable product in production and delivers measurable value." We can combine. Now Responsibilities: list from "In This Role, You Will". Let's extract each bullet: - Own the roadmap end to end: intake, prioritization, sequencing, and trade-offs across the applications it produces. - Run the program to a quarterly cadence, breaking work into thin slices so each product reaches an MVP in production within 90 days. - Manage dependencies, integration points, and common data and security standards so separately delivered products work as one system. - Embed with Business Process Owners and SBU leaders to source requirements from how the job is actually performed, not from submitted requests. - Author what the work is built against, including problem statements, user stories, acceptance criteria, and a definition of done. - Decide the delivery approach for each product, whether internal development, vendor delivery, or platform configuration, and own the outcome either way. - Hold vendor work to the same cadence and 90-day expectation, structuring Statements of Work so they enable iterative delivery. - Run a weekly rhythm of plan, unblock, decide, and demonstrate, reordering the backlog on what each demo reveals. - Manage the financial plan and continuously evaluate budget across the program. - Track delivery health using flow metrics, and report both delivery performance and realized operational value after release. - Manage the quality of deliverables, including cybersecurity, data governance, NERC CIP where relevant, and training for adoption. - Mentor direct reports within the program. We'll put each as
• . Now Requirements/Qualifications/Skills: we can make one section maybe "Requirements". But we have headings for Requirements, Qualifications, Skills. Could split into Requirements (education, experience) and Skills (technical, interpersonal). But to avoid many thin sections, maybe combine into Requirements. Let's decide: We'll have

  Requirements

  and include all bullet points from "Why you're the perfect addition to our Team (about you):". That's fine. Pay:

  Pay

  with

  The initial compensation will range from $137,500 to $158,100 depending on experience.

  Schedule:

  Schedule

  with

  Full-time position requiring 40 hours per week. Additional time may be required during heavy workloads or to meet deadlines. Ability to sit or stand for long periods, communicate verbally and in writing, and handle long periods of screen time. Travel to operating facilities up to 30%. Site work requires protective equipment and mobility to traverse stairways, ladders, and uneven terrain. Fit for Duty All employees will participate in the Fitness for Duty Program. This program includes a post-offer physical examination and drug screening and post-employment random drug screening. There are extensive smoking restrictions in and around the facility. NAES Safe Safety is a core value