Sr GTF Fleet Manager (Onsite)

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Remove boilerplate, navigation, EEO, etc. Keep all substantive info. Let's parse the posting. Key info: - Date posted, country, location, role type: Onsite. Might be metadata; we can put in a short

maybe. - Position Role Type: Onsite. - U.S. Citizen requirement: U.S. citizenship required. - Security clearance: None/Not Required. - Job Description: paragraphs about RTX, Pratt & Whitney, etc. - What You Will Do: list of responsibilities: Customer Management, Financial Management, Operational Management, Contract Management. Each with bullet points. - What You Will Learn: Contract Management skills and strategies to increase customer satisfaction and company profitability. - Qualifications You Must Have: Bachelor’s degree and 10 years of cross functional teaming experience to include external support and problem solving skills or an Advanced degree and 7 years of cross functional teaming experience to include external support and problem solving skills. - Qualifications We Prefer: list: 3 years of professional financial analysis, program management, or business case experience. Prior customer-facing work experience in a technical or business role. Strong communication, influencing, presentation, and data management/analysis skills. Proven leadership skills coupled with a history of attaining results through influence and collaboration. A fundamental understanding of gas turbine engines, airline operations and engine maintenance practices. - Salary range: 132,400 USD - 251,600 USD. - Benefits: list: 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, holidays. Also mention short-term and/or long-term incentive compensation programs (not guaranteed). Also mention that specific benefits depend on business unit and collective bargaining. - Schedule: Not explicitly given; only mention onsite, flexible work schedules as a benefit. No explicit schedule like full-time, part-time. So we should not create a Schedule section unless posting actually states them. It does not state schedule explicitly; only "flexible work schedules" as benefit. So we omit Schedule. - Pay: we have salary range, so include Pay section. - Benefits: we have benefits list, include Benefits. - Skills: we have skills list in Qualifications We Prefer (communication, influencing, presentation, data management/analysis, leadership, etc). Could be a Skills section. - About the role: we have description about RTX, Pratt & Whitney, Fleet Management role. Could be About the role. - Responsibilities: we have What You Will Do with four streams. - Requirements: we have U.S. citizenship requirement, security clearance none, maybe also location? But we can put Requirements: U.S. citizenship required, security clearance not required. Also maybe mention onsite? But that's role type. - Qualifications: we have Must Have and Preferred. We need to avoid repeating job title as heading. Not needed. We need to output only HTML fragment, no /. Use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. Remove boilerplate: EEO, privacy policy, etc. Also remove duplicated lines, navigation, application instructions like "Learn More and Apply", "What is my role type?" etc. Also remove "Date Posted", "Country", "Location" maybe we can keep as metadata in a short

  but not as heading. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we can include a short

  with location, date posted, role type, citizenship requirement maybe. But we also have a Requirements section for citizenship and clearance. Might be better to put those in Requirements. Let's structure:

  Posted: 2026-09-15 • Location: East Hartford, CT, USA • Role type: Onsite

  Then sections:

  About the role

  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 three market‑leading businesses, world‑class operations and investments in research and development, RTX offers 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. Pratt & Whitney is a world leader in the design, manufacture and service of aircraft engines and auxiliary power systems and has been revolutionizing modern flight for over 100 years. Join us and help shape the future of aerospace and defense. The Pratt & Whitney Commercial Aftermarket team is responsible for long‑term engine maintenance agreements with airline customers. Fleet Management is an exciting customer‑facing role with substantial financial and contractual accountability.

  Responsibilities

  • Customer Management: Team with the Sales and Customer Support organizations to host regular day‑to‑day interaction with airline and leasing customers, deliver contract services, ensure reliable engine operations, and resolve commercial disputes.
  • Financial Management: Drive the long term profitability plan for assigned contracts, identify and execute opportunities to improve financial outcomes, and tactically manage the flow and collection of invoices to the customer. Propose contract language modifications for improved feasibility of financial outcomes.
  • Operational Management: Maintain engine removal forecasts, coordinate maintenance activity with our global network of MRO facilities, and establish technical guidance for optimal financial and operational outcomes.
  • Contract Management: Thoroughly understand all agreement obligations, ensure terms are met, and hold stakeholders accountable to assigned responsibilities. Propose and execute strategies for optimizing contract profitability. Negotiate solutions with airlines and lessors to solve disputes, driving closure of unpaid invoices and de‑risking key contract provisions.
  Maybe also include "What You Will Learn" as part of Responsibilities or a separate section? Could be under Responsibilities or maybe a separate "What you will learn" but not a standard heading; we could incorporate into Responsibilities or maybe a separate "Learning Opportunities". However instruction: use headings only for the listed ones; we can add other headings if they correspond to content? It says: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't restrict to only those headings, but suggests those as examples. Safer to stick to those headings. "What You Will Learn" could be placed under Responsibilities or maybe under Qualifications? It's more like a learning outcome; could be part of About the role or Responsibilities. I'd put it under Responsibilities as an additional bullet maybe. But we have a separate bullet for "What You Will Learn: Contract Management skills and strategies to increase customer satisfaction and company profitability". Could be a separate

  after Responsibilities. Alternatively, we could create a section "Skills" for skills learned. But we already have Skills section for skills required/preferred. Might be confusing. Better to add a

  after Responsibilities:

  What you will learn: Contract Management skills and strategies to increase customer satisfaction and company profitability.

  Now Requirements section: include citizenship requirement and security clearance.

  Requirements

  • U.S. citizenship is required (only U.S. citizens authorized to access information under this program/contract).
  • Security clearance: None/Not required.
  Qualifications: we have Must Have and Preferred. Could split into two subsections? But we only have Qualifications heading. Could include both Must Have and Preferred under Qualifications, maybe using
  with sub-items. We need to preserve all detail. So:

  Qualifications

  Must have: Bachelor’s degree and 10 years of cross‑functional teaming experience (including external support and problem‑solving skills) OR an advanced degree and 7 years of cross‑functional teaming experience (including external support and problem‑solving skills).

  Preferred:

  • 3 years of professional financial analysis, program management, or business case experience.
  • Prior customer‑facing work experience in a technical or business role.
  • Strong communication, influencing, presentation, and data management/analysis skills.
  • Proven leadership skills coupled with a history of attaining results through influence and collaboration.
  • A fundamental understanding of gas turbine engines, airline operations, and engine maintenance practices.
  But we need to follow rule: Use
  • for any list of duties/requirements/benefits, and

    for prose. So for the Preferred list we should use

    • . The "Must have" could be a

      . That's fine. Now Skills section: we could extract skills from Preferred list (communication, influencing, presentation, data management/analysis, leadership, etc). But we already listed them under Qualifications Preferred. The instruction says prefer a few substantive sections over many thin ones. So maybe we don't need a separate Skills section; we can incorporate skills into Qualifications. However they asked to use headings for Skills if we have content. Since we already have skills listed under Qualifications Preferred, we could still have a Skills section but that would duplicate. Better to not create a Skills section to avoid thin duplication. We'll omit Skills. Benefits section: we have list of benefits.

      Benefits

      • Medical insurance
      • Dental insurance
      • Vision insurance
      • 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
      • Holidays
      • Short‑term and/or long‑term incentive compensation programs (eligibility dependent on position level and collective‑bargaining coverage; payments not guaranteed)
      Pay section: salary range.

      Pay

      The salary range for this role is $132,400 USD – $251,600 USD.

      We might also mention that the range is a good faith estimate, etc. But that is extra detail; we should preserve all substantive information. The posting includes: "The salary range provided is a good faith estimate representative of all experience levels. RTX considers several factors when extending an offer, including but not limited to, the role, function and associated responsibilities, a candidate’s work experience, location, education/training, and key skills." That's substantive; we should include it. Also mention that hired applicants may be eligible for benefits etc. Already captured in Benefits. Also mention about incentive compensation programs. Already in Benefits. We could add a

      after Pay:

      The salary range provided is a good faith estimate representative of all experience levels. RTX considers several factors when extending an offer, including but not limited to the role, function and associated responsibilities, a candidate’s work experience, location, education/training, and key skills.

      Now we need to ensure we didn't include boilerplate like EEO, privacy policy, etc. We removed those. We also need to remove