New Product Development Manager
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT include Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading with filler/placeholder text. Prefer few substantive sections over many thin ones.
We need to parse the job posting.
Content:
- Intro paragraph about SPX Technologies, RiSE, etc. Could be "About the role" or maybe "About the company". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map sections.
We have:
- "How You Will Make An Impact (Job Summary)" -> This is job summary; could be "About the role" or maybe "Job Summary". Use "About the role" heading.
- "What You Can Expect In This Role (Job Responsibilities)" -> Responsibilities.
- "What We Are Looking For (Required/Ideal Experience, Skills, Education)" -> This includes Required Experience & Skills, Ideal Experience & Skills, Education & Certifications. Could be "Requirements" and "Qualifications" and "Skills". We need to decide.
We have sections: Required Experience & Skills, Ideal Experience & Skills, Education & Certifications.
We could combine Required and Ideal into "Requirements" and "Qualifications". Or we could have "Requirements" for required, "Qualifications" for ideal/education. The instruction says use headings for those categories if content exists.
We also have "Travel & Working Environment" - not in list of allowed headings; but we could maybe put under "About the role" or ignore? The instruction says use headings only from list; we should not create other headings. So we need to incorporate that content somewhere else, maybe in a
under About the role or Responsibilities? But it's not duties; it's about working environment. Could be placed under "About the role" as prose.
We also have "How We Live Our Culture" and "What benefits do we offer?" -> Benefits section.
We also have "Our commitment to embrace diversity..." etc. That's EEO boilerplate; should be removed.
We need to preserve all substantive information; do not invent or summarize away detail. Remove boilerplate.
Thus we need to extract substantive content:
Intro: "Building the people that build the world. With platforms in HVAC and Detection and Measurement, SPX Technologies builds innovative solutions that enable a safer, more efficient, sustainable world. Through our RiSE talent development framework, we Reach, Identify, Strengthen, and Engage our employees to support them in their continued development. We’re a global company of problem solvers, collaborators, and innovators, and our businesses build solutions that impact the world. As part of HVAC Cooling, SPX Cooling Technologies is a leader in high quality industrial HVAC equipment used to cool large facilities like hospitals, data centers, and power plants. With cooling towers, fans, and refrigeration units, companies rely on brands like Marley, Recold, and SGS to provide comfort and mission critical and industrial cooling solutions."
That's about company; could go under About the role.
Job Summary: "SPX is a diverse team of unique individuals who all make an impact. The New Product Development (NPD) Program Manager is responsible for leading the planning, coordination, and disciplined execution of new product development programs from concept through commercialization. This highly technical role partners with Engineering, Product Management, Operations, Sourcing, Quality, Sales, and other cross-functional stakeholders to translate product development objectives into well-defined project plans and ensure programs are executed against established scope, schedule, cost, quality, and performance expectations. The NPD Program Manager provides leadership across multiple development programs, establishing consistent processes, milestones, accountability, and visibility to ensure projects progress effectively through the NPD process. The role proactively identifies risks, resolves barriers, facilitates cross-functional decisions, and communicates program status to business and technical leadership. Success requires a strong engineering foundation combined with program management expertise, business judgment, and the ability to lead complex cross-functional initiatives through influence and accountability. This role encourages innovation and continuously improves efficiency of technical support, monitors advances of technology and competition, and supports global and acquisition-related technical issues in areas of expertise."
That's substantive.
Responsibilities: bullet list under "While each day brings new opportunities at SPX, your core responsibilities will be:" then list items:
- NPD Program Leadership & Execution
- Lead multiple complex new product development programs from initial concept and project definition through design, validation, launch, and commercialization.
- Develop and maintain comprehensive program plans defining scope, deliverables, schedules, milestones, resources, dependencies, and key decision points.
- Establish clear ownership and accountability for project deliverables and ensure cross-functional teams execute against established commitments.
- Maintain appropriate rigor and discipline throughout the NPD process while balancing speed, technical risk, business priorities, and resource constraints.
- Cross-Functional Technical Leadership
- Lead cross-functional program teams consisting of Engineering, Product Management, Sourcing, Operations, Quality, Manufacturing, Sales, and other functions as required.
- Serve as the primary coordination point between technical and business functions throughout the product development process.
- Facilitate technical and business discussions necessary to resolve issues, evaluate alternatives, and maintain program momentum.
- Ensure technical requirements, customer needs, manufacturability, quality expectations, cost objectives, and commercialization requirements are appropriately integrated into program execution.
- Program Governance, Risk, & Performance
- Establish and manage program milestones, stage reviews, decision points, and other governance mechanisms required by the NPD process.
- Proactively identify technical, schedule, resource, cost, supplier, and execution risks and ensure appropriate mitigation and recovery plans are developed.
- Develop and maintain program metrics and reporting tools that provide visibility to project health, milestones, risks, resource needs, and overall NPD portfolio performance.
- Conduct regular program reviews with project teams and leadership, escalating critical issues and facilitating timely decisions when necessary.
- NPD Process & Continuous Improvement
- Champion consistent application of the organization’s NPD process, tools, standards, and project management practices across development programs.
- Identify and implement improvements to NPD processes that increase execution speed, predictability, accountability, and overall effectiveness.
- Capture lessons learned from completed programs and integrate improvements into future product development activities.
- Partner with Engineering and business leadership to improve resource planning, project prioritization, portfolio visibility, and overall NPD execution capability.
We need to output as
- for any list of duties/requirements/benefits. So each bullet can be
- . Could group sub-bullets? Probably each line as
- . Could also nest but not required.
Now Requirements/Qualifications/Skills:
We have "What We Are Looking For (Required/Ideal Experience, Skills, Education)" with subsections:
Required Experience & Skills:
- 7–10 years of progressive experience in engineering, product development, program management, or a related technical environment.
- Demonstrated experience leading complex new product development or engineering programs from concept through launch.
- Experience leading cross-functional teams and managing projects involving multiple technical and business disciplines.
- Strong written and verbal communication skills with the ability to effectively communicate program status, risks, and recommendations to technical teams and business leadership.
- Strong ability to coordinate people and resources without losing focus on project priorities and deadlines.
- Excellent problem-solving and decision-making skills with the ability to identify issues, evaluate alternatives, and drive resolution.
- Proficiency with Microsoft Office and project planning or scheduling tools.
- Demonstrated commitment to safety, quality, continuous improvement, and operational efficiency.
- Ability to work effectively in both office and laboratory/test environments.
Ideal Experience & Skills:
- Strong technical foundation with the ability to understand complex engineering concepts, requirements, risks, and tradeoffs.
- Strong program and project management skills, including scope, schedule, resource, risk, and milestone management.
- Strong process orientation and ability to establish structure and discipline around complex development activities.
- Ability to manage multiple complex programs and competing priorities in a fast-paced product development environment.
- Strong business judgment and ability to balance technical requirements with schedule, cost, quality, and commercial objectives.
- Demonstrated commitment to continuous improvement and development of more effective NPD processes and tools.
- Experience within HVAC, industrial equipment, engineered products, or a related industry preferred.
Education & Certifications:
- Bachelor’s degree in Mechanical Engineering, Civil Engineering, Electrical Engineering, or a related engineering discipline required.
- Project or program management certification (PMP or similar) preferred but not required.
Travel & Working Environment:
- Onsite office environment, Monday – Friday; Hybrid work schedule available after satisfactory completion of probationary period.
- The position may require working occasionally outside normal work hours.
- Lifting up to 70 pounds.
- Bending and stooping.
- Ability to communicate effectively verbally.
- Working at heights less than 50 feet above ground.
- Work with exposure to bad weather and/or excessive heat.
We need to decide headings: Could use "Requirements" for required experience & skills, "Qualifications" for ideal experience & skills and education, "Skills" maybe for skills? But we have overlapping.
We could create sections: "Requirements" (required experience & skills), "Qualifications" (ideal experience & skills + education), "Skills" maybe not needed separately. But we need to avoid filler. The instruction says prefer few substantive sections over many thin ones. So maybe combine required and ideal into one "Requirements" section, and education into "Qualifications". Or we could have "Requirements" and "Qualifications" and "Skills" as separate if we have distinct content.
We have skills listed in required and ideal; could put under "Skills". But we also have experience years etc. Might be better to have:
-
About the role
(company intro + job summary)
- Responsibilities
(list)
- Requirements
(required experience & skills)
- Qualifications
(ideal experience & skills + education)
- Benefits
(benefits list)
- Possibly Schedule
if we have schedule info: we have hybrid work schedule after probation, Monday-Friday, occasional outside hours. That's schedule info. Could put under Schedule.
But we also have travel & working environment details (lifting, bending, heights, etc.) - maybe could be under About the role or Responsibilities? Not exactly duties. Could be under "About the role" as prose.
We need to avoid creating sections with filler like "Pay" if not specified. No pay info given, so omit Pay section.
Schedule: we have some schedule info (Monday-Friday, hybrid after probation, occasional outside hours). That's specific enough to create a Schedule section.
Benefits: we have bullet list under "What benefits do we offer?" with items:
- 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 should include those as - .
Now we need to remove boilerplate: "How We Live Our Culture", "Our commitment to embrace diversity..." etc. Also remove "SPX is an affirmative action and equal opportunity employer..." etc.
Also remove duplicated lines? Not seeing duplicates.
Now we need to output HTML fragment only, no /, no markdown fences.
We'll produce:
About the role
... (company intro + job summary)
Responsibilities
- ...
...
Requirements
for prose. Do NOT repeat job title as heading. Do NOT include Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading with filler/placeholder text. Prefer few substantive sections over many thin ones. We need to parse the job posting. Content: - Intro paragraph about SPX Technologies, RiSE, etc. Could be "About the role" or maybe "About the company". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map sections. We have: - "How You Will Make An Impact (Job Summary)" -> This is job summary; could be "About the role" or maybe "Job Summary". Use "About the role" heading. - "What You Can Expect In This Role (Job Responsibilities)" -> Responsibilities. - "What We Are Looking For (Required/Ideal Experience, Skills, Education)" -> This includes Required Experience & Skills, Ideal Experience & Skills, Education & Certifications. Could be "Requirements" and "Qualifications" and "Skills". We need to decide. We have sections: Required Experience & Skills, Ideal Experience & Skills, Education & Certifications. We could combine Required and Ideal into "Requirements" and "Qualifications". Or we could have "Requirements" for required, "Qualifications" for ideal/education. The instruction says use headings for those categories if content exists. We also have "Travel & Working Environment" - not in list of allowed headings; but we could maybe put under "About the role" or ignore? The instruction says use headings only from list; we should not create other headings. So we need to incorporate that content somewhere else, maybe in a
under About the role or Responsibilities? But it's not duties; it's about working environment. Could be placed under "About the role" as prose. We also have "How We Live Our Culture" and "What benefits do we offer?" -> Benefits section. We also have "Our commitment to embrace diversity..." etc. That's EEO boilerplate; should be removed. We need to preserve all substantive information; do not invent or summarize away detail. Remove boilerplate. Thus we need to extract substantive content: Intro: "Building the people that build the world. With platforms in HVAC and Detection and Measurement, SPX Technologies builds innovative solutions that enable a safer, more efficient, sustainable world. Through our RiSE talent development framework, we Reach, Identify, Strengthen, and Engage our employees to support them in their continued development. We’re a global company of problem solvers, collaborators, and innovators, and our businesses build solutions that impact the world. As part of HVAC Cooling, SPX Cooling Technologies is a leader in high quality industrial HVAC equipment used to cool large facilities like hospitals, data centers, and power plants. With cooling towers, fans, and refrigeration units, companies rely on brands like Marley, Recold, and SGS to provide comfort and mission critical and industrial cooling solutions." That's about company; could go under About the role. Job Summary: "SPX is a diverse team of unique individuals who all make an impact. The New Product Development (NPD) Program Manager is responsible for leading the planning, coordination, and disciplined execution of new product development programs from concept through commercialization. This highly technical role partners with Engineering, Product Management, Operations, Sourcing, Quality, Sales, and other cross-functional stakeholders to translate product development objectives into well-defined project plans and ensure programs are executed against established scope, schedule, cost, quality, and performance expectations. The NPD Program Manager provides leadership across multiple development programs, establishing consistent processes, milestones, accountability, and visibility to ensure projects progress effectively through the NPD process. The role proactively identifies risks, resolves barriers, facilitates cross-functional decisions, and communicates program status to business and technical leadership. Success requires a strong engineering foundation combined with program management expertise, business judgment, and the ability to lead complex cross-functional initiatives through influence and accountability. This role encourages innovation and continuously improves efficiency of technical support, monitors advances of technology and competition, and supports global and acquisition-related technical issues in areas of expertise." That's substantive. Responsibilities: bullet list under "While each day brings new opportunities at SPX, your core responsibilities will be:" then list items: - NPD Program Leadership & Execution - Lead multiple complex new product development programs from initial concept and project definition through design, validation, launch, and commercialization. - Develop and maintain comprehensive program plans defining scope, deliverables, schedules, milestones, resources, dependencies, and key decision points. - Establish clear ownership and accountability for project deliverables and ensure cross-functional teams execute against established commitments. - Maintain appropriate rigor and discipline throughout the NPD process while balancing speed, technical risk, business priorities, and resource constraints. - Cross-Functional Technical Leadership - Lead cross-functional program teams consisting of Engineering, Product Management, Sourcing, Operations, Quality, Manufacturing, Sales, and other functions as required. - Serve as the primary coordination point between technical and business functions throughout the product development process. - Facilitate technical and business discussions necessary to resolve issues, evaluate alternatives, and maintain program momentum. - Ensure technical requirements, customer needs, manufacturability, quality expectations, cost objectives, and commercialization requirements are appropriately integrated into program execution. - Program Governance, Risk, & Performance - Establish and manage program milestones, stage reviews, decision points, and other governance mechanisms required by the NPD process. - Proactively identify technical, schedule, resource, cost, supplier, and execution risks and ensure appropriate mitigation and recovery plans are developed. - Develop and maintain program metrics and reporting tools that provide visibility to project health, milestones, risks, resource needs, and overall NPD portfolio performance. - Conduct regular program reviews with project teams and leadership, escalating critical issues and facilitating timely decisions when necessary. - NPD Process & Continuous Improvement - Champion consistent application of the organization’s NPD process, tools, standards, and project management practices across development programs. - Identify and implement improvements to NPD processes that increase execution speed, predictability, accountability, and overall effectiveness. - Capture lessons learned from completed programs and integrate improvements into future product development activities. - Partner with Engineering and business leadership to improve resource planning, project prioritization, portfolio visibility, and overall NPD execution capability. We need to output as
- for any list of duties/requirements/benefits. So each bullet can be
- . Could group sub-bullets? Probably each line as
- . Could also nest but not required.
Now Requirements/Qualifications/Skills:
We have "What We Are Looking For (Required/Ideal Experience, Skills, Education)" with subsections:
Required Experience & Skills:
- 7–10 years of progressive experience in engineering, product development, program management, or a related technical environment.
- Demonstrated experience leading complex new product development or engineering programs from concept through launch.
- Experience leading cross-functional teams and managing projects involving multiple technical and business disciplines.
- Strong written and verbal communication skills with the ability to effectively communicate program status, risks, and recommendations to technical teams and business leadership.
- Strong ability to coordinate people and resources without losing focus on project priorities and deadlines.
- Excellent problem-solving and decision-making skills with the ability to identify issues, evaluate alternatives, and drive resolution.
- Proficiency with Microsoft Office and project planning or scheduling tools.
- Demonstrated commitment to safety, quality, continuous improvement, and operational efficiency.
- Ability to work effectively in both office and laboratory/test environments.
Ideal Experience & Skills:
- Strong technical foundation with the ability to understand complex engineering concepts, requirements, risks, and tradeoffs.
- Strong program and project management skills, including scope, schedule, resource, risk, and milestone management.
- Strong process orientation and ability to establish structure and discipline around complex development activities.
- Ability to manage multiple complex programs and competing priorities in a fast-paced product development environment.
- Strong business judgment and ability to balance technical requirements with schedule, cost, quality, and commercial objectives.
- Demonstrated commitment to continuous improvement and development of more effective NPD processes and tools.
- Experience within HVAC, industrial equipment, engineered products, or a related industry preferred.
Education & Certifications:
- Bachelor’s degree in Mechanical Engineering, Civil Engineering, Electrical Engineering, or a related engineering discipline required.
- Project or program management certification (PMP or similar) preferred but not required.
Travel & Working Environment:
- Onsite office environment, Monday – Friday; Hybrid work schedule available after satisfactory completion of probationary period.
- The position may require working occasionally outside normal work hours.
- Lifting up to 70 pounds.
- Bending and stooping.
- Ability to communicate effectively verbally.
- Working at heights less than 50 feet above ground.
- Work with exposure to bad weather and/or excessive heat.
We need to decide headings: Could use "Requirements" for required experience & skills, "Qualifications" for ideal experience & skills and education, "Skills" maybe for skills? But we have overlapping.
We could create sections: "Requirements" (required experience & skills), "Qualifications" (ideal experience & skills + education), "Skills" maybe not needed separately. But we need to avoid filler. The instruction says prefer few substantive sections over many thin ones. So maybe combine required and ideal into one "Requirements" section, and education into "Qualifications". Or we could have "Requirements" and "Qualifications" and "Skills" as separate if we have distinct content.
We have skills listed in required and ideal; could put under "Skills". But we also have experience years etc. Might be better to have:
-
About the role
(company intro + job summary) -Responsibilities
(list) -Requirements
(required experience & skills) -Qualifications
(ideal experience & skills + education) -Benefits
(benefits list) - PossiblySchedule
if we have schedule info: we have hybrid work schedule after probation, Monday-Friday, occasional outside hours. That's schedule info. Could put under Schedule. But we also have travel & working environment details (lifting, bending, heights, etc.) - maybe could be under About the role or Responsibilities? Not exactly duties. Could be under "About the role" as prose. We need to avoid creating sections with filler like "Pay" if not specified. No pay info given, so omit Pay section. Schedule: we have some schedule info (Monday-Friday, hybrid after probation, occasional outside hours). That's specific enough to create a Schedule section. Benefits: we have bullet list under "What benefits do we offer?" with items: - 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 should include those as- .
Now we need to remove boilerplate: "How We Live Our Culture", "Our commitment to embrace diversity..." etc. Also remove "SPX is an affirmative action and equal opportunity employer..." etc.
Also remove duplicated lines? Not seeing duplicates.
Now we need to output HTML fragment only, no /, no markdown fences.
We'll produce:
About the role
... (company intro + job summary)
Responsibilities
- ... ...
Requirements
- .
Now we need to remove boilerplate: "How We Live Our Culture", "Our commitment to embrace diversity..." etc. Also remove "SPX is an affirmative action and equal opportunity employer..." etc.
Also remove duplicated lines? Not seeing duplicates.
Now we need to output HTML fragment only, no /, no markdown fences.
We'll produce: