IT Program Management Lead
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the job description.
We have:
- About the role: The description includes "As an IT Program Management Lead here at Honeywell, you will lead and execute complex IT projects..." plus "This role is responsible for leading complex IT initiatives..." etc. Also "Highly visible leadership role...". So we can put that in About the role.
- Responsibilities: There's a "Responsibilities" heading with bullet points under KEY RESPONSIBILITIES. We need to extract each bullet as list items.
- Qualifications: There's a "Qualifications" heading with "YOU MUST HAVE" and "WE VALUE". We need to combine? The instructions: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we have Qualifications. Possibly also Requirements? The posting includes "YOU MUST HAVE" which are requirements. Could treat as Requirements section. But we also have "WE VALUE" which could be Skills. However we need to decide.
We have "Benefits Of Working For Honeywell" which is benefits.
Pay: Not mentioned. So we should not include Pay section.
Schedule: There's mention of Hybrid work schedule, note about first 90 days 100% onsite. So we have schedule info. So include Schedule section.
We also have "About Honeywell Technologies" etc. That's company description, not needed? Could be part of About the role? Probably not needed. The instruction: preserve ALL substantive information; do not invent or summarize away detail. Remove boilerplate etc. The "About Honeywell Technologies" and "About Us" etc are boilerplate? Might be considered company overview, not required? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Company overview may be considered not essential but could be kept? The instruction: "Preserve ALL substantive information". The company overview is substantive? It's generic but maybe considered boilerplate. However it's not clearly boilerplate like EEO. It's describing the company. Might be considered okay to keep? But the sections we have limited to those headings. We could include a section "About the company" but not in allowed headings. So we should omit it.
Thus we will produce sections:
About the role
with paragraphs summarizing the role description (the first paragraph and the highly visible leadership role paragraph). Ensure we keep all details.
We need to preserve all substantive information: So we need to include details like reporting to Director IT Business Partner, location Charlotte, NC or Atlanta, GA, hybrid schedule, first 90 days 100% onsite M-F. Also the role responsibilities details.
We'll put that in About the role.
Then Responsibilities: list items from KEY RESPONSIBILITIES.
We need to capture each bullet:
- Strategic Business Partnership
Serve as a trusted advisor to business leaders, proactively identifying opportunities where technology can enable business strategy and operational excellence.
Build strong, collaborative relationships across business and IT stakeholders to ensure alignment on priorities, outcomes, and value realization.
- Program & Change Leadership
Lead end-to-end delivery and execution of ERP, commercial and digital capabilities and across SAP, S4 HANA, SFDC, CPQ, AI and Data analytics initiatives
Support and manage business operation systems
IT initiatives and transformation initiatives, ensuring alignment with enterprise objectives, timelines, and success measures.
Drive adoption of new processes and technologies by embedding change into business operations, with a focus on sustainable impact rather than standalone training efforts.
- Value Delivery & Outcomes
Translate business needs into actionable IT strategies, roadmaps, and solutions that deliver measurable business value.
Monitor and communicate progress against business outcomes, proactively addressing risks and driving continuous improvement.
- Stakeholder Engagement & Influence
Facilitate decision-making by engaging senior leaders and cross-functional stakeholders, ensuring clarity, transparency, and alignment.
Provide strategic guidance and thought leadership on transformation initiatives, organizational readiness, and process optimization.
- Organizational Readiness & Adoption
Assess business readiness for change and implement targeted strategies to support adoption, focusing on integration into day-to-day operations.
- Continuous Improvement & Innovation
Stay current on emerging technology and industry trends, applying insights to enhance business capabilities and competitive advantage.
Drive innovation in delivery approaches, stakeholder engagement, and value measurement.
We need to format as - each bullet? The instruction: Use
- for any list of duties/requirements/benefits. So we can make a list where each
- contains the heading (bold?) but we can't use markdown. We can include the heading inside the li as plain text. Probably each responsibility area as a list item with subtext. Could also break each sentence into separate li but better to keep as one li per responsibility area with the description.
Thus:
- Strategic Business Partnership: Serve as a trusted advisor ... Build strong ...
- Program & Change Leadership: Lead end-to-end delivery ... Support and manage ... Drive adoption ...
... etc.
We'll need to preserve line breaks? Not needed.
Next, Qualifications: We have "YOU MUST HAVE" and "WE VALUE". Could split into Requirements and Skills sections. But we have allowed headings: Requirements, Qualifications, Skills. We could put mandatory qualifications under Requirements, and valued ones under Skills. Or we could put all under Qualifications. The instruction: Prefer a few substantive sections over many thin ones. So maybe combine into Qualifications section only. But we have both mandatory and valued; we could still put all under Qualifications. However we have also a separate "Requirements" heading allowed; we could use Requirements for mandatory, Skills for valued. That yields more sections but still substantive. Let's do that: Requirements (mandatory), Skills (valued). Also we have "Benefits" section.
Thus:
Requirements
with - for each mandatory requirement.
Mandatory requirements list:
- Bachelor's degree in IT, business, Computer Science, or related field, or equivalent work experience
- A minimum of 5 years of working experience in IT program management and tools, commercial and digital transformation, change management, preferably in a global or complex organization.
- Hands-on ERP, commercial and Digital technology/system experience (SAP, S4 HANA, Salesforce, CPQ)
- A minimum of 3 years of experience in managing and leading IT projects, business transformation as consultants or analyst.
Note there is a typo "Hand-on". We'll preserve as is? It says "Hand-on ERP, commercial and Digital technology/system experience (SAP, S4 HANA, Salesforce, CPQ)". We'll keep exactly.
Now Skills (valued):
- A proven track record of managing successful IT transformations and business operations, delivering measurable results and value.
- A strong knowledge of change and learning theories, models, frameworks, and methodologies, and the ability to apply them in various contexts and situations.
- Project management tools (Jira etc.)
- An excellent communicator, facilitator, and presenter, with the ability to engage and influence diverse audiences and stakeholders at all levels.
- A collaborative and flexible team player, with the ability to work effectively in a cross-functional and matrix environment.
- A creative and innovative thinker, with the ability to solve problems and adapt to changing needs and priorities.
- A self-motivated and results-oriented individual, with the ability to manage multiple projects and tasks simultaneously.
- A passionate and committed learner, with the willingness to learn new skills and share knowledge and best practices.
Now Benefits: we have a paragraph describing benefits. We'll put in
.
Benefits text: "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. Learn more ( https://benefits.honeywell.com/ )"
We should keep the link? Probably keep as plain text.
Now Schedule: we have hybrid work schedule note. Also location. We'll put schedule info.
Schedule text: "Hybrid work schedule. Note: For the first 90 days, New Hires must be prepared to work 100% onsite M-F. Location: Charlotte, NC or Atlanta, GA. Reports to Director IT Business Partner."
We could also include location in About the role but we already have location there. Might duplicate. Better to put location and schedule in Schedule section. But About the role also mentioned location and hybrid schedule. To avoid duplication, we could keep location and schedule in About the role and not repeat. However we need to include schedule section only if posting has real specific content for it. It does: hybrid schedule and first 90 days onsite. So we can include schedule section with that info. About the role can still mention the role but not repeat schedule details? The instruction: preserve ALL substantive information. If we omit schedule details from About the role, we lose them unless we put them in Schedule section. So we should put schedule details in Schedule section, and About the role can focus on role description without schedule/location. But About the role currently includes location and hybrid schedule. We can edit About the role to exclude those details, moving them to Schedule. That's okay as we are not losing info; we just relocate.
Thus About the role paragraph: "As an IT Program Management Lead here at Honeywell, you will lead and execute complex IT projects, ensuring they align seamlessly with our business objectives and foster innovation. You will report directly to our Director IT Business Partner. This role is a highly visible leadership position for an experienced IT professional who excels at partnering with business leaders to drive strategic outcomes. You will lead complex IT initiatives, aligning digital IT, ERP and data solutions with business priorities, and ensuring successful delivery of transformation programs that create measurable value across the organization."
We need to ensure we kept all substantive info: reporting to Director IT Business Partner, leading complex IT projects, aligning with business objectives, fostering innovation, highly visible leadership role, partnering with business leaders, drive strategic outcomes, lead complex IT initiatives, aligning digital IT, ERP and data solutions with business priorities, ensuring successful delivery of transformation programs that create measurable value across the organization. That's covered.
Now Schedule section: include hybrid work schedule, first 90 days 100% onsite M-F, location Charlotte, NC or Atlanta, GA.
Now Benefits section as above.
Now we need to output only HTML fragment, no /, no markdown.
We'll produce:
About the role
...
Responsibilities
- ...
...
Requirements
- ...
...
Skills
- ...
...
Benefits
...
Schedule
...
Check that we didn't include Pay (not present). Good.
Now ensure we didn't include any boilerplate like "Learn more (https://benefits.honeywell.com/)" - that's part of benefits, we keep.
Now check for any duplicated lines: we removed.
Now ensure we didn't invent content.
Now produce final HTML.
Let's craft the text precisely.
About the role paragraph:
"As an IT Program Management Lead here at Honeywell, you will lead and execute complex IT projects, ensuring they align seamlessly with our business objectives and foster innovation. You will report directly
About the role
with paragraphs summarizing the role description (the first paragraph and the highly visible leadership role paragraph). Ensure we keep all details. We need to preserve all substantive information: So we need to include details like reporting to Director IT Business Partner, location Charlotte, NC or Atlanta, GA, hybrid schedule, first 90 days 100% onsite M-F. Also the role responsibilities details. We'll put that in About the role. Then Responsibilities: list items from KEY RESPONSIBILITIES. We need to capture each bullet: - Strategic Business Partnership Serve as a trusted advisor to business leaders, proactively identifying opportunities where technology can enable business strategy and operational excellence. Build strong, collaborative relationships across business and IT stakeholders to ensure alignment on priorities, outcomes, and value realization. - Program & Change Leadership Lead end-to-end delivery and execution of ERP, commercial and digital capabilities and across SAP, S4 HANA, SFDC, CPQ, AI and Data analytics initiatives Support and manage business operation systems IT initiatives and transformation initiatives, ensuring alignment with enterprise objectives, timelines, and success measures. Drive adoption of new processes and technologies by embedding change into business operations, with a focus on sustainable impact rather than standalone training efforts. - Value Delivery & Outcomes Translate business needs into actionable IT strategies, roadmaps, and solutions that deliver measurable business value. Monitor and communicate progress against business outcomes, proactively addressing risks and driving continuous improvement. - Stakeholder Engagement & Influence Facilitate decision-making by engaging senior leaders and cross-functional stakeholders, ensuring clarity, transparency, and alignment. Provide strategic guidance and thought leadership on transformation initiatives, organizational readiness, and process optimization. - Organizational Readiness & Adoption Assess business readiness for change and implement targeted strategies to support adoption, focusing on integration into day-to-day operations. - Continuous Improvement & Innovation Stay current on emerging technology and industry trends, applying insights to enhance business capabilities and competitive advantage. Drive innovation in delivery approaches, stakeholder engagement, and value measurement. We need to format as- each bullet? The instruction: Use
- for any list of duties/requirements/benefits. So we can make a list where each
- contains the heading (bold?) but we can't use markdown. We can include the heading inside the li as plain text. Probably each responsibility area as a list item with subtext. Could also break each sentence into separate li but better to keep as one li per responsibility area with the description.
Thus:
- Strategic Business Partnership: Serve as a trusted advisor ... Build strong ...
- Program & Change Leadership: Lead end-to-end delivery ... Support and manage ... Drive adoption ... ... etc. We'll need to preserve line breaks? Not needed. Next, Qualifications: We have "YOU MUST HAVE" and "WE VALUE". Could split into Requirements and Skills sections. But we have allowed headings: Requirements, Qualifications, Skills. We could put mandatory qualifications under Requirements, and valued ones under Skills. Or we could put all under Qualifications. The instruction: Prefer a few substantive sections over many thin ones. So maybe combine into Qualifications section only. But we have both mandatory and valued; we could still put all under Qualifications. However we have also a separate "Requirements" heading allowed; we could use Requirements for mandatory, Skills for valued. That yields more sections but still substantive. Let's do that: Requirements (mandatory), Skills (valued). Also we have "Benefits" section. Thus:
- for each mandatory requirement.
Mandatory requirements list:
- Bachelor's degree in IT, business, Computer Science, or related field, or equivalent work experience
- A minimum of 5 years of working experience in IT program management and tools, commercial and digital transformation, change management, preferably in a global or complex organization.
- Hands-on ERP, commercial and Digital technology/system experience (SAP, S4 HANA, Salesforce, CPQ)
- A minimum of 3 years of experience in managing and leading IT projects, business transformation as consultants or analyst.
Note there is a typo "Hand-on". We'll preserve as is? It says "Hand-on ERP, commercial and Digital technology/system experience (SAP, S4 HANA, Salesforce, CPQ)". We'll keep exactly.
Now Skills (valued):
- A proven track record of managing successful IT transformations and business operations, delivering measurable results and value.
- A strong knowledge of change and learning theories, models, frameworks, and methodologies, and the ability to apply them in various contexts and situations.
- Project management tools (Jira etc.)
- An excellent communicator, facilitator, and presenter, with the ability to engage and influence diverse audiences and stakeholders at all levels.
- A collaborative and flexible team player, with the ability to work effectively in a cross-functional and matrix environment.
- A creative and innovative thinker, with the ability to solve problems and adapt to changing needs and priorities.
- A self-motivated and results-oriented individual, with the ability to manage multiple projects and tasks simultaneously.
- A passionate and committed learner, with the willingness to learn new skills and share knowledge and best practices.
Now Benefits: we have a paragraph describing benefits. We'll put in
. Benefits text: "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. Learn more ( https://benefits.honeywell.com/ )" We should keep the link? Probably keep as plain text. Now Schedule: we have hybrid work schedule note. Also location. We'll put schedule info. Schedule text: "Hybrid work schedule. Note: For the first 90 days, New Hires must be prepared to work 100% onsite M-F. Location: Charlotte, NC or Atlanta, GA. Reports to Director IT Business Partner." We could also include location in About the role but we already have location there. Might duplicate. Better to put location and schedule in Schedule section. But About the role also mentioned location and hybrid schedule. To avoid duplication, we could keep location and schedule in About the role and not repeat. However we need to include schedule section only if posting has real specific content for it. It does: hybrid schedule and first 90 days onsite. So we can include schedule section with that info. About the role can still mention the role but not repeat schedule details? The instruction: preserve ALL substantive information. If we omit schedule details from About the role, we lose them unless we put them in Schedule section. So we should put schedule details in Schedule section, and About the role can focus on role description without schedule/location. But About the role currently includes location and hybrid schedule. We can edit About the role to exclude those details, moving them to Schedule. That's okay as we are not losing info; we just relocate. Thus About the role paragraph: "As an IT Program Management Lead here at Honeywell, you will lead and execute complex IT projects, ensuring they align seamlessly with our business objectives and foster innovation. You will report directly to our Director IT Business Partner. This role is a highly visible leadership position for an experienced IT professional who excels at partnering with business leaders to drive strategic outcomes. You will lead complex IT initiatives, aligning digital IT, ERP and data solutions with business priorities, and ensuring successful delivery of transformation programs that create measurable value across the organization." We need to ensure we kept all substantive info: reporting to Director IT Business Partner, leading complex IT projects, aligning with business objectives, fostering innovation, highly visible leadership role, partnering with business leaders, drive strategic outcomes, lead complex IT initiatives, aligning digital IT, ERP and data solutions with business priorities, ensuring successful delivery of transformation programs that create measurable value across the organization. That's covered. Now Schedule section: include hybrid work schedule, first 90 days 100% onsite M-F, location Charlotte, NC or Atlanta, GA. Now Benefits section as above. Now we need to output only HTML fragment, no /, no markdown. We'll produce:
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Skills
- ... ...
Benefits
...
Schedule
...
Check that we didn't include Pay (not present). Good. Now ensure we didn't include any boilerplate like "Learn more (https://benefits.honeywell.com/)" - that's part of benefits, we keep. Now check for any duplicated lines: we removed. Now ensure we didn't invent content. Now produce final HTML. Let's craft the text precisely. About the role paragraph: "As an IT Program Management Lead here at Honeywell, you will lead and execute complex IT projects, ensuring they align seamlessly with our business objectives and foster innovation. You will report directly
Requirements
with