Sr. Manager, Business & Program Management (Hybrid)

The user wants me to reformat a job posting into clean, well-structured semantic HTML. I need to follow the rules: - 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. - Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. - Preserve ALL substantive information; do NOT invent or summarize away detail. - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. - IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. - Prefer a few substantive sections over many thin ones. - Output ONLY the HTML fragment — no /, no markdown code fences. Now, I need to parse the job posting and extract sections. The posting includes: - Date Posted, Country, Location, Position Role Type, U.S. Citizen requirements, Security Clearance Type/Status. These are metadata. Should I include them? The instruction says: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So I can include a short paragraph with location, role type, citizenship requirement, clearance. But not as headings. - Company description: "At RTX, the world's largest aerospace and defense company..." This is about the company. Could be an "About the company" section? But the instruction says use headings like "About the role". Might include a brief intro paragraph. - "The Digital Technology Program Management Office is currently searching for a seasoned Program Manager to manage Merger & Acquisition projects..." This is about the role. - "This is a hybrid position, with the ideal candidate based in one of the following locations: Cedar Rapids, IA; Charlotte, NC; Windsor Locks, CT; or Richardson, TX." This is location info. - "** What You Will Do:" followed by bullet points (though not explicitly bulleted, but each line is a duty). Should be Responsibilities section. - "What YOU will Learn:" bullet points. Could be a section "What You Will Learn" or "Learning Opportunities". - "Qualifications You Must Have:" list. This is Requirements. - "Qualifications We Prefer:" list. This is Preferred Qualifications. - "Qualifications We Prefer What We Offer:" Actually there is a duplication: "Qualifications We Prefer What We Offer:" then list of benefits. That's Benefits section. - Then there is a paragraph about Digital Technology team, etc. That's more about the role/team. - Then "Please consider the following role type definitions as you apply for this role. Hybrid: ..." This is about schedule/role type. - "At Collins, the paths we pave together..." marketing. - "Apply now and be part of the team..." application instruction. - "As part of our commitment to maintaining a secure hiring process..." interview process. - "The salary range for this role is 132,400 USD - 251,600 USD." This is Pay. - "The salary range provided is a good faith estimate..." more pay details. - "Hired applicants may be eligible for benefits..." more benefits details. - "This role is a U.S.-based role..." location/pay structure. - "RTX anticipates the application window closing approximately 40 days..." application window. - EEO statement, privacy policy. We need to remove boilerplate: EEO, privacy policy, application instructions, duplicate lines. We need to include sections only when there is real content. Potential sections: - About the Role (or Overview) - Responsibilities (What You Will Do) - What You Will Learn (optional) - Requirements (Qualifications You Must Have) - Preferred Qualifications (Qualifications We Prefer) - Benefits (What We Offer) - Pay (Salary range) - Schedule/Work Arrangement (Hybrid details) But note: "What You Will Learn" is a list, could be included. Also, the location and citizenship requirement could be in a short paragraph at top. Let's structure: First, a paragraph with metadata: location, hybrid, citizenship, clearance. Then maybe an "About the Role" paragraph describing the role. Then Responsibilities (h3) with ul. Then What You Will Learn (h3) with ul. Then Requirements (h3) with ul. Then Preferred Qualifications (h3) with ul. Then Benefits (h3) with ul. Then Pay (h3) with p (salary range). Then Schedule (h3) with p (hybrid description). But note: The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state salary range and benefits, so include them. Also, the posting includes "What We Offer" list of benefits, and later more benefits details. Combine. Now, need to ensure we don't duplicate. Let's extract each list. **What You Will Do:** (each line is a duty) - You will ensure effective execution of committed projects in the portfolio. - Drive processes and meeting cadences for scope management, risk and opportunity management, financial reporting, technical reviews, issue escalation, and stakeholder communications across the portfolio. - Drive end‑to‑end project planning, including scope definition, timelines, milestones, dependencies, and integration checkpoints for all workstreams. - Lead readiness assessments for Day 1 and post‑close integration, confirming critical capabilities, access, systems, and support structures are in place. - Manage budget forecasting and tracking for integration activities, ensuring financial transparency and alignment with leadership expectations. - You will partner with Digital leaders for resource assignments and development of integrated schedules and milestone commitments. - You will lead teams to development and implement effective risk mitigations and issue resolution. - You will lead teams to develop effective stakeholder communications. - Collaborate effectively to build teams. - Build trust and demonstrate accountability to customers, stakeholders, and staff. - Communicate effectively and efficiently with a wide variety of stakeholders. **What YOU will Learn:** - You will foster relationships with Digital, Collins and RTX peers all over the world that work and WANT to work at RTX. - You will strengthen project management skills through leading multi-million dollar projects. - You will advance executive communications and your network by leading conversations and program reviews across all levels of the organization. **Qualifications You Must Have:** - Typically requires a University Degree and minimum 10 years prior relevant experience or an Advanced Degree in a related field and minimum 7 years of experience - 3+ years’ experience with project management oversight of infrastructure and software development initiatives. - 3+ years’ experience building and managing schedules in MS Project. - Have experience partnering with a variety of customers, stakeholders, and teams to develop and deliver complex systems and services. - Have experience implementing management systems with applicability to a portfolio of projects including program financials, risk and opportunity management, schedule and scope management, and other project management fundamentals. - Must be willing and able to travel 25% of the time. **Qualifications We Prefer:** - Demonstrated program management experience. - Experience with program management systems including resource management, program scheduling and cost controls (i.e. Planview) - Experience working in a government and/or manufacturing environment. - Knowledge of aerospace policies, procedures and system requirements including quality, manufacturing, and program management - Experience interfacing with internal customers. - Experience with using change management frameworks and methodologies. - Understanding of key digital transformation topics and technologies. **What We Offer:** (benefits list) - Medical, dental, and vision insurance. - Three weeks of vacation for newly hired employees. - Generous 401(k) plan that includes employer matching funds and separate employer retirement contribution, including a Lifetime Income Strategy option. - Tuition reimbursement program. - Student Loan Repayment Program. - Life insurance and disability coverage. - Optional coverages you can buy pet insurance, home and auto insurance, additional life and accident insurance, critical illness insurance, group legal, ID theft protection. - Birth, adoption, parental leave benefits. - Ovia Health, fertility, and family planning. - Adoption Assistance. - Autism Benefit. - Employee Assistance Plan, including up to 10 free counseling sessions. - Healthy You Incentives, wellness rewards program. - Doctor on Demand, virtual doctor visits. - Bright Horizons, child, and elder care services. - Teladoc Medical Experts, second opinion program. - And more! Later there is another benefits paragraph: "Hired applicants may be eligible for benefits, including but not limited to, medical, dental, vision, life insurance, short-term disability, long-term disability, 401(k) match, flexible spending accounts, flexible work schedules, employee assistance program, Employee Scholar Program, parental leave, paid time off, and holidays." This is somewhat duplicate but includes additional items like short-term disability, long-term disability, flexible spending accounts, Employee Scholar Program, paid time off, holidays. Should we include both? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should include both lists, but avoid duplication. Could combine into one Benefits section with all unique items. But the first list is "What We Offer" and the second is "Hired applicants may be eligible for benefits...". They are similar but not identical. I'll include both as separate bullet points or combine. Since they are separate paragraphs, maybe keep both as separate bullet points? But they are both benefits. I'll create a Benefits section with a combined list, but ensure all items are included. However, the instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." So I should not remove any benefit mentioned. I'll include both lists as separate sub-lists? But the HTML structure expects

  • for any list. Could have two
    s? But the heading is one. Could do a single
    with all items, but that would merge. Might be okay to have two separate
    under same heading? But the instruction says use
    • for any list of duties/requirements/benefits. It doesn't forbid multiple lists. I'll include both lists as separate
      under Benefits heading, maybe with a brief intro. But the second benefits paragraph is more of a prose list. I'll convert to bullet points. Also, there is a paragraph about Digital Technology team: "Do you want to be part of a new, exciting initiative to combine foundational IT with new digital technologies? ..." This is more marketing, could be part of About the Role. The role type definitions: "Hybrid: Employees who are working in Hybrid roles will work regularly both onsite and offsite. Ratio of time working onsite will be determined in partnership with your leader. Regardless of your role type, collaboration and innovation are critical to our business and all employees will have access to digital tools so they can work with colleagues around the world – and access to Collins sites when their work requires in-person meetings." This is schedule/work arrangement. The salary range: "The salary range for this role is 132,400 USD - 251,600 USD." plus details. Now, we need to output only HTML fragment. Let's design the HTML: First, a paragraph with metadata:

      Location: Cedar Rapids, IA; Charlotte, NC; Windsor Locks, CT; or Richardson, TX. Hybrid role. U.S. citizenship required. Security clearance: None required.

      But the posting says "Position Role Type: Hybrid" and "U.S. Citizen, U.S. Person, or Immigration Status Requirements: U.S. citizenship is required..." and "Security Clearance Type: None/Not Required". So include. Then maybe an "About