Program Manager, NASP - 518866

We need to output only HTML fragment, with headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes many details: description, responsibilities, requirements, qualifications, skills, etc. No explicit Benefits, Pay, Schedule given (Salary: Competitive but that's vague; we should not create Pay section unless actual numbers; "Competitive" is placeholder, so we should not include Pay). Benefits not mentioned. Schedule not mentioned. So we can have sections: About the role (maybe from Position Purpose), Responsibilities (Principal Accountabilities), Requirements (Minimum Requirements), Qualifications (maybe Education, Experience, Certification/License, Knowledge/Skills/Abilities), Skills (maybe list of specific technical skills). We need to avoid duplication. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve all substantive information, not invent or summarize away detail. Must not include boilerplate like EEO, Drug-Free Workplace, How To Claim Vet Preference, How To Submit Documentation, etc. Also remove duplicated lines. We need to parse the posting and extract relevant content. Let's extract sections: - About the role: Could be "Position Purpose" paragraph(s). Also maybe "Position is Responsible for collaborating across the enterprise..." etc. We'll combine into prose. - Responsibilities: "Principal Accountabilities" bullet list (though it's paragraph sentences). We'll turn each sentence into

• . - Requirements: "Minimum Requirements" includes Education, Experience, Certification/License, Knowledge/Skills/Abilities. Could be separate sub-sections but we can just list as
  . - Qualifications: Might be overlapping with Requirements; but we can treat Requirements as qualifications. However instructions: use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can have both Requirements and Qualifications if distinct. But we can combine to avoid thin sections. Prefer few substantive sections. So maybe we have About the role, Responsibilities, Requirements (which includes education, experience, certifications, knowledge/skills). Skills could be separate list of technical skills (systems administration, SharePoint Online Management, SQL, software development, AI, etc.) but those are already in description. Could create Skills section. Let's decide: We'll have:

  About the role

  ... (position purpose paragraphs)

  Responsibilities

  • ... each accountability

  Requirements

  • ... education bullet, experience bullet, certification bullet, knowledge/skills bullet

  Skills

  • ... list of specific technical skills: systems administration, SharePoint Online Management, SQL, software development, troubleshooting, AI driven solutions, Maximo, C55 Copperleaf, PowerPlan, Cognos, SAP S4 HANA, Primavera P6, Power BI, Copilot, etc.
  We must not repeat job title. No metadata like Posting Open/Close, Relocation, etc. Should we include location? Possibly not required; but location is substantive? The instruction: preserve ALL substantive information; do not invent or summarize away detail. Location is substantive. Should we include it? It's not a heading; we could fold into a short

  under About the role maybe. But they said do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Location maybe minor metadata but could be included in a short p. However they said preserve ALL substantive information; location is substantive. So we should include it somewhere, maybe in About the role paragraph. Also Salary: Competitive - we should not create Pay section because it's vague. But we could include salary info in About the role as a short sentence? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It states Salary: Competitive, which is vague but still states something. However they said never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. "Competitive" is somewhat placeholder but it's still stated. Safer to not create Pay section; we could include salary info in a paragraph under About the role? But they said preserve ALL substantive information; if we omit salary, we lose info. Could include it in About the role as a sentence: "The position offers a competitive salary." That preserves it without a dedicated Pay section. Similarly, we could include posting dates? They are metadata; maybe fold into short p or drop. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. So we could include a short p with posting open/close dates, location, relocation not offered, etc. But we need to preserve all substantive information; posting dates maybe not crucial but still info. We'll include a short p under About the role maybe. Let's craft About the role paragraph: combine position purpose and maybe location, posting dates, salary. Position Purpose: "Position is Responsible for collaborating across the enterprise to assess and improve TVA project performance, ensuring that TVA projects are planned and executed in a manner that meet or exceed stakeholder expectations; satisfying all safety, environmental, scope, cost, schedule, and quality goals. Position is responsible for assigned programmatic functional area performance and provides governance and oversight for assigned programmatic functional area(s). Responsibility includes project assurance through oversight of assigned programs to ensure that early warning signs of issues on projects are recognized and corrective actions are properly identified and taken. Analyzes project and programmatic performance, identifies opportunities for improvement, and guides TVA project management and support teams in implementing best practices and project performance improvement initiatives and to ensure proper direction of multifunctional/cross-disciplinary teams of TVA employee and staff augmentation contractors. This position supports planning, estimation, contract & material management, and implementation of plant project modification activities ensuring that managed activities are conducted in accordance with applicable TVA, Federal, and state regulations. This Position supports the development, execution, and upkeep of a Projects Asset Management Plan to identify capital projects needed to sustain the Nuclear plant for 80-100 years of operation." We'll put that in

  . Add location: "Work Location: Chattanooga, TN. Relocation is not offered for this position." Could be a short p. Add posting dates: "Posting Open: 09/14/2026. Posting Close: 09/20/2026 11:59 PM EST." Could be short p. Add salary: "Salary: Competitive." Could be short p. But we need to avoid too many small paragraphs; maybe combine into one p: "Located in Chattanooga, TN, this position does not offer relocation. The posting is open from 09/14/2026 to 09/20/2026 11:59 PM EST and offers a competitive salary." That preserves info. Now Responsibilities: we need to extract each accountability from "Principal Accountabilities". Let's list them: - Maintain Procedures, Process and Guidance documents up-to-date with relevant industry, Nuclear Quality Assurance Plan, and regulatory requirements. - Act as Subject Matter Expert (SME) and provide recommendations for decision making. - Manage Peer team or Working Group meetings. - Participate in developing the new processes and procedures to support project performance requirements. - Coordinates with Manager for Program and Process change approval. - Propels standardization and process improvements across all TVA project management organizations. - Develop and execute oversight, benchmarking, and self-assessment plans. - Lead the compliance efforts to ensure project executing organizations are adhering to TVA Project Management SPPs. - Utilize the Corrective Action Program (CAP) and Issue Resolution Program to correct deficiencies and improve program performance. - Collaborate across the enterprise to maintain a high level of technical expertise and business acumen; including industry experience to ensure processes are successful, effective, and documented in a robust standardized procedure system and hierarchy. - Drives accountability throughout TVA project executing organizations for closing gaps to excellence in project performance - Oversee program KPIs, performance metrics, and review project and or program performance reporting requirements. - Oversee the accountability and performance measurement systems to analyze, monitor, and trend key project performance indicators. - Collaborate with key stakeholders across project executing organizations to lead performance improvement initiatives. - Coordinate with Joint Project Teams, Plant Operations, Senior Management and other TVA organizations to conduct post-project reviews of significant projects to determine lessons learned and for dissemination and implementation of the best practices into future projects. - Participate in evaluating and implementing the project and or program management tools - Communicate and Escalate issues to leadership that pose nuclear safety, regulatory, personal safety, and financial risk. - Identify training for Self and others (TVA and Contractors). - Perform other duties, as assigned. We'll turn each into

  • . Ensure we keep the exact wording. Now Requirements: Minimum Requirements includes: Education — B.S. degree in engineering, nuclear operations, engineering technology, math, physics, chemistry, information technologies, data science, or related science, or equivalent combination of education, experience, and training. Experience — 5 or more years of power utility and related business/professional work experience with at least 1 years of increased responsibilities leading program or project related teams and or project management experience. Must possess knowledge and expertise in the use of project management and or programmatic management techniques. Ability to look beyond existing methodologies and own disciple to define and resolve complex problems. Certification/License, etc — Must obtain and maintain requirements for nuclear plant unescorted access. Must be able and willing to assume “on-call” rotational assignments which may include 24 hour-a-day, 7 day-a-week availability, and serve as a Project Control Center Manager when assigned. Knowledge/Skills/Abilities — Working knowledge of management techniques and human relations skills to enable him/her to guide TVA Projects and Program management toward goals. Ability to communicate effectively. Demonstrated ability to establish and maintain effective working relationship with other TVA organizations and to communicate clearly orally and in writing. Strong commitment to and skills in employee communication, to be able to build teamwork and convey mission, objective, expectations and philosophy. Demonstrated ability to interpret broad policy matters and provide guides to Project Management personnel. Demonstrated ability to successfully contribute to the cohesiveness, effectiveness and success of Projects. Demonstrated openness to questions, suggestions and concerns, and ability to pursue answers and resolutions. Demonstrated high productivity level, sense of urgency, and respect for meeting deadlines. We could break these into separate
  • items: Education, Experience, Certification/License, Knowledge/Skills/Abilities (which itself is a list). But we could also flatten: each bullet as a sentence. We'll create
    with
    • for each of the four categories, preserving the text. Now Skills: we need to list specific technical skills mentioned: systems administration, SharePoint Online Management, SQL, software development, troubleshoot technical issues, AI driven solutions, Maximo, C55 Copperleaf, PowerPlan, Cognos, SAP S4 HANA, Primavera P6, Power BI, Copilot. Also maybe "artificial intelligence and data-driven technologies". Also "project management and programmatic management techniques". But those are more generic. We'll focus on the concrete list. We'll create
      • ... each skill separated by commas or separate
      • . Better separate each as
      • . Now ensure we don't repeat content. The skills list may overlap with description but okay. Now produce HTML fragment: start with

        About the role

        ...

        then

        Responsibilities

        ...
        then

        Requirements