Program Manager

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which headings to use. The posting includes: Job Summary (maybe About the role), Responsibilities, Requirements (Experience, Knowledge, Skills, Abilities, Education), Qualifications (Education & Certifications), Skills (maybe part of requirements), Benefits. We should avoid thin sections. Could combine Requirements and Qualifications into one "Requirements" section? But we have both required experience and education/certifications. Could make two sections: Requirements and Qualifications. Skills: Could be part of Requirements; but we could make a Skills section if there is explicit skill list. The required experience includes many skills: Strong organizational skills, written/verbal, etc. Could be a Skills section. But we need to avoid filler. Let's extract concrete lists. From "What we are looking for (Experience, Knowledge, Skills, Abilities, Education)" we have bullet-like sentences: - Eight (8) or more years of relevant industrial experience in a technical role. - Five (5) or more years of program/project and people management experience. - Knowledge of the technical and administrative aspects of all phases of project management. - Demonstrated ability to develop comprehensive program schedules, detailed timelines, resource plans, and project tracking mechanisms. - Experience leading cross-functional teams and coordinating activities across multiple functional disciplines. - Demonstrated ability to identify, prioritize, resolve, and document program risks and issues. - Strong organizational skills, including effective follow-up on individual responsibilities and assigned Program Team actions. - Strong written, verbal, interpersonal, and presentation skills. - Demonstrated teamwork and leadership abilities, including persistence when addressing complex problems. - Ability to understand and interpret product strategies and translate them into program requirements and execution priorities. - General knowledge of operations, including scheduling, procurement, manufacturing, product testing, marketing, and quality systems. - Proficiency with Microsoft Office applications, including Word, Excel, and PowerPoint, with the ability to develop graphs, tables, PivotTables, reports, and presentations. - Sound business acumen. That's a list of requirements. Then "Preferred Experience, Knowledge, Skills, And Abilities" list: - Experience managing complex engineering or new product development programs within an industrial or manufacturing environment. - Knowledge of mechanical engineering techniques, sheet-metal fabrication, and high-volume assembly processes. - Experience utilizing formal project scheduling and tracking tools. - Experience facilitating Stage-Gate or similar structured product-development processes. - Ability to communicate effectively with internal and external customers at all levels of an organization. Then "Education & Certifications": - Bachelor's degree in a technical discipline required. - MBA preferred. - Project or program management certification preferred. - Six Sigma techniques and methodology certification preferred. Thus we could have sections: Requirements (required), Preferred Qualifications (maybe Qualifications), Education & Certifications (maybe Qualifications). But we need to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could map: - About the role: Job Summary paragraph. - Responsibilities: the responsibilities list. - Requirements: required experience list. - Qualifications: preferred experience list + education/certifications? Could combine. - Skills: maybe we could extract skills from required list (strong organizational skills, strong written/verbal, etc.) but that seems redundant. Might be better to omit Skills if no explicit separate skill list beyond what's already in Requirements. But we could still create Skills section with those skill items. However that would duplicate content. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Duplicating is okay as long as we preserve? It might be considered repeating but not prohibited. However better to avoid thin sections. If we put Skills, we need to have specific skill content. We could extract skill sentences: Strong organizational skills, Strong written, verbal, interpersonal, and presentation skills, Demonstrated teamwork and leadership abilities, Ability to understand and interpret product strategies, General knowledge of operations, Proficiency with Microsoft Office applications, Sound business acumen. That's a list. But those are already in Requirements. Duplicating might be okay but could be considered redundant. The instruction: "Prefer a few substantive sections over many thin ones." So better to not create Skills if it's thin and duplicates. We'll omit Skills. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits. Now Benefits list: "What benefits do we offer?" includes: - Generous and flexible paid time off including paid personal time off, caregiver, parental, and volunteer leave - Competitive health insurance plans and 401(k) match, with benefits starting day one - Competitive and performance-based compensation packages and bonus plans - Educational assistance, leadership development programs, and recognition programs We'll make

• . Now we need to output only HTML fragment, no /, no markdown. We'll produce:

  About the role

  ... job summary paragraph ...

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...

  Qualifications

  • Preferred Experience...
  ...
  Maybe also include Education & Certifications inside Qualifications? Could separate but we have only one Qualifications heading allowed. We could combine preferred experience and education/certifications into one list under Qualifications. That's okay. Thus Qualifications list items: preferred experience items and education/certification items. Now ensure we preserve all substantive information. Let's extract exact text. Job Summary paragraph: "SPX is a diverse team of unique individuals who all make an impact. As a Program Manager, you will provide leadership for assigned engineering programs, managing program schedules, resources, and funding to ensure timely completion of Stage-Gate deliverables consistent with product strategy, quality, safety, performance, schedule, and cost requirements. You will lead cross-functional program teams, establish project objectives and detailed schedules, identify and manage program risks, and maintain accountability for execution throughout the program lifecycle. Success in this role requires strong communication, leadership, technical, and organizational skills, along with the ability to apply effective problem-solving techniques to identify, resolve, and document issues associated with complex cross-functional programs." We need to keep that as

  . Responsibilities: The block after "What You Can Expect In This Role (Job Responsibilities)" includes many sentences. We'll split each sentence into list items. Let's extract sentences: - Establish project objectives, policies, procedures, performance standards, and comprehensive program schedules within the boundaries of company policies and project specifications. - Define program Stage-Gate deliverables, funding requirements, and resource loading. - Develop and maintain detailed program timelines using appropriate project scheduling and tracking tools. - Manage execution against established program schedules by leading Program Teams and facilitating communication and interaction among cross-functional representatives. - Track programs against schedules, budgets, and Stage-Gate deliverables to ensure projects are completed on schedule, within budget, and in accordance with established requirements. - Develop and implement corrective measures for schedule deviations, unexpected conditions, and other issues affecting program execution. - Ensure program activities support the introduction of products that meet or exceed company quality standards and established technical, safety, performance, schedule, and cost requirements. - Identify and manage program risks in partnership with the Program Team, including risk prioritization and development of mitigation plans. - Facilitate program reviews and Stage-Gate reviews, including preparation of required documentation and refinement of supporting systems and processes. - Monitor program progress and provide regular status updates to the Lead Program Manager and updates to executive leadership as needed. - Identify, resolve, and document issues affecting cross-functional program execution. - Develop graphs, tables, PivotTables, and other reports using Microsoft Word, Excel, PowerPoint, and related business tools to communicate program status and performance. - Coordinate with customers through Marketing and Sales to provide appropriate program status information and obtain customer feedback. - Understand and interpret product strategies to ensure program execution remains aligned with business and product objectives. - Communicate effectively with internal and external customers at all levels of the organization through clear written, verbal, and interpersonal communication. - Maintain awareness of the technical and administrative aspects of all phases of project and program management. - Apply knowledge of mechanical engineering techniques, sheet-metal fabrication, and high-volume assembly processes in support of assigned programs. - Maintain general knowledge of operations, including scheduling, procurement, manufacturing, product testing, marketing, and quality systems. - Use technical knowledge and cross-functional input to support effective problem-solving and program decision-making. - Perform other related duties and responsibilities as required to support program and organizational objectives. Check if any missing: also earlier bullet "Program Planning & Execution" etc but those are headings inside responsibilities block; we already captured the sentences after those headings. The headings themselves are not substantive content; they are just section titles. We can ignore them as they are not required to be preserved? The instruction: preserve ALL substantive information; do not invent or summarize away detail. The headings like "Program Planning & Execution" are not substantive detail but could be considered section titles. However they are part of the responsibilities description; but we already captured the sentences under them. It's okay to omit the heading titles as they are not adding new info beyond the sentences. Might be okay. Now Requirements list items: we need to copy each bullet exactly as in text. List: - Eight (8) or more years of relevant industrial experience in a technical role. - Five (5) or more years of program/project and people management experience. - Knowledge of the technical and administrative aspects of all phases of project management. - Demonstrated ability to develop comprehensive program schedules, detailed timelines, resource plans, and project tracking mechanisms. - Experience leading cross-functional teams and coordinating activities across multiple functional disciplines. - Demonstrated ability to identify, prioritize, resolve, and document program risks and issues. - Strong organizational skills, including effective follow-up on individual responsibilities and assigned Program Team actions. - Strong written, verbal, interpersonal, and presentation skills. - Demonstrated teamwork and leadership abilities, including persistence when addressing complex problems. - Ability to understand and interpret product strategies and translate them into program requirements and execution priorities. - General knowledge of operations, including scheduling, procurement, manufacturing, product testing, marketing, and quality systems. - Proficiency with Microsoft Office applications, including Word, Excel, and PowerPoint, with the ability to develop graphs, tables, PivotTables, reports, and presentations. - Sound business acumen. Now Qualifications list: combine preferred experience and education/certifications. Preferred Experience items: - Experience managing complex engineering or new product development programs within an industrial or manufacturing environment. - Knowledge of mechanical engineering techniques, sheet-metal fabrication, and high-volume assembly processes. - Experience utilizing formal project scheduling and tracking tools. - Experience facilitating Stage-Gate or similar structured product-development