Operations Product Manager (Onsite)

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. Must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Please ensure the role type defined below is appropriate for your needs before applying to this role." etc. Also remove "RTX is an Equal Opportunity Employer..." etc. Also remove "Privacy Policy and Terms". Also remove "For onsite and hybrid roles..." etc. Also remove "This position may be eligible for relocation." etc. Also remove "The salary range provided is a good faith estimate..." etc. Actually we need to keep Pay section if posting actually states them. The posting includes: "The salary range for this role is 132,400 USD - 251,600 USD." So we need a Pay section with that content. Also Benefits: they list many benefits. So include Benefits section. Schedule: they mention Onsite role type, but schedule not explicitly given. They say "Onsite: Employees who are working in Onsite roles will work primarily onsite." That's about role type, not schedule. No explicit schedule like "Full-time" etc. So we should not create Schedule section unless posting actually states them. It does not give schedule like "Monday-Friday 9-5". So omit Schedule. We need sections: About the role (maybe from introductory paragraph), Responsibilities (What You Will Do), Requirements (U.S. Person, etc), Qualifications (You Must Have, Qualifications We Prefer), Skills (maybe from preferences?), Benefits, Pay. We must not repeat job title as heading. Use

for each section heading. We need to preserve all substantive information, not invent or summarize away detail. Must not omit details like "U.S. Person" definition, security clearance none, etc. Also include location details? The location is given: US-FL-MELBOURNE-307 ~ 1100 W Hibiscus Blvd ~ BLDG 307. Should we include that? It's substantive. Where to put? Possibly under About the role or a separate section? There's no heading for location; we could include it in a paragraph under About the role. The instructions: "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." Location is minor metadata? Might be considered location info; we could fold into a short

under About the role. However they said "Prefer a few substantive sections over many thin ones." So we can include location in About the role paragraph. We must remove duplicated lines, boilerplate. Also remove "For a complete definition of “U.S. Person” go here. https://..." That's a link; maybe we keep the definition but drop the link? The definition is substantive: "U.S. Person is a lawful permanent resident as defined in 8 U.S.C. 1101(a)(20) or who is a protected individual as defined by 8 U.S.C. 1324b(a)(3). U.S. citizens, U.S. nationals, U.S. permanent residents, or individuals granted refugee or asylee status in the U.S. are considered U.S. persons." We should keep that. The link can be dropped as it's just a reference; but we could keep it? Probably drop the link as it's not essential. But we need to preserve ALL substantive information; the link is not substantive info, it's a reference. So we can drop. Also remove "Security Clearance Type: None/Not Required Security Clearance Status: Not Required". That's substantive? It says none required. Could be considered minor metadata; but we could include under Requirements? Might be okay to include as a short paragraph. However they said fold minor metadata into a short

or drop it. So we could include a short p under Requirements: "Security clearance: None/Not required." Also remove "At RTX, the world's largest aerospace and defense company..." That's about the company; could be part of About the role. Also remove "Collins Aerospace is a leader..." etc. Also remove "Join us and help shape the future of aerospace and defense." That's fluff but maybe part of About the role. We need to ensure we don't include EEO boilerplate at end. Now construct HTML. Structure:

About the role

Location: Melbourne, FL (1100 W Hibiscus Blvd, BLDG 307). At RTX, the world's largest aerospace and defense company, 185,000 great minds are united by purpose and inspired to make a difference solving the world’s most complex problems. With our three market leading businesses, world-class operations and investments in research and development, we offer capabilities and opportunity no one else can. Together, we push the boundaries of known science and find new ways to connect and protect our world. Collins Aerospace is a leader in technologically advanced, intelligent solutions that help redefine the aerospace and defense industry. With a comprehensive portfolio and deep technical expertise, we help customers meet the demands of the global market. Join us and help shape the future of aerospace and defense. As the Operations Product Manager – Customer Focal, you will serve as the primary operational interface for key customer product lines, ensuring strong alignment between customer expectations and factory execution, driving performance across cost, quality, schedule, and delivery.

But we need to avoid repeating job title? The job title is "Operations Product Manager – Customer Focal". The instruction says do NOT repeat the job title as a heading (the page already shows it). It doesn't forbid mentioning it in prose. So okay. Now Responsibilities:

Responsibilities

• Act as the primary operations liaison to General Managers and product leadership, owning operational commitments and ensuring alignment across customer, program, and business objectives.
• Integrate and coordinate cross-functional teams to ensure operational plans are realistic, executable, and aligned with factory capabilities.
• Drive operational readiness and execution by prioritizing tasks, maintaining visibility of risks and actions, and coordinating across functional areas.
• Communicate clearly and consistently with customers and internal stakeholders regarding manufacturing plans, performance, risks, and mitigation strategies.
• Lead operational status updates, reviews, and readouts for assigned products, providing accurate representation of factory performance and timely escalation of issues.
• Support capacity planning, staffing models, and resource allocation decisions to ensure readiness to meet operational commitments.
• Partner with Quality, Production, Supply Chain, and Engineering to monitor performance, identify trends, and drive corrective actions.
• Translate customer priorities into executable factory actions and timelines.
• Support new product introductions, engineering changes, and production transitions to ensure seamless integration into operations.
• Drive problem-solving efforts and resolve issues impacting product flow, material availability, or quality performance.
• Support continuous improvement initiatives aligned with RTX operational excellence principles.

Requirements:

Requirements

U.S. Person required: a lawful permanent resident as defined in 8 U.S.C. 1101(a)(20) or a protected individual as defined by 8 U.S.C. 1324b(a)(3). U.S. citizens, U.S. nationals, U.S. permanent residents, or individuals granted refugee or asylee status in the U.S. are considered U.S. persons.

Security clearance: None/Not required.

Qualifications: We have "Qualifications You Must Have:" and "Qualifications We Prefer:". Could combine into Qualifications section with two subparts? But we must use

for section headings only; we could have a single Qualifications section and inside we can have paragraphs or lists. 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." So we can have Qualifications section with

  Qualifications

  then maybe a

  for the must-have prose and a

  for preferred? But the must-have is also a list of bullet-like statements but they are sentences. Could treat as
  as well. However they said use
  • for any list of duties/requirements/benefits. The qualifications are requirements, so we can use
    . We'll separate must-have and preferred maybe as two
    with headings? But we cannot add extra headings besides

    . Could use

    to introduce then

    . That's fine. Thus:

    Qualifications

    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 or in absence of a degree, 14 years of relevant experience.
    • 5+ years of operations experience in a manufacturing environment

    Preferred:

    • Experience conducting PFMEA’s, DFMEA’s.
    • Proficient in PowerPoint presentations, Excel, SAP.
    • Effective communication and interpersonal skills, with the ability to collaborate with cross-functional teams to achieve operational goals.
    • Detail-oriented and capable of managing multiple priorities in a fast-paced environment.
    • Experience using analytical and problem-solving skills to effectively identify and resolve issues and mitigate risks.
    • The ability to remain focused under pressure to assess and resolve challenges.
    • Collins Enterprise Values including Safety | Trust | Accountability | Respect | Collaboration | Innovation
    Skills: The posting does not have a separate Skills section; we could incorporate skills into Qualifications or maybe create a Skills section from the preferred items like communication, analytical, etc. But we already have them under Qualifications preferred. The instruction says prefer a few substantive sections over many thin ones. So we could skip a separate Skills section and keep skills within Qualifications. However they listed Skills as a possible heading; we should only include if posting has real specific content for it. The posting does have skills like "Effective communication and interpersonal skills", "Experience using analytical and problem-solving skills", "Detail-oriented", etc. Those are skills. But we already placed them under Qualifications preferred. Could we create a Skills section and move those there? That would duplicate content. Better to keep them under Qualifications. So no separate Skills section. Benefits: We have a long list. We'll create

    Benefits

    then
    with each benefit. We need to preserve all substantive information; we should not drop any benefit items. The list includes: - 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