F135 Training Business Manager (Onsite)
or drop it. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can include location, date posted maybe as a short paragraph at top? Not required but we can include as a
with metadata. However we must not create sections for them unless they have content. Probably we can include a short
with location and date posted. We need sections: About the role (the introductory paragraph about RTX and Pratt & Whitney). Responsibilities (the bullet list under "What You Will Do"). Requirements (the security clearance and citizenship maybe). Qualifications (must have and preferred). Skills (maybe not explicit; we could infer from qualifications? But we should only include if posting has real specific content. There's no explicit "Skills" section; we could omit Skills. Benefits: there is a paragraph about benefits. Pay: salary range given. Schedule: maybe not explicit; there is mention of "Onsite" role type, but schedule not given. Could we include Schedule? Not given. So omit Schedule. We must not create sections with filler like "commensurate with experience". So only include sections where we have content. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. We need to use
for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive information. Let's extract.
About the role: The paragraph starting "At RTX, the world's largest aerospace and defense company..." includes description of RTX, Pratt & Whitney, and the role purpose. We'll put that in
.
Responsibilities: The bullet list under "What You Will Do:" includes multiple items. We'll make
- each.
Also there is mention "10% - 20% travel" maybe part of responsibilities? Could be a separate line; we can include as a
- under Responsibilities.
Requirements: The security clearance and citizenship requirement. Also maybe "U.S. Citizen, U.S. Person, or Immigration Status Requirements:" but that's just heading. We'll capture: "The ability to obtain and maintain a U.S. government issued security clearance is required. U.S. citizenship is required, as only U.S. citizens are eligible for a security clearance." Also "Security Clearance Type: DoD Clearance: Secret" and "Security Clearance Status: Active and existing security clearance required after day 1". These are specifics. We'll include them.
Qualifications: Must have: Bachelor's degree..., Minimum 8+ years..., At least 4 years experience with EVMS, ability to obtain clearance, US citizenship. Preferred: Advanced degrees..., Familiarity with F135 engine programs..., etc.
We'll separate Must Have and Preferred maybe as two
under Qualifications? Could be separate headings but we only have Qualifications section. We can include two lists: one for Must Have, one for Preferred, each with ? But we only allowed for section headings. Inside we can use
or
. We could do Must Have:
then . Or we can just combine into one list with items. Better to separate for clarity but still within Qualifications section. Use for intro then
.
Skills: Not present, omit.
Benefits: Paragraph about benefits: 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 annual short-term and/or long-term incentive compensation programs. We'll capture that.
Pay: Salary range: 107,500 USD - 204,500 USD. Also note that it's a good faith estimate. We'll include that.
We must not include duplicated lines. Ensure we don't repeat the security clearance requirement multiple times.
We need to output only HTML fragment, no /, no markdown fences.
Let's craft.
Start with maybe a for metadata: Date Posted and Location? Could include as a short paragraph: "Posted: 2026-09-18 | Location: East Hartford, CT (400 Main St, BLDG ETC)". Not required but okay.
But 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
for metadata.
Let's do:
Posted: 2026-09-18 | Location: East Hartford, CT (400 Main St, BLDG ETC)
Then sections.
Now produce HTML.
Check for any boilerplate removed: We removed EEO, equal opportunity, privacy policy, etc. Also removed "Learn More & Apply Now!" and the role type description etc. Also removed "This position is classified as: Onsite" etc. But we might want to keep the role type? It's minor metadata; could be included in the metadata paragraph. But we already have location; we could add "Role type: Onsite". However the instruction says "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." So role type is minor metadata; we can include in the short
. Let's include: "Role type: Onsite". Also maybe "10% - 20% travel" is part of responsibilities, not metadata.
Thus metadata paragraph: "Posted: 2026-09-18 | Location: East Hartford, CT (400 Main St, BLDG ETC) | Role type: Onsite".
Now sections.
About the role: We'll combine the paragraphs about RTX, Pratt & Whitney, and the role purpose.
Original: "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. 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 F135 Training Business Manager supports the Training organization by planning, managing, and reporting on the business and operational activities that enable successful delivery of training programs. This role oversees contracted training services, training‑related projects, and budgets associated with Field Sustainment and Support Training. The Training Business Manager ensures cost, schedule, and performance objectives are achieved by applying sound business practices, collaborating across functional teams, and using Earned Value Management System (EVMS) and Integrated Master Schedule (IMS) tools effectively. Reporting to the Training Program Manager, this position works closely with EV analysts, financial oversight teams, and customer stakeholders to maintain accurate performance metrics, establish baseline budgets, assess variances, and recommend corrective actions. The Training Business Manager is responsible for maintaining monthly business rhythm requirements and contributing to proposal development for future training contracts."
We'll put that in a
.
Responsibilities: list items:
- Manage Training Services projects funding, including future mock-up sales, mock‑up engine builds, training product development, and other initiatives assigned by the Associate Director.
- Oversee Materials Resource Planning (MRP) activities and interpret Bill of Materials (BOM) data for training hardware and materials.
- Prepare Basis of Estimate (BOE) inputs and support reviews of Statements of Work (SOW) and contract modifications.
- Drive continuous improvement in business management processes, EVMS discipline, and IMS integration by identifying root causes and implementing corrective actions.
- Review financial data to ensure accuracy, completeness, and alignment with expected program performance.
- Deliver all monthly business rhythm requirements, including updates to EVMS, IMS, and financial systems.
- Support future proposal development by providing historical performance data, cost inputs, and risk assessments.
- Participate in Monthly Program Reviews (MPR), Estimate at Completion (EAC) reviews, Integrated Baseline Reviews (IBR), and Review for Cause (RFC) audits to communicate issues, risks, and opportunities.
- 10% - 20% travel
We'll put each as
- .
Requirements: we need to include security clearance details.
- Ability to obtain and maintain a U.S. government issued security clearance is required.
- U.S. citizenship is required (only U.S. citizens eligible for a security clearance).
- Security Clearance Type: DoD Clearance: Secret.
- Security Clearance Status: Active and existing security clearance required after day 1.
We'll put as
.
Qualifications: Must Have and Preferred.
We'll maybe have a for "Must Have:" then
, then a for "Preferred:" then
.
Must Have items:
- Bachelor’s degree in engineering, Business, Operations Management, Program Management, or related field.
- Minimum 8+ years of program or project management experience required.
- At least 4 years of experience with Earned Value Management System (EVMS).
- Ability to obtain and maintain a U.S. government issued security clearance is required.
- U.S. citizenship is required.
Preferred items:
- Advanced degrees in Engineering, Business Management, Operations Management, or Program Management with 3+ years of related professional experience.
- Familiarity with F135 engine programs or military sustainment training operations.
We'll include those.
Benefits: list items:
- 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
- Annual short-term and/or long-term incentive compensation programs (eligibility dependent on level and collective-bargaining agreement; payments not guaranteed)
We'll put as .
Pay: Salary range: 107,500 USD - 204,500 USD. Also note it's a good faith estimate representative of all experience levels; factors considered.
We'll put in .
Now ensure we didn't include any boilerplate like "EEO", "Equal Opportunity Employer", "Privacy Policy", "Learn More & Apply Now!", etc.
Check for duplicated lines: we have security clearance requirement appears both in Requirements and Qualifications Must Have; that's okay as it's substantive info repeated but we must preserve all substantive info; duplication is okay if it's in original. However we might want to avoid repeating same sentence but it's fine.
Now produce HTML.
Let's craft:
Posted: 2026-09-18 | Location: East Hartford, CT (400 Main St, BLDG ETC) | Role type: Onsite
for prose. We must preserve all substantive information. Let's extract. About the role: The paragraph starting "At RTX, the world's largest aerospace and defense company..." includes description of RTX, Pratt & Whitney, and the role purpose. We'll put that in
. Responsibilities: The bullet list under "What You Will Do:" includes multiple items. We'll make
- each. Also there is mention "10% - 20% travel" maybe part of responsibilities? Could be a separate line; we can include as a
- under Responsibilities.
Requirements: The security clearance and citizenship requirement. Also maybe "U.S. Citizen, U.S. Person, or Immigration Status Requirements:" but that's just heading. We'll capture: "The ability to obtain and maintain a U.S. government issued security clearance is required. U.S. citizenship is required, as only U.S. citizens are eligible for a security clearance." Also "Security Clearance Type: DoD Clearance: Secret" and "Security Clearance Status: Active and existing security clearance required after day 1". These are specifics. We'll include them.
Qualifications: Must have: Bachelor's degree..., Minimum 8+ years..., At least 4 years experience with EVMS, ability to obtain clearance, US citizenship. Preferred: Advanced degrees..., Familiarity with F135 engine programs..., etc.
We'll separate Must Have and Preferred maybe as two
- under Qualifications? Could be separate headings but we only have Qualifications section. We can include two lists: one for Must Have, one for Preferred, each with
- .
Requirements: we need to include security clearance details.
- Ability to obtain and maintain a U.S. government issued security clearance is required.
- U.S. citizenship is required (only U.S. citizens eligible for a security clearance).
- Security Clearance Type: DoD Clearance: Secret.
- Security Clearance Status: Active and existing security clearance required after day 1.
We'll put as
- .
Qualifications: Must Have and Preferred.
We'll maybe have a
for "Must Have:" then
- , then a
for "Preferred:" then
- .
Must Have items:
- Bachelor’s degree in engineering, Business, Operations Management, Program Management, or related field.
- Minimum 8+ years of program or project management experience required.
- At least 4 years of experience with Earned Value Management System (EVMS).
- Ability to obtain and maintain a U.S. government issued security clearance is required.
- U.S. citizenship is required.
Preferred items:
- Advanced degrees in Engineering, Business Management, Operations Management, or Program Management with 3+ years of related professional experience.
- Familiarity with F135 engine programs or military sustainment training operations.
We'll include those.
Benefits: list items:
- 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
- Annual short-term and/or long-term incentive compensation programs (eligibility dependent on level and collective-bargaining agreement; payments not guaranteed)
We'll put as
- .
Pay: Salary range: 107,500 USD - 204,500 USD. Also note it's a good faith estimate representative of all experience levels; factors considered.
We'll put in
. Now ensure we didn't include any boilerplate like "EEO", "Equal Opportunity Employer", "Privacy Policy", "Learn More & Apply Now!", etc. Check for duplicated lines: we have security clearance requirement appears both in Requirements and Qualifications Must Have; that's okay as it's substantive info repeated but we must preserve all substantive info; duplication is okay if it's in original. However we might want to avoid repeating same sentence but it's fine. Now produce HTML. Let's craft:
Posted: 2026-09-18 | Location: East Hartford, CT (400 Main St, BLDG ETC) | Role type: Onsite
? But we only allowed
for section headings. Inside we can use
or
- . We could do
Must Have:
then- . Or we can just combine into one list with items. Better to separate for clarity but still within Qualifications section. Use
for intro then
- .
Skills: Not present, omit.
Benefits: Paragraph about benefits: 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 annual short-term and/or long-term incentive compensation programs. We'll capture that.
Pay: Salary range: 107,500 USD - 204,500 USD. Also note that it's a good faith estimate. We'll include that.
We must not include duplicated lines. Ensure we don't repeat the security clearance requirement multiple times.
We need to output only HTML fragment, no /, no markdown fences.
Let's craft.
Start with maybe a
for metadata: Date Posted and Location? Could include as a short paragraph: "Posted: 2026-09-18 | Location: East Hartford, CT (400 Main St, BLDG ETC)". Not required but okay. But 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
for metadata. Let's do:
Posted: 2026-09-18 | Location: East Hartford, CT (400 Main St, BLDG ETC)
Then sections. Now produce HTML. Check for any boilerplate removed: We removed EEO, equal opportunity, privacy policy, etc. Also removed "Learn More & Apply Now!" and the role type description etc. Also removed "This position is classified as: Onsite" etc. But we might want to keep the role type? It's minor metadata; could be included in the metadata paragraph. But we already have location; we could add "Role type: Onsite". However the instruction says "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 shortor drop it." So role type is minor metadata; we can include in the short
. Let's include: "Role type: Onsite". Also maybe "10% - 20% travel" is part of responsibilities, not metadata. Thus metadata paragraph: "Posted: 2026-09-18 | Location: East Hartford, CT (400 Main St, BLDG ETC) | Role type: Onsite". Now sections. About the role: We'll combine the paragraphs about RTX, Pratt & Whitney, and the role purpose. Original: "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. 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 F135 Training Business Manager supports the Training organization by planning, managing, and reporting on the business and operational activities that enable successful delivery of training programs. This role oversees contracted training services, training‑related projects, and budgets associated with Field Sustainment and Support Training. The Training Business Manager ensures cost, schedule, and performance objectives are achieved by applying sound business practices, collaborating across functional teams, and using Earned Value Management System (EVMS) and Integrated Master Schedule (IMS) tools effectively. Reporting to the Training Program Manager, this position works closely with EV analysts, financial oversight teams, and customer stakeholders to maintain accurate performance metrics, establish baseline budgets, assess variances, and recommend corrective actions. The Training Business Manager is responsible for maintaining monthly business rhythm requirements and contributing to proposal development for future training contracts." We'll put that in a
. Responsibilities: list items: - Manage Training Services projects funding, including future mock-up sales, mock‑up engine builds, training product development, and other initiatives assigned by the Associate Director. - Oversee Materials Resource Planning (MRP) activities and interpret Bill of Materials (BOM) data for training hardware and materials. - Prepare Basis of Estimate (BOE) inputs and support reviews of Statements of Work (SOW) and contract modifications. - Drive continuous improvement in business management processes, EVMS discipline, and IMS integration by identifying root causes and implementing corrective actions. - Review financial data to ensure accuracy, completeness, and alignment with expected program performance. - Deliver all monthly business rhythm requirements, including updates to EVMS, IMS, and financial systems. - Support future proposal development by providing historical performance data, cost inputs, and risk assessments. - Participate in Monthly Program Reviews (MPR), Estimate at Completion (EAC) reviews, Integrated Baseline Reviews (IBR), and Review for Cause (RFC) audits to communicate issues, risks, and opportunities. - 10% - 20% travel We'll put each as
- .
Requirements: we need to include security clearance details.
- Ability to obtain and maintain a U.S. government issued security clearance is required.
- U.S. citizenship is required (only U.S. citizens eligible for a security clearance).
- Security Clearance Type: DoD Clearance: Secret.
- Security Clearance Status: Active and existing security clearance required after day 1.
We'll put as