Senior Technical NPI Program Manager
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only if posting has real specific content.
We have job description: includes responsibilities, qualifications, benefits. No explicit Pay or Schedule details (though mentions hybrid work schedule location, but not schedule specifics). The posting says "You will work out of our Salem, Oregon and/or Atlanta, Georgia location on a hybrid work schedule." That's schedule info? It mentions hybrid work schedule but not specifics like hours. Probably we can include a Schedule section? The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It states hybrid work schedule, so we can include Schedule section with that detail. Benefits section is present: they list benefits. Pay: not mentioned (no salary). So omit Pay.
We also need About the role section: we have introductory paragraphs describing role. Could put that under About the role.
Responsibilities: list bullet points.
Qualifications: includes "YOU MUST HAVE" and "WE VALUE". Could combine under Qualifications? The rule: use headings for Qualifications, Skills, etc. We have qualifications and maybe skills. The posting includes "Strong project management, communication, presentation, leadership and collaboration skills." That's skills. Also "Servant leadership approach." Could be under Skills. Also "Advanced engineering degree..." etc under WE VALUE could be qualifications or preferred qualifications. We'll treat "YOU MUST HAVE" as Requirements (or Qualifications). The heading list includes Requirements and Qualifications. We need to decide which to use. The posting has both mandatory and preferred. Could put mandatory under Requirements, preferred under Qualifications. Or combine under Qualifications. Since we have both headings available, better to split: Requirements for must-have, Qualifications for preferred/value.
Skills: we can extract skills like project management, communication, presentation, leadership, collaboration, servant leadership, problem-solving, analytical, Agile/Waterfall, PMP desired, etc.
Benefits: we have benefits paragraph.
Schedule: hybrid work schedule location.
We must not repeat job title as heading. No Job ID etc.
We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details like location (Salem, Oregon and/or Atlanta, Georgia), hybrid work schedule, reporting to Engineering Program Manager, etc.
We need to ensure we don't include boilerplate like cookie/navigation/legal/EEO etc. The posting includes some about Honeywell Technologies etc. That's not boilerplate? It's company description; maybe we can include under About Honeywell? Not a required heading. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The company description about Honeywell Technologies is not boilerplate but could be considered "About Us". Not in heading list; we could omit or include as a paragraph under maybe About the role? But we should preserve all substantive information. However the instruction says output only HTML fragment with headings from list; we can still include paragraphs not under headings? The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose." It doesn't forbid other paragraphs outside headings, but likely they expect sections with headings. We could include a brief intro paragraph before first heading? Might be okay. But to be safe, we can put the introductory description under About the role heading.
Thus About the role will contain the prose describing role: "As a Senior Technical NPI Program Manager here at Honeywell, you will be responsible for leading new product development and sustaining projects in the Supra and Onity product line for the Building Automation (BA) group. You will play a crucial role in driving innovation, ensuring the successful development and delivery of high-quality products, and contributing to the growth and success of our organization. You will report directly to our Engineering Program Manager, and you'll work out of our Salem, Oregon and/or Atlanta, Georgia location on a hybrid work schedule. In this role, you will have a significant impact on the development and enhancement of our Supra and Onity product line, ensuring that our products meet the needs of our customers and align with industry standards. You will collaborate with cross-functional teams, including engineering, manufacturing, and quality, to drive project success and deliver products on time and within budget. In this role, you will impact the successful execution and enhancement of NPI, contributing to the organization's overall success and competitiveness in the market."
That covers a lot.
Responsibilities: bullet list from "KEY RESPONSIBILITIES". We'll list each line.
Requirements: "YOU MUST HAVE" bullet list.
Qualifications: "WE VALUE" bullet list.
Skills: we can extract skills from both mandatory and preferred: project management, communication, presentation, leadership, collaboration, servant leadership, problem-solving, analytical, Agile, Waterfall, PMP certification desired, etc. Also maybe "Ability to work in ambiguity and navigate through complex and uncertain situations." That's more a requirement. We'll put under Skills.
Benefits: paragraph describing benefits.
Schedule: mention hybrid work schedule and locations.
We must not include Pay.
Now ensure we don't repeat info unnecessarily. But we must preserve all substantive information; some info may appear in multiple sections (like location appears in About the role and Schedule). That's okay duplication? Might be considered duplication but we need to preserve all info; we could keep location only in Schedule and not repeat in About the role, but then we lose location from About the role. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep location somewhere. If we put it only under Schedule, we still preserve it. The About the role could omit location to avoid duplication but still preserve it. However the About the role currently includes location; we could remove it from there and keep only under Schedule. That would still preserve all info (just not duplicated). That's acceptable.
Similarly, hybrid work schedule appears in Schedule.
Now check for any other info: reporting to Engineering Program Manager (we can keep under About the role). Impact statements etc.
Now produce HTML.
Structure:
About the role
... (prose)
Responsibilities
- Lead new product development and sustaining projects in the Supra and Onity product line.
- Collaborate with cross-functional teams to ensure successful project execution.
- Manage and deliver programs within scope, schedule, and budget.
- Ensure alignment of programs with strategic objectives and customer needs.
- Drive innovation and continuous improvement in product development processes.
- Ensure products meet customer needs and industry standards.
- Manage project timelines, budgets, risks, issues, and resources.
- Provide technical leadership and guidance to project team members.
Requirements
- Bachelor’s degree from an accredited institution in a technical discipline such as technology, engineering or mathematics.
- 5 plus years of engineering experience in NPI Development within a global organization including leading at least two software/hardware products to high volume manufacturing.
- Ability to work in ambiguity and navigate through complex and uncertain situations.
- Strong project management, communication, presentation, leadership and collaboration skills.
- Servant leadership approach.
Qualifications
- Advanced engineering degree in a relevant field.
- Experience in the building automation industry and knowledge of industry standards and regulation.
- Strong problem-solving and analytical skills.
- PMP (Project Management Professional) certification is highly desired.
- Experience using both Agile and Waterfall methodologies.
Skills
- Project management
- Communication
- Presentation
- Leadership
- Collaboration
- Servant leadership
- Problem‑solving
- Analytical thinking
- Agile methodology
- Waterfall methodology
Benefits
In addition to a competitive salary, leading-edge work, and developing solutions side‑by‑side with dedicated experts in their fields, Honeywell employees are eligible for a comprehensive benefits package. This package includes employer subsidized Medical, Dental, Vision, and Life Insurance; Short‑Term and Long‑Term Disability; 401(k) match, Flexible Spending Accounts, Health Savings Accounts, EAP, and Educational Assistance; Parental Leave, Paid Time Off (for vacation, personal business, sick time, and parental leave), and 12 Paid Holidays.
Schedule
Hybrid work schedule; work location options include Salem, Oregon and/or Atlanta, Georgia.
Check for any leftover substantive info: mention of reporting to Engineering Program Manager is in About the role? We omitted it. We need to include that. Let's add to About the role paragraph.
Also mention "You will play a crucial role in driving innovation, ensuring the successful development and delivery of high-quality products, and contributing to the growth and success of our organization." Already there.
Also mention "You will report directly to our Engineering Program Manager". Add.
Also mention "In this role, you will have a significant impact on the development and enhancement of our Supra and Onity product line, ensuring that our products meet the needs of our customers and align with industry standards." Already.
Also mention "You will collaborate with cross-functional teams, including engineering, manufacturing, and quality, to drive project success and deliver products on time and within budget." Already.
Also mention "In this role, you will impact the successful execution and enhancement of NPI, contributing to the organization's overall success and competitiveness in the market." Already.
Also mention "About Honeywell Technologies" etc. That's company description; not required heading but could be omitted? The instruction says preserve ALL substantive information. That includes company description. However we have no heading for that; we could add a paragraph under About the role or maybe a separate section like "About Honeywell" but not in heading list. Since we cannot create arbitrary headings, we could include it as a paragraph after the About the role section without a heading. That would preserve info. The instruction didn't forbid extra paragraphs outside headings. It said use for section headings (e.g...). It didn't say you cannot have other sections. So we can add a
about Honeywell Technologies after the About the role.
Similarly "THE BUSINESS UNIT" etc about Honeywell Building Automation (BA). That's also substantive. We could add another paragraph.
Also "About Us" duplicate of earlier Honeywell Technologies description; we can ignore duplicate.
We need to avoid duplication: there are two similar paragraphs about Honeywell Technologies; we can keep one.
Thus after About the role, we can add a paragraph describing Honeywell Technologies (the first block). Then another paragraph describing Honeywell Building Automation (BA) unit.
Let's extract the relevant content:
From posting:
"About Honeywell Technologies Honeywell Technologies is a global, pure-play automation company with a legacy of innovating to help solve the world’s most mission-critical challenges, enhancing the quality of life for people and communities around the world. We serve the building, industrial, and process sectors with a broad portfolio of services, solutions, and products, underpinned by our Honeywell Technologies Accelerator operating system and Honeywell Technologies Forge intelligence layer. By combining the deep domain expertise of our more than 50,000 employees with decades of data from our global installed base, we are uniquely positioned to lead the industrial sector’s transition from automation to autonomy. Learn more"
Then later:
"THE BUS
- for any list of duties/requirements/benefits, and
for prose." It doesn't forbid other paragraphs outside headings, but likely they expect sections with headings. We could include a brief intro paragraph before first heading? Might be okay. But to be safe, we can put the introductory description under About the role heading. Thus About the role will contain the prose describing role: "As a Senior Technical NPI Program Manager here at Honeywell, you will be responsible for leading new product development and sustaining projects in the Supra and Onity product line for the Building Automation (BA) group. You will play a crucial role in driving innovation, ensuring the successful development and delivery of high-quality products, and contributing to the growth and success of our organization. You will report directly to our Engineering Program Manager, and you'll work out of our Salem, Oregon and/or Atlanta, Georgia location on a hybrid work schedule. In this role, you will have a significant impact on the development and enhancement of our Supra and Onity product line, ensuring that our products meet the needs of our customers and align with industry standards. You will collaborate with cross-functional teams, including engineering, manufacturing, and quality, to drive project success and deliver products on time and within budget. In this role, you will impact the successful execution and enhancement of NPI, contributing to the organization's overall success and competitiveness in the market." That covers a lot. Responsibilities: bullet list from "KEY RESPONSIBILITIES". We'll list each line. Requirements: "YOU MUST HAVE" bullet list. Qualifications: "WE VALUE" bullet list. Skills: we can extract skills from both mandatory and preferred: project management, communication, presentation, leadership, collaboration, servant leadership, problem-solving, analytical, Agile, Waterfall, PMP certification desired, etc. Also maybe "Ability to work in ambiguity and navigate through complex and uncertain situations." That's more a requirement. We'll put under Skills. Benefits: paragraph describing benefits. Schedule: mention hybrid work schedule and locations. We must not include Pay. Now ensure we don't repeat info unnecessarily. But we must preserve all substantive information; some info may appear in multiple sections (like location appears in About the role and Schedule). That's okay duplication? Might be considered duplication but we need to preserve all info; we could keep location only in Schedule and not repeat in About the role, but then we lose location from About the role. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep location somewhere. If we put it only under Schedule, we still preserve it. The About the role could omit location to avoid duplication but still preserve it. However the About the role currently includes location; we could remove it from there and keep only under Schedule. That would still preserve all info (just not duplicated). That's acceptable. Similarly, hybrid work schedule appears in Schedule. Now check for any other info: reporting to Engineering Program Manager (we can keep under About the role). Impact statements etc. Now produce HTML. Structure:
About the role
... (prose)
Responsibilities
- Lead new product development and sustaining projects in the Supra and Onity product line.
- Collaborate with cross-functional teams to ensure successful project execution.
- Manage and deliver programs within scope, schedule, and budget.
- Ensure alignment of programs with strategic objectives and customer needs.
- Drive innovation and continuous improvement in product development processes.
- Ensure products meet customer needs and industry standards.
- Manage project timelines, budgets, risks, issues, and resources.
- Provide technical leadership and guidance to project team members.
Requirements
- Bachelor’s degree from an accredited institution in a technical discipline such as technology, engineering or mathematics.
- 5 plus years of engineering experience in NPI Development within a global organization including leading at least two software/hardware products to high volume manufacturing.
- Ability to work in ambiguity and navigate through complex and uncertain situations.
- Strong project management, communication, presentation, leadership and collaboration skills.
- Servant leadership approach.
Qualifications
- Advanced engineering degree in a relevant field.
- Experience in the building automation industry and knowledge of industry standards and regulation.
- Strong problem-solving and analytical skills.
- PMP (Project Management Professional) certification is highly desired.
- Experience using both Agile and Waterfall methodologies.
Skills
- Project management
- Communication
- Presentation
- Leadership
- Collaboration
- Servant leadership
- Problem‑solving
- Analytical thinking
- Agile methodology
- Waterfall methodology
Benefits
In addition to a competitive salary, leading-edge work, and developing solutions side‑by‑side with dedicated experts in their fields, Honeywell employees are eligible for a comprehensive benefits package. This package includes employer subsidized Medical, Dental, Vision, and Life Insurance; Short‑Term and Long‑Term Disability; 401(k) match, Flexible Spending Accounts, Health Savings Accounts, EAP, and Educational Assistance; Parental Leave, Paid Time Off (for vacation, personal business, sick time, and parental leave), and 12 Paid Holidays.
Schedule
Hybrid work schedule; work location options include Salem, Oregon and/or Atlanta, Georgia.
Check for any leftover substantive info: mention of reporting to Engineering Program Manager is in About the role? We omitted it. We need to include that. Let's add to About the role paragraph. Also mention "You will play a crucial role in driving innovation, ensuring the successful development and delivery of high-quality products, and contributing to the growth and success of our organization." Already there. Also mention "You will report directly to our Engineering Program Manager". Add. Also mention "In this role, you will have a significant impact on the development and enhancement of our Supra and Onity product line, ensuring that our products meet the needs of our customers and align with industry standards." Already. Also mention "You will collaborate with cross-functional teams, including engineering, manufacturing, and quality, to drive project success and deliver products on time and within budget." Already. Also mention "In this role, you will impact the successful execution and enhancement of NPI, contributing to the organization's overall success and competitiveness in the market." Already. Also mention "About Honeywell Technologies" etc. That's company description; not required heading but could be omitted? The instruction says preserve ALL substantive information. That includes company description. However we have no heading for that; we could add a paragraph under About the role or maybe a separate section like "About Honeywell" but not in heading list. Since we cannot create arbitrary headings, we could include it as a paragraph after the About the role section without a heading. That would preserve info. The instruction didn't forbid extra paragraphs outside headings. It said usefor section headings (e.g...). It didn't say you cannot have other sections. So we can add a
about Honeywell Technologies after the About the role. Similarly "THE BUSINESS UNIT" etc about Honeywell Building Automation (BA). That's also substantive. We could add another paragraph. Also "About Us" duplicate of earlier Honeywell Technologies description; we can ignore duplicate. We need to avoid duplication: there are two similar paragraphs about Honeywell Technologies; we can keep one. Thus after About the role, we can add a paragraph describing Honeywell Technologies (the first block). Then another paragraph describing Honeywell Building Automation (BA) unit. Let's extract the relevant content: From posting: "About Honeywell Technologies Honeywell Technologies is a global, pure-play automation company with a legacy of innovating to help solve the world’s most mission-critical challenges, enhancing the quality of life for people and communities around the world. We serve the building, industrial, and process sectors with a broad portfolio of services, solutions, and products, underpinned by our Honeywell Technologies Accelerator operating system and Honeywell Technologies Forge intelligence layer. By combining the deep domain expertise of our more than 50,000 employees with decades of data from our global installed base, we are uniquely positioned to lead the industrial sector’s transition from automation to autonomy. Learn more" Then later: "THE BUS